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!
Related
I just bought an NC 1.2.0
no need to bore anyone with details but it is safe to say that it is virtually bricked. i would love a surefire way to get it completely back to the stock to start all over again.
i tried the repartitioning and reformatting technique using cm7 without any luck whatsoever. when i boot the device gets to the big N and "contains Reader mobile technology..." screen and never fully boots.
does anyone have a solution?
Presumably, one of those boring details involved writing an image to an SDcard:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
There's a decent chance the problem with your install is that you were using an older version of CWM on a newer NC, and it didn't write all the partitions correctly. Regardless, get the current version now.
Grab a B&N 1.2 image:
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
and install zip from sdcard > choose zip from sdcard in CWM.
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
mvnsnd said:
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
Click to expand...
Click to collapse
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Taosaur said:
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Click to expand...
Click to collapse
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
mvnsnd said:
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
Click to expand...
Click to collapse
It does if you flash it from ROM Manager, regardless of whether you have ROM Manager running internally or on a CM7 SD install. If he hasn't done that, 8 failed boots should work, but I'm not 100% sure on a repartitioned device.
First and foremost,
Standard Disclaimer
By flashing this you should understand that I am not responsible for bricked devices. In order to flash this file, you would have already rooted your device, voiding the warranty. YOU are choosing to make these modifications, and I take no blame or responsibility if you brick your device and/or your device catches fire.
I would like to start off saying that I used the eMMC dual boot option referenced here [eMMC]Updated Dual Boot Guide[CM 7.1+][Phiremod 7+][Stock 1.3] and ran into the problem where the main partition (CM7 in my case) was booting normally, however, the alternate partition (Stock 1.3 rooted) would continually boot loop. After research, I found out that it was boot looping due to the incorrect versions of Adobe Flash and Air being installed. They were also installed to /system instead of /data.
I found two excellent guides located here and here that helped diagnose the problem. Unfortunately, these only helped with the primary partition.
In order to fix the boot looping of the alternate partition, I modified the updater-script provided by jaromnelson to reflect the alternate partition.
What this file does is removes the incorrect Adobe Air and Adobe Flash from /system folder on the alternate partition and installs the correct Adobe Air and Adobe Flash to /data folder. DO NOT INSTALL THIS FILE IF YOU ARE NOT RUNNING eMMC DUAL BOOT by Taosaur. If you continue to boot loop after you install, you are not boot looping because of Adobe Air and/or Flash.
To Install:
Download the file located here
Put the file onto your SD Card
Boot into CWM recovery
To be on the safe side, Wipe Cache and Dalvik (not sure if this helps but I do it anyway).
Code:
CWM > Wipe Cache Partition
CWM > Advanced > Wipe Dalvik Cache
Install the attached ZIP through CWM.
Reboot into your alternate partition and enjoy.
I am by no means a developer, just a guy that does a lot of research.
Full credit goes to:
Taosaur for creating the eMMC dual boot guide
jaromrnelson for creating the guide to fixing the boot looping
GMPOWER for the initial ZIP
Do you happen to still have this file, file seems to not exist.
I'm having the same issues you were
You can always upload it here as an attachment
Wow. I can't believe this may actually help someone. All this time, I thought I would have been the only one to encounter this problem. Unfortunately it would not let me attach the file to the post. Anyhow, here is an updated link. I'll update the OP too.
http://www.mediafire.com/?8e8vxgl8haag2a5
Mikey, after looking, it appears that the original referenced thread has been updated to a new method of installing dual boot to emmc. When I get home I will check to make sure that the new version uses the same boot partitions. So for now (until I can check) this zip is only good for the old method.
edit: I looks like the new method uses the same boot partitions (primary system: 0p5 and primary data: 0p6 --- secondary system: 0p9 and secondary data: 0p10) as the old method. So, if you are using the new method and experiencing the same boot loops as before, it should be safe. In reality, I'm not even sure if the Adobe problems exist anymore with the new method. As stated in the OP though, I'm not responsible for bricked devices.
To be honest, my wife has been reading on the nook so much lately, she hasn't let me mess around with it. As soon as she finishes up this book that she's on now, I plan on updating to the newest stock and ICS.
Sent from my LG-P999 using XDA
Always boots to CWM
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Hoser88 said:
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Click to expand...
Click to collapse
Try this post. Not exactly the same issue, but this person solved his CWM boot loop issue.
http://forum.xda-developers.com/showthread.php?p=23864432
Sent from my Nook Color running ICS and Tapatalk
@Leapinlar
Thanks for the help. That thread was perfect. I'm up and running now!
I have been trying for a week now to restore a nook color back to stock with no avail. When I started there was no boot image or stock recovery and it would only boot from a CWR sd card but not mount or read the sd card to install any zip files Now i have it booting with the stock boot image but only to the "n" screen and no further. I have tried the factory recovery and reset but get nothing. I have a PC with a working ADB install but am unable to "push" the system.img to the sd card or anywhere for that matter and then dd it to the correct block on the internal memory. I am also unable to boot CM7 from the sd card because it freezes during the install. So basically what I'm asking for, is help fixing this darn thing cause I'm tired of it kicking my ass. thank you in advance for the info.
Sounds like your emmc partitions are messed up. Go to my partition repair thread linked in my signature. But if you cannot flash any zips, my repairs will not work. Try using my CWM bootable card from my tips thread also linked in my signature. Put the repair zips on the boot card before you boot.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
Sounds like your emmc partitions are messed up. Go to my partition repair thread linked in my signature. But if you cannot flash any zips, my repairs will not work. Try using my CWM bootable card from my tips thread also linked in my signature. Put the repair zips on the boot card before you boot.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
I will try both when i get home from work and let you know how it works. Thanks.
steve_o2291 said:
I will try both when i get home from work and let you know how it works. Thanks.
Click to expand...
Click to collapse
ok so after reading your links i have tried both of those methods already and neither of them works. I am beginning to wonder if i don't just have a group of six bad sd cards. They will boot CWR and begin the install of CM7 but thats as far as they get. I have tried everything I can find on forums and nothing works so far. If i could just get the system.img pushed with adb then i think that would get it but it just won't work.
I have also read about the system not loading if the serial number is not on it but I have done some file searching and found that it is in place so i don't think thats the prob. If you could think of anything different that would be awesome but I think I'm about to the point of having to bring it to B&N for service or just replace it.
Is there a place i could put the system image for the factory reset to take care of the install on its own.
steve_o2291 said:
Is there a place i could put the system image for the factory reset to take care of the install on its own.
Click to expand...
Click to collapse
Go to my tips thread and I have a new section about 8 failed boots. But you need the stock recovery on /boot for it to work. I know you cannot flash my stock recovery zip, but you could open the zip and extract the uRecImg and uRecRam and push them with adb to /boot (mount /dev/block/mmcblk0p1 as /boot first). Then follow my guide on how to do the 8 failed boots. That should wipe your device (including media) and install the original stock on your system.
leapinlar said:
Go to my tips thread and I have a new section about 8 failed boots. But you need the stock recovery on /boot for it to work. I know you cannot flash my stock recovery zip, but you could open the zip and extract the uRecImg and uRecRam and push them with adb to /boot (mount /dev/block/mmcblk0p1 as /boot first). Then follow my guide on how to do the 8 failed boots. That should wipe your device (including media) and install the original stock on your system.
Click to expand...
Click to collapse
Ive already got the stock recovery on /boot but 8 failed boots still does nothing because i have system.img for it to recover. I have all the partitions formatted the way they are supposed to be with fdisk but i still can't push the system.img to sdcard because it can't find it and if i try to put it on the nook i either get a protocol error or not enough room on the device error.
steve_o2291 said:
Ive already got the stock recovery on /boot but 8 failed boots still does nothing because i have system.img for it to recover.
Click to expand...
Click to collapse
I don't understand what you mean, you 'have system.img for it to recover'. The 8 failed boot uses factory.zip in partition 3 and if it enters the process (via stock recovery), it clears data and flashes that.
leapinlar said:
I don't understand what you mean, you 'have system.img for it to recover'. The 8 failed boot uses factory.zip in partition 3 and if it enters the process (via stock recovery), it clears data and flashes that.
Click to expand...
Click to collapse
I didn't realize i had to have facotry.zip on p3. I am going to try to dd it there and see what it does from there
Ok just tried like that and still get the install failed screen.
steve_o2291 said:
I didn't realize i had to have facotry.zip on p3. I am going to try to dd it there and see what it does from there
Ok just tried like that and still get the install failed screen.
Click to expand...
Click to collapse
Where did you get your factory.zip? Did you just rename a stock zip? It looks the same but I'm not sure everything is. When it says install failed, did the recovery start and fail or did it say that right off? Are you sure the recovery you used is the real stock recovery? You cannot just remove kernel-recovery and ramdisk-recovery from the stock zip and push those as uRecImg and uRecRam. Those get patched as the rom installs. Take the ones from my zip and push them. They are the patched versions.
You say you dd it but I hope you mean push to the mounted partition.
leapinlar said:
Where did you get your factory.zip? Did you just rename a stock zip? It looks the same but I'm not sure everything is. When it says install failed, did the recovery start and fail or did it say that right off? Are you sure the recovery you used is the real stock recovery? You cannot just remove kernel-recovery and ramdisk-recovery from the stock zip and push those as uRecImg and uRecRam. Those get patched as the rom installs. Take the ones from my zip and push them. They are the patched versions.
You say you dd it but I hope you mean push to the mounted partition.
Click to expand...
Click to collapse
I am unable to mount /dev/block/mmcblk0p1 in shell with a /boot directory. gives me a "Device or resource busy". so i just pushed the recovery files to /boot with
"adb push XXXX /boot"
and yes the recovery starts to load then fails
If i do
adb mount /boot
I get the help menu for a wrong entry
and i used the files from your download for the factory recovery
steve_o2291 said:
I am unable to mount /dev/block/mmcblk0p1 in shell with a /boot directory. gives me a "Device or resource busy". so i just pushed the recovery files to /boot with
"adb push XXXX /boot"
and yes the recovery starts to load then fails
If i do
adb mount /boot
I get the help menu for a wrong entry
Click to expand...
Click to collapse
Boot must already be mounted by CWM.
Just do an 'adb mount' command and it will tell you the things already mounted.
As for dd'ing the system.img to p5, can't you just dd it with adb from your PC?
And the factory.zip? You pushed that to p3?
leapinlar said:
Boot must already be mounted by CWM.
Just do an 'adb mount' command and it will tell you the things already mounted.
As for dd'ing the system.img to p5, can't you just dd it with adb from your PC?
And the factory.zip? You pushed that to p3?
Click to expand...
Click to collapse
yes i pushed factory.zip to p3
as for dd'ing system.img to p5 with adb i have to do dd with a shell command and i errors out when i try to push it data so i can't dd it to p5
this would be a lot easier if the damn sd card would work. I have no clue why it isn't because it worked fine until it crashed
Try formatting the SD with an SD formatting program (in a USB card reader, not your PC's internal slot). Sometimes SDs formatted with PCs are not readable in the nook. Search the net for one.
leapinlar said:
Try formatting the SD with an SD formatting program (in a USB card reader, not your PC's internal slot). Sometimes SDs formatted with PCs are not readable in the nook. Search the net for one.
Click to expand...
Click to collapse
Already did that several times with multiple cards on different machines. One with windows the other a mac
One final suggestion. Use my CWM SD (version 5.5.0.4) since it has the option of flashing things from internal memory.
Do an 'adb mount' to verify that p8 is mounted. If it isn't, mount it. Then push the zips that you want to flash there. Then the new CWM can flash from there.
Tried that just now and 5.5.0.4 tells me no zip found. I guess this is something that'll have to be done by a professional. After a week of trying and trying again I don't think Im going to be able to do it because I've tried everything i can find on the net and nothing works except for get the factory boot image back in place and getting the factory recovery to start but won't install anything. The factory reset also starts and erases all data but won't still only boots to the "n" screen. thanks for the help
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
judgerey said:
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
Click to expand...
Click to collapse
You need to get my bootable CWM card from my tips thread linked in my signature. Then you can flash a new 1.4.3 that I have also in my tips thread. I also have flashable CWM zips there to put CWM on emmc. And if that does not fix it run my partition repair zips using my CWM. ROM Manager does not always install the CWM to emmc properly.
Sent from my HD+ running CM10 on SD with XDA Premium
judgerey said:
I've got a NC running stock 1.4.3 that's stuck in a boot loop. I've tried everything to either (1) root it to CM7.2 or (2) restore stock Nook os, including trying to fix the partitions as suggested by leapinlar. I think the problem is that there is no eMMC recovery, so when I try to reboot to recovery to fix the partitions, I get bounced back into the bootloop. I tried installing CWM recovery to eMMC using a bootable microSD with CM7 and RomMgr premium, as well as using CWM with some of the eMMC recovery .zip files found in other posts, and it looks like it gets flashed, but when I then try to boot into recovery I get an error "Install Failed (with an icon of the NC and !). I was thinking of trying to flash recovery to eMMC using adb. When I boot with the CM7 microSD, I'm able to access adb from my desktop. Can't seem to find the right files or instructions on how to flash CWM recovery to eMMC using adb. Any suggestions?
Click to expand...
Click to collapse
You ever get it working? This is my underlying issue EXACTLY except I have working ADB when booted from SD card.
40Glock said:
You ever get it working? This is my underlying issue EXACTLY except I have working ADB when booted from SD card.
Click to expand...
Click to collapse
Nope. Never got it working.
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.