Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
nemith said:
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
Click to expand...
Click to collapse
My Ubuntu image does not mount this partition.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yep-- this is all taken care of in cm9
Update: I don't think you mentioned, but for completeness, there's also the serial file in /rom at devconf/DeviceId that will trigger a rom reformat if it goes missing. there are also some edge conditions that will trigger recovery/flashing such as the presence of certain update.zip files on SD. Also SD boots are treated differently by default, don't increase the boot count, etc. In short, this is very similar to how NookColor works with the added disadvantage of having to deal with, rather than simply ignore or remove, these various "go to recovery' conditions.
I can verify that Bauwks script works and allows internal booting without a bootloop.
Nemith, if you find the time can you add something like this to your CWM recovery.img? I think just adding the /bootdata mount and dd calls to the init.rc file should work. I was going to build my own CWM .img but figured you already had the source code handy.
I'de like to dabble in a CM7 port soon, while CM9 and Ubuntu ports are in-work
Thanks for all your hard work guys!
CWM recovery bootloop
bauwks said:
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
I flashed cm9 alpha 0.2 on my nook tablet using the nook tablet recovery apk. It booted into cyanoboot, however it had an error message that said disc majic error. I noticed I had put the wrong boot image on my sd card from the alpha 0.1. I rebooted 8 times and booted into cwm. Now in cwm I flashed a backup of my tablet. I then made the common mistake of clicking reboot recovery. Then trying to fix the bootloop into cwm recovery while unaware of the sevarity of what I was doing I went into mounts and storage and formated each bootdata, cache, data, emmc, rom, and system. I just restored my backup again and now I know what I need to do. My stock Nook recovery was overwriten when I clicked reboot recovery. Also I formated my rom folder and that might have contained my serial number and info.
I basicaly deleted my partions. while stuck in the cwm boot loop. Can you please send me or send me the link to a step by step way that I can get my nook tablet 16gb stuck in the cwm boot loop back to normal.
I tried using fastboot but I dont know the commands to open it. Also I dont know how to use adb either. I have a 2gig, and a 256 mb micro sd. I have a windows pc. Can you show me step by step how to restore those partions, how to do it on adb or fastboot, or the update zip method. I need help as soon as possible. Thanks.
Its similar to this
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
An image of /factory would be nice as well But less important as we're all (likely) using CM.
edit
Actually disregard this.. I have the nook hd+, but the /bootdata format info will probably be handy for any nook device.
Don't format bootdata or factory!
roustabout said:
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Click to expand...
Click to collapse
pbassjunk said:
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
Click to expand...
Click to collapse
To fix the Recovery Boot Loop caused by invalid/missing BCB and BootCnt in /bootdata, flash Succulent's flashable_fix_bootloop.zip posted at his blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (see under heading "I am stuck in a recovery boot loop?").
An image of /factory would be nice as well But less important as we're all (likely) using CM.
Click to expand...
Click to collapse
/factory contains a backup copy of stock ROM as well as a backup copy of the device data in /rom partition (romdata.zip), the latter includes data that is unique to each Nook (such as MAC address, security certificate, etc.) and hence is not replaceable with a copy from another Nook.
...
Don't format bootdata or factory!
Click to expand...
Click to collapse
Nor /romdata. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info.
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
weasel5i2 said:
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
Click to expand...
Click to collapse
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
tinkering said:
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
Click to expand...
Click to collapse
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
digixmax said:
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
Click to expand...
Click to collapse
Thanks for the link to leapinlar's post. That helps me to understand the problem and fix a bit better. I didn't see the zip that seemed to fit my situation on his post. I did a SD install non-rooted and I see only only emmc fixes on his post. I tried your fix with these steps and I must have done something wrong. Maybe you could point me in the right direction.
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
tinkering said:
...
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
Click to expand...
Click to collapse
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
digixmax said:
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
Click to expand...
Click to collapse
Sorry, I probably should have updated my last post. I was attempting to flash the repair incorrectly. Unfortunately, I have a new problem and have moved my question to the "[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc" thread.
The device would boot from SD. Was running CM10.2 and CWM recovery. The trouble I am having now is that I can't flash anything from the SD in CWM recovery because it wont mount the SD. (See details in thread referenced above.)
Thanks
Related
Hi all, I built my sdcard per: http://iamafanof.wordpress.com/2012/...r-nook-tablet/ (built by"Succulent")
My kids have two NT's. With two 16GB Sdcards, one class4 the other class 10. I know class4 is recommended, but one poster in forums said he's taken images of CM built on class4's and applied this image to class 10's in several cases and has had no problems. So I thought what the heck, can't hurt to try, so that's what I did (using Winimage). It booted fine 5 or 6 times for me, and I installed several APK's of games from Humble Bundle . I turned over the Nook to my little girl and she brought it back to me later showing she gets errors on boot, after swiping the lock symbol to unlock it. One is "Unfortunately, Talk has stopped". If you click OK on this, you get ""Unfortunately, Trebuchet has stopped". Clicking OK on this does nothing, it keeps popping up indefinitely. I don't know if the sdcard is hot pluggable (can be removed with power to the tablet), but she did admit to doing this. So I'm wondering if some corruption occurred to the CM build on the sdcard. Has anyone seen these errors? I could reflash it from the image I made off the class 4, but want to understand what happened so we don't run into it again. The funny thing is, I don't recall the startup wizard off the 1st class4 card prompting me with several screens regarding Google crap like it did on the 2nd card which was flashed from the same image. That was even after telling it I had no Google acct hoping it would leave me alone.
can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
baytee said:
...
So my question is, can anyone explain the boot menu you get when you press the N button? (I'm not including the faded selections) I'm wondering especially about the recovery options. Here's my menu:
INT BOOT ( I assume will boot to B&N native OS?)
INT RECOVERY ?
SDC RECOVERY ?
SDC BOOT (Iassume, boot to CM10 off sdcard?)
SDC ALTBOOT ?
START FASTBOOT ?
Click to expand...
Click to collapse
Yes,
internal boot - boots Rom in emmc
Internal recovery - recovery in emmc
Sdcard boot - boots your sdcard Rom.
Sdcard recovery - boots sd card recovery ( keep recovery.img in root of sdcard for it to load recovery)
Sdcard altboot - alternate recovery ( not necessary, unless you want both cwm and twrp at same time)
Fastboot - fastboot mode , fastboot commands to flash .img file etc with this method .
As for your problem, try entering recovery, wipe cache and dalvik cache partition (I've done this on emmc version, never tried sdcard version of any Rom) this may solve the issue. If not try factory reset.
And removing sdcard while device is switched on is called hot swapping , hot plug is a CPU governor. Not sure if sdcard roms are hot swappable, but I think not.
Sent from my ST27i
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? Once you get into it, you have various choices like the ones you mention? (I'd read that this choice was to backup your NT to sdcard). And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
baytee said:
Thanks.
emmc=internal nook memory I assume?
Oh, and...just to clarify, I haven't modified (rooted) my tablet. (you mention factory reset). I should mention that with the sdcard out, it boots B&N OS just fine.
And the part you say about wiping the two caches, so I should go into SD Card Recovery to do that? I'd read that this choice was to backup your NT to sdcard. But once you get into it, you have various choices like the ones you mention? And please, I want to be very, very careful not to wipe out the B&N stock OS, so please, any detailed instructions you can give so I don't make that mistake, I'd greatly appreciate it. (I see so many posts on these forums about people bricking their Nook tablets it worries me.)
Click to expand...
Click to collapse
Um I don't know much about how it works for sdcard Rom. I've always only used emmc version. I guess if you were to enter recovery, it would access the stock cache partition by default , and we aren't trying to clear that.
Try this - use titanium backup (only talking about your sdcard Rom here, nothing to do with your stock) and in options, you may be able to wipe your cache or dalvik cache.
Or,
boot into your sdcard Rom, in settings > backup and restore > factory reset. This will delete all user data and return Rom to original Cm10 that you flashed on sdcard.
Or if it's only google talk and trebuchet launcher issue, install a new launcher (go launcher, adw etc) , then use titanium backup to uninstall trebuchet and talk.
Sent from my ST27i
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
baytee said:
From what I see, titanium backup is an android app. If I can't boot to Android (Trebuchet error loops as I said) I don't know how I can install this to do anything? Nor can I install another launcher or go into Settings as the error doesn't let you get any further.
I guess if there was a way to browse files/folders on the sdcard partitions on the sd to manually delete the cache files.....but if they're linux partitions (ext3 or4) you can't do that under windows...
Click to expand...
Click to collapse
In cwm, enter mounts and backup, then (if) you see /sdcard /cache, mount that and format that ONLY.
Do not format anything else as some options can brick device (Rom, bootdata, factory etc)
Wiping cache is safe (99%)
Again, I have never used sdcard Rom so I don't know what will show up in your recovery. But if you see something like sdcard cache, it can be cleared. If it doesn't specify sdcard, let us assume it refers to stock emmc.
Sent from my ST27i
How do I get into CWM?
baytee said:
How do I get into CWM?
Click to expand...
Click to collapse
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
digixmax said:
Select SDC Recovery on the Cyanoboot boot menu -- see steps 7 & 8 of the post at http://forum.xda-developers.com/showthread.php?t=2061536.
If you want to backup the BN stock ROM just in case, see step 9.
Click to expand...
Click to collapse
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
baytee said:
I chose sd recovery, chose Backup & Restore, then Backup. It started running right away. It said:
SD Card space free: 228MB
Backing up boot image
Backup of boot image completed
Backing up recovery image
Backup of recovery image completed
Backing up system
Error while making a backup image of /system!
I plug sdcard into PC card reader and the FAT partition has 0 bytes free. So, appears it ran out of space. I saw your comment about 600MB space being needed. So I'm redoing the partitions now.
Click to expand...
Click to collapse
Why backing up now when it's not working? Fix your issue, then make a backup. So the next time there's a problem you can restore to working condition.
Sent from my ST27i
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
I ran into lost chains - convert to cluster msgs trying to delete the folder of the first failed backup, but it never would delete even after a chkdsk, so I formatted the card and put the original image back onto it, adjusted the partitions, and then ran into a new probem.....the Cyanomod spinning logo never stopping spinning so it won't boot up. So I give up. I don't know if it's that it's a class 10 card that all these problems are happening. barring any other suggestions, I guess I'll make sure the other NT we have runs stable for a few weeks and if so I'll order another class 4 like that one has.
Click to expand...
Click to collapse
I don't know about your bootloop issue, but I don't think it's a sdcard class issue.
Anyhow, now that you have stock backup, aren't you going to consider flashing cm10 internally? Do you actually use stock?
Sent from my ST27i
I'm a little leery of it, at least while it's under warranty. I don't know how reliable recovery is.? Besides, my daughter wasn't thrilled with it being down for several days with me fussing with it and asked if she could have her "B&N boot" back I admit It is a bit of a pain having to pull it out of it's case, lift the flap, pop-in or out the sdcard to switch between them. (& also to have to remember to always turn it off b4 removing/inserting)
I may do it in the future though. Thanks for the help
FWIW, you don't have to actually remove the card to boot into stock. Just reboot, hold "n" to get into Cyaonoboot menu and choos "int boot" or something like that, and it will boot to stock with the sd-card still inserted.
Great, thanks for that tip!
Card died
I think many of these symptoms could have been caused by a dying card. It did have a corruption error once, and then it finally completely died. Just for anyone else that runs into these.
baytee said:
Well, backing up, I think, was a good suggestion by Digimax. So I'm glad I did it. and now i know how to do it for future. Just in case anything EVER goes wrong, I'll always have that image now on my pc. Bad thing was, apparently B&N nook OS apparently keeps lots of APKs around after installing them. I had to make my 1st fat32 partition over 2GB for the entire backup to process without running out of space. backup size=1.6gb
...
Click to expand...
Click to collapse
FWIW, /cache does not need to be backed up, which should help reduce the backup space requirement.
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
datallboy said:
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
Click to expand...
Click to collapse
I tried that didn't work, thanks.
Sent from my SGH-T999 using Tapatalk 2
Wiping ROM seems to have the effect of triggering a recovery every boot, which if you had the stock recovery should recover all the device info stored there. I had to use a repart.img sdcard which loaded stock 1.4.2 or 1.4.3 (Search for files and guides). Then I used a CWM sdcard and put custom recovery and ROM back on.
Sent from my Barnes & Noble Nook Tablet using xda premium
digixmax said:
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
This did not work either. thanks
somerandomname said:
This did not work either. thanks
Click to expand...
Click to collapse
The next likely cause of your problem is missing factory-installed device data (e.g., WiFi MAC address, security encryption keys, etc.) that are stored in /rom and /factory partitions which you stated in the OP you had wiped. Unfortunately I am not aware of any way to recover this original set of individual device specific data.
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
dejello said:
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
Click to expand...
Click to collapse
Yeah I was able to use the thread by Adam to redo my tablet with the normal files for Rom through a SD card boot since the touch was not working.
Thank you, this was a great learning experience in my 5 years of playing around first time to cause a brick...
Sent from my SGH-T999 using Tapatalk 2
I'm glad you got it figured out this droid charge i'm on right now used to brick every time i flashed, then started working right one time I've just learned to take it easy and see about fixing things
Sent from my SCH-I510 using xda app-developers app
CWM Bootloop...
Hello all!
It seems I've gotten myself into a bit of trouble with my Nook Tablet. I had been running CM7 for quite some time and finally upgraded to CM10. Very nice! However I landed myself in a CWM boot loop after about a week and have not been able to recover.
First, I attempted to recover back to BN Stock, not knowing that it would not replace CWM with stock recovery. I still have CWM and half of a stock installation (repart.img from bn_142_factory_recovery.zip). From what I understand, the stock BN software is trying to boot to recovery to complete the install, although it was in bootloop before that attempt was made.
Since then, I have tried flashable_fix_bootloop.zip as well as cwm_6.0.2.9_acclaim_recovery_sdcard.img to no avail. I fear that I may have made the mistake of formatting too many things as mentioned at the top of this thread to get into myself here in the first place. What is my next step?
Much appreciated!
-byrd
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
asawi said:
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
Click to expand...
Click to collapse
Thank you for your reply, asawi!
I've begun the download. From what I understand, this will give me a bootable MicroSD into CM10. If that is correct and it boots as it should, I can then install this image as firmware in some fashion or at least be able to repair the damage done so that I can reinstall CM10?
[Warranty is of no concern. I bought this Nook Tablet in used condition quite some time ago with intent to use CM as primary OS, hence the use of CM7 for well over a year.]
-byrd
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
asawi said:
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
Click to expand...
Click to collapse
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
byrdeth said:
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
Click to expand...
Click to collapse
If /boot was successfully restored, that's what matters the most (please, tell me you did NOT erase /rom, because if you did, you're in a really bad situation). You don't need to restore asawi's FULL backup. If the /boot partition is functioning normally now, you should be able to boot into your internally flashed CWM, wipe data/factory reset, wipe dalvik cache, and wipe system, then FLASH the ROM and gapps. You should not be experiencing the bootloops anymore (make sure to take out the SD card BEFORE rebooting to internal CWM).
I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as the case with CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this installation process will not be valid for those future builds with merged /data+media partition].
The following is the process using SD-based recovery to install CM11 internally (i.e., on emmc) on a Nook Tablet running stock ROM. [If your NT is already running CM10.x, see http://forum.xda-developers.com/showthread.php?t=2670589 for a simpler process to update from CM10 to CM11]. This same process can also be used to install CM12.x -- see http://forum.xda-developers.com/showpost.php?p=64624390&postcount=21 for needed corresponding versions of CM12 ROM, Android 6.0 GApps, and EMMC-based CWM recovery.
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
Obtain and copy to the SD card the following files:
first MLO, then next u-boot.bin and flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
TWRP (TeamWin Recovery Project) version 2.6.3.0 or later, e.g., openrecovery-twrp-2.6.3.1-acclaim-sdcard.img from http://techerrata.com/browse/twrp2/acclaim, rename it to recovery.img before copying to SD card.
the flashable_CWM_6.0.4.5_chrmhoffmann.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds).
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select SDC Recovery.
[Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
Select Wipe data & factory reset.
Select install zip from SD card and install flashable CWM recovery zip file.
Select install zip from SD card and install CM11 zip file.
Select install zip from SD card and install Gapps zip file.
Remove SD card and select reboot.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service on your NT your apps will be auto-downloaded (but their settings will not be auto-restored).
Notes
If the Nook fails to boot off SD -- the two most common symptoms of failed SD boot and their likely causes are:
The NT boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
The NT screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. When in doubt, compare the size of the two copies of the files in bytes.
Installing CM11 ROM and Gapps will override your NT's current boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to previous ROM if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
Also, I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
bad boot image
I have followed your instructions carefully. But got an error message after selecting SDC recovery option from the boot menu..
booti: bad boot image magic (in memory).
I have tried to seat the card several times, no difference. This is a SanDisk 16GB class 10 card. I have installed CM11 on it, and worked. So the card can work. Now I want to install CM11 internally.
Don't know what else to try at this point. Please help. Thanks!
---------- Post added at 10:55 PM ---------- Previous post was at 10:28 PM ----------
gammaworks said:
I have followed your instructions carefully. But got an error message after selecting SDC recovery option from the boot menu..
booti: bad boot image magic (in memory).
Click to expand...
Click to collapse
Never mind, I have picked the wrong recovery.img. Ooops.
did not work for me
Installing it internally for the first time. Did not work...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-... SNAPSHOT-M4-acclaim.zip'
Error flashing zip '/sdcard/cm-11...SNAPSHOT-m4-acclaim.zip'
It appears I have bricked my nook tablet.
gammaworks said:
Installing it internally for the first time. Did not work...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-... SNAPSHOT-M4-acclaim.zip'
Error flashing zip '/sdcard/cm-11...SNAPSHOT-m4-acclaim.zip'
...
Click to expand...
Click to collapse
Which version of SD based recovery did you use?
Also, you might want to consider to first flash CM10.x (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163) then later update to CM11.
come back from the dead
digixmax said:
Which version of SD based recovery did you use?
Also, you might want to consider to first flash CM10.x (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163) then later update to CM11.
Click to expand...
Click to collapse
Thanks. An youtube video helped me out in the end: watch?v=3YYXtGAt6GY
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc, I rebooted NT without a SD card. The TWRP boot menu came up. I put the SD card back in. The SD card has CM11 and Gapps zip files. I then selected internal EMMC recovery (that is the key I think):
factory reset
install cm-11-20140405-SNAPSHOT-M5-acclaim.zip
install pa_gapps-modular-mini-4.4.2-20140321a-signed.zip
Now I have Android 4.4.2 running on my NT.
gammaworks said:
...
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc
...
Click to expand...
Click to collapse
The TWRP openrecovery-twrp-2.7.0.0-acclaim-sdcard.img is for SD card, the corresponding version for emmc openrecovery-twrp-2.7.0.0-acclaim.img.
gammaworks said:
Thanks. An youtube video helped me out in the end: watch?v=3YYXtGAt6GY
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc, I rebooted NT without a SD card. The TWRP boot menu came up. I put the SD card back in. The SD card has CM11 and Gapps zip files. I then selected internal EMMC recovery (that is the key I think):
factory reset
install cm-11-20140405-SNAPSHOT-M5-acclaim.zip
install pa_gapps-modular-mini-4.4.2-20140321a-signed.zip
Now I have Android 4.4.2 running on my NT.
Click to expand...
Click to collapse
I did the same as you and get stuck at the CM boot screen. Tried 2x reflashing and keep getting stuck at the CM boot screen with the spinning arrow.
nm, 3rd time was the charm for some reason . Going through setup now, thanks!
bobzdar said:
I did the same as you and get stuck at the CM boot screen. Tried 2x reflashing and keep getting stuck at the CM boot screen with the spinning arrow.
nm, 3rd time was the charm for some reason . Going through setup now, thanks!
Click to expand...
Click to collapse
How long did you wait for the first-time boot to complete?
FWIW successful first-time boot typically takes 3 to 4 min.
digixmax said:
How long did you wait for the first-time boot to complete?
FWIW successful first-time boot typically takes 3 to 4 min.
Click to expand...
Click to collapse
I waited around 15 minutes the first two times. I could tell it was doing something different the 3rd time as the swirling arrow would stop briefly as it presumably loaded things while the first two times it just swirled non-stop.
Great procedures
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as the case with CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this installation process will not be valid for those future builds with merged /data+media partition].
The following is the process using SD-based recovery to install CM11 internally (i.e., on emmc) on a Nook Tablet running stock ROM. [If your NT is already running CM10.x, see http://forum.xda-developers.com/showthread.php?t=2670589 for a simpler process to update from CM10 to CM11].
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
Obtain and copy to the SD card the following files:
first MLO, then next u-boot.bin and flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
TWRP (TeamWin Recovery Project) version 2.6.3.0 or later, e.g., openrecovery-twrp-2.6.3.1-acclaim-sdcard.img from http://techerrata.com/browse/twrp2/acclaim, rename it to recovery.img before copying to SD card.
the flashable_CWM_6.0.4.5_chrmhoffmann.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds).
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select SDC Recovery.
[Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
Select Wipe data & factory reset.
Select install zip from SD card and install flashable CWM recovery zip file.
Select install zip from SD card and install CM11 zip file.
Select install zip from SD card and install Gapps zip file.
Remove SD card and select reboot.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service on your NT your apps will be auto-downloaded (but their settings will not be auto-restored).
Notes
If the Nook fails to boot off SD -- the two most common symptoms of failed SD boot and their likely causes are:
The NT boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
The NT screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. When in doubt, compare the size of the two copies of the files in bytes.
Installing CM11 ROM and Gapps will override your NT's current boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to previous ROM if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
Also, I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Your procedures worked out great. I've managed to take a stock Nook Table and have it running KitKat 4.4.4 in 3 day. The 1st 2 days I had only managed to root it and play around a bit. Thanks to every ones great work I'm up and running. 1st boot was a bit interesting as I renamed openrecovery-twrp-2.6.3.1-acclaim-sdcard.img to recovery.img.img but after review the SD Card / rebuilding there were no more issues. it it booted and worked great. Thanks again ===
I ran into a problem and am hoping for a hand. My NT boots perfectly form the SD card and loads up the recovery screen while following the instructions, I made a backup, but when I go to do the data wipe and factory reset or start to install the CWM file I get an error of "E: Unable to mount '/BootData' ".
I have tried starting over by resetting up the Nook and registering it again, but same thing. If I pull out the SD card it boots right up into use as a standard NT ready to register and go.
I am going to try again starting over and with a different version of TWRP just in case that is the issue.
Thanks for the help!
Allkair said:
I ran into a problem and am hoping for a hand. My NT boots perfectly form the SD card and loads up the recovery screen while following the instructions, I made a backup, but when I go to do the data wipe and factory reset or start to install the CWM file I get an error of "E: Unable to mount '/BootData' ".
I have tried starting over by resetting up the Nook and registering it again, but same thing. If I pull out the SD card it boots right up into use as a standard NT ready to register and go.
I am going to try again starting over and with a different version of TWRP just in case that is the issue.
...
Click to expand...
Click to collapse
Did you try TWRP v2.6.3.0 (openrecovery-twrp-2.6.3.0-acclaim-sdcard.img at http://techerrata.com/browse/twrp2/acclaim)?
Working
Thanks for the help. Along the way I did get it working on the night of 11/10, I just forgot to post that . 9th try is the charm I guess? In any case I tried first with TWRP 2.8.1.0 and then went back to 2.6.3.1 and then on my last attempt tried again with 2.8.1.0 and it worked so I have a NT running the last monthly of 11 and so far no issues. The sad news is that I have no idea what I did different to make it work the final time vs the first couple of try's.
YES YES YES!! It works! I've been struggling for more weeks than I care to admit to install CM 12. I've followed nearly every tutorial I can find and pursued WAY too many paths (bootable SD, fastboot, root) and couldn't get anything to work. Probably my very minimal knowledge of this subject is the culprit, but I've done a ton of research. Finally I decided to give CM 11 a shot and found this post. What a life saver!! Thank you everyone for your contributions to make this possible even for laymen like me!
FWIW, I couldn't get it to work with the "flashable_TWRP_2.6.3.1.zip" included in the mediafire folder provided by digixmax. I deleted that from the SD, downloaded 2.6.3.1 from the TWRP website (note: SD version) and it worked! I also tried the non-SD version of TWRP 2.6.3.1 and it didn't work...required the SD version to work. You guys rock!
coloradonate said:
...
FWIW, I couldn't get it to work with the "flashable_TWRP_2.6.3.1.zip" included in the mediafire folder provided by digixmax. I deleted that from the SD, downloaded 2.6.3.1 from the TWRP website (note: SD version) and it worked! I also tried the non-SD version of TWRP 2.6.3.1 and it didn't work...required the SD version to work. You guys rock!
Click to expand...
Click to collapse
You need to use the SD version of CWM or TWRP to flash CM from SD.
flashable_TWRP_2.6.3.1.zip is a flashable zip to flash and install TWRP itself into EMMC.
So if I download the most recent TWRP and CM 12.1 zip, could I simply replace the 2 older TWRP and CM 11 files on my SD? Would that actually work to get 12.1? It seems like the other files are only related to the bootloader and should be universal to work with any recovery and CM zip. Somehow I doubt it's that easy..
coloradonate said:
So if I download the most recent TWRP and CM 12.1 zip, could I simply replace the 2 older TWRP and CM 11 files on my SD? Would that actually work to get 12.1? It seems like the other files are only related to the bootloader and should be universal to work with any recovery and CM zip. Somehow I doubt it's that easy..
Click to expand...
Click to collapse
The function of the 2 files MLO and u-boot.bin is to boot the NT and load CyanoBoot (the 3rd file flashing_boot.img) which in turns would enable you to select and load the recovery.img file on the SD card; hence they should be invariant of the CM version you want to flash.
All you need is a copy of SD-based (TWRP) recovery.img version that is compatible with CM12.x and the GApps package.
Wow, it worked with 12.1! I have stumbled upon THE thread that finally helped me get this to work. Countless dead ends and I finally found it.
I took the plunge and tried installing cm12.1. Per post #1 in this thread, I used the same flashing_boot.img, MLO, and u-boot.bin that's in digixmax's mediafire folder. Also used the same flashable_CWM_6.0.4.8_chrmhoffmann.zip per post #1.
The files that are different from post #1 in this thread are: the most recent CM12.1 release (as of tonight: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip), the most recent TWRP for SD (as of tonight: twrp-2.8.6.0-acclaim-sdcard.img; renamed to recovery.img before copying to SD as suggested) and a compatible gapps version. A little google searching led me to the pico gapps from TKruzze that I got from post #1 of this link (http://forum.xda-developers.com/android/software/tk-gapps-t3116347). I downloaded this from the BasketBuild link under "Proper DPI Play Services" of the Pico Modular Package in post #1 of that link I just mentioned. I followed the same directions that were in post #1 of this thread that originally gave me success with CM11, and sure enough it all worked great with CM12.1. I'm now running CM12.1 and couldn't be happier.
A HUGE THANK YOU to digixmax and everyone else who contributed to the creation of these seemingly universal files (e.g., flashing_boot.img, MLO, u-boot.bin, etc.) to enable this to work. And of course a THANK YOU to the CWM, TWRP and CM developers. Seriously, you guys rock.
can someone check if my files are correct? especially the first 3 since I cant boot from SD no matter how many time I reformat, redownload, recopy....
ddvche said:
can someone check if my files are correct? especially the first 3 since I cant boot from SD no matter how many time I reformat, redownload, recopy....
Click to expand...
Click to collapse
Did you boot from power-off by inserting a powered USB cable?
Also, make sure that MLO is the very first file you copy to the freshly reformatted, empty SD card.
Hi
I'll try to make it brief. Some time ago, my stock Nook slowed down like a mule so I decided to root it, then applied Trimmer to enable trim. Beforehand I'd checked the eMMc with a Brickbug app and it popped up with "sane chip", as I'd read some Nooks had a faulty Samsung eMMc.
It went into a bootloop, and only started showing shredded Nook letters on an abstract background during boot. Then I tried various bootable SD cards to try to flash various stuff, as per available XDA threads, especially - leapinlar's, verygreen's and amaces'. First it would not complete the flashing of a ROM, just froze towards the end, then eventually wouldn't boot up at all.
Here's the weird part. Without an SD card, it doesn't boot up at all.
When I make a bootable SD, it only boots to TWRP 2.6.0.0 (some other versions [amaces] it won't boot to), but doesn't see any zips on the card and won't let me flash anything, even though it previously did, but wouldn't complete the flash.
Whatever else I burn on the card, it either doesn't boot up at all, or boots to whatever it is you can see on the attached printscreens, and won't mount anything. So if I'm guessing right, the eMMc is not borked, as it seems the device boots to some remnants of something that's there, and not on the SD.
Is there a way of fixing that mess? I'd appreciate any ideas.
Best
W.
You can try to flash this flashable_fix_bootdata-ovation.zip which typically should cure corrupted or missing bootdata issues.
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it won't see the zips on it. So how can I flash the fix bootdata zip?
wojtasys said:
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it w on't see the zips on it. So how can I flash the fix bootdata zip?
Click to expand...
Click to collapse
Have you tried the verygreen's old SD-based CWM recovery?
If you mean the one from that thread:
https://forum.xda-developers.com/showthread.php?t=2600572
I have. The download links for the initial card image don't work. I looked elsewhere - nowhere to be found.
Sorry about the trouble, guys, forgot to update the dns when the server moved. I just updated it, but it'll take some time to propagate. The actual new ip address is now 178.34.187.142 - you can place it into your hosts file if you don't want to wait.
Nook HD+ Bootloop error
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
wojtasys said:
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
Click to expand...
Click to collapse
Assuming that your flashing of stock recovery was successful (recovery's reports of successful completion can sometimes be erroneous) and also your factory backup partition is still intact, you can try to initiate a factory reset by using the "8 failed boots" method: with the Nook in the power-off state, power it on, then as soon as the boot screen appears hold down the power button until it powers off, do this 8 times, and the Nook should go into stock recovery to revert to factory-fresh state.
Flashing your flashable_restore_stock-recovery-ovation zip ends with the screen I'm attaching.
Then I tried "8 failed boots" but it only boots to CWM SD, without the card - it doesn't power up at all.
Eventually, nothing changes.
Tried putting the stock ROM on the card and flashing that, but the partition size is too small, even though its a 16GB card.
wojtasys said:
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
Click to expand...
Click to collapse
If the issue is about the two files, you could mount /bootdata and copy them manually (ADB shell should be functional with any of these recoveries). You'd extract BCB and BootCnt from ZIP, and copy them onto SD card, then do something like:
Code:
mkdir -p /bootdata
mount -t vfat /dev/block/mmcblk0p6 /bootdata
cd /external_sd or /sdcard or /emmc (wherever SD card root is mounted)
cp BCB BootCnt /bootdata/
Or, you could edit the updater-script inside ZIP to remove the device assert line like in the attachment here. By the way, are the updated images here also failing?
Flashing your flashable_fix_bootdata-ovation-no-assert.zip shows "install from sd card complete" but the device still won't power up without the card.
Trying to mount bootdata results in "error mounting bootdata".
There's no adb command line in that sd recovery, just adb sideload. TWRP 2.6 had it but it didn't access the files on the sd.
Then, I'm not sure I'll know how to edit the updater-script inside ZIP to remove the device assert line.
Chances are your EMMC is hosed, in which case you can try running CM entirely off SD card using the succulent special build available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.