[Q][SOLVED] CWM Recovery on new update - Barnes & Noble Nook Tablet

I recently updated my ROM through the goo manager app to this:
http://goo.im/devs/succulent/acclaim/cyanogenmod/sdcard/cm_acclaim_10.1_17MAR2013_HD_SDC.zip
In the new update CWM Recovery was updated to 6.0.2.9. I did a dirty installation, flashed ROM onto SD card, and reset my nook. Everything worked fine, but I forgot to flash the gapps so I downloaded them and reset my Nook. In Cyanobot I selected SDC Recovery, but it went to a black screen for a few seconds and reset my Nook then booted from emmc (my stock.)
Question being, is there something I'm missing to get the SDC recovery to work? Do I need to just download a recovery.img and put on my sd card?

datallboy said:
I recently updated my ROM through the goo manager app to this:
http://goo.im/devs/succulent/acclaim/cyanogenmod/sdcard/cm_acclaim_10.1_17MAR2013_HD_SDC.zip
In the new update CWM Recovery was updated to 6.0.2.9. I did a dirty installation, flashed ROM onto SD card, and reset my nook. Everything worked fine, but I forgot to flash the gapps so I downloaded them and reset my Nook. In Cyanobot I selected SDC Recovery, but it went to a black screen for a few seconds and reset my Nook then booted from emmc (my stock.)
Question being, is there something I'm missing to get the SDC recovery to work? Do I need to just download a recovery.img and put on my sd card?
Click to expand...
Click to collapse
Solved the problem. I just downloaded the latest version, CWM 6.0.2.9, and put it on my SD card. Works just fine. Downloaded from here:
http://goo.im/devs/succulent/acclaim/recovery

Related

Can't seem to successfully flash with CWM anymore?!

I was running the latest CM7 nightly for a while (release 116). I decided to give CM9 a try. I wanted to go back to CM7 so I tried flashing back but something went wrong. I had backup so I tried restoring that in CWM but it gave me a checksum error.
So I tried out the vanilla ICS 4.0.3 (KP8) build using odin. Used it for a bit and then decided to go back to CM7. I flashed to my original OS using ODIN, rooted the phone. Now, whenever I try to flash anything in CWM, it installs but then just goes into a endless boot sequences. Tried flashing MIUI and CM7 with no luck.
I'm on a rooted KI3 release atm.
How can I completely wipe my phone? I've reformatted my external and usb storage with no luck.
...................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Root with same CWM as backup .
Boot recovery restore backup .
jje
Thanks! Following the processes. Wasn't able to unmount SD card to format it but /data /system and /cache formatted fine. *crosses fingers*
going to use a freshly downloaded copy of CM7 nightly too incase my old zip got corrupted somehow.
I can install my stock firmware and root it with odin.
But, once I try to install Rom Manager and update CWM recovery things start going wrong. It reboots into the regular android recovery console and fails to install the update.
But, if I battery pull and boot into recovery it boots into CWM recovery 4.0.0.5. I can apply the update.zip ROM manager downloaded. But, then when I try to flash anything it doesn't install properly and I get stuck in an endless boot loop. Can't even boot into recovery. Have to start all over again with ODIN.
Rom Manager is causing you grief.
Had a similar thing happen a while back. I wouldn't use it at all if I were you and stick to using CW Recovery. I don't know the why/how/wherefore, I just know that time I tried to use it, it broke recovery & put me in a bootloop same as you.

Won't turn on

I downloaded androwook 2.1 and cleared my whole sd card. Which was one of the options for androwook. Then I flashed another rom that bootlooped. Now when i go to cwm recovery and install a zip the only zip that shoes up is the one that doesn't work.What should I do. I am new at this.

Think I may have bricked my prime?

I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer

[Q] Keeps booting into Clockwork Recovery instead of CM

So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Try this
SarahAnne said:
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
Click to expand...
Click to collapse
Try this : http://www.mediafire.com/?4s77jvehqvsuruu
1)Download it
2)put the files ( flashing.boot Mlo etc...) on your sdcard,
3)completely turn off your nook ,
4)put your sd card on nook and turn it on.
5) press the ''N'' button when you see ''cyaogenboot'' (it also saids press ''n'' button for BOOT MENU)
6) in Boot Menu just choose option #1 (Internal Boot) it should boot into cm10
I had the same issue, but after a time (after making some supid things) i bricked my tablet, I figured this out with some help, It worked for me so it should work for you too.
So I was able to randomly boot into the bootloader and boot into CM but now it keeps rebooting into clockwork.
I have also attempted installing CM10 using the following link including using the flashable_fix_bootloop.zip that I cannot sadly can't link to due to being a new user
and the only difference is that now CWM went from blue accents to orange.
The function of flashable_fix_bootloop.zip is to reset BootCnt counter and BCB flag (see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1) in the event they do not get reset properly in some installation/recovery process. It seems that your "recovery boot-loop problem" might have a different underlying root-cause, hence re-setting these counter+flag by itself will not cure the problem.
Which particular build version of CM10 and AOKP ROM did you try?
Also, did you do "wipe data & factory reset" & "wipe cache" as part of the ROM installation?
Have you tried reflashing the ROM once you're in CWM? (As I underestand you may have, but just making sure!)
Maybe download it again (or try another one) and the flash it again (after the usual wipes) with your new recovery.
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
SarahAnne said:
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
Click to expand...
Click to collapse
When you boot from the SD card have you tried holding down 'n' to get to the menu then selecting SDC boot? It should boot cm10.1. Try selecting SDC recovery also and see what it does. You might be doing something wrong during the process.
You can also try renaming your boot file for cm10.1 to altboot. Then try it.
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
SarahAnne said:
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
Click to expand...
Click to collapse
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
DavDoc said:
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
Click to expand...
Click to collapse
6.0.3.1
SarahAnne said:
6.0.3.1
Click to expand...
Click to collapse
Still may be a shot in the dark, but try downgrading CWM to an earlier version, but not so early as to be unable to flash CM10. Maybe 6.0.2.5 to 6.0.2.9
Not ensuring this will work but it may be worth a shot. At least it won't put you in any worse condition than what you are in now.
Good Luck
Another thought, did you make a backup of your last ROM before flashing CM10? If you did I would assume you tried flashing your backup already, but have to ask.
It looks like you may have used two different builds of CWM based on one of your earlier posts - change of font color.
You also try the repart image if you don't have a stock backup. Find it on raywaldo site. It will re write your internal storage with stock ROM. Then flash cm afterward.
Woot I got the factory rom reinstalled, time to install cynogenmod again
I had the same problem
This worked:
digixmax said:
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Click to expand...
Click to collapse
However I was still unable to install any 4.2.2 ROMs + gapps.
I was on cwm 6.0.2.8 (or whatever the exact numbers are)
updated to cwm 6.0.3.7
wipe data
install rom
install gapps
wipe cache
wipe dalvik
everything works now.

Tried flashing CM11 , but installation aborted.

So I plan on installing 4.4 kit kat. So I went ahead and downloaded cm11. I then went into recovery , I wiped data, wiped cache and dalvik.
Then went into mounts and storage and formated system ,data and cache. I then went to install cm11 and I got this error:
ELerror in /emmc/kitkat/cm11-xxxxx nightly.
(status 7)
Installion aborted
Please help me . How do I get past this error? I'd really love to have 4.4 on my phone
bump
You need to flash a KK compatible CWM first........
Sent from my Infected KitKat bar.....
First install 4.3 jelly bean, and then 4.4. This worked for me
Sent from my GT-I9100 using XDA Premium 4 mobile app
Except that you don't even need to install JB.......as I said in my original reply, the ONLY thing you have to flash is a KitKat compatible CWM......
To make things even easier, here's a copy of the CWM I flashed (via CWM) that enabled me to flash straight to KK..(CWM courtesy of @infected_)........
https://www.dropbox.com/s/rskqnncy8s0k05y/CWM-KitKatCompatible-i9100.zip
Sent from my Infected KitKat bar.....
I solve mine when I flashed CM10.2 nightly. Then do not restart your phone. Instead go to advanced options and restart recovery. Then you will see the latest CWM. Then flash CM11 and their GApps.
OP......flashing a temporary ROM is NOT necessary....it's just overcomplicating things......
ALL you have to do is......
1) download your chosen ROM and GApps....
2) download the CWM package I linked you to....
3) reboot into your EXISTING recovery....
4) flash the CWM that you downloaded at step 2....
5) reboot recovery...
6) flash your chosen ROM/GApps while following all wipe/install instructions......
JOB DONE.....SIMPLE AS.....
NO NEED TO FLASH A TEMPORARY ROM.......
Sent from my Infected KitKat bar.....
Stucked S2
keithross39 said:
OP......flashing a temporary ROM is NOT necessary....it's just overcomplicating things......
ALL you have to do is......
1) download your chosen ROM and GApps....
2) download the CWM package I linked you to....
3) reboot into your EXISTING recovery....
4) flash the CWM that you downloaded at step 2....
5) reboot recovery...
6) flash your chosen ROM/GApps while following all wipe/install instructions......
JOB DONE.....SIMPLE AS.....
NO NEED TO FLASH A TEMPORARY ROM.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
I ve just followed your list after root but my S2 stucked.
I will be happy for further info.
Thanks
OK.....this is the exact order that I did things coming from CM10.1....
1) downloaded ROM, gapps and KK compatible CWM to my REMOVABLE micro SD card.
2) rebooted the phone into existing CWM and flashed KK compatible version.
3) turned the phone off and removed micro SD card.
4) rebooted into new CWM, went to mounts and storage, and formatted EVERYTHING....
5) turned the phone off and re inserted micro SD card.
6) rebooted back into CWM and installed ROM and gapps.
7) wiped cache and dalvik and factory reset
8) rebooted the phone into Android....
Just remember that the first boot WILL take longer than normal.....
Good luck.....
Sent from my infected_ KitKat
Stucked
keithross39 said:
OK.....this is the exact order that I did things coming from CM10.1....
1) downloaded ROM, gapps and KK compatible CWM to my REMOVABLE micro SD card.
2) rebooted the phone into existing CWM and flashed KK compatible version.
3) turned the phone off and removed micro SD card.
4) rebooted into new CWM, went to mounts and storage, and formatted EVERYTHING....
5) turned the phone off and re inserted micro SD card.
6) rebooted back into CWM and installed ROM and gapps.
7) wiped cache and dalvik and factory reset
8) rebooted the phone into Android....
Just remember that the first boot WILL take longer than normal.....
Good luck.....
Sent from my infected_ KitKat
Click to expand...
Click to collapse
OK. let me explain my situation exactly right now.
I have "Samsung Galaxy S2 GT-I9100"
and it s original right now as software
I mean I didn't root it right now.
my question is "what should I do exactly from right now to CM-11"
Let me explain what I did before:
1) I ve rooted it with " Jeboo_kernel_i9100_v1-2a.tar " via Odin
2) I downloaded SuperSu then Titanium Backup Root
3) I copied to my SD card into phone
1# CWM-KitKatCompatible-i9100.tar
2# CM-10.1.3-i9100.zip
3# CM-11-20140308-SNAPSHOT-M4-i9100.zip
4# CM-11-20140310-NIGHTLY-i9100.zip
5# gapps-jb-.....zip
6# gapps-kk-....zip
4) I applied 2# then 5# (didn't occur any problem) and rebooted my phone
5) All is done!
6) Then I upgraded CWM with 1#
7) I applied 4# then 6# (didn't occur any problem) and rebooted my phone
8) Phone was stucked at the just start with "Samsung Galaxy S2" and there was a " ! " sign under it.

Categories

Resources