Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
N0he said:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
Click to expand...
Click to collapse
+1 on this, I am seeing the exact same behavior. After running a while there seems to start cascading failures of apps. Browser stopped, google play most common, MTP host stops...
TWRP hangs on the splash screen , Ive tried all (3) 3.0.2. variants.... I am running the NDE63P 7.1 build...
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
N0he said:
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?).
Click to expand...
Click to collapse
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
N0he said:
Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Click to expand...
Click to collapse
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
mikeataol said:
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
Click to expand...
Click to collapse
Yes, all these recoveries clear the boot count, but only after they finish booting. When TWRP doesn't finish a full boot, the system is still marked for recovery.
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
amaces said:
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
The rom boots and runs normally from emmc, no signs anywhere that there is corruption, except subtle hints... (change settings on an app, clear data and cache on an app, and on the successful reboot into the rom those changes don't seem to have stuck.
mikeataol said:
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
Click to expand...
Click to collapse
Right, CWM is one of the recoveries on the SD card. No recovery that supports F2FS and wants to access /data will work at this point; it just happens that CWM can skip that step.
@amaces and as you suggested, booting cwm from the card
reformatting userdata (make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata )
allowed TWRP to work again just ducky.....
Thank you for taking your time to help me!
amaces said:
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
amaces said:
Sounds like your userdata partitions got corrupted; F2FS?
Click to expand...
Click to collapse
I did not know what F2FS is, but from googling, I assume it is something the user would have to manually set, which did not happen in my case.
amaces said:
Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
Click to expand...
Click to collapse
Is it possible to do so without access to recovery? Can you give me some directions to where I can get the info to be able to do so? Any good posts on that, or any keyword I could research around? Would fastboot work? I'm not too sure where to start.
amaces said:
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
Click to expand...
Click to collapse
From what I have seen in the forums, I assumed having a "rescue microSD card" would make flashing ROMs fairly save, but I guess I'll stick to stable builds from now on then. But then again, doing stupid stuff does make me learn new things, and I was willing to risk bricking my tablet.
Anyways, thank you for helping me and for all your work to keep the Nooks alive!
N0he said:
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
Click to expand...
Click to collapse
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
mikeataol said:
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
Click to expand...
Click to collapse
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
I was able to do this while stuck on a TWRP splash screen
this will reset your file system back to ext4, (and wipe it) . if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
the NBD90Z 161019 build is working very well for me....
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
So, it never presents the external recovery menu, where you could select CWM before? You might need to format and re-build that SD card if that's the case.
mikeataol said:
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
Click to expand...
Click to collapse
Yes, do try this even with the eMMC recovery; ADB should be working, and you might be able format userdata if it was ext4 before. With some F2FS corruption, it's less likely to work, since it'll say /data is in use, and you can't unmount it.
mikeataol said:
if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
Click to expand...
Click to collapse
I think you should stick to ext4 while testing these issues. I did notice more corruption with F2FS on the new kernel, but didn't have time to investigate yet.
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
N0he said:
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
Click to expand...
Click to collapse
I think you should format it mkfs.ext2 then, ....
that should allow you to boot into the internal recovery and then convert it to ext4
Thank you both for taking your time to help me!
I'm going to summarize what I did to get my tablet back to working:
1. Having the tablet shut down because of low battery seems to have been the reason why I could boot from the microSD card again. So what can be done in that situation is to boot into the emmc recovery (which gets stuck at the splash screen) and then just leave it on until it shuts itself off. Then charge it up again and try to boot into the microSD card. Worked for me.
2. To then actually fix the problem, make sure to have CWM on the microSD card. There are at least two ways to get the tablet to work again:
- Boot into CWM, then connect to a pc with adb, reformat with adb shell using "make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata" (didn't work for me, as it couldn't find make_ext4fs)
- Boot into CWM, install stock recovery, use it to factory reset the tablet, boot into stock ROM once to make sure, boot into CWM, flash all your stuff.
Related
Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions on internal memory.
DizzyDen has prepared some .img files that can be burned to emmc to repair some of these issues, and they work well. But some of the files are very large and it takes a little knowledge of adb commands on the part of the users. And some users cannot get adb working on their machines. So I started investigating other solutions, and I have made some tools that work that I hope are user friendly.
Dean Gibson has a thread that describes how to repartition emmc to set the partition sizes for data and media to the user's preference. He repartitions partitions p6 (data), p7 (cache) and p8 (media). In studying his zip, I figured out how to make his tool repair partitions p4 (extended), p5 (system), p6 (data), p7 (cache), and p8 (media). And I was able to add additional commands to also repair partition p1 (boot). I asked Dean's permission to post his tools as modified by me and he agreed. Thanks Dean!
So that takes care of partitions 1, 4, 5, 6, 7, and 8.
Partitions 2 and 3 are very special and one must be very careful with them. Partition 2 is 'rom', which holds information that is specific to the user's device (serial number, etc.), and it is used by the system to set flags for deciding whether to boot to recovery or not and set the boot count that is used to decide whether to do a reset to factory conditions (8 failed boots). Partition 3 is 'factory' and holds the factory.zip file used by the 8 failed boot reset (if you want to learn more about the 8 failed boot reset, go to my tips thread linked in my signature). It also holds a backup of the device information in partition 2. So it is possible to repair partition 2 if partition 3 is still intact.
A few users have somehow managed to flash Nook Tablet ROMs to their Nook Colors and really messed up partition 4. (Edit: and now I know how it happened, some idiot recommended that they remove the first line of the updater script. NEVER do that! That line is a safety check to make sure you are flashing to the right device. You can also defeat the safety check by using an old CWM that has the toggle, 'disable asserts'. Never do that either.) And since partition 4 is the extended partition that holds partitions 5, 6, 7, and 8, they get messed up too. To repair those partitions along with partition 1, use CWM recovery to flash the two zips attached below. Be warned that everything in emmc media (p8) will be wiped out, so you may want to back that up first if you still can. The first zip to flash is 'NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip'. It will recreate those partitions on emmc. As soon as you have sucessfully flashed that zip, you must reboot the Nook Color back to CWM so that the updated partition table is read by CWM. Then you need to flash 'NookColor-emmc-format-partitions-5-6-7-8.zip' (partitions 1 and 4 do not need formatting). It will format the newly created partitions to the correct structure. Now you can use CWM to restore an earlier nandroid backup or flash your favorite ROM (including stock, get version 1.4.3 that I have modified to be flashable with CWM here, or DizzyDen has posted some excellent 1.4.1 stock ROMs here). If you are going to flash a stock ROM, you must be sure to use the format zip or the stock ROM will not boot properly.
If you are in a recovery bootloop, the first thing I recommend trying is to use my CWM version 5.5.0.4 bootable SD that is discussed in my tips thread linked in my signature and has been modified to help get out of some kinds of recovery flag bootloops. If you are in a recovery bootloop that just hangs, it may get you out of it after exiting my CWM with the 'reboot' command in the menu. But if you are still in the loop after doing that, it may be because your device info is missing or corrupted in partition 2. It will not boot to a ROM without this info. (Specifically, it needs a file in /rom/devconf named DeviceID. It is a text file with your 16 digit serial number in it followed by a line feed, 17 bytes.) Try flashing with CWM my 'NookColor-emmc-repair-partition-2.zip' attached to this post to recreate that info. But I recommend this as a last resort, since messing with that partition is risky. That zip will recreate the partition, reset the flags and copy your device specific information from partition 3. But your partition 3 must be intact for this to work. If it is not, the zip will abort and do nothing.
Additionally, for those that do not want to use CWM, I have made a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message when trying to flash these zips. It also has been modified to get you out of some kinds of bootloops.
Two points of information. First, I have included a temporary copy of CWM 5.5.0.4 on the boot partition of my repair so that if tries to reboot to emmc before you put a ROM on it, it goes to CWM. It will be removed as soon as you restore a backup or flash a ROM. Second, the new partition scheme created with my zip is for the original Nook Color's 1GB data and 5GB media. If you want one of the other schemes (5GB data/1GB media or 2GB data/4GB media) go to Dean Gibson's thread and flash his zips after you have repaired your system with mine. See his thread here.
I'm adding a little extra information about emmc partition structure for those interested. With any MBR disk there can be a maximum of four primary partitions. So to have more than four partitions the last primary partition is created as an extended partition so multiple logical partitions can be made inside it. The emmc structure is: p1 (boot, fat, primary), p2 (rom, fat, primary), p3 (factory, ext3, primary), p4 (extended, going from end of p3 to end of the disk), p5 (system, ext2, logical, inside the extended), p6 (data, ext3, logical, inside the extended), p7 (cache, ext3, logical, inside the extended) and p8 (media, fat, logical, inside the extended).
You save my nook color
Thank you so much. My serial number and other information were recovered successfully. Without those information I could not boot into any rom. If you cannot boot into ROM after following the first 2 steps, try recover partition 2. It works for me.
:laugh::laugh::laugh::laugh::laugh:
Thanks
My nook has been stuck in a "will not boot" state for about a week. I could run CWM and cyanoboot, but when ever I tried to boot CM I would get stuck at the "loading..." screen. I tried loading both CM7 & CM9 but neither one would boot.
I ran both repair scripts, reloaded CM7.1 and success!
Thanks Leapinlar! :good:
THANK YOU!!!!!!
Right from my 1st install I couldn't get the bar at the bottom of the screen, which made using the Kindle app more than a little difficult. This finally cleared everything off so I could start with a clean slate, and BINGO! I know have the bottom bar on all the screens. I assume when I go in to the Kindle app it will be ok now also (I just have to format a 16gb microSD and put in the Nook Color 1st).
I can't thank you enough!!!!
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
czarofthefrozentundra said:
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
Click to expand...
Click to collapse
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
leapinlar said:
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
czarofthefrozentundra said:
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
Click to expand...
Click to collapse
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
leapinlar said:
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
Click to expand...
Click to collapse
Worth a shot. Have nothing more to lose other than time. Maybe adb will work with you card in it. It didn't work with everything else I tried.
OMG OMG thank you soooo much for this thread , you saved my reading addict self from going insane ......
You've done a great job on collecting all of these useful things, especially for those who are stuck with their Nook Color boot looping. (I was once that guy) Dean helped me out with his data zips as well way back! Thanks for all this! :good: :victory:
Much thanks, leapinlar. Restored a nandroid with TWRP that was corrupted and lost my boot partition. I used your first 2 repair zips and I'm back in business. Your many contributions are greatly appreciated.
Mike T
OMG! Thank you so much for putting this up! Back at the beginning of the year I was having problems with my NC not going into USB Mode and only showing a black arrow when trying to load books and following this finally fixed it. Great write-up and instructions, thanks for the hard work.
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
jmiklus01 said:
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
leapinlar said:
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
jmiklus01 said:
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
Click to expand...
Click to collapse
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Restore NC back to stock
View attachment 1500490
leapinlar said:
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Click to expand...
Click to collapse
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
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
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
big64dave said:
View attachment 1500490
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
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
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
Click to expand...
Click to collapse
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
leapinlar said:
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
Click to expand...
Click to collapse
Thx for replied, the Nook just stock on loading and it won't let me do anything except for power up and down
So my Nook HD+ has been running Evergreen's CM 10.1 EMMC fine for a couple weeks. I've had some lag issues so I ran Lagfix and it worked great (though that's another topic). Today, I ran Lagfix again and my HD+ froze. I pressed the power button for 12 seconds to shut it off and it wouldn't boot, just a black screen. Crap.
Ok, no panic. I try pressing the power button for 30 seconds, plug it in, etc. Nothing. Ok, no biggie, going to have to reflash, right? So I download the updated 6/13 Cm10.1 EMMC, copy it over to my CWM SD card, stick it into my HD+ and boot. Boots into CWM no problem. First thing I see is:
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
Click to expand...
Click to collapse
Well I've seen that before, so I don't panic as I seem to recall its not a serious error. So I wipe cache thinking that maybe its corrupted. Not sure if that was smart or stupid but it seems it doesn't matter, because I try and install from SDcard and I get can't mount SDcard. Yikes! I choose install from internal SD and I get can't mount EMMC. Yikes!! I try and restore a backup, there is no backup as sdcard can't mount! Ok so I reboot and try it again a few times, the same error. I try running chkdsk on the SD card on my desktop and it checks out fine, no errors. I tried swapping in another clean and newly formatted fat32 SD card with only CM10.1 on it and it won't mount either.
I try going to advance->boot to recovery and pull out the sdcard. My HD+ boots and then is stuck at the screen where it says "NOOK" in white. Right before recovery should load. Its like recovery is missing or something.
Ok, I'm getting nervous that I have a serious problem. I boot my CWM SD card again and plug the HD+ into my desktop (Windows) and run ADB. I can adb shell, so I try and mount sdcard from the shell. I get
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: no such file or directory.
Click to expand...
Click to collapse
Ok, lets try sideload: adb sideload cm.zip.
failed to write data 'protocol fault (no status)
Click to expand...
Click to collapse
Ok, I have a trick I did one time before when I had a similar problem. I try and run:
adb shell mount -t tmpfs none /sdcard
This should mount my ram as sdcard and then I can push the rom to ram and flash from there. However, the error I get is like tmpfs doesn't exist. Ok, I am no expert so at this point I am stuck.
I didn't want to wipe anything yet as I don't know what that would do. At this point being able to boot into my CWM SD card is the only thing that works and I don't want to mess with it as I am now out of my knowledge area.
Anyone know what I can do here? I mean I can't restore a backup or flash a new rom. Does the HD+ have a download mode so I can use Odin? Is fastboot an option here? I am a few days behind on my backup but I can live with a factory reset if that is called for, no problem.
I've hit panic time, please help! Thanks!
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
silkshadow said:
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
Click to expand...
Click to collapse
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can't access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD or adb?
Edit: BTW, Lagfix also runs fstrim on /cache as well, I had forgotten.
silkshadow said:
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can;t access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD?
Click to expand...
Click to collapse
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I've actually been wanting to put CWM instead of TWRP, but I've been nervous about messing with recovery since I had a problem doing that on an old Samsung. Man I wish I had just bit the bullet and re-flashed CWM.
I know how to DD, but repairing the partitions is a step above what I've done before. Is there a tutorial on how to do this? Thanks!
Edit: Wait maybe I don't know how to DD. cat proc/mtd gives an error. How do I identify what to backup?
Edit2: Nevermind, I knew I saw it somewhere and there it is in your tips thread. Sorry, my bad. I'll report back after I have done it.
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Edit: Fastboot doesn't seem to work in CWM recovery?
silkshadow said:
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Click to expand...
Click to collapse
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks, trying it now.
Ok:
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.445588 seconds, 35.9MB/s
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.397918 seconds, 37.7MB/s
Click to expand...
Click to collapse
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
silkshadow said:
Ok:
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Click to expand...
Click to collapse
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
silkshadow said:
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
Click to expand...
Click to collapse
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
---------- Post added at 09:20 AM ---------- Previous post was at 09:16 AM ----------
silkshadow said:
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
Click to expand...
Click to collapse
It would be best if you could restore the boot and recovery from a stock backup. Then stock can try to repair itself.
Edit: if it will not turn on without the SD inserted, you may have also messed up xloader and bootloader partitions.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Ouch but /data loss is not too big, especially at this point. I just want to say you are awesome and thank you so much for helping me here! Anything I can do next? I am not sure what I could've done to wipe data. My HD was lagging a bit today but nothing serious. Just ran lagfix and it froze, but as soon as it froze I shut the Nook down.
Is it strange that I cannot mount EMMC? Is it possible that CWM is not seeing /data on EMMC but just a virtual /data?
Edit: Ok, will try to restore from stock imgs right now.
Ok these are definitely the stock boot and recovery CWM backup images:
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.401123 seconds, 37.4MB/s
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.443817 seconds, 36.1MB/s
Click to expand...
Click to collapse
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
silkshadow said:
Ok these are definitely the stock boot and recovery CWM backup images:
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
Click to expand...
Click to collapse
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
silkshadow said:
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
Click to expand...
Click to collapse
try dding these.
http://d-h.st/SG6
Sent from my Nook HD+ running CM10.1 on emmc.
Thank you very much! I will download and DD right now.
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Sammy321 said:
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Click to expand...
Click to collapse
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
bitdomo said:
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
Click to expand...
Click to collapse
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Sammy321 said:
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Click to expand...
Click to collapse
Download AIO-toolkit from the developement forum. Install itt, and install nvflash drivers with it.
At the main screen select option 2, and then select option 2 again. Follow teh instructions on the screen, and select TWRP 2.5.0.0 to be installed, or cwm 5.0.2.8, both have working mass storage.
(6.0.3.1 has broken massstorage and adb interface. I think you installed cwm 6.0.3.1 through rom manager, if it that true you are on old bootloader.)
bitdomo said:
(6.0.3.1 has broken massstorage and adb interface.
Click to expand...
Click to collapse
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Sammy321 said:
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Click to expand...
Click to collapse
Can you try twrp 2.5.0.0?
bitdomo said:
Can you try twrp 2.5.0.0?
Click to expand...
Click to collapse
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Sammy321 said:
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Click to expand...
Click to collapse
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
bitdomo said:
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
Click to expand...
Click to collapse
YES! I thought factory reset would delete the internal SD, so I didn't even consider that, but it worked like a charm! Thank you so much for caring and helping! You just made my week! :highfive:
1. Currently on verygreen's CM 11.0 EMMC with EMMC CWM v6.0.4.6, I think the recovery is bugged.
2. I have the bugged eMMC so the tablet is practically unusable without TRIM enabled, which this rom lacks.
3. I'm trying to flash back to CM 10.2 EMMC, but get this annoying error on every flash. Actually, I get this error with trying to FLASH anything, lower version of CWM, TWRP, any other ROM.
assert failed getprop("ro.product.device ") == "ovation" || getprop("ro.build.product") == "ovation"
4. I tried booting from SD using images such as "emmc-cwm-early3.1.img" (ie the one used to install CM 11.0 in the first place), "NookHDplus-bootable-SD-TWRP-2.6-for-emmc-4GB-rev0-(09.18.13).img" and "NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).img".
The problem is that, for some reason, maybe the way it was meant to be, I keep on booting into my EMMC CWM v6.0.4.6 regardless of the boot image that I use. It seems that my EMMC recovery takes priority over whatever recovery I put on my SD.
I need a way of downgrading my recovery, which does not allow me to flash anything, or somehow bypass this asset failed error.
Thanks
zonlicht said:
1. Currently on verygreen's CM 11.0 EMMC with EMMC CWM v6.0.4.6, I think the recovery is bugged.
2. I have the bugged eMMC so the tablet is practically unusable without TRIM enabled, which this rom lacks.
3. I'm trying to flash back to CM 10.2 EMMC, but get this annoying error on every flash. Actually, I get this error with trying to FLASH anything, lower version of CWM, TWRP, any other ROM.
assert failed getprop("ro.product.device ") == "ovation" || getprop("ro.build.product") == "ovation"
4. I tried booting from SD using images such as "emmc-cwm-early3.1.img" (ie the one used to install CM 11.0 in the first place), "NookHDplus-bootable-SD-TWRP-2.6-for-emmc-4GB-rev0-(09.18.13).img" and "NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).img".
The problem is that, for some reason, maybe the way it was meant to be, I keep on booting into my EMMC CWM v6.0.4.6 regardless of the boot image that I use. It seems that my EMMC recovery takes priority over whatever recovery I put on my SD.
I need a way of downgrading my recovery, which does not allow me to flash anything, or somehow bypass this asset failed error.
Thanks
Click to expand...
Click to collapse
Well, honestly - CM 11 has TRIM enabled.
JanSpatschek said:
Well, honestly - CM 11 has TRIM enabled.
Click to expand...
Click to collapse
It doesn't have TRIM enabled.
http://forum.xda-developers.com/showpost.php?p=49195328&postcount=13
http://forum.xda-developers.com/showthread.php?p=49589067#post49589067
zonlicht said:
It doesn't have TRIM enabled.
http://forum.xda-developers.com/showpost.php?p=49195328&postcount=13
Click to expand...
Click to collapse
I'm confused. But I thought it was patched and enabled.
wellersl said:
http://forum.xda-developers.com/showthread.php?p=49589067#post49589067
I'm confused. But I thought it was patched and enabled.
Click to expand...
Click to collapse
That link you posted points to a thread for CM10.2, not CM11 which we are talking about in here
Anyways I solved the issue. Booted into recovery using a SD CWM v6.0.4.6 image and was able to flash to 10.2.
Seems that either the eMMC CWM v6.0.4.6 is either bad or I my recovery flash was somehow bad/correct.
My Nook HD+ feels like a potato without trim enabled. With TRIM, it is laggy but usable.
Glad you were able to flash CM10.2, but still: CM11 has TRIM.
Sent from my BN NookHD+ using Tapatalk
Stable release of CM 10.2 and CM 11 nightlies have Trim enabled. Some of the 10.2 nightlies may after a certain date not sure if I remember that correctly or not but the stable does.
N0he said:
That link you posted points to a thread for CM10.2, not CM11 which we are talking about in here
Click to expand...
Click to collapse
True that.
I got lost looking for Verygreen's assertion that TRIM had been patched/enabled. I'll swear I read that somewhere in this jungle.
zonlicht said:
Anyways I solved the issue. Booted into recovery using a SD CWM v6.0.4.6 image and was able to flash to 10.2.
Click to expand...
Click to collapse
Could you happen to point me in the direction of where you got the SD CWM 6.0.4.6 image?
I've only been able to find the EMMC versions, and that won't let me install things from SD card.
twiztid_ said:
Could you happen to point me in the direction of where you got the SD CWM 6.0.4.6 image?
I've only been able to find the EMMC versions, and that won't let me install things from SD card.
Click to expand...
Click to collapse
This should be the image I used. I can't be certain, but this should 99% be the image I used. (I can't remember exactly because I tried all kind of things, trying to flash recovery from within in ROM, completely nuking everything on the tablet. I believe when I manged to fix my HD+, there was nothing on the tablet. It only had a recovery. This recovery that I got into won't even read files on the SD card. I had to ADB push a ROM (and find a working ADB driver) directly to eMMC from within the recovery.)
NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip
from
http://forum.xda-developers.com/showthread.php?t=2062613
Yes, I know that should be CWM 6.0.2.8, but some reason it boots up as SD CWM 6.0.4.6 for me. One thing that I did different was booting from the bootloader menu, from there select boot from SD, then it should say something along the lines of loading recovery from SD card.
zonlicht said:
This should be the image I used. I can't be certain, but this should 99% be the image I used. (I can't remember exactly because I tried all kind of things, trying to flash recovery from within in ROM, completely nuking everything on the tablet. I believe when I manged to fix my HD+, there was nothing on the tablet. It only had a recovery. This recovery that I got into won't even read files on the SD card. I had to ADB push a ROM (and find a working ADB driver) directly to eMMC from within the recovery.)
NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip
from
http://forum.xda-developers.com/showthread.php?t=2062613
Yes, I know that should be CWM 6.0.2.8, but some reason it boots up as SD CWM 6.0.4.6 for me. One thing that I did different was booting from the bootloader menu, from there select boot from SD, then it should say something along the lines of loading recovery from SD card.
Click to expand...
Click to collapse
Thanks.
Maybe I'm just so new to this that I'm doing something wrong, but I ended up getting CWM-based Recovery 6.0.2.8. I extracted the zip to the 3.67GB img file and used Win32DiskImager to write it to my SD card.
I was looking for the SD version of CWM Recovery v6.0.4.5b or higher so that I can try kitkat out, without installing CWM to the device (not sure if it can be easily removed in case I need to revert to stock), but I think I'll just have to take the plunge and install it.
I'm actually going to try out TWRP 2.6.3, since there's a SD bootable version of it available.
And that didn't work like I hoped either... Trying to find an updated version of CWM Recovery that will run, and install, from SD card, but that doesn't seem to exist. All the guides I've read require you to write an image to SD, copy some files to the device, then boot from the SD card and install from the device.
Anyway, thanks again.
I have a Nook HD+ that stuck in a boot loop, and nothing I do will fix it. It seems nothing is actually getting flashed to it. When I try to flash something or restore from a nandroid backup, it boots back up like I never flashed anything to it, still in a boot loop. I think it may have bad EMMC. So, I'd like to do an SD install (run CM off the SD card instead of internal EMMC) so that the tablet can be used again. The instructions here say to put the ROM on the internal storage of the Nook. How can I do this if the Nook won't boot? I can still get into CWM recovery. Can I even do an SD install since the EMMC is possibly dead?
sega dude said:
I have a Nook HD+ that stuck in a boot loop, and nothing I do will fix it. It seems nothing is actually getting flashed to it. When I try to flash something or restore from a nandroid backup, it boots back up like I never flashed anything to it, still in a boot loop.
Click to expand...
Click to collapse
I think it may have bad EMMC. So, I'd like to do an SD install (run CM off the SD card instead of internal EMMC) so that the tablet can be used again. The instructions here say to put the ROM on the internal storage of the Nook. How can I do this if the Nook won't boot? I can still get into CWM recovery. Can I even do an SD install since the EMMC is possibly dead?
Click to expand...
Click to collapse
The SD-based ROM at the link you referenced still makes use of EMMC (e.g., for /cache). If your EMMC is dead, you need to use a special "no-emmc" SD-based ROM image -- see http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67 and https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
I couldn't get either of the two to work. When I tried the CM11 ROM, TWRP couldn't mount /boot. When I tried the CM10.1 ROM, I couldn't push the rom zip to /sdcard using adb push. Every time I tired, it just flashed the usage instructions for adb.
I was able to get the CM 10.1 ROM working, and the tablet is now fully functional. Thanks for your help!