Issue with recovery freezing - Barnes & Noble Nook Tablet

Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.

Use this thread to install CWM, I'm not a fan of TWRP. http://forum.xda-developers.com/showthread.php?p=25786947 I used this and had no problems updating
Sent from my NOOK Tablet running CM10

deltantor said:
Recently decided to try and switch over to CM10, and have been having an issue with recovery. Both of the latest CWM and TWRP recoveries freeze for me after booting into them. The only recovery that works for me is the one that is flashed with the old app by Indirect but that flashes a really old CWM recovery. The recoveries that I have tried flashing are the ones linked to in the http://forum.xda-developers.com/showthread.php?t=1877217 thread. Both http://celticstorage.co.uk/cm10/CWM_v6.0.1.5_emmc.zip and http://celticstorage.co.uk/cm10/TWRP_v2.3.1.1_emmc.zip are doing it. I have a 16GB that ive kept (rooted) stock forever.
What happens is i go to boot to recovery, go through cyanoboot to recovery, and then CWM freezes up and blackscreens after I try to wipe something or install a zip, TWRP just locks up immediately and gives me a black screen. Any help fixing this would be greatly appreciated.
Click to expand...
Click to collapse
This has been happening to me occasionally. I have found that when I get the black screen, pressing the Power button launches Recovery (CWM in my case). See if that works for you.

I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.

To the rescue
Ok, I have posted this on a different day. Try this with a blank sd card. Look at the bottom post called "Here is a video"
It a external boot cwm v.5 but you can copy this into your sd then flash and you have cwm v6.0.1.5 internal. Either way you have two ways to do recovery (external and internal):victory:
djd338 said:
I now have the exact same problem. I've always ran off emmc. It says cwm 6.0.1.5 is installed. When I try to either wipe, or install zip-from-sd, cwm freezes then goes to the black screen. I cannot install any zips, so right now the tablet has nothing installed only a freezing cwm recovery it seems. I can use the power button to get out of the black screen and into cwm thru cyanoboot all day, but get nothing but these same steps reoccurring. Freeze, then black sod. I'm ready to try anything but cannot flash anything.
Click to expand...
Click to collapse

Thanks very much for the reply & link!
I'll do this ASAP when I get back home & report. Thx again!
Sent from my Nexus 7 using Tapatalk 2

Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!

Look pass the fear and go one step at a time, before you know it, your there.
It looks like you have already resolved this from this thread.
Ok, basically I'll go step by step.
1. Download ubuntu iso from ubuntu website (you can donate or put 0$ then download iso) and burn it to cd. 5 minutes
2. Stick the cd into a system that you don't plan to look at the video that is showing you the process and boot it up from a reboot and not from within windows. Select the left square which basically load the ubunbu from cd but does not install anything to your hard drive.3 minutes
3. You can view the whole video but I would skip to the section in video (3:28 watch to 4:43, 6:56 watch to 8:06 ) where I mentioned the setting the two flags in your sd after quick format fat32 and extracting the four files into your sd within ms windows platform from the post . I did this with a normal mini sd card adapter and not the usb stick adapter he used in the video. Since you are doing this to a blank mini sd then there really nothing to worry about since it is blank in the first place. 2 minute
4. If you had your apps backup with titanium backup then it still will be on the main mini sd and not the one that working with for this recovery.
5. I notice you did not mention wipe dalvik cache from your post. You should always wipe dalvik then wipe factory then do a single flash to test boot up.. You can flash gapps after a successful boot up into jellybean. (here's a video showing that I'm using external cwm v.5 even though its recommended to use v.6 .) You can always use cwm v.6 on your next cm10 test rom or use cwm v.6 to reflash to same rom once a successful boot up have been obtained with external cwm v.5. This purpose is to get it running on your nt.
6. Be patient for the first boot. Should not be more than 5 minutes max. It will look black then load. If it boot loops then wipe dalvik then wipe factory and do a single flash to test boot up again.
This will at least get cm 10 flavored rom on to your nt.
djd338 said:
Well, I think I need to clarify more. Maybe somebody can help if I give more info. I've had cm7 running perfect, then decided to install cm10. I first flashed a cwm 6.0.1.5 zip to emmc. I did a factory reset via this recovery thinking my next move would be to flash the cm10 zip I'd put on the sd. No joy. This is where I'm at now.
In recovery it freezes and reboots to the "2 androids" screen with a sod. I hold power for 20 sec.s to turn off, then turn back on and get to cyanoboot fine. There, if it's allowed to just boot it freezes at the 2 androids. If I hold "n" to get the menu and recovery (6.0.1.5) it looks normal, will boot to recovery OK until anything is selected like the cm10 zip. It freezes before any selections can be finalized, and boots to that sod screen.
I know nothing of ubuntu! Sorta scared to go there with my limited knowledge. But will read up if it's required. Is it possible that this new recovery image don't play with what is currently on the sd? Is there anything I can put there that it may recognize in order to get a flash? Man, I'm lost!
Click to expand...
Click to collapse

Got it back! Thank you for your help & patience. Also for the timely responses. I now have a bootable "recovery sd card" for curing these type problems. I've labeled it & filed away for any future borks of this kind! And I have cm10 up & running stable.
Thank you!
Sent from my Nexus 7 using Tapatalk 2

Related

[Q] [Solved!] HELP!! How to unbrick my tablet? - fix inside

I am one of the lucky ones who got their tablet from woot/amazon for $280.
I got it in yesterday and absolutely hated the Tap Tap interface.
Naturally, I wanted to install a new ROM. I could only get the TnT Lite to install, but still not what I wanted. I tried Vegan and G-Harmony and I got the dreaded 3 bird screen. I downloaded and successfully installed 3588 and rebooted it. I noticed the ClockworkMod is no longer on there, which is no problem.
I followed the directions to install Clockwork and ROMS from here:
http://forum.xda-developers.com/showthread.php?t=865245
I, for some reason, decided to install Vegan again w/o clockwork installed.
I mounted the internal memory card, copied he ROM over as update.zip with the Recovery folder and the command file set to install from SDCARD. A reboot later and now I am stuck at the 3 birds...
I was able to do the Power +Vol and get the "Recovery key detected" message and it seems to load something, hitting the home button gives me the verbose which indicated that it was trying to install something off SDCARD2.
I have tried 3588, clockworkmod and Vegan as update zip on the external SD card with the Recovery folder command file pointing to SDCARD2.
When booting into Recovery, the verbose says: "FORMATTING MISC... REBOOTING..." takes about 4 seconds to complete, reboots and back to the 3 birds screen.
So, how do I [email protected]#$ myself here?
UPDATE!
I got my tablet to boot into CWM!! I ended up putting the MicroSD version of CWM and held down the Power +Vol longer that normal, saw the Android text and it installed the update.zip.
I tried in vain to boot into CWM, but it would re-install the update.zip. *Head smack* took out the SD card and now it boots into CWM!
Now, to try to install a ROM w/o those damn 3 bird screen...
Bootlogo not part of a ROM
You can replace the birds logo, but it is not part of a ROM. Search for replace boot logo, but make sure you know the correct partition to push your custom logo too. Read the entire thread when you find it first. There are tools out there that will let you back up your partitions, I highly recommend doing that first. Search for backup bct and look for PooR's thread and tools.
michaeljwestii said:
You can replace the birds logo, but it is not part of a ROM. Search for replace boot logo, but make sure you know the correct partition to push your custom logo too. Read the entire thread when you find it first. There are tools out there that will let you back up your partitions, I highly recommend doing that first. Search for backup bct and look for PooR's thread and tools.
Click to expand...
Click to collapse
The boot logo is not my issue, it's just that it does not go past it no matter what non-TnT ROM I try to install.
I just want to install anything other than the factory OS or a modified factory OS (no disrespect to the dev who made TnT Lite).
I started another thread on my troubles getting a new ROM on there:
http://forum.xda-developers.com/showthread.php?p=13113438

[Q] Rooted my first time tonight, something went wrong?

Hey All, I rooted tonight Via Revolutionary tool but now my phone won't boot.
Basically, I followed all the steps with the tool, Got root and Clockwork and installed the SU.
I rebooted and had a rooted phone.
I proceeded to install Rom Manager, and I backed up my Rom (Created a Nandroid backup I believe thats what it was).
I then downloaded CM7 (the latest one in the Rom Manager) and installed it.
The phone rebooted for about 10 minutes with that CM7 Boot animation looping. I took the battery out, held down the volume button and used Recovery to recover my nandroid backup from before.
Now I'm trying to reboot it and its stuck on the White screen with the HTC Logo just sitting there.
Really unsure what to do...
Edit: this is all kind of assuming you flashed the newest clockwork recovery after you d/l ROM manager ( version 5x of clockwork recovery)
Seeing as how your phone won't boot you will need an sdcard reader to do this. So assuming you have one or another phone with internet you can swap the card into:go [url="http://forum.xda-developers.com/showthread.php?t=1179386]here[/url] and download the clockwork recovery version 4.0.1.5 and place it on the root of the sdcard. (not in any folders) rename the file to PG05IMG.zip EXACTLY and put the sdcard back in the thunderbolt. Now hold volume down plus power Untill the bootloader screen appears. (you may have to select bootloader from the list with the volume rocker and tap the power button to select it) once in the bootloader give it a minute and it will find the file and ask you to press volume up to update. Do it. When its done select reboot and then boot back into the bootloader and choose recovery. Now try restoring your backup. It should.work now. The problem is Clockwork recovery version 5.x is having issues right now with restoring backups.
Sent from my HTC Thunderbolt
Original problem of OP's CM7 install bootlooping was because he didn't wipe data/cache.
As for the white HTC screen it's hanging after restoring for some reason. People have reported this with CWR5 (if that's what you have) but I have been unable to reproduce it as of yet.
That said, it's probably only preventing that restore from booting. You should still be able to boot to hboot (pwr+VolDwn from an off state) and then select recovery at which point you can wipe data/cache and flash something from your sdcard. If you don't want to mess with an adapter to put something on your sdcard, you should still have CM7 on there. You said you used RomManager to download it so it should be in /sdcard/clockworkmod/download when you want to flash it.
Thanks so much! Since I couldn't get a quick response, I used an RUU and went back to complete stock S-OFF. Could you relink the clockwork recovery earlier version please? That link isn't working for me for some reason.
Thanks so much!!!!!!
JBO1018 said:
Edit: this is all kind of assuming you flashed the newest ( version 5x of.clockwork recovery)
Seeing as how your phone won't boot you will need an sdcard reader to do this. So assuming you have one or another phone with internet you can swap the card into:go [url="http://forum.xda-developers.com/showthread.php?t=1179386]here[/url] and download the clockwork recovery version 4.0.1.5 and place it on the root of the sdcard. (not in any folders) rename the file to PG05IMG.zip EXACTLY and put the sdcard back in the thunderbolt. Now hold volume down plus power Untill the bootloader screen appears. (you may have to select bootloader from the list with the volume rocker and tap the power button to select it) once in the bootloader give it a minute and it will find the file and ask you to press volume up to update. Do it. When its done select reboot and then boot back into the bootloader and choose recovery. Now try restoring your backup. It should.work now. The problem is Clockwork recovery version 5.x is having issues right now with restoring backups.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
^^^^^ Follow this to the T and you should be golden. Same thing was happening to me the other night and it all started after I updated to CWM 5.0.1.0
On another note after that debacle I switched to the unofficial TeamWin Recovery and have yet to have an issue. If you're interested you can flash it the same exact way as mentioned in the previous post but download the file from Rootzwiki
http://rootzwiki.com/showthread.php...ery-Project-for-Thunderbolt-(8-8-1.0.3-rbox.2
OK. so let me update yall.
I installed the latest version of clockwork, before yes, and it F'ed me up with the looping bootloader.
I installed the older version of CW recovery, renamed it and flashed it with Hboot.
My Flashes now are all 100% not looping and booting perfectly.
Thanks all!
Double check the backup files. i had a similar issue and noticed the files were backed up as .zip instead of .img. You will probably need to install another rom through clockwork.
GMac0051 said:
Double check the backup files. i had a similar issue and noticed the files were backed up as .zip instead of .img. You will probably need to install another rom through clockwork.
Click to expand...
Click to collapse
His problem with restoring the backup should be fixed now. Koush released CWR 5.0.2.1 which should have fixed the ext3 problem with sense roms.

[Q] Permabricked 16Gb nook, no adb, can't boot recovery, can't restore from sd

It doesn't seem real common, but I seem to have permabricked my nook. I can't connect to it via adb, can't boot to recovery from sd or the emmc, and can't seem to get it to recover via sdcard. I've tried Adam's Unbuntu Unbrick, copying the recovery to the sdcard, and trying to recover to 1.4.2 via the sdcard.
How I broke it:
I installed Goomanager and installed TWRP, and then flashed to CM9 with the 3.0 kernel. The recovery and CM9 were working as well as could be expected, but CM9 had too many Sleep of Death issues so I decided I wanted to roll back to a nandroid backup of CM7. TWRP couldn't see my backups, so I decided I'd flash the recovery back to CWM via indirect's nookrecoveryflasher.apk. This was the end.
The symptoms:
I rebooted after using the nookrecoveryflasher flashing back to CWM, and now it just displays the n with the copyright info. It then flashes white briefly, then a slightly bigger n is displayed, it gets brighter, then dimmer, then a black screen (still backlit). The charger goes from red-orange to green after the screen goes black, and charging appears to be halted. If I hold down the power button for 8 secs, the backlight goes off and the charger light turns back to red-orange and it seems to charge. ADB lists no devices.
Are there any suggestions for things I should try that I haven't already? I thought this was pretty much unbrickable but something went really badly, and this should have been a relatively "safe" operation.
Update:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Did you try removing and inserting the sdcard back in while in twrp?
I stayed with cwm and I was able to flash both kernel versions of cm9 just fine. Since u already tried the 1.4.2 revert to stock, your situation seems quite troublesome indeed
Sent from my Nook Tablet using xda premium
I can't get into either TWRP or CWM now.
Hm sounds like your recovery is screwed up...
Sent from my Nook Tablet using xda premium
Do you know what kind of bootloader you are using? Is it cyanoboot?
Sent from my Nook Tablet using xda premium
Cyanoboot was installed when I installed CM9, but after trying to flash back to TWRP, it doesn't seem to be coming up any more.
Wow that's unfortunate. I was thinking if u were using cyanoboot you would be able to hold the n button to choose where to boot from...
Sent from my Nook Tablet using xda premium
Have you tried burning a clockworkmod recovery image to an sdcard and booting into cwm via said sdcard? If you can get this to work, you can flash the internal cwm recovery zip to overwrite the internal recovery partition.
Also try the 8 failed boots method. Each time you see the gray n logo dissapear when powering on, pressand hold both the n button and the power button until your nook tablet shuts off. Repeat this 8 times and your tablet should be forced to boot into recovery mode. Good luck!
Sent from my Nook Tablet using xda premium
I don't think that will work, as it sounds as though the recovery partition was broken with indirect's app (it happens and I think there is a thread he made with 1 method of fixing broken partitions but it requires you to have drivers set up properly for it).
I had this same thing happen to me when indirect pushed his new app that supports the 8GB and 16gb models out. I got the big N and I ended up flashing cwm via sdcard cwm and then flashing cm9 again via the newly flashed internal cwm.
Yes I've tried putting CWM on the sdcard but the same thing happens. I've also tried 3 different sdcards 2,8,16Gb. I've tried meghd00t's repart.img and it all behaves the same. It's as if the code that gets called to read the sdcard is broken now.
It sounds like after that white flash is when CMW should load but instead I get a bit bigger n, and then it goes black.
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
comat0se said:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Click to expand...
Click to collapse
try locating the stock 1.4.2 rom in the development section and flash that. see if it works.
In general if you are in CWM you have adb access at that time. The world is at your wish when adb works. Push stock recovery, etc., etc. Instead of trying to flash (which continues to fail) use adb to recover by of the many methods available. I would begin with pushing stock recovery and boot recovery (by command or power + N).
Good Luck.
Lars for tobdaryl
Did you flash TWRP using the .zip from the 1st-2nd page? That TWRP .zip is bugged so as not to recognize an external sd. I had a problem like this until I used a recovery sd (ill put a link in here in a sec)
I had a terrible 13 hour run of trying to fix it before I finally got it to boot, then I opened up my gmail inbox and found out that I had won a Transformer Pad 300 from Phandroid.com, needless to say after 13 hours I was nearly hysteric when I found this out, hope your issue gets resolved.
I also couldnt mount sd, couldnt adb, couldnt fastboot, couldnt get sd to show up in TWRP so maybe this method will work:
http://forum.xda-developers.com/showthread.php?t=1640958
Sent from my Transformer Prime TF300T using XDA Premium HD app

Need Help Fixing Tablet

Hey guys,
I have a 16gb Nook Tablet that I rooted using Albert's bootable zip. I installed CWM via the recovery flasher included in the root pack and then proceeded to install a rom. When I went to boot in to CWM using just the sytem itself, the screen stays on the white screen with the box and it jumps around(looks like top of box is broken but it isn't). I have a bootable recovery sd that allows me to go in to CWM but i am getting E: can't open /cache/recovery/last.log
I've tried reinstalling the ROM and it gets to the boot screen and then starts jumping too.
Has anyone had success with fixing this issue?
That sounds like very strange behavior, it sounds like you might have an issue with CWM on the device itself. In fact, after you apply the root and everything you shouldn't need to be back in CWM again unless something goes wrong.
Can you boot the tablet into the normal OS, or does it only try and go to CWM?
It only goes in to CWM. I should be able to use fastboot from CWM right?
I don't know to be honest. If you can't boot into anything else, I'd go back tot he start. I know there is a thread around here that you can actually use CWM to restore back to 1.4.2 stock, then you can re-root from there.
I think I may have it, but I'd have to look.
http://forum.xda-developers.com/showthread.php?t=1663836
Here bro. This should bring you back to full 1.4.2.

[Q] will not boot into recovery

Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
miapjp said:
Hi,
I have a rooted (using Indirect's method, I believe, with help from Albert W.'s video) Nook Tablet 16GB. I'd like to try a custom ROM and installed GooManger (1.2.1). I can download a recovery file (openrecovery-twrp-2.3.1.1 -blaze.img), and it says it installed it, but when I try to boot into recovery ("Reboot recovery" option) it just reboots normally. If I try to browse compatible ROMs, it says "No roms were found".
Googled but could not find an answer. I would appreciate if someone could point me in the right direction!
Thanks,
Pat
Click to expand...
Click to collapse
I think you're trying to use the wrong recovery file. Try downloading CWM or TWRP from the links listed in the first post of this thread -- I've used both with no problems on my NT.
Saludos,
Steve
Removing CM9
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Mauler85 said:
HELP! I installed CM9 on my nook tablet 8gb and I am not happy with it. I want to take it back to stock so I can load CM7. HOWEVER I cannot find a single website with this information. I keep trying to power it off and then hold the power and n to no avail. The cyanoboot menu just loads and I cant load any of the ROMs. Its really pissing me off and I would like to just get rid of this os. Can anyone help?
Click to expand...
Click to collapse
You don't need to go back to stock to downgrade from CM9 to CM7. All you need to do is boot into recovery and flash the new ROM. With that being said, it would be well worth your time to start by installing Titanium Backup and backing up your system before you do anything else... That will let you restore any apps you've downloaded and want to keep (along with their settings and data), which will eliminate one headache after you flash the new ROM...
Review this thread from Lavero.Burgos about installing a customer recovery on your tablet. You've already got one installed if you're running CM9, but the thread has got lots of really good info, and if you have the Clockwork Mod 6.x recovery installed, you need to replace that with Clockwork Mod 5.x to flash CM7.
Next, check this thread from Celtic Web Solutions. The link to the internal CM7 ROM is in the first thread, along with the instructions for installing this ROM to your emmc (internal) storage.
Now, when you start you tablet, instead of holding Power + n to boot into recovery, wait for the Cyanoboot splash screen to open (the one that says CYANOBOOT, not the animated CM9 splash screen), then press and hold the n button until the boot menu appears. From here you can select to boot normally into CM9, into your internal recovery, or into a recovery.img loaded on your SD card. Select one of the recovery options, and you should be able to do a nandroid backup of your device, then install CM7. Since you're changing to a completely new ROM, I strongly recommend that you do a factory wipe/reset as well as wiping the cache partition and Dalvik cache.
NOTE: There's a big difference between an Titanium Backup backup and a Nandroid backup! You'll want to do both as you go through this. Titanium Backup will take a snapshot of your apps (including the settings and data associated with them) that you can restore after installing the new ROM. Super helpful, since you don't have to re-install everything from the Play Store, nor do you lose data like savegames, etc. Nandroid runs from recovery mode, and will do a complete image of your system, including the ROM. It protects you in case you run into a major problem while flashing a new ROM -- it's saved my life a couple of times...

Categories

Resources