Won't boot after using windows Bios flash utility

I used the windows bios flash utility i found on the toshiba website for this sat a135-s2386, all looked good until reboot, now just a white screen.

Attitude is not going to get you far.
Let's try a proper system reset, and see if this helps bring the unit back. Power off your system, unplug everything including the AC, remove the battery, press and hold down the power on button for 30 seconds, replace battery and AC, power on, if you see the Toshiba logo press the 'F2' key to enter BIOS Setup, in setup press 'F9' to load setup defaults, press 'F10' to save and exit, then try to boot into Windows.
Please let us know what happens. Good luck.
Mike

Similar Messages

MSI X99S XPOWER won't boot after a Windows 8.1 Update

Hi all, two days ago I was using my PC as normally and Windows needed to restart because of an update from Windows Update. It restarted and won't be able to boot again. I get a 04 debug code (Power on South Bridge Initialization) and I've tried clearing CMOS, without SSD/HDD... and there is no way.
I'm reading something about an Intel drivers update that can modify the firmware, do you know anything about it?
Board: MSI X99S XPOWER
Bios: Version 1.4
VGA: MATRIX GTX 780Ti
PSU: Enermax Platimax 850W
Intel Core i7 5820K
MEM: G.Skill 32GB in 4 sticks (8 GB each) @2400 MHz XMP
HDD: OCZ Vertex 450 256GB
COOLER: Akasa Venom Vodoo
OC: 4 GHz 1.15v
OS: Windows 8.1 x64
Thanks

Windows is not corrupted, I've tried that SSD on another computer without problems and in my computer without HDD/SSD and won't boot anyway.
If I'm able to boot with the secondary BIOS, I'll recover the first one by the following steps:
Quote
BIOS recovery with AFUDOS command
When BIOS updating fails or causes the computer non-bootable, you can recover the
failed BIOS by the steps below.
Preparation:
1. Prepare a bootable USB flash drive.
2. Download the latest BIOS file from the MSI official website at www.msi.com, and
then decompress the file.
3. Copy the AFUDE238.exe and the BIOS file to the bootable USB flash drive
BIOS recovery steps:
1. Power off the computer.
2. Set the Multi-BIOS switch to the functional BIOS ROM.
3. Insert the bootable USB flash drive you have made to the USB port.
4. Boot the computer into the bootable USB flash drive.
5. Set the Multi-BIOS switch to the failed BIOS ROM.
6. Execute the below command to flash the BIOS:
For example: AFUDE238 EXXXXIMS.XXX
7. Restart the computer after the BIOS flashing is complete.
Important
Do not use the Multi-BIOS switch when system is booting up.
But I have a doubt with the "Important" note because I need to change from safe BIOS to failed BIOS with the PC booted, right? So I'll use the Multi-BIOS switch with the system up...
Thanks a lot

SSD won't boot after using Win 7 recovery discs

Hi, I bought a Samsung SSD 850 EVO 1TB for my HP Pavilion dv7-4012eg which had a 1TB hard drive (same size).
I took off the original hard drive and attached the SSD on the primary slot, leaving the original hard drive unattached until I configure everything with the new one not to confuse things.
I had burned the 6 recovery DVDs from my HP and had used them before on the original hard drive without any problems.
So I did the procure I am used to, and after the 6 DVDs the recovery said the laptop was going to restart to install and configure the OS. But when I restart it says there's no bootable device, that I should insert one.
I inserted the DVDs again and went through the whole process again just in case, but still got the same no bootable device message.
I installed Ubuntu and it was very successful, and I can boot Ubuntu fine. When I try to boot the Windows partition now it starts something but says something like that the installation was not finished.
I also have my Windows 7 Home Premium 64-bit OA HP license readable under my laptop, so I tried to download the Win7 from the Microsoft Software Recovery but it says to contact HP because the Windows was pre-installed on my laptop.
What can I do? Any ideas why I got the no bootable device error after going through the 6 recovery DVDs?
Cheers.

Hi @jessymeyer ,
Welcome to the HP Forums!
It is a superb place to find answers and tips!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I understand that you are replacing the hard drive in your Pavilion dv7-4012e with a SSD. You were able to do the recovery but when it went to reboot you got the error no bootable device found.
Did you change the boot order in the bios back to the HDD first?
You could also try restoring the defaults in the bios so that it will scan for hardware and find the new hard drive.
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

X1 carbon 20A7 won't boot after 1.13 BIOS update, ecreen also corrupted.

After updating the BIOS to 1.13 the X1 refuses to boot . After several attempts to diagnose the problem (trying to boot under legacy and uefi with various rescue pen drives) I doing a restore with the recovery media (created using the inbuilt software) but that didn't help, it just wiped my partitions and reinstalled windows (I'm assuming since I have no way to check at this point) but still refuses to boot. I can boot the windows rescue thumb drive under legacy though. After the update the screen was also corrupted, picture here http://i.imgur.com/ScfD1Uz.jpg.
At this point I'm not sure what to do anymore, it seems that the BIOS update failed in some way or somehow broke something.

this seems to have caused uneven lighting in the LED display, very strange problem. You may need to get warranty service on it.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

KT6 Delta won't boot after clearing the BIOS

I have just put together the machine as per my signature and run into a few problems. The XP 2800 mobile is not recognised as such but as a XP1800 when I set the FSB to 133. Am I right in saying this CPU should run at 1.65 volts as it seems to wants to run at 1.75. I changed the V Core to 1.65 and it boots ok but when I tried it at 1.6 it did not want to boot, ie no video output. I no longer get the single BIOS bleep and the monitor stays on standby. This has happened before and I got it running again by clearing the CMOS and reseating the RAM but this time I have done the same and it won't boot. Is there anything else I should be doing please. Many thanks.
Having looked at the Socket A sticky I see that my diagnostic D bracket is showing 1,2 and 3 showing red and four not on at all which would seem to point at the graphics as being the problem.

Hello!
Voltages should be set to "CPU default" or similar. Your processor comes in different versions, try setting to 166 instead of 133. Always when changing processor one should clear CMOS, by powering off, unplugging power cable, and then move JBAT jumper for a short time, a minute or so.

ITunes won't open after using Windows Media Center

Today I used Windows Media Center so I could play my music and videos through my X-Box. Now when I try to open iTunes it comes up with the message "The folder itunes is on a locked disk or you do not have write permission for this folder". Nothing has been changed, I did not lock anything, and now the folder automatically reverts itself to Read-Only. Please help

I also tried un and re-installing itunes but it did nothing

Won't boot after resizing Windows partition

So I'm dual-booting Windows 7 with OSX using Boot Camp. The Windows partition had very little space left so I decided to go ahead and resize it. I first used Disk Utility inside OSX to shrink the size of the OSX partition. Worked like a beauty.
I then went into Windows and resized the Windows partition using Paragon's Partition Manager....big mistake.
I would gander a guess that in order to resize, the Paragon software has to reboot and boot into a partition it created. Which is all fine and good except I don't think (version 2010 of Partition Manager) the Mac bootup hardware likes this. Unfortunately, this seemed to have nuked my bootup of anything, including OSX.
Is there a way to recover/repair this without having to do wipe everything and reinstall?

Welcome to Apple Discussions,
You can boot to the Mac OS Install disk that came with the computer and run Disk Utility from from the disk to attempt to repair the Mac OS partition of the logical drive. If it can repair it then you may be able to boot.
Live partitioning is like doing open heart surgery on yourself. Its not a simple process. Doing it with a utility that isn't necessarily made for handling an HFS+ partition table (Like what the Mac OS uses) is tricker still.
Give Disk Utility a try. There are other directory repair programs out there (Drive Genius, Disk Warrior, etc.) that can do deeper levels of repair.
Were it my drive, I would probably just erase it and restore from backup (assuming you have all your data backed up and are confident that the backup is good). You don't want to keep working with a potentially damaged partition table. But thats just me.
Hope that helps.

Firewire external hard drives won't mount after using Windows Vista

Hi to All,
I installed Windows Vista Business in a SATA hard drive I added to my Mac Pro. Every time I select the HD from the start up disk in my preferences and restart, the next time I start up with Mac OS 10.6.1 all my firewire devices don't mount. I have to shut down my Mac unplug the power cord for a few minutes to get my firewire devices back. Do you know of any workarounds to this issue? Thanks in advance!

Yea, don't use Snow Leopard or don't use Firewire for now.
Nothing to do with Vista Business.

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

M8330f PC won't boot after accidentally having I-pod plugged in prior to booting

My computer won't boot after having my i-pod charge cord inserted in computer prior to booting. I have tried f8 f9 f10 f11 nothing is getting me to a point where I can actually get the computer to boot. I realize I may need to provide more info, but don't know what else to provide you right now. HELP!

I used version 1.B for my motherboard.
Yes i did. I describded what happens, when i run 1 and 2 sticks.
-If these are timings then - 9 9 9 25
-1600mhm before bios update and 1337mhz after update
-Voltage: 1.5V in auto probably
Edit1: I got a response on other forum -
Could this be true:Quote
The Hyper X Fury operate off of PnP and aren't compatible with the P55 chipset natively?
In that case i could try to refund the ram, cause the place where i bought it said its compatible with P55
Edit2: I added some info on what kingston homepage (no P55) says and specification pdf also what my seller says in description of this ram type:
I`am am confused, honestly.
Edit3: Aperrantly its might not support my p55 chipset, found a reply on another similar problem tread replied by kingston tech support:
Quote
Hi, I'm Jewel with Kingston Technical Support and would like to offer some clarification. Our currently manufactured memory, including the HyperX Fury line, is compatible with Intel 6-series chipsets and later. The DH55TC has an Intel H55 chipset which is part of the Intel 5-series chipsets. As such, the HyperX Fury memory is not compatible with your system and we do not currently offer any memory that would be compatible with your system. You can try looking online for recently discontinued part numbers like KVR1333D3N9HK2/8G or KVR1333D3N9H/4G which are compatible with your motherboard. If you are unable to return the memory to your place of purchase, please contact us and we will do our best to work with you. Please check http://www.kingston.com/company/contacts to reach support in your area.
If that`s the case then - outdated spec information everywhere...

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

Mac Mini won't boot after update

I have a Mac Mini that won't boot after the most recent software update. Since the Mini has only a bluetooth keyboard and mouse, a number of the usual options (hold down shift, etc.) won't work. I've tried a reset, also no luck. At the moment, I can't locate my Tiger install CD either.
When holding the power button on during boot, I get a series of flashes from the status light on the front (a set of very rapid flashes, followed by a slower set, followed by a slow set) but no startup chime, or fan, or video. My display and power source are both known-good (work fine with my Powerbook)
Any suggestions, other than buying a hardwired keyboard/mouse?

Welcome to Apple Discussions!
The 'newer version of OS X" error occurs because the installer on the DVD you have booted to has by default been set to update the version of MacOS on the hard drive, which of course it can't do because the version of MacOS it is installing is newer. The only way to install in this situation is to select a different option. However, that isn't what you want to do at this point, because as it says, you'll loose your data if you do an 'erase and install'.
Instead, you should see menus at the top of the screen when it's booted to that install disk. Click the Utilities menu, select Disk Utility, and then click the top entry for the internal hard drive on the left. Once done, click on the 'Repair Disk' button (not Repair Permissions). This will test the drive to make sure it's OK. If it reports errors, and then reports 'error or exit' with the drive not repaired, you will either need a 3rd party application such as Alsoft's Disk Warrior, or to perform an erase and install (which of course you don't want to do at this point because your data is not backed up).
If the Repair Disk process completes with no errors, next select Repair Permissions, and let that process complete, then reboot the system as normal to see if you can now access the drive.

Mac won't boot after power chord became unplugged accidently.

Mac won't boot after power chord became unplugged accidently.
I have a Mac Mini running very latest version of OSX. I was making a recording with QuickTime; when I needed to plug in a USB recording device into the back of the Mac Mini, as I pulled the Mac off my shelf to do this, the power cable came out and the Mac lost power.
I plugged it back in and powered up the Mac. I get the grey screen with Apple logo and the spinning grey wheel; then it goes to a blue screen (as usual) and I get the "starting OSX..." progress bar. When the progress bar finishes, I'm left with a blue screen only, no dock, no apple icon at top left, nothing across the top, no nothing.
So far, I've booted from the original disc and repaired the permissions as well as the disc, then re-booted, but same old blue screen.
I have another iMac G5 machine, so is there any way I can at least retrieve the important HD files from the Mac Mini to my G5, before throwing the broken Mac Mini away?
Can anyone advise please?

Hi, Nigel.
Not to differ with my colleagues here, but there's an important question that wasn't asked.
1. You wrote: "So far, I've booted from the original disc and repaired the permissions as well as the disc, then re-booted, but same old blue screen."Did Disk Utility report any errors it could not fix when you ran Repair Disk? I suggest you run the procedure specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ. Perform the steps therein in the order specified.
2. You may also want to run the Apple Hardware Test that came with your Mini to be sure nothing shorted when the power cable was removed from the computer. I've seen it happen, hence I usually recommend removing the power cable at the wall before disconnecting the power cable from the computer. See my "Apple Hardware Test" FAQ.
3. Repair Disk gives your Mini a clean bill of health, the blue screen may be the result of some Startup or Login item that was corrupted due to the sudden power outage. My "Troubleshooting Startup and Login Items" FAQ can help you pin that down if such an item is causing the problem and may help you avoid and Archive and Install.
4. If you elect to go the Archive and Install route, see my "General advice on performing an Archive and Install" FAQ for some important tips on this process.
5. As FYI, this is the kind of problem that makes one glad they've implemented a comprehensive backup and recovery solution. For advice on the backup and recovery solution I employ, see my "Backup and Recovery" FAQ. Computing without a comprehensive backup and recovery solution is like driving without auto insurance.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Mac OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

Mac won't boot after the latest update. It is loading the update and suddenly shuts down

My MacBook Pro won't boot after a minor update. The update was all fine and my Mac acted like it used to but when I tried to boot my Mac it just loads the the update then goes back to the Apple logo and then shuts down.
I hope that someone has got a solution because I do not want to restore my Mac for the 4th time.....

Hello JonasHallund,
We've an article that contains information and steps that can help get your MacBook Pro to boot again.
Troubleshooting: My computer won't turn on
http://support.apple.com/kb/TS1367
Cheers,
Allen

Won't boot after using windows Bios flash utility

Similar Messages

Maybe you are looking for