Related
I need to swap out my NC due to screen issues. I have a setup I like with NF 0.6.7 on eMMC. Is it safe to do a nandroid backup of my setup through CWM (or make images of my partitions using dd commands through ADB) to restore to my new NC? Or am I better off just starting from scratch? It's not a big deal either way, but I could save a few hours of work.
As far as I understand, Clockwork mod doesn't work as it should with Froyo. I've tried booting into a CWM bootable sd card, then swaping it out with another sd card because of storage issues. I then tried a backup and it failed to work. I kept getting errors.
If you can get CWM to backup a Froyo install please share how you did this.
You may be able to dd your eMMC partitions, then make your own CWM flashable zip to restore. How reliable this might be is above me.
All in all, it's not that complicated nor time consuming to just redo everything on your new nook.
Best of luck.
woot1524 said:
As far as I understand, Clockwork mod doesn't work as it should with Froyo. I've tried booting into a CWM bootable sd card, then swaping it out with another sd card because of storage issues. I then tried a backup and it failed to work. I kept getting errors.
If you can get CWM to backup a Froyo install please share how you did this.
You may be able to dd your eMMC partitions, then make your own CWM flashable zip to restore. How reliable this might be is above me.
All in all, it's not that complicated nor time consuming to just redo everything on your new nook.
Best of luck.
Click to expand...
Click to collapse
Your are probably right. Better to just set everything up again. Just hope I don't run to problems like some others have been reporting with the market, etc.
I attempted to perform a backup of NF on internal memory using CWM from SD, and it failed to work. I installed CWM through Rom Manager (rebooted immediately after flashing) because it did not install with the flashable zip. I booted into recovery via Rom Manager and performed a nandroid backup. It took about 8 minutes and produced a 252Mb backup. I have no idea how reliable it is. Perhaps I will attempt to flash back to rooted 1.1 or 1.0.1, then restore the NF nandroid before I return the NC to see if it works or not.
You actualy got CWM to boot after flashing it with rom manager to the eMMC? I've always read that, that's not possible with Froyo on the eMMC.
I have flashed at least two different backups of 2.2 and stock 2.1.
didn't do anything special.
-edit- i suppose i should mention this was with cwm on emmc.
woot1524 said:
You actualy got CWM to boot after flashing it with rom manager to the eMMC? I've always read that, that's not possible with Froyo on the eMMC.
Click to expand...
Click to collapse
I was a bit leery since I read about folks getting into bootloops installing CWM, but figured it was supposed to be installed with the flashable NF 0.6.7 zip, so thought how much trouble could I get into?
I also read that you must reboot immediately after flashing CWM through Rom Manager to avoid bootloops (this advice seemed related to NC's Eclair 1.0.1 or 1.1) - I have no idea if that was necessary, but figured there was no harm in following the directions.
I thought I should be able to nandroid off of the CWM running from SD (it is possible I was using Monster's CWM image, which I understand will not nandroid from SD?), but didn't have success so figured I would try flashing it to eMMC.
lafester said:
I have flashed at least two different backups of 2.2 and stock 2.1.
didn't do anything special.
-edit- i suppose i should mention this was with cwm on emmc.
Click to expand...
Click to collapse
How were you able to make backups of 2.2? I have froyo 6.7 on eMMC with CWM flashed via rom manager and I'm completly unable to boot into it. I've tried using the option in rom manager to boot into recovery, I also tried holding menu+PWR at boot and that did not work.
I was trying to install CM10 onto my Nook HD and I somehow screwed it up. I flash ROMS all the time on my MyTouch 4G and i am not a complete stranger to flashing, but I messed it up some how. Now the Nook HD will get past the Nook Banner. I tried a hard reset but it gets like 98% then shuts off. I can still insert an SD and access CWM but nothing will flash and i get this error when I try to do anything.
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 made a backup on the internal SD but it says there are no files in recovery. I am at a loss. This is my first post I am hoping someone would have an idea.
Thanks
If you tried a hard reset, the first thing it does is format everything. That is why you no longer have a backup on internal memory. Never store backups on internal memory without copying them to SD or your PC for safekeeping. It is the first thing lost on a reset.
Those cache errors mean that the cache partition is not formatted. You need to boot to a CWM SD for stock and format /system, /cache and /data. Then flash the plain stock 2.0.0 stock ROM that I have linked in my HD/HD+ CWM thread. Then you can boot to it, let it update and register again.
Then you can start over with CM10 to SD. And when you said you tried to install it earlier, I hope you meant install to SD. It cannot be installed to internal memory.
Sent from my Nook HD+ running CM10 on Hybrid SD
I'm the same situation. The problem is that these partitions are physically gone.
How do we recreate them? It sounds like something that has to be done using adb, a disk partioning utility (fdisk maybe?) and the names of the devices that need to be created, and then marking /boot as boot.
I've tried to format /cache and the other partitions but it says they don't exist. This problem is also preventing me from installing images including the stock Nook HD software, too, which apparently needs these partitions to exist already.
Thanks in advance for any advice.
aegrotatio said:
I'm the same situation. The problem is that these partitions are physically gone.
How do we recreate them? It sounds like something that has to be done using adb, a disk partioning utility (fdisk maybe?) and the names of the devices that need to be created, and then marking /boot as boot.
I've tried to format /cache and the other partitions but it says they don't exist. This problem is also preventing me from installing images including the stock Nook HD software, too, which apparently needs these partitions to exist already.
Thanks in advance for any advice.
Click to expand...
Click to collapse
I will give you two clues, then do some research.
First to understand the HD/HD+ partition structure, go to my HD/HD+ Tips thread linked in my signature and read item 16.
Second, the HD/HD+ uses a GPT partition structure rather than the standard DOS MBR structure. You need to use gdisk instead of fdisk. Search the Nook Tablet forum to understand a little more about gdisk and GPT. The NT also uses it.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I will give you two clues, then do some research.
First to understand the HD/HD+ partition structure, go to my HD/HD+ Tips thread linked in my signature and read item 16.
Second, the HD/HD+ uses a GPT partition structure rather than the standard DOS MBR structure. You need to use gdisk instead of fdisk. Search the Nook Tablet forum to understand a little more about gdisk and GPT. The NT also uses it.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the clues. I was hoping someone could have a plug-and-play solution for this that I can use.
But, I'll see what I can do to solve this puzzle but I'm about to mail this thing to someone who can restore it and buy a new one at this point.
.
bricked my nook hd+
Hi guys, I'm a noob and yet I took a chance to upgrade my nook hd+ into CM 10.2. On the initial boot with CWM sd card, my nook recognized it right away. I followed "installing cyanogenmod 10.2(instead of 10.1) for dummies After much trouble I was able to "reboot system now". Now as I rebooted from the CWM 10.2 install, all I get is an initial boot with nook for a few seconds which flashes in and out then switches to the cyanogen universal bootloader after power button is pressed a number of times. Then much to my surprise it loaded the page EMMC CWM Based recovery v6.0.3.2. I pressed reboot system now but it didn't load CWM cyanogenmod but only loads nook's initial boot page, flashes same page in & out, then after pressing on the power button a number of times, would switch to the cyanogen universal bootloader, pressing the power button some more brings the screen to EMMC CWM Based recovery v6.0.3.2. The choices here are: 1. reboot system now, 2. install zip from sd card (CWM sd card is still inserted in nook hd+), 3. install zip from sideload, 4. wipe data/factory reset, 5. wipe cache partition, 6. backup and restore, 7. mount & storage, and 8. advanced. What should be done from here? PLEASE HELP. Thanks
newbienyc said:
Hi guys, I'm a noob and yet I took a chance to upgrade my nook hd+ into CM 10.2. On the initial boot with CWM sd card, my nook recognized it right away. I followed "installing cyanogenmod 10.2(instead of 10.1) for dummies BUT when I was about to "reboot system now", instead of pressing the n button, the power button was pressed. Now as I rebooted from the CWM 10.2 install, all I get is an initial boot with nook for a few seconds and switches immediately to the cyanogen universal bootloader and NEVER progresses but simply stays there. The only way to turn it off is by pressing on the power button to shut it off. Is the nook hd+ rendered useless from now on?Is there any remedy to this? If and when I download and write on another microsd card the nook 2.1 zip to revert to the original nook will the nook hd+ be able to recognize the microsd card and boot from it? Thank you.
Click to expand...
Click to collapse
Quick question leapinlar. Does the 8 failed boots hard reset also restore the /boot partition to stock given your recovery is stock and not cwm or other?
ididitforthenookie said:
Quick question leapinlar. Does the 8 failed boots hard reset also restore the /boot partition to stock given your recovery is stock and not cwm or other?
Click to expand...
Click to collapse
You need stock recovery still on internal memory for the 8 failed boot to work. But if it works, everything is completely back to stock, including /boot.
Sent from my Nook HD+ running CM10.1 on emmc.
newbienyc said:
Hi guys, I'm a noob and yet I took a chance to upgrade my nook hd+ into CM 10.2. On the initial boot with CWM sd card, my nook recognized it right away. I followed "installing cyanogenmod 10.2(instead of 10.1) for dummies BUT when I was about to "reboot system now", instead of pressing the n button, the power button was pressed. Now as I rebooted from the CWM 10.2 install, all I get is an initial boot with nook for a few seconds and switches immediately to the cyanogen universal bootloader and NEVER progresses but simply stays there. The only way to turn it off is by pressing on the power button to shut it off. Is the nook hd+ rendered useless from now on?Is there any remedy to this? If and when I download and write on another microsd card the nook 2.1 zip to revert to the original nook will the nook hd+ be able to recognize the microsd card and boot from it? Thank you.
Click to expand...
Click to collapse
The only 10.2 out yet is an SD install. If you haven't already, I would suggest to power off, remove the SD card and try booting from internal storage.
Sent from my HD+ Running CM 10.1 from emmc
Sherip said:
The only 10.2 out yet is an SD install. If you haven't already, I would suggest to power off, remove the SD card and try booting from internal storage.
Sent from my HD+ Running CM 10.1 from emmc
Click to expand...
Click to collapse
Hi, thanks for the quick response. Do you mean rebooting the nook hd+ without the CWM sd card? Yes, I've done this step to no avail. It would boot to the EMMC CWM based recovery v6.0.3.2. I've to be honest, whilst waiting for a response, I tried to remedy the situation by trying to install CWM 10.1 but the upgrade cannot get installed, then the android mascot just seemed to die (open chest with an exclamation point inside a red triangle). Does this mean it's irreparable?
newbienyc said:
Hi, thanks for the quick response. Do you mean rebooting the nook hd+ without the CWM sd card? Yes, I've done this step to no avail. It would boot to the EMMC CWM based recovery v6.0.3.2. I've to be honest, whilst waiting for a response, I tried to remedy the situation by trying to install CWM 10.1 but the upgrade cannot get installed, then the android mascot just seemed to die (open chest with an exclamation point inside a red triangle). Does this mean it's irreparable?
Click to expand...
Click to collapse
As Sherip said, the CM10.2 is an SD install only. You should not have been following the Dummies guide for installing that. That is for installing to internal memory. You need to go to my HD/HD+ CWM thread linked in my signature and put stock recovery back on internal. I have a link to it in my item 5 in that thread. Then the device can successfully do an 8 failed boot to get back to stock.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
As Sherip said, the CM10.2 is an SD install only. You should not have been following the Dummies guide for installing that. That is for installing to internal memory. You need to go to my HD/HD+ CWM thread linked in my signature and put stock recovery back on internal. I have a link to it in my item 5 in that thread. Then the device can successfully do an 8 failed boot to get back to stock.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks. (sorry for being such a dummy) I tried flashing NookHDpus-emmc-...zip to my nook hd+ but this is the response I get each time I try and choose zip from sdcard, E: Can't mount /sdcard?
ididitforthenookie said:
Quick question leapinlar. Does the 8 failed boots hard reset also restore the /boot partition to stock given your recovery is stock and not cwm or other?
Click to expand...
Click to collapse
Forgive me but does 8 failed boots mean turning on my nook and the initial phase of boot-up with"nook" just fades in and out and does hard reset mean pressing on power and n buttons simultaneously till it comes on? Thanks
newbienyc said:
Forgive me but does 8 failed boots mean turning on my nook and the initial phase of boot-up with"nook" just fades in and out and does hard reset mean pressing on power and n buttons simultaneously till it comes on? Thanks
Click to expand...
Click to collapse
It means
1. turn on the nook,
2. when it starts to boot up press and hold power until it turns off.
3. turn it back on,
4. repeat steps 2 & 3 8x.
It needs to be 8 "failed" boots, that get interrupted before it has a chance to get all the way through the process.
bpaulien said:
It means
1. turn on the nook,
2. when it starts to boot up press and hold power until it turns off.
3. turn it back on,
4. repeat steps 2 & 3 8x.
It needs to be 8 "failed" boots, that get interrupted before it has a chance to get all the way through the process.
Click to expand...
Click to collapse
I did this twice and it booted up alright but right into this screen "EMMC CWM based recovery v6.0.3.2". I'm at myself, but I thank you all for your best efforts at helping me .
newbienyc said:
I did this twice and it booted up alright but right into this screen "EMMC CWM based recovery v6.0.3.2". I'm at myself, but I thank you all for your best efforts at helping me .
Click to expand...
Click to collapse
8 failed boots will not work unless you have stock recovery still on emmc. It looks like you replaced stock recovery with CWM. You either have to flash a stock ROM (which also replaces the CWM with stock recovery) or you need to flash my stock recovery zip from my HD/HD+ CWM thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
8 failed boots will not work unless you have stock recovery still on emmc. It looks like you replaced stock recovery with CWM. You either have to flash a stock ROM (which also replaces the CWM with stock recovery) or you need to flash my stock recovery zip from my HD/HD+ CWM thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks, I will be following your instruction (perhaps flash your stock ROM) with a new microsd card. :fingers-crossed: Hope i'll get it right this time.
leapinlar said:
8 failed boots will not work unless you have stock recovery still on emmc. It looks like you replaced stock recovery with CWM. You either have to flash a stock ROM (which also replaces the CWM with stock recovery) or you need to flash my stock recovery zip from my HD/HD+ CWM thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I did try using a new sd card and an old one, both failed; why is the message always "E: Can't mount /sdcard/"? I was hoping to sideload but my laptop cannot even recognize the nook attached by usb.
newbienyc said:
I did try using a new sd card and an old one, both failed; why is the message always "E: Can't mount /sdcard/"? I was hoping to sideload but my laptop cannot even recognize the nook attached by usb.
Click to expand...
Click to collapse
I don't know why it gives you that error message. I recommend you go to my HD/HD+ CWM thread linked in my signature and make one of my CWM bootable SDs from item 1. Then flash my plain stock 2.1.0 zip from my item 6.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I don't know why it gives you that error message. I recommend you go to my HD/HD+ CWM thread linked in my signature and make one of my CWM bootable SDs from item 1. Then flash my plain stock 2.1.0 zip from my item 6.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'll do that, thanks.
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.
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.
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.