Hi all, this is my first time posting here, but I have been looking around for the past week at guides and How-to's.
Anyway to my point, my Nook Tablet is bricked and I can't find anyway to bring it back. As of right now, If I remove the SD card so It doesn't boot to CWM, or CM7 it just goes to the grey "N" logo screen with the "Adobe reader" text at the bottom, then immediately shuts off. If I plug in the USB it just goes to the same screen and keeps rebooting over and over. I fear I may of formatted something without really thinking about what I was doing (yes that was stupid of me) and to top that off, in my haste to root I forgot to make a backup (I know really stupid) I've tried many of the different guides and I can't figure out what to do now. So far these are the things I've done or have with my Nook Tablet [16GB]
-I have a CWM SD card
-I can boot from SD to CM7
-I've used ADB and used parted which showed my table, but no fix option. (I compared the table, it matched another user's table that was "fine"
-In ADB I managed to follow Lavero.burgos' guide and redo my partitions.
-I've tried various recovery roms, and I've also tried Adam's Ubuntu Recovery, but I get stuck at "writing zeroes to MLO"
-I also have the "E:\ can't mount" error's in CWM
-I've tried Ray Waldo's method in his video that involves the green check mark, but the NT will show a red X and will power off, powering it back on just leads to the grey "N" logo boot.
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
I've tried more things, I'm sure they'll come back to me the more I think about it. So what it seems is that I can't boot from internal anymore, that's just my guess. sorry for having this wall of text, I'm just trying to provide as much info as possible. I would just return it assuming that they wouldn't find rooted files or anything of the like since it won't even boot properly, but this Nook was brought into my store and traded in second hand. (Still have the box though)
Thanks for your time!
Hey, just some quick info. I bricked my nook the first week I got it. I users the sd restore method with the green check mark. It seemingly worked however when it booted it would go the screen with the yellow arrow. After getting frustrated from numerous boot loops, I left it plugged in overnight and the next day it was working fine. Anyways that method MAY be doing the same for you? Good luck and don't get too frustrated!
Sent from my SGH-T679 using xda app-developers app
Do you mean just leave it plugged into the wall charger or computer? Also do you mean you just left in plugged in so it would continuously go to the grey N logo screen?
Thanks for the reply by the way!
*edit*
On my original post, I clarified that Ray Waldo's green check mark method didn't produce a green check, just a red X
I left it plugged in charging overnight to the wall. But, I also got the green check mark before having done that. It would boot to the n screen then go to the yellow arrow screen immediately after. I don't have any other suggestions for you, sorry. I consider myself a noob when it comes to the nook. It seems like more of a pain in the ass than most other Android devices.
Sent from my SGH-T679 using xda app-developers app
can you list the "can't mount" errors?
ShinnAsuka said:
can you list the "can't mount" errors?
Click to expand...
Click to collapse
I believe he is referring to these errors (same as mine):
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
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
ShinnAsuka said:
can you list the "can't mount" errors?
Click to expand...
Click to collapse
Thanks for taking the time to post.
Anyway, the mount errors I get are the same as DanimalManimal.
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
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
Depardieu said:
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
Click to expand...
Click to collapse
I get this too. I'd be interested in knowing how to fix the issue.
Depardieu said:
Thanks for taking the time to post.
Anyway, the mount errors I get are the same as DanimalManimal.
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
**this first set of errors usually occurs when you accidentally format the usrdata partition which in stock partitions is the 1gb of user space on the 16gb nook. i had that happen and just followed the following thread to get it fixed: http://forum.xda-developers.com/showthread.php?t=1513583 **
and these as well:
Formatting /data....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache....
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext....
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/ .android_secure...
Data wipe complete.
Click to expand...
Click to collapse
this second set of mounting errors looks like your partitions are screwed up. but you say you fixed your partitions using lavero burgo's thread? is there any way you can confirm that your partitions are formatted the right way?
liquidzoo said:
I get this too. I'd be interested in knowing how to fix the issue.
Click to expand...
Click to collapse
the serial number with all zeroes is normal. its just adb not getting the correct information from the nook tablet. if you go into the rom folder and locate something that deals with a serial number and open it to view it, you will see that it isn't all zeroes...
not sure why adb gets serial information as all zeroes but w/e... as long as adb works thats all that matters.
Depardieu said:
Hi all, this is my first time posting here, but I have been looking around for the past week at guides and How-to's.
Anyway to my point, my Nook Tablet is bricked and I can't find anyway to bring it back. As of right now, If I remove the SD card so It doesn't boot to CWM, or CM7 it just goes to the grey "N" logo screen with the "Adobe reader" text at the bottom, then immediately shuts off. If I plug in the USB it just goes to the same screen and keeps rebooting over and over. I fear I may of formatted something without really thinking about what I was doing (yes that was stupid of me) and to top that off, in my haste to root I forgot to make a backup (I know really stupid) I've tried many of the different guides and I can't figure out what to do now. So far these are the things I've done or have with my Nook Tablet [16GB]
-I have a CWM SD card
-I can boot from SD to CM7
-I've used ADB and used parted which showed my table, but no fix option. (I compared the table, it matched another user's table that was "fine"
-In ADB I managed to follow Lavero.burgos' guide and redo my partitions.
-I've tried various recovery roms, and I've also tried Adam's Ubuntu Recovery, but I get stuck at "writing zeroes to MLO"
-I also have the "E:\ can't mount" error's in CWM
-I've tried Ray Waldo's method in his video that involves the green check mark, but the NT will show a red X and will power off, powering it back on just leads to the grey "N" logo boot.
-Also my device ID in ADB shows up as a string of zero's "000000000000000" I guess that's the cherry on top of this sundae. (Is the serial number the same as the one on the box and SD flap? If so I guess I still have the number)
I've tried more things, I'm sure they'll come back to me the more I think about it. So what it seems is that I can't boot from internal anymore, that's just my guess. sorry for having this wall of text, I'm just trying to provide as much info as possible. I would just return it assuming that they wouldn't find rooted files or anything of the like since it won't even boot properly, but this Nook was brought into my store and traded in second hand. (Still have the box though)
Thanks for your time!
Click to expand...
Click to collapse
Here is a link to a thread dedicated to your partition problems. http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
ShinnAsuka said:
this second set of mounting errors looks like your partitions are screwed up. but you say you fixed your partitions using lavero burgo's thread? is there any way you can confirm that your partitions are formatted the right way?
Click to expand...
Click to collapse
Well I guess all I can really confirm was when I fixed the partitions, and ran a parted command, my Partition Table came up, and It had no mention of errors or told me to "type Y to fix corrupted partitions". I cross checked the partition sizes and they looked very similar to this:
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.9GB 12.9GB ext4 userdata
Which is, from what I've read, correct or what it should look like.
Perhaps I overlooked something within the repartition process, but from what it seems if I did do the repartition correct, I'd be good to go and get my nook back to working order? If so then obviously I must of missed something which I suppose can narrow it down considerably.
Thanks for your time by the way, it means a lot to actually talk to someone about the issue after being a bit frustrated.
tobdaryl said:
Here is a link to a thread dedicated to your partition problems. http://forum.xda-developers.com/showthread.php?t=1513583
Good Luck!
Click to expand...
Click to collapse
Ok I want to say I'm really close to fixing this now, I'm currently in ubuntu, since that was the only way I could ADB, I have the repartition files, I'm pretty sure I have it all mounted properly, and I can see my device ID come up, when i type in
Code:
parted /dev/block/mmcblk0 print
Then it tells me
Code:
WARNING: You are not superuser. Watch out for permissions.
Error: Could not stat device /dev/block/mmcblk0 - No Such file or directory
Which immediately leads me to believe I must be missing something important, or perhaps I haven't mounted everything correctly? Should my nook tablet be in CWM if that really matters?
*Edit*
To clarify to my previous post about my Partition Table, when I run the parted command, the file size match up, and it doesn't give an error saying its corrupt, but under the File system column, there is none, its just blank if that matters.
liquidzoo said:
I get this too. I'd be interested in knowing how to fix the issue.
Click to expand...
Click to collapse
My device shows up in ADB with my serial number, however it gets stuck on "first need to make sure you didn't lie about it showing up, I also need to check for root incase you want to run any updates!" I was using Nook&Zergy for ADB.
Hopefull the fact that my serial number still shows up in ADB is a good thing? Any help?
Well, I figure I'd just go for broke with this, and I started this guide for Completely Dead Nook's and fixing the Partition Table. Everything worked great up to the part where you recreate your partition, when I input that command, I get a "Permission Denied" error. I went back to the start but this time enabled "su" and I still get a Permission Denied.
Essentially I think I could get this working, except I'm just stonewalled at this one part. (Although I guess I could dig in for the long haul and manually recreate using the parted way...right?)
*edit*
OK I finally believe I've made some headway. While I got the "Permission Denied" error, I figured I could just go a manually recreate all my partitions, which I went and did going off the guide. Now when I boot back into CWM I no longer have the string of E:Mount Errors !
I'll report back on progress, I assume I'm heading in the right direction if the errors are gone no?
*Update*
Well the errors are gone in CWM, but I still am stuck with a bootloop/constant restarting at the grey/silver "n" logo. I tried Ray Waldo's unbrick, which has the whole green check mark stuff, but I still get a red x. Perhaps I missed something, any clues?
Another update, Adam's Ubuntu Recovery is no longer stuck at "writing zeroes to MLO". This seems to be a very good sign
Another update, It's working! I used Ray Waldo's unbrick method, got the green check, but now I get an error when it registers the device, which I know is tied to partition 5 which i recreated, I thought I had made a proper backup, but I guess I made a backup of when it was already formatted, so is it possible to get my Serial Number, MAC address what-have-you back, if not what are the options I have?
Depardieu said:
Well, I figure I'd just go for broke with this, and I started this guide for Completely Dead Nook's and fixing the Partition Table. Everything worked great up to the part where you recreate your partition, when I input that command, I get a "Permission Denied" error. I went back to the start but this time enabled "su" and I still get a Permission Denied.
Essentially I think I could get this working, except I'm just stonewalled at this one part. (Although I guess I could dig in for the long haul and manually recreate using the parted way...right?)
*edit*
OK I finally believe I've made some headway. While I got the "Permission Denied" error, I figured I could just go a manually recreate all my partitions, which I went and did going off the guide. Now when I boot back into CWM I no longer have the string of E:Mount Errors !
I'll report back on progress, I assume I'm heading in the right direction if the errors are gone no?
*Update*
Well the errors are gone in CWM, but I still am stuck with a bootloop/constant restarting at the grey/silver "n" logo. I tried Ray Waldo's unbrick, which has the whole green check mark stuff, but I still get a red x. Perhaps I missed something, any clues?
Another update, Adam's Ubuntu Recovery is no longer stuck at "writing zeroes to MLO". This seems to be a very good sign
Another update, It's working! I used Ray Waldo's unbrick method, got the green check, but now I get an error when it registers the device, which I know is tied to partition 5 which i recreated, I thought I had made a proper backup, but I guess I made a backup of when it was already formatted, so is it possible to get my Serial Number, MAC address what-have-you back, if not what are the options I have?
Click to expand...
Click to collapse
well since you redid your partitions, most likely the rom partition is missing files. that partition has all that info: serial number mac address,etc...
you can get the serial number easily if you registered your nook with b&n. just go to their website and log in to your b&n account and under my nook you should see it.
if you didn't register your nook, then that might be a bit more difficult. there is a thread in the dev section i think on getting back your original serial number.
also you can bypass registration if you want to get your nook back in working order with a custom rom and the like. just do a quick search on youtube and there will be video about it by albertcwertz
ShinnAsuka said:
well since you redid your partitions, most likely the rom partition is missing files. that partition has all that info: serial number mac address,etc...
you can get the serial number easily if you registered your nook with b&n. just go to their website and log in to your b&n account and under my nook you should see it.
Click to expand...
Click to collapse
Alright, I can confirm I have the serial, I just don't know how to put it back into the device, so the registration page picks it up. Any advice?
Thanks for the reply by the way!
Depardieu said:
Alright, I can confirm I have the serial, I just don't know how to put it back into the device, so the registration page picks it up. Any advice?
Thanks for the reply by the way!
Click to expand...
Click to collapse
sorry i am drawing a blank there. i restored my nook tablet using adam's total wipe and i had the problem your having now. not being able to register. i decided to just screw it since i won't use b&n software anyways. i bypassed regsitration and rooted again and then installed custom rom and all is fine lol.
even now when i use adb to get serial info it comes up as all zeroes, but when i go into my rom partition and open the serial number file, my serial number is in there. so i don't really know why registration doesn't pick up the serial number.
maybe b&n has a specific location for the registration process to find out where to look for the serial number info.
all i know is that the rom partition contains information pertaining to the device itself (serial num, mac address, etc).
hopefully someone else will be able to answer your question in more detail.
Well, I think I can just say case closed for now, I guess I didn't want to use stock B&N (Why else would I be here in the first place) I have found a rom I'm starting to really like. Thanks for your help though it is greatly appreciated!
Alrigh Nook gurus, I desperately need your help...please note that I'm only a few degrees above a noob:
*
NT 8GB, formerly running CM7 Beta.
*
I've accidently formatted my emmc and it's causing all kinds of mounting issues, mostly when locating or mounting the cache. Whenever I try to install anything (e.g. backup, new ROM, stock recovery, stock repart) the error "can't mount /cache" comes up and prevents me from doing most everything. When I power the unit on the 'n' splash screen appears for about 3 seconds, then the cyanoboot universal loader comes up states "loading emmc recovery" and goes right into TWRP. Although it states "hold 'n' for menu" it will continue to boot TWRP. Therefore I do not have the option of accessing fastboot, and even if I did it would likely result in the usual "can't mount /cache" error that I get when trying to flash anything. Here's what I've tried and a summary of the result:
*
I've tried the "repart.img" stock recovery method. It will load the downward arrow and say "updating", then it states that it will reboot and reminds me to remove my sd card. It does not reboot automatically, and when I manually power on it goes right back into TWRP.
*
I've tried the Ubuntu boot method, but after I downloaded the 1GB file, unzipped it, added .img to the file, flashed to SD, inserted into NT, power on...then goes right back into TWRP.
*
Everything else involving flashing recoveries (cwm, twrp, stock) I've tried, always resulting in cache mount errors and no change boot up. I am able to boot CM7 Alpha Final via SD card, but only when I insert the card and power the NT up via PC-USB connection. Also, I can boot into CWM recovery via SD card when powering via PC-USB connection. When I power up normally (with the power button) its as though the tablet disregards what is in the SD slot and goes right into the emmc recovery. If anybody has any insight as to what might fix this, please let me know.
Sent from my VS920 4G using xda app-developers app
spacetwin4 said:
Alrigh Nook gurus, I desperately need your help...please note that I'm only a few degrees above a noob:
*
NT 8GB, formerly running CM7 Beta.
*
I've accidently formatted my emmc and it's causing all kinds of mounting issues, mostly when locating or mounting the cache. Whenever I try to install anything (e.g. backup, new ROM, stock recovery, stock repart) the error "can't mount /cache" comes up and prevents me from doing most everything. When I power the unit on the 'n' splash screen appears for about 3 seconds, then the cyanoboot universal loader comes up states "loading emmc recovery" and goes right into TWRP. Although it states "hold 'n' for menu" it will continue to boot TWRP. Therefore I do not have the option of accessing fastboot, and even if I did it would likely result in the usual "can't mount /cache" error that I get when trying to flash anything. Here's what I've tried and a summary of the result:
*
I've tried the "repart.img" stock recovery method. It will load the downward arrow and say "updating", then it states that it will reboot and reminds me to remove my sd card. It does not reboot automatically, and when I manually power on it goes right back into TWRP.
*
I've tried the Ubuntu boot method, but after I downloaded the 1GB file, unzipped it, added .img to the file, flashed to SD, inserted into NT, power on...then goes right back into TWRP.
*
Everything else involving flashing recoveries (cwm, twrp, stock) I've tried, always resulting in cache mount errors and no change boot up. I am able to boot CM7 Alpha Final via SD card, but only when I insert the card and power the NT up via PC-USB connection. Also, I can boot into CWM recovery via SD card when powering via PC-USB connection. When I power up normally (with the power button) its as though the tablet disregards what is in the SD slot and goes right into the emmc recovery. If anybody has any insight as to what might fix this, please let me know.
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
Your tablet is basically in recovery mode. So you most likely have your partitions screwed up. Look at the thread in the development section about repartitioning your internal memory
Sent from my Barnes & Noble Nook Tablet using xda premium
Related
Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
dav3wash said:
Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
Click to expand...
Click to collapse
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
MonkySlap said:
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
Click to expand...
Click to collapse
tried that, it didn't work either. It still takes me into recovery even though i put adb reboot download. I think I'm just going to have Asurion replace it again
Boot into Clockwork recovery and post the results of:
adb shell mount
silow said:
Boot into Clockwork recovery and post the results of:
adb shell mount
Click to expand...
Click to collapse
Once i go into clockwork, my computer no longer recognizes clockwork.
Idk if its the same thing, but here's what it says outside of clockwork
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
MonkySlap said:
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
Click to expand...
Click to collapse
Looks like this at least let me get into dl mode ... flashing stock now, we'll see what happens
Good to hear. I bet when you reformated in windows, it formated the internal sdcard as NTFS which Android cant read.
Just to put it out there if you press the menu button from recovery i believe its the same as DL mode .
got it!
First off, thanks for all the tips guys.
I had to flash Eugene's Froyo that doesnt brick with re-partition checked (no other rom would work) which brought me back, and then i downgraded from there.
Just in case anybody else gets that!
did it get rid of the mbr checksum error? I still have it but can flash whatever.
Just got a factory refurbished Nook Tablet 16GB from B&N and rooted it and installed CYM 7 and it seemed to be working. After doing so, I started having issues with the SD card readers. I originally had a 16GB class 6 Sandisk card in it, but also tried a class 4 4GB Sandisk and a class 10 Microcenter one and all have problems reading. What I'm trying to do now is restore it to stock and see if I can get some help from B&N. Right now, it will give me the N screen and then will show Cyanoboot(it won't let me hold down N to get any menu) and say loading recovery from EMMC and then it will only go into TWRP. I try to install various images from the different SD cards but all will fail. Error messages in the log show E:failed to mount /emmc and E:unable to mount messages. Any ideas on what else I can try?
Thanks,
Col
IJust in case it's not a hardware fault:
Try making a bootable CWM card, boot into it at start over again.
Or you could try the "repart.img" unbrick card.
Searches should bring you to either.
asawi said:
IJust in case it's not a hardware fault:
Try making a bootable CWM card, boot into it at start over again.
Or you could try the "repart.img" unbrick card.
Searches should bring you to either.
Click to expand...
Click to collapse
Tried the repart.img to a card. It appears like it works and then says it's going to reboot and never does. Rebooting then brings back the cyanoboot screen and TWRP.
I can boot from a CWM card, but I'm not sure what to select. When I try to factory reset, I get errors:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/cache
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2
Formatting /sdcard/.android_secure...
Data Wipe complete.
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
OK, if you can boot into a CWM card, do that and put something flashable at the same card so it's there when you boot into it.
I'm guessing your bootable CWM card is 5.x.x so you cannot flash CM10 with it. Try putting a CM7 on the card before booting into CWM. That way you have a working system.
TWRP did not play well with my NT and my SD card. CWM has never failed me though!
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
I guess I'm suggesting something along this post (even though I haven't followed that particular routine myself)
http://forum.xda-developers.com/showthread.php?t=2037368
FWIW, I did something like what's in post 25 of that topic to install my CM10.
OMG! My memoery is really bad! I totally forgot that I had trouble getting into cyanoboot when doing that! I see now my own post in that topic, just a few days ago... I used a CM10 sd-card just to get inti cyanoboot, and then I went on from there.
And by the way, what happens when you run the repart.img? What should happen is first it says "don't turn off you device" (or words to that effect),a dn after a not too long while a green checkmark appear. At that point, remove the card and it probably reboots itself, and goes into a new (smaller) "don't turn off..." and that part takes wuite a while.
I just load everything on EMMC and have a copy of the NT recovery flasher apk on hand in case I need to revert to stock.
Well, I tried to boot to a CM7 boot image on the SDcard and it starts to boot and gives me the CM7 screen, but then kicks back to the Nook N screen and boots back into TWRP.
I tried to the repart.img again and it boots, gives me the Please do not turn off, etc. screen, but with a red X in the corner. It then gives me the message that it's done and will reboot, but never turns back on. If I boot it again, it goes back into the TWRP boot.
Stupid question...is the EMMC the SD card or the internal memory? It seems like the errors I get are related to the emmc.
thanks for all the help.
More updates...I got it to boot from a CWM-based recovery SDcard v.5.5.0.4 and when I try to flash a zip file from the SD card, I get the errors:
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
Error mounting /emmc!
Ok, what's in this post makes my head spin, but it seems like it could fix the problem...
http://forum.xda-developers.com/showpost.php?p=23602314&postcount=10
Trying to get adb running and seeing the device, but no dice right now. Windows seems to recognize it and see storage, but ADB doesn't see it. Am going to keep fighting with that to see if I can do anything through there.
colavsman said:
Trying to get adb running and seeing the device, but no dice right now. Windows seems to recognize it and see storage, but ADB doesn't see it. Am going to keep fighting with that to see if I can do anything through there.
Click to expand...
Click to collapse
Check android_winusb.inf (Program Files -> Android -> Extra -> USB Driver) to see if you have an entry for the NT.
FInally got adb running on a different PC booting off a USB Ubuntu installation and followed the instructions in the post that Asawi recommended. After that, I used the repart.img file and restored it and it came back up. Now I have to figure out how to tell if the SD card reader is bad.
Thanks for all your help!
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.
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Are you sure that's the right CWM for CM 12.x? To flash 10.2 long ago I used CWM 6.0.2.x
Seems unlikely that an earlier version would be used for CM 12.x
That's a good point, your're on to something. I saw that in the cyanogenmod tutorial it says CWM doesn't support CM > 10.1.3. So your almost certainly right. (Why that's the active link in the beginner tutorial is still confusing to me.) I also see that CWM says it is not in active development for acclaim. So now on to twrp.
I tried the "Bootable SD card" instructions on the twrp acclaim page but can't get that to work. I've copied the img file to the root of the SD and renamed it to recovery.img but I don't know how to "boot TWRP using the cyanoboot menu from your sdcard". There is no cyanoboot menu on the sd card, it's only the img file, so no wonder nothing boots. How do I get the cyanoboot menu on the sd? My initial search led me to a page that has complex instructions on formatting the sd. Is that really the only way to get cyanoboot and ultimately get twrp to run??
Alternatively I've tried to burn the img to the sd using the dd command (thinking that an img file is meant to image an entire sd, not just live as a file on the sd). That gives me the errors that I posted originally (see section "Potentially related side note"). So I think you're right that I need a recovery other than CWM, but how do I get twrp to work?
Being a noob I feel like I'm missing something obvious but have been working for hours (ok, days) with no success.
Yeah, I think it *might* be that CWM is not going to cut it for CM 12.x, but the truth is I have no experience with TWRP so you're asking the wrong guy
I assume you looked at the "official" CM 12 thread here. For me the problem is what it is for you. There's not enough info there for someone who can follow good directions but is not already very familiar with all the ins and outs. What's needed is for digixmax to write a "how-to", but the last one he did was for CM 11. His directions are very clear. I was able to follow them as a noob for CM 10.2 without any trouble.
The hard way to do this is to sneak up on it by starting with CM 10.2, updating to CM 11 following digixmax's directions and then....well there must be a way to go from CM 11 to CM 12....maybe.....
I notice the sparse directions at CyanogenMod for CM 12 on Acclaim do refer to CWM so who knows?
coloradonate said:
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Click to expand...
Click to collapse
Your description sounds exactly like the SD card was not properly formatted with an MSDOS partition table with a primary partition as FAT32. From the CyanogenMod wiki: "Put the micro SD card (SD card from now on) in the computer. Backup all the information on the SD card. Everything on it will be deleted. Make a new MSDOS partition table and add a FAT32 partition as the first primary partition with a minimum of 300 MB. Then make sure you enable the boot and lba flags. This can be done in Ubuntu using GParted. Formats like EXT2, EXT3, and EXT4 do not work. It is not necessary to allocate the entire card. You can add other partitions to the card, but they need to be manually mounted on your Nook anyway." When you set up the partition table a the primary partition, the format must be written/saved to the SD card. Unmount the SD card and mount it again to ensure that the formatting took. Once that is verified then you can write to files to the SD card, unmout it again, and insert it into the Tablet and go through the install steps.
I'm looking at putting 12.1 on my Tablet, which currently has 10.2 and runs pretty well. But the basic setup instructions for the SD card are the same - MSDOS table with a FAT32 primary partition. You can add 3 more FAT32 partitions, but they must be primary and FAT32.
Thanks for the reply. Unfortunately I did partition just like it asked. It is set as Primary, Fat 32, and the boot and lba flags are on.
I'm still stuck, but I'm understanding a few things. The Cyanogenmod install wiki is obviously out of date (even though it says it was last modified Oct. 25, 2015 when I looked tonight). The wiki has you download CWM 5.0.x, which is a 2012 file intended to work with CM 10.x. Then later in the same wiki it says that CWM no longer supports CM>10.1.3, so obviously it is not up to date for CM 11.x and 12.x. Unfortunately the wiki was not updated to provide a link to a recovery that works...at least not that I've found. I've lost faith in that wiki.
I'm totally fine using Twrp, but I can't even get a version of twrp that works with the latest CWM 12.1 release. Should be simple, but for some reason can't get it to work. If anybody is still willing to try to help me, please point me in the right direction!
And here's a total noob question that may solve my problems: why does the cyanogenmod downloads page have a link for the .zip and a "recovery" .img? Is that img THE recovery that I should be using for that particular version of CM? I tried writing the image to the SD but have the same SD errors as I previously reported.
So...did you try following these directions? They are sketchier than I am comfortable with but it is the "official" thread. And there's certainly a recovery link there.
I'm thinking about upgrading from 10.21 but I just can't find directions that make me feel like I'm not going to trash what I already have
2 things to report: 1) I'll respond to the reply above. 2) got it working with CM 11!
1) Yes I have tried following that and read it more times than I can count, but my extreme noobiness has left me floundering in tutorial after tutorial. I tried fastboot, couldn't get it to install. Finally got it to install, couldn't get it to connect to the NT. I tried bootable SD, couldn't get it. Tried root, couldn't get that. Why couldn't I get any of that to work?? I have absolutely no idea, but I hit dead end after dead end and was left unbelievably frustrated by this whole thing. On to #2...
2) I got CM 11 to work! I don't care one bit that it's not 12.1, what's important is that I got CM finally running on my stock NT! I followed this tutorial (http://forum.xda-developers.com/showthread.php?t=2692403). It required one *very* slight modification that I posted at the very end of that thread (post #14.) Don't laugh at my excitement, I'm just happy this things is finally over. (For now at least...I'm sure I'll be digging further now that I've gotten this far.)
I'm really glad that worked for you I still remember how I felt when I got CM 10.21 working starting from stock on an ebay special.
You've given me a little push to get serious about upgrading to CM 11 or perhaps CM 12. I need to read (and reread) those posts until I feel like I've got it down. Your discovery will help, I'm sure.
Just to wrap up this thread, I got CM12.1 to work! Please refer to my last post (post #18) in the following thread for somewhat detailed instructions for how I did it: http://forum.xda-developers.com/showthread.php?t=2692403&page=2#post63932363
I hope that explains it all to anyone interested, or anyone else who was floundering around like I was. Now I'm happily running CM12.1 and loving it. Thanks to all the developers, especially Digixmax for the post that finally helped me through this!
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/.