Related
Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !
lucid said:
Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !
Click to expand...
Click to collapse
Did you try to downgrade to Vista and try to flash the original SnapVue?
Can't even get to the BIOS
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.
lucid said:
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.
Click to expand...
Click to collapse
Can you do a Fn>F10 to boot from a cd drive? If so, boot your Windows 7 from the cd to do a repair....That's what I had to do.
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.
Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.
I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!
You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?
Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great
My wife and I have Nook Colors and I recently decided to root mine using AutoNooter. I went through all the steps, crossed referenced the steps with other sites, and went through the steps again. Here's the problem I run into; upon inserting the microSD card into the NC(while off)and plugging it into the computer using the USB cable the darn thing won't boot up.
Everything I've tried:
-a different SD card(I have now tried a 4GB PNY microSDHC and a 2G Sandisk microSD.....and a generic microSD card from my cellphone)
-I've tried loading the image from different sites and using different browsers
-I've tried different imaging software
-I've tried using BOTH mine and my wifes NC.
-I've tried it from 2 different laptops(a Toshiba and a Gateway)
-I've tried downloading the image from both laptops integrated disk reader using an adapter and I've tried loading it using an external USB card reader that reads/writes a microSD directly without needing an adapter.
-I've tried de-registering the NC and re-registering.
-I've let the NC sit for an hour while plugged in.
NOTHING. The light on the USB cable goes from amber to green....which is where the whole process ends.
-I'm running firmware v1.1.0 therefore I'm using AutoNooter 3.0
-I tried it a while back when running 1.0.1 using AutoNooter 2.12.25 with the same results. I'm getting impatient waiting for B&N's rumored update so I decided to try again.
-I do know how to format the SD card so that is not the problem
It's gotta be something simple. PLEASE HELP! Thanks for taking the time to read this. So frustrated
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Same here. I thought I botched the install but the android showed up eventually when it finally booted and I'm running market apps so i know it worked. Very weird though.
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
chris peas said:
What are you using to "burn" the .img to the SD card? If you see the same file written to the card after burning, its not imaged properly. I had this problem the night I bought my nook and it drove me nuts. Use WinImage. From the top menu select Disk>> Restore virtual hard disk image to virtual drive>> select SD card>> select file. The burn should take about 10 secs and you should see a file system structure on the card when opened. If you get an error that the file is in use when you go to burn it, log out, log in and try again or reboot. Burning the image is key, the rest is cake.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I've used WinImage 8.5 and Win32DiskImager. I know it has to be an issue with the image but the files on the sd card after it's been written look identical to screen shots I've seen of the image on multiple "how to" websites. How long did you wait before the NC booted up?
Taeseong said:
I don't think autonooter has any coding in it to prompt the screen to turn on to let you know its installing, but usually (at least in windows) when you plug in your Nook you can hear it mount to the computer...I usually wait for this, leave it on then unplug//remove the uSD card and boot up my Nook.
Click to expand...
Click to collapse
According to NookDevs when using the latest autonooter for use with NC firmware v1.1.0 the NC will boot up automatically once it's connected to the usb cable after a few minutes. Not to be confused with the previous autonooter for use with firmware v1.0.1 where you connect, let sit for 10 minutes, then boot after removing from the usb cable and the sd card. Tried that one too with no luck.
donballz said:
Sorry if you already know this but nothing happens when you boot the autonooter image. The screen stays black. All the magic just happens in the background. All the basic nooter does is enable side loading apps. Some of the others to more. Find your favorite apk and try
adb install myApp.apk
If it works then so did nooter. Find a launcher and go nuts.
Click to expand...
Click to collapse
I never get to the point of seeing the new boot up process, skipping log-in, logging in to youtube, enabling softkeys, etc. It's funning that I quote the sequence without actually having done it. It's because I've read the steps so many times.. So frustrating!
You have to connect it to a PC to initiate the boot from SD. You should connect it to a pc where its NEVER been connected to before. A few things you can try. Connected to the PC, hold down the nook's power button for up to a minute. Did you hear a chime on the PC as if you connected a device to it? No? Next, open device manager on your PC with the nook connected. From the Action menu >> scan for new hardware. Did it find anything new? Do see anything with the name "gadget" or portable gadget in the device list? Right click, delete it. Again, scan for new hardware. Did windows find new hardware now? Did it boot from SD? Try plugging into a different PC. This is THE ctritical step.
I had this problem when i wiped my device and rerooted. Because the device drivers were already installed, my nook wouldn't boot n root. Chances are you connected it to your PC before attempting to root. You have to get windows to detect as a new device and the PC should fail to load the drivers. If you get that far with no luck, keep deleting the device from device manager and reconnecting it with the cable. Hope this helps...
vlucchetti said:
I used autonooter yesterday on my nc, and it never did reboot. I waited awhile, then just unplugged, turned it on and the android came up.
I did not care for it so I then did the emmc version of custom froyo 6.8 (as I will never use the NC for how it was intended) and am in hog heaven.
Click to expand...
Click to collapse
Went this route and couldn't be happier with the result. Thanks so much for your input!
OP I have the same issues as you, very frustrating!
How did you solve the problem in the end?
edit: NM figured it out.
Hello fellow Shift lovers,
My SnapVue is slow as hell and want to flash a new ROM but have no idea which rom and how to. Have searched but found so many Roms I have no idea which one i should choose.
At the moment I run i00 ROM that was installed when I liberated my shift.
I don't need much. Just a snappy rom with phone capability is good enough.
pelle.jansen said:
Hello fellow Shift lovers,
My SnapVue is slow as hell and want to flash a new ROM but have no idea which rom and how to. Have searched but found so many Roms I have no idea which one i should choose.
At the moment I run i00 ROM that was installed when I liberated my shift.
I don't need much. Just a snappy rom with phone capability is good enough.
Click to expand...
Click to collapse
Hi. Try Thaihugos Age of Reason rom
http://forum.xda-developers.com/showthread.php?t=495143
or Romeos Shift
http://forum.xda-developers.com/showthread.php?t=576408
Incidentally, did you manage to get your drivers for Windows 7 to work. I just installed Windows 7 in a Shift and all the drivers installed correctly. If you are still having any issue unzip the the drivers file in one folder say call it "Shift Windows 7 Drivers". Now go to Device manage and any device showing not to be properly installed (with some yellowish exclamation mark) right click on it select Update Driver and Point it to the Drivers folder and you get each of your drivers installed.....
PlayStation said:
Hi. Try Thaihugos Age of Reason rom
http://forum.xda-developers.com/showthread.php?t=495143
or Romeos Shift
http://forum.xda-developers.com/showthread.php?t=576408
Incidentally, did you manage to get your drivers for Windows 7 to work. I just installed Windows 7 in a Shift and all the drivers installed correctly. If you are still having any issue unzip the the drivers file in one folder say call it "Shift Windows 7 Drivers". Now go to Device manage and any device showing not to be properly installed (with some yellowish exclamation mark) right click on it select Update Driver and Point it to the Drivers folder and you get each of your drivers installed.....
Click to expand...
Click to collapse
Ok, will try the ROMs and keep the best
About the drivers:
I am getting totally sick and tired of the problems with my shift.
The driver install went fine, all drivers installed nice and everything works except from one *** problem: When i try to do certain tasks the shift freezes hopelessly. But the strange thing is that the CPU usage stays around 5%, ram is around 400 MB available but the hard drive light stays on. If I listen closely i can hear the hard drive doing crunch --- 1 second wait --- crunch --- 1 second wait --- crunch --- 1 second wait --- crucurcurnch and the cycle repeats until the power button is hold for 5 seconds. It happens when I: change the network location from public to home, try to uninstall a program using control panel but not using uninstaller from start menu,when trying to move a folder into program files and a few other places I forgotten. It is really annoying the crap out of me. I even feel like leaving out the f in shift
PLEASE let there be a solution for this. Everything else works like a charm but that poblem is to worse to ignore.
pelle.jansen said:
Ok, will try the ROMs and keep the best
About the drivers:
I am getting totally sick and tired of the problems with my shift.
The driver install went fine, all drivers installed nice and everything works except from one *** problem: When i try to do certain tasks the shift freezes hopelessly. But the strange thing is that the CPU usage stays around 5%, ram is around 400 MB available but the hard drive light stays on. If I listen closely i can hear the hard drive doing crunch --- 1 second wait --- crunch --- 1 second wait --- crunch --- 1 second wait --- crucurcurnch and the cycle repeats until the power button is hold for 5 seconds. It happens when I: change the network location from public to home, try to uninstall a program using control panel but not using uninstaller from start menu,when trying to move a folder into program files and a few other places I forgotten. It is really annoying the crap out of me. I even feel like leaving out the f in shift
PLEASE let there be a solution for this. Everything else works like a charm but that poblem is to worse to ignore.
Click to expand...
Click to collapse
Sorry to hear about that. I am surprised because after i upgraded Vista to 7 the Shift is very fast and feels like a whole new thing. I came very close to purchasing a 2 Gb ram to make it even faster but decided against it since I intend to upgrade to a Windows Tablet soon. Figured out that I am better of buying a newer device than spending more money on the Shift which will end up being used much less with a Tablet in the bag... I am holding out for Windows 8 Tabs which I believe will be amazing compared to Android Tabs and Ipad
Now did you Shift behave the way you have described when you were on Windows Vista? If with Vista it behaves ok then it must be that something went wrong while installing Windows 7. A bad software install can cause one to feel like throwing the thing out of the window. If the behaviour is the same with both Vista and 7 then I fear that your HDD could be on its way home.....
Hello! I recently bought a laptop which had 8gb RAM and i7 processor. When i first switched on the computer, the first thing i saw was whether i wanted 32 bit or 64 bit windows 7. i chose 32 bit (i completely forgot that i upgraded from 4gb RAM to 8gb RAM). then later after installing windows 7 professional, i looked at system and saw that only 2.66gb of the 8gb RAM was available!! I then realised that i had clicked 32 bit instead of 64 bit!! now i want the 64 bit windows 7 but i dont know how to get it. The windows 7 did not come in a disc (it came with laptop). Can anyone help me? Any help would would be appreciated!!
I've got plenty of time today so i'll see what i can find out.
What laptop is it?
DirkGently1 said:
I've got plenty of time today so i'll see what i can find out.
What laptop is it?
Click to expand...
Click to collapse
Its the Toshiba Portege R830-2014U. i got a free 8 gb RAM upgrade from 4gb.
Unlucky, for more available ram until you can fix it, if its easy take out the other 4, but being the option on boot, try pressing f12 on startup and try boot a recovery partition?
(also I don't recommend taking it out )
Sent from my GT-I9100 using Tapatalk
In the Toshiba program group there should be a media creation utility, use it to create recovery media just in case, then assuming it's the same as their R700's, reboot the laptop and after the Toshiba screen keep tapping the F8 key to bring up the Windows boot menu options, one should be recovery, select that and you should then have the option to do a factory restore.
Ah what xxacers said, I assumed the key would be f12,
Sent from my GT-I9100 using Tapatalk
There you go Try the above and hopefully you'll be prompted which version to install again.
xaccers said:
In the Toshiba program group there should be a media creation utility, use it to create recovery media just in case, then assuming it's the same as their R700's, reboot the laptop and after the Toshiba screen keep tapping the F8 key to bring up the Windows boot menu options, one should be recovery, select that and you should then have the option to do a factory restore.
Click to expand...
Click to collapse
there is a "recovery media creator" program on my toshiba laptop. And it allows me to create recovery media. is that what you are talking about?
Create recovery media as a safety net. You'll never know when it may come in handy. It's the next step that xaccers detailed that should get you back to factory condition though.
DirkGently1 said:
Create recovery media as a safety net. You'll never know when it may come in handy. It's the next step that xaccers detailed that should get you back to factory condition though.
Click to expand...
Click to collapse
Xactly
Been rolling out about 30 R700's at work, which involved creating new base images with some of the required software pre installed, so did lots of restores to factory settings as Microsoft only allow 3 goes at creating a base image.
Very nice laptops they are too, although they need the latest bios and fingerprint drivers to work with Toshibas docking stations (something most home users will never use).
I've got a 4-5 year old P200 that is still going strong, and my older A100 has only just given up the ghost and that's after a year of 24/7 use sat on top of my Sky HD box as a media PC (ex's cat dropped a bed on it breaking the LCD but everything else still worked).
Just had a read of the user manual for your laptop. Once you've finished creating recovery media, to factory reset the machine the instructions were to turn it off and then back on whilst holding down the '0' key.
This should get you into the Toshiba recovery menu.
DirkGently1 said:
Just had a read of the user manual for your laptop. Once you've finished creating recovery media, to factory reset the machine the instructions were to turn it off and then back on whilst holding down the '0' key.
This should get you into the Toshiba recovery menu.
Click to expand...
Click to collapse
Lol whoops should have read the user manual. if i do a Restore Original Factory Image, will the programs that came preinstalled with the toshiba be available?
androidlover123 said:
Lol whoops should have read the user manual. if i do a Restore Original Factory Image, will the programs that came preinstalled with the toshiba be available?
Click to expand...
Click to collapse
Yes, they will. Everything should be the same as it was when you turned it on for the very first time. If you have any important files on there that you don't want to lose, back them up now!