I flashed an ICS nightly from over in the development forum and I'm left with a Nook that won't boot. Basically I flashed the nightly, booted ICS and then rebooted as I forgot to flash gapps. Upon rebooting I got the new cyanoboot bootloader however I can not boot into anything. I just get loading... If I try to boot into recovery I get loading recovery... and nothing. I tried flashing recovery onto my SD card and selecting each one of the 3 SD card boot options from the bootloader menu however none of them work. Everything hangs at loading. Any ideas one what my next step should be?
Sigh!!!
eMMC or uSD?
votinh said:
Sigh!!!
eMMC or uSD?
Click to expand...
Click to collapse
Here's the original thread. My best guess is that it's eMMC.
http://forum.xda-developers.com/showthread.php?t=1526115
Obviously the recovery image I tried was flashed to the external SD card.
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
tlenker09 said:
Got it! Turned out to be a shotty card reader. Swapped it out with another I had lying around and it worked just fine. Thanks anyway!
EDIT: I got recovery working on the external SD card so I tried flashing a stock image. (nookcolor_1_4_1_signed-cwm-OC) I made sure to format everything first. After flashing I held in the power button, removed the sd card, placed it in my reader and formatted it. I reinserted it into the nook and booted. Everything seemed to boot fine until it got to the "nook color by barnes & noble" screen. The gradient bar goes back and forth across the lettering a bit and then I get a flash of a black screen and then back to the lettering. It keeps doing this over and over again like its in a boot loop. Any ideas?
Click to expand...
Click to collapse
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
DizzyDen said:
Since you just flashed the stock firmware with OC and CWM (as alternate) you should also have the ability to boot eMMC Recovery Mode... do that... it will clear data... and restore the data from the original rombackup.zip file... should solve your problem.
Click to expand...
Click to collapse
I actually did something along these lines last night but since I flashed the stock firmware that was pre-rooted and with CWM... I booted into CWM, wiped everything, mounted usb, copied over the stock pre-rooted zip file, flashed it and then fixed permissions. Everything booted fine.
i have the same problem but im on emmc. im just stuck with loading... any solution for me?
Related
I setup my memory card through WinImage to install size agnostic 1.3. I put CM7 Nightly #177 on my Boot partition of memory card and then put memory card in Nook and it installed and shutdown when completed. I turn on my Nook and it begins with the Read Forever Logo and boots off emmc... It doesn't even try to boot of the Memory card.... I noticed this after I updated my stock Nook on the emmc to B&N 1.3??? Any Ideas why my nook wont boot up Cyanogenmod boot able card? Before B&N 1.3 I would see the Cyanogenmod Logo and I could hold the home key to boot up the boot menu and select either memory card or Stock... But I can't get it too from the memory card? Any Ideas?
Thanks In Advance,
Jer
Any Ideas or Suggestions... What if I copied the u-boot.bin from the boot of the sdcard to the emmc... maybe then I could get it to boot into the cyanogenmod boot and choose the sd to boot.... I don't understand it booted up on the sd card to install the nightly(for the first time that is) and then it just doesn't boot again... it just goes directly to the stock... I know the memory slot works because I used a different memory card and it installed the nightly.... I even tried a different nightly and it install just fine but it wont boot from the memory card again.???
Power the NC off, remove the uSD, insert it back in the NC again, power on.
Try a couple times.
If still having problem, do a fresh clean install again.
Tried what you said... it still shows "Read Forever" instantly after turning it on... no cyanogenmod logo... so it is obviously not even trying to load the SD card. When you say fresh clean install, on what do I do it on... A new memory card and install the latest nightly or Factory reset on stock nook?
votinh said:
Power the NC off, remove the uSD, insert it back in the NC again, power on.
Try a couple times.
If still having problem, do a fresh clean install again.
Click to expand...
Click to collapse
Press and hold the N button, then press the power button. Hold them until the green Cyangenmod logo shows AND "booting into recovery" shows up. Then release both.
It will explode CM7 the display will dim (around a 1 minute).
Watch the backlight and when it goes off, reboot the same way. It will flash the green Cyangenmod and the display will go back off (normal.)
Reboot again the same way and then instant you see the green Cyanogenmod logo release both buttons and let it boot up. It will take about 30 seconds for the CMy guy to show up and about a minute total to get to the main screen.
The problem still remains... I don't get to see the Cyanogenmod Logo... It shows the Read Forever logo and boots into Nook stock??? Its like I don't have a memory card in there.... When In stock nook it show the memory card logo in the bottom left and I can click on it it displays the files on it ... u-boot.bin file and all the others.... I just don't understand why it wont boot when turned on.
I wonder if it has anything to do with that I had Clockwork Mod on my emmc and I used the Clockwork Mod remover to get it back to stock recovery??? Maybe this messed up the boot sequence??? It s weird though when I put Cynogenmod on the memorycard the first time... it boots up the card correctly and begins the Linux Penguin install... So obvious it boots from the memory card.... I don't know what to do.
Help!!!
Just curious, but did you try to read the card in the card reader?
If you wrote it in Windows, you might have to check via disk management that a boot partition was made.
winimage sucks. Many, including myself, have had the same issue. Use win32diskimager instead. That's what worked for me.
Thank you Thank you
Win32Diskimager was the key... and too easy to use.... Thank you so much.... It took so long to find out the answer... Thanks to all that tried to help!!!
After several agonizing hours of writing image, formatting, reading, and panicking, I have finally installed CM7 via verygreen's method.
Thanks for the tip about win32diskimager. this made all the difference!
amp3d said:
After several agonizing hours of writing image, formatting, reading, and panicking, I have finally installed CM7 via verygreen's method.
Thanks for the tip about win32diskimager. this made all the difference!
Click to expand...
Click to collapse
Check your stock Nook. Did you end up with Clockwork Recovery on it?
how do i check?
as far as i know, there wasnt a CWM on verygreen's method, was there?
When I wrote the image using WinImage, the NC always booted up stock. nothing out of the ordinary.
When I wrote it with Win32, it immediately loaded the installer.
but now after turning the device off, taking out the sd, booting stock, and powering off to put the sd card in, cm7 can't seem to get a wifi connection... hope to find the answer soon
Hello, my u8800 just died..
i got a blue screen a couple of time and had to pull the battery.
now it is completely dead... ? how so?
it was running MIUI just fine and i just rebooted it and got a blue screen..
What happens if you press and hold Vol+,Vol- and Power?
Can you still get into Bootloader?
Bluescreen usually wipes the Bootloader, but you can fix that if you can still access it...
In case you lost all the data in Bootloader (pink screen), format the partition with FAT32, create a folder called "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
If you can't access the Bootloader (pink screen), I'm afraid it's going back to warranty.
same thing happened to mine, still trying to fix it. managed to flash CWM recovery like that but now factory reseting leads me no where, of course, and restoring a backup from the sd didn't work either, all i get is a bootloop.
i'm so very lost please help, tell me what you need to know to help me
DON'T factory reset or restore a backup! Once you've had a blue screen, you CAN'T restore or factory reset a Rom.
You should flash a custom Rom directly. Just copy the Oxygen.zip (http://sourceforge.net/projects/u8800oxygen/files/) in the root folder of the SD card and then wipe data, cache and dalvik cache.
Flash the new Rom by Selecting "install zip from SD" and select the Oxygen.zip archive, the installation process does everything else.
katu2006 said:
What happens if you press and hold Vol+,Vol- and Power?
Can you still get into Bootloader?
Bluescreen usually wipes the Bootloader, but you can fix that if you can still access it...
In case you lost all the data in Bootloader (pink screen), format the partition with FAT32, create a folder called "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
If you can't access the Bootloader (pink screen), I'm afraid it's going back to warranty.
Click to expand...
Click to collapse
Thanks GOD!
It was completely dead, but when i wake up this morning i got it on with bluescreen again, hooked it up with my pc and copied the files u linked.
now it seems MIUI is booting fine again!
but how come it got wiped in the first place?
Not sure to be honest...It's some sort of miscommunication between bootloader and Rom (kernel) and Huawei designed a fail-over mechanism that wipes the bootloader (screen becomes blue when this happens).
Anyway, glad to hear that you got it going again.
wow thanks katu2006 xD I just realised how stupid I was
you see this whole thing happened, I think, because I tried formatting a NTFS sd card I put in the phone. I wanted to put files bigger than 4GB in it...
so when I got the blue screen and then managed to boot into CWM recovery, all I had to do was flash a ROM, I knew that, but my internal sd card was wiped clean and I couldn't access it in my PC when I plugged the phone. then I just figured I should get another sd and put MIUI in it and then stick in the phone LOL it's working fine now, thanks a lot
Glad to hear that you problem was resolved as well.
I have the same problem with my U8800. And I follow your direction and I can log in to the Miui rom, but it has the notification "Blank SD card or unsupported file system" and ask me to format the SD card. But when I format the SD card, it change into the blue screen again in the next reboot time. What should I do.
balderhell said:
I have the same problem with my U8800. And I follow your direction and I can log in to the Miui rom, but it has the notification "Blank SD card or unsupported file system" and ask me to format the SD card. But when I format the SD card, it change into the blue screen again in the next reboot time. What should I do.
Click to expand...
Click to collapse
OK, you should copy the SD Card contents to your computer, format it with FAT32, copy the folders back and then try to boot in Recovery and reinstall Miui again.
I also had such a problem. And as in your situation, my solution was to copy those files into 'image' folder. Though, blue-screen-trouble is still actual and we have to blame only huawei-guys
Is your IMEI allright? after some of theese operations, I had mine nulled.
OK, you should copy the SD Card contents to your computer, format it with FAT32, copy the folders back and then try to boot in Recovery and reinstall Miui again.
Click to expand...
Click to collapse
Thanks for your advice; I have flash the new Miui rom, and I can format it normally. Now, my phone is ok.
so i have the same problem i just did wat u say the phone give me the ideos screen then restarts also cant get into bbotloader
iwas on 2.3.5 version the files r the same or others
thnx
Thanks Man
Thanks for tips Katu2006, i tried it as you said and it worked as well !!!
Now i know what do in future if blue screen shows up again ))
lobfredd said:
Thanks GOD!
It was completely dead, but when i wake up this morning i got it on with bluescreen again, hooked it up with my pc and copied the files u linked.
now it seems MIUI is booting fine again!
but how come it got wiped in the first place?
Click to expand...
Click to collapse
i have downloaded the stuff you wrote and the blue screen don't appear not longer. but when i turn on the huawei it stays on for about 30 seconds and then the screen goes black. what did i do wrong?
katu2006 said:
DON'T factory reset or restore a backup! Once you've had a blue screen, you CAN'T restore or factory reset a Rom.
You should flash a custom Rom directly.
Click to expand...
Click to collapse
I beg to differ - for me when I had a blue screen yesterday - tried everything other than reflash. In the end I pushed a clockworkmod backup to the internal sd card via adb, did a restore and problem solved.
lobfredd said:
Hello, my u8800 just died..
i got a blue screen a couple of time and had to pull the battery.
now it is completely dead... ? how so?
it was running MIUI just fine and i just rebooted it
Click to expand...
Click to collapse
Same thing happened to my phone can't get into bootloader and no display even when i connect it charger or PC..
please help!
Thanx in Advance!
Blue screen
I was stuck with a blue screen for days after i formated the internal mem, i got stuck until I came across your post . downloaded the files to image folder and here i am with a working phone, thanks a million.
Had been running CM7 Mirage Kang on my Nook Color internal memory for the past few days. Than last night I rebooted into recovery and since than it will not go to recovery nor CM7. It show Cyanogenmod loading for maybe 20 seconds and than nothing screen blanks out.
Than I loaded into CWM via SD card. Wiped and formatted everything. Re-installed CM7 & Gapps, but no progress. It does same thing.
When I look at mounts & storage via CWM it appears that Nook doesn't even see emmc. Look at the pictures below.
Any help appreciated.
When the boot image first shows up, hold the n button until the boot menu shows up. Then choose boot to emmc. I think the boot to recovery flag is set, so no matter what you do it tries to boot to recovery and it sounds like recovery is borked. If you get it working, go to ROM Manager and flash a new recovery.
Sent from my Nook Color running ICS and Tapatalk
Wow I was afraid many people will tell and argue about everything but what I needed to know.
Your message was short and straight to the point. Thank you very much.
What's funny is that I knew about the Boot Menu and had been messing with it all morning with no success. Somehow after reading your post tweaking with the Boot Menu within few minutes I am back in business.
Now I am able to see format/ emmc on the CWM again like before. So I was able to format/ emmc for a full wipe clean install.
Thank again.
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
bassmosphere said:
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
Click to expand...
Click to collapse
I ended up getting it booting up into Jellybean. First I tried restoring as mentioned above with the SD card.
This next part, I believe is the key as the device revived after this step. I put it into a bootloader restore mode by powering on with volume down and flicking the screen lock switch once the device vibrated. After this, it continued with the tablet setup mode and booted into Jellybean.
How it started: I use a NC with mirage 7.2 flashed to the emmc in my car. It runs Torque to display engine data, and is switched in and out of sleep with the ignition. Two days ago I started the car and got the low-battery "exclamation point" icon thing, so I figured the charging cable must have come loose*. I took it all out and left it charging overnight, but when I went to boot it in the morning it was stuck in a cyanoboot loop. I couldn't power the device down or enter emmc recovery. When I completely unplug the NC I can't do anything, the screen remains black no matter what I press, except it flashes white every 5 seconds or so. If I manage to plug it on, get to the cyanoboot loading screen and unplug it while holding the power button down at the right time, I can sometimes get it to power off completely.
What I have done so far: Tried various recovery SD methods, none of which worked. Wiped cache/data/system, factory reset, tried loading 7.2 again over the top of whatever is left in there, lol. Basically after it first happened I probably made a big mess of the file system in a desperate attempt for some kind of stability. I tried this recovery SD: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 ; section A10, and managed to get into CWR. I've never felt such joy in my life.
What finally worked: I repaired the 2nd partition with the help of this thread: http://forum.xda-developers.com/showthread.php?t=1759558 . I did not repair or format any other partitions though. After repairing the partition, I did a factory reset and flashed mirage 7.2 and gapps back onto the emmc. Before I rebooted, I swapped a clean SD in but it still went back into the bootloop..BUT...when I put my recovery SD back in it booted into 7.2! I set everything up and was happy to have it running again. Battery level was at 88%.
What made it stop working: I was testing to make sure the NC would enter sleep mode when disconnected from power, so I unplugged it. Everything went black, no "sleeping" screen, just a hard shut-down. I powered it back on and I'm now back in a cyanomod boot loop.
So...any ideas? If there's a way to completely wipe and reinstall everything I'm OK with that. I've never used ADB before but I'll give it a shot if someone can lead me in the right direction. Thanks in advance.
*I'm using a 2amp USB car charger with a modified data-looped cable for a/c style charging in the car. I know the supplied nook cables are prone to going bad, and this may have happened with the vibration of the car and all. Not sure.
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
SPLEclipse said:
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
Click to expand...
Click to collapse
To completely wipe and reflash everything, do the other two zips that you said you did not do from my partition repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Sounds like there might be some bad data in emmc, I had this problem before and fixed it by formatting everything , even emmc and wiping dalvik cache. Then boot off a SD card using the latest cwm.
Sent from my NookColor using xda app-developers app
SPLEclipse said:
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Click to expand...
Click to collapse
It is possible that your partition table is messed up. The only way to find out is to boot to recovery, connect your USB cable to the PC and run ADB. It is also possible to make a CM bootable SD and use terminal emulator to check it out.
Once you get ADB shell or terminal emulator working, type the following command:
fdisk -l /dev/block/mmcblk0
It should say 965 cylinders, 4 heads, 63 sectors.
If it does not, we need to do a manual repair.
You can also abandon emmc and just run off SD.
Sent from my Nook HD+ running CM10 on Hybrid SD