Related
I did a search for 'boot recovery' and read a few thread going back to May, but none of them seem to quite fit what happened to me. If I have missed the instructions, please link to them and I'll check it out.
First the setup:
My NC is stock 1.2 on the EMMC. I then followed the instructions in the Size-agnostic SD Card image and CM7 installer for SD Cards. The only step I cheated on was copying both update-cm-7.0.3-encore-signed.zip and gapps-gb-20110613-signed.zip to the SD card after the card was imaged. The rom and gapps installed and work as intended.
Next it was my intent to install update-CM7-dalingrin-OC-sd-063011.zip for a little speed boost. But I couldn't get it to boot into recovery with the various hold this button timings and choosing reboot from the power button options. I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin
Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
In your case, after you booted into recovery (using power button, and its options), you should be all set.
I don't now what makes you went into ROM Manager and flashed it
votinh said:
Did you just say up there "which flashed 3.2.01 to the EMMC"? why did you expect it "should have flashed the CWM recovery to the SD card"?
Click to expand...
Click to collapse
Because I thought that when you flashed a rom to the SD card and booted off the SD card it was treated the SD card as the 'local disk'. With the EMMC just being seen as additional storage when you where running off the SD. So when I booted from the SD card and opened Rom Manager while running from the SD card, I should think it would have flashed the CWM to the SD card.
votinh said:
Anyway, if you want to run from uSD, then anything related to eMMC or files that have "emmc" on file name, then ignore, discard it.
Click to expand...
Click to collapse
I didn't say anything about using files that said emmc in the OP.
votinh said:
In your case, after you booted into recovery (using power button, and its options), you should be all set.
Click to expand...
Click to collapse
The only way I can get to recovery is to remove the SD. How can I make sure to install update-CM7-dalingrin-OC-sd-063011.zip to the SD card? Can the SD card be put back in after booting to recovery?
votinh said:
I don't now what makes you went into ROM Manager and flashed it
Click to expand...
Click to collapse
When it wouldn't boot into recovery after the clean install from my OP, I started to look for other options. When I launched Rom Manager it said there was no recovery option installed.
-Zhin
Zhindel said:
I then went into ROM Manager and Flash ClockworkMod recovery, which flashed 3.2.01 to the EMMC. I have confirmed that by removing my CM7 SD card and successfully booting to recovery.
So now what? I would have thought the Rom Manager should have flashed the CWM recovery to the SD card, as that is what I had booted from. How can I uninstall the CWM from EMMC and force it to installed to the SD card?
Thanks,
Zhin
Click to expand...
Click to collapse
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.
stolenmoment said:
Rom Manager is useless for SD installs; just don't run it. It's not like most Android apps that only look at filesystem names (/sdcard, /emmc, etc), it uses the hardware device names (/dev/block/...) for its manipulations and pretty much assumes an emmc install.
Click to expand...
Click to collapse
Ahhh ha! That makes sense. I never knew that.
stolenmoment said:
Having CWM on emmc isn't a problem, it won't interfere with running the stock NC software from an emmc boot. I haven't run stock in forever, I don't know what they had for a recovery boot, but there are "restore to stock" threads that will show you how to find the parts if you want to put it back.
Click to expand...
Click to collapse
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
stolenmoment said:
What were you intending to do by installing CWM? The recovery that comes with the SD install is what flashes new builds for you, so you don't want to mess with it. You can install CWM on the SD as an alternate boot instead of a recovery (uAltImg and uAltRam instead of uRecImg and uRecRam) and use the u-boot that comes with recent CM7 builds to boot it if you want to play with it.
Click to expand...
Click to collapse
The install instructions for the dalingrin kernels said they were CWM flashable. I wasn't going to get too fancy, but maybe I should look at some of the alternate boot options.
Thanks!
Zhin
I accidentally did the same exact thing before I realized VG included his own recovery on the SD. From what I've read, to uninstall CMW from the emmc, you need to create a separate CMW SD and do a full restore to stock.
http://forum.xda-developers.com/showthread.php?t=931720
As for putting CMW on the SD, IDK. VeryGreen's method of just appending "update-" to rom file names and placing them on the root of the SD has worked for me.
I didn't say anything about using files that said emmc in the OP.
Click to expand...
Click to collapse
Because you were confusing as indicated in your thread, I was just suggesting eliminating anything about "emmc" if you intended to run off uSD. I did not say you did it, I just recommend it. For instance, Dalingrin OC kernel, there are several versions out there and anything with "emmc", then you should ignore them. That's all
I can restore to stock easily enough. I have an image of the stock install for easy recover for just these circumstances.
Click to expand...
Click to collapse
I assume you are all set.
Am I right? or still need help
I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?
dna59 said:
I did the same thing and am too wondering how to remove it for warranty purposes. My Nook came w/ 1.2...does that mean 'd have to restore to stock 1.0.1 and then upgrade to 1.2?
Click to expand...
Click to collapse
Get one of those 2
http://forum.xda-developers.com/showthread.php?t=1050520
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
bluevolume said:
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
Click to expand...
Click to collapse
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
bluevolume said:
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
Click to expand...
Click to collapse
Then it is the set flag issue I mentioned in the first part of my post. Not sure how to get it cleared. Just exercising CWM? Try flashing something else. Gapps again maybe. It won't hurt to flash them twice.
Edit: btw, what version of CWM are you running?
Sent from my Nook Color running ICS and Tapatalk
CWM v3.2.0.1
I installed gapps again, same problem. Gremlins!
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
cmendonc2 said:
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
Click to expand...
Click to collapse
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
leapinlar said:
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
Click to expand...
Click to collapse
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
Yes, I've had CWM flashed into the emmc for a while. So I could use the boot menu utility to boot to CWM if needed.
BTW - this is the ROM i'm using: http://forum.xda-developers.com/showthread.php?t=1344873
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
Click to expand...
Click to collapse
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue. I'll revisit that later today.
bluevolume said:
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue.
Click to expand...
Click to collapse
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
leapinlar said:
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
Click to expand...
Click to collapse
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I'm not that comfortable with adb commands so I starting looking for other solutions. Since you mentioned that its the actual boot files that are missing/corrupted, I searched around and found this:
http://forum.xda-developers.com/showthread.php?t=958748
I loaded the RecoveryFix.zip on my SD card and flashed it with CWM. Rebooted, and I was back to the 'Future of reading..." boot logo, but it still went straight to CWM. So I flashed the ROM again (the ROM I listed earlier in the thread), wiped cache, fixed permissions. Rebooted, and the "Cyanogenmod" boot logo was back. And instead of going right to CWM, the screen was blank for quite a while then I saw the little Android guy skate by... And I'm back in business.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
bluevolume said:
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
Click to expand...
Click to collapse
The next step I was going suggest if you could not fix it was to flash a new CWM to your boot files. Good job finding that.
Glad you got it running. I learned a lot myself and maybe that info will help others.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Click to expand...
Click to collapse
Got it, thanks m8
That clears up my mind.
I had the same problem, followed the thread you found. Did the same thing, now I'm back in business too. Thanks!
Just wanted to say thanks for figuring this out! I was in a similar situation after downgrading from cm9 back to cm7. Installed CWM using recoveryfix_3.0.2.8.zip from the thread above, and was back up and running after a restore of a cwm backup. Headed on vacation tomorrow and the wife would have had my head for being such an FW... you're a lifesaver!
I inherited a failed dual-boot install, Nook BNRV200-A.
It starts and runs perfectly from SD card. But nothing successfully starts and runs from internal; mostly just boot loops. When I try to get into recovery, I get the dual-boot selector menu. This works OK, but if I select to boot recovery through it, no recovery comes up. If I try the trick with holding down both volume + and volume -, it just boot loops.
I would like to completely blow away all the internal partitions, recreate them and then restore standard boot, some ROM and CWM recovery. Is there a (current) procedure out there to do this? Happy to do this through ADB if somebody could tell me what to type.
The main thing is the dual-boot menu itself. I have tried reformatting /boot from CWM, but the durned thing still comes back.
(Wish we had something like the RUU or NVFlash utilities...)
TIA,
glg
Possible solution
Try following this guide ...( http://forum.xda-developers.com/showthread.php?t=1275859 )(eMMC 2/22 Dual Boot Guide 2.0 ) make sure you download all the needed files too.. It will allow you to wipe and repartition the internal eMMC .... then sets up a dual boot internal for you. Works slick and easily... Takes 20 - 30 min to do and is rock solid.
I used it and I am running CM7.2 (Mirage) on primary and B&N 1.4.1 on Alt boot... works great and is soooo fast (works great using Nook Tweaks to overclock to 1300)
Try it ... I think it will work fine
Tinpau
tinpau60 said:
Try following this guide (eMMC 2/22 Dual Boot Guide 2.0 )
Tinpau
Click to expand...
Click to collapse
Thanks for the quick reply. I did try that (at least the part about Revert from Dual-boot. I don't want a dual-boot setup).
So far, I have a working CM9 setup that successfully reboots and will now boot into recovery. But, for some reason, it doesn't recognize the SD card. I think it still has something to do with the partition table being messed up.
glg
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Problem solved
k8108 said:
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
These steps were very helpful. I had an additional problem where the SDcard I was trying to use was formatted oddly. Instead of a single Primary partition, it was a /logical/ partition on an extended partition. Probably the vendor loaded some crapware on there in the empty space. So it never was seen by the Nook. When I deleted the logical and extended partitions and created a single 8GB primary partition, and formatted it as FAT32, the card was usable. Totally up and running.
Thanks,
glg
This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app
geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4
oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.
khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.
oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.
I'm not sure what else you were expecting from a "factory reset"
creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).