I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
shieldsit said:
I used ManualNooter 4-5-18 and then 4-6-16 and then did the permissions fix that they said to do.
Everything worked fine for about 3 days. I went to turn it on it showed the Nook Color logo and froze. Now it won't do anything.
The only thing I can do is boot from SD with ClockWork Mod but it won't read it correctly, can't mount, can restore zip's etc.
Tried to push the Boot.img which seemed to have worked, but when I try to push the System.img it dies with a protocol error and the Nook powers off.
Please please someone tell me they know how to fix this! I can even give access to the machine it's hooked up to and let you have at it!
Click to expand...
Click to collapse
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/showthread.php?t=1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?id=jackpal.androidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
I'll go through these and see what happens, but I wouldn't call what's happening to mine a boot loop. Nothing shows on the screen at all unless I boot from SD card.
And thank you for replying and trying to help me. I'm lost without my Nook. If I get it working I'm not risking rooting it again.
Related
I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.
Incriminified said:
I just powered on the nook, and then it immediately told me that a new software update is being installed. This occurred before the rainbow nook logo. Since I already had 1.01, that doesn't make sense. As well, I hadn't had wifi on the last time I was using the nook. I very recently had 1.0 and was rooted, then updated to 1.01 and auto nootered. I had performed both /system and /data wipes. I can't help but think that somehow, the failed boot counter was incrementing each time I powered the nook on. Either that, or something along those lines. If I'm not using the nook, I generally power it off instead of leaving it in standby. Although not a definite, I would say it has been roughly 8 power offs since I had updated to 1.01. I'm tempted to try that out once I restore this back to they way it was.
I noticed a couple of other people in the forums have run into this.
Click to expand...
Click to collapse
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.
HotShotAzn said:
Easy way to find out. Power off/on a few time. Plug it into your pc and pull the file:
Code:
adb pull /rom/devconf/BootCnt
Open with notepad and see what the boot count is set to.
Or use a file explorer that can see system files (Root Explorer) and open that file on the NC and check the book count.
Click to expand...
Click to collapse
Thanks for that. I restored most of everything, powered off a few times, and checked it out with root explorer. It shows the count as 0. Hmmm, I guess it's not that.
So I'm booting Honeycomb off SD and all was fine and dandy. I got Market setup and all was well.
Well I decided to get a little adventurous thinking there wasn't much to lose and decided to push the system folder for all the GApps in the Froyo walkthrough. Now my Nook just boot loops, each time displaying an activation screen with LogicPD Zoom2 then immediately rebooting.
I have an idea of what is wrong, its trying to run a Google activation when it boots up, but since its the wrong device is boot looping. What I'm looking for is what apk to take off the SD card and in what directory I would find it to get myself out of this pickle. I'm trying to avoid starting over with the Honeycomb build, but it wouldn't be the end of the world.
So I'm thinking it may be OneTimeInitilizer.apk but am realizing I can't access the partition on the SD card directly from Windows. Any ideas
Edit: I may be able to get adb shell for a few seconds before reboot if that helps, I may be able to queue up the commands necessary and get them off in time.
Edit 2: Tried my (most likely wrong) attempt at the above idea. Created a batch file to mount as rw and then run adb uninstall /system/app/OneTimeInitializer.apk but it never worked. Either gave me Failure or "Error: Could not access the Package Manager. Is the system running?"
I could use some help getting my bluetooth to work. I've tried several of the CM7 nightlys, their RC4, phiremod v5, v5.2, and v5.3. They all flash just fine, and work great, except when I try to turn on the bluetooth. When I go to the settings and try to turn it on, it just spends 30 seconds trying then goes back to having it off. I've flashed and re-flashed the system, and have read everything I can find, but don't know what I'm doing wrong.
My steps.
1) Downloaded 8gb_clockwork-0.1-ext4.tar.gz
2) Burned the contained img file to an sd card (used the dd command)
3) Copied system image to sd card (ie phiremod-nook-V5.3.zip)
4) Unmounted sd card and inserted it into my rooted nook
5) Turned nook on
6) Formated /system /data and /cashe
7) installed from sd card, selecting zipped image (ie phiremod-nook-V5.3.zip)
8) when complete, unmounted sd card
9) removed sd card
10) rebooted
11) it always fails to boot the first time, but works find after a restart.
Can anybody see what I'm doing wrong?
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
luciferii said:
What works for me is pressing 'fix permissions' in rom manager then reboot and badabing.
Sent via Tehduck Uberdistro Encore RC4 n.33/Tapatalk Pro
Click to expand...
Click to collapse
That did the trick!, thank you very much luciferii
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
rogerdugans said:
Just a note as I try to avoid "Fix Permissions" when possible-
Anyone with this problem MAY be able to turn bluetooth on by rebooting and enabling it as quickly as possible.
This seems to work most of the time for most people. Not always..
If not, fix permissions and a reboot does seem to take care of it the rest of the time.
Click to expand...
Click to collapse
Why would you avoid fix permissions? It just sets things to sane values.
As for me, the fix I heard and what worked for me was to turn off Wifi, Power off, power back on, turn on Bluetooth and let it init, then turn on Wifi. Now both will turn on.
khaytsus said:
Why would you avoid fix permissions? It just sets things to sane values.
Click to expand...
Click to collapse
Two reasons:
#1) While I am not afraid to mess with root access or abilities I also try to avoid doing so whenever I can. If I don't NEED to, I don't. Same way I work on my linux computers. And if I have done nothing to mess perms up they SHOULD be ok.
#2) I think the simplest fix is best, every time. (As long as it actually FIXES the problem, of course.)
If all that is actually NEEDED is a reboot and turning on bluetooth quickly, why do anything else?
Hey guys I picked up a Nook Color yesterday and attempted to root the device but failed. It came stock running 1.2, so after doing some research I found I would need to use manual nooter over autonooter. I'll give full details below but I followed the instructions at these 2 links:
http://forum.xda-developers.com/showthread.php?t=1054027
http://forum.xda-developers.com/showthread.php?t=987735
I went through the instructions and was able to root the device. After the root process I booted into Android and successfully installed some app's. I attempted to reboot the device again just to test stability and this is where it went downhill. The device would continually display the nook color image looping one after another; it would not fully boot. In order to return to stock I held the power button, up volume, and n button and restored the device.
Some details:
win32diskimager - During the process of making a boot-able ClockworkMod SD win32diskimager version .2 and .3 will gives me an error saying - "Not enough disk space". I used version .1 for my attempt and it let me burn. I have a 2 gig SanDisk MicroSD card and downloaded 2gb_clockwork-3.0.2.8.rar. Not sure if this is even related to the error.
Before root - I copied an epub book over to internal memory.
App's after root - I installed Angry Birds, Crazy Snowboard, Dophin HD, Facebook, Twitter, Flash 10.3, Google doc's. I also followed the steps in the links from the instructions above (setting up marketplace).
What do you guys think is going on here? The only problem I saw was with the disk image, but I don't want to buy a new MicroSD unless I really need to. It was weird that I was able to boot once after root, but after rebooting that's when it fails; like I installed something bad. Anyone have any recommendations for me? Also is the power button, volume up, n button trick a pretty solid way to restore? I was worried!
Thanks.
joey-g said:
Hey guys I picked up a Nook Color yesterday and attempted to root the device but failed. It came stock running 1.2, so after doing some research I found I would need to use manual nooter over autonooter. I'll give full details below but I followed the instructions at these 2 links:
http://forum.xda-developers.com/showthread.php?t=1054027
http://forum.xda-developers.com/showthread.php?t=987735
I went through the instructions and was able to root the device. After the root process I booted into Android and successfully installed some app's. I attempted to reboot the device again just to test stability and this is where it went downhill. The device would continually display the nook color image looping one after another; it would not fully boot. In order to return to stock I held the power button, up volume, and n button and restored the device.
Some details:
win32diskimager - During the process of making a boot-able ClockworkMod SD win32diskimager version .2 and .3 will gives me an error saying - "Not enough disk space". I used version .1 for my attempt and it let me burn. I have a 2 gig SanDisk MicroSD card and downloaded 2gb_clockwork-3.0.2.8.rar. Not sure if this is even related to the error.
Before root - I copied an epub book over to internal memory.
App's after root - I installed Angry Birds, Crazy Snowboard, Dophin HD, Facebook, Twitter, Flash 10.3, Google doc's. I also followed the steps in the links from the instructions above (setting up marketplace).
What do you guys think is going on here? The only problem I saw was with the disk image, but I don't want to buy a new MicroSD unless I really need to. It was weird that I was able to boot once after root, but after rebooting that's when it fails; like I installed something bad. Anyone have any recommendations for me? Also is the power button, volume up, n button trick a pretty solid way to restore? I was worried!
Thanks.
Click to expand...
Click to collapse
It sound to me like you installed flash 10.3 without uninstalling the old flash. If that is what you did, follow the directions HERE to get back to a clean install. Then when you are back up and running, download “Titanium Back” from the marketplace, then uninstall flash, and then update to flash 10.3. Let me know if you run into any problems along the way.
awesome thanks! I'll try it out tomorrow.
This also happens if you try to update Adobe Air without uninstalling. Again, Titanium Backup can remove it for you.
Hi,
I have a Nook HD+ which i run with CM13 (cm_ovation-ota-MOB30D.160422) and I've run now into a bizarre problem:
Last week, suddenly the nook started over night to get into an infinite reboot cycle where it goes throught nook start up screen, then cyanogemod universal boot loader screen followed by the pulsing cyanogemod logo. Sometimes it gets to the login screen, sometimes it reboots before but never did i manage to log in.
Trying to restore now older nandroid backups and/or flashing different ROMs and they all fail as they cannot properly update /system (restore fails as it fills up the filesystem even though i haven't resized /system and it definitely was not full at the time of backup; flashing ROM fails as it complains that after update /system did contain unexpected content.
Starting to tinkering with adb shell, i notice that any changes, e.g., adding or removing files, i do on the internal storage (be it /data or /system) seems to be reflected by ls in the same mount cycle but as soon as i umount and remount the device the state is restored to the old state! Similarly, any mkfs.* run without error on the various /dev/block/mmcblk0p* but nothing really changed if i remount the same device after that (i.e., content is not wiped and filesystem type is still what it was before). [the same happens if i try the various wipes/factory reset options in the recovery. No error but no effect].
Note this all happened regardless of recovery (CWM 6.0.4.6 / TWRP 2.8.7.5; the former via external sdcard, the latter internal to the nook). Also strangely, as i boot "normally" (and end up in the boot cycle) i can't run adb logcat as the device is listed as 'unauthorized'. Also for some operations with CWM it warns me at the end that ''root access possibly lost' and asks me whether i want to fix /system/xbin/su) [but either option i choose doesn't change the noticeable behaviour]. Lastly, the whole boot cycles and actions in recovery are very sluggish.
This almost sounds like there is a rootkit on the nook which masquerades the changes but ignores them to stay in control. However, googling i didn't immediately found any hits referring to such a rather sophisticated rootkit.
Did anybody ever see such a behaviour and/or have an idea what's happening? Any thoughts to reset the whole device?
-michael-
PS: Strike-out above part about unauthorized device for logcat: i was trying to do logcat from a device which apparently i've never used before for the nook; doing it on another one which i've previously used allowed for logcat to work but the log itself didn't really give any insights and the adb logcat died a few seconds before the nook rebooted, so i don't have any of these criticial parts of the log ...
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Sent from my SM-T707V using XDA Premium HD app
leapinlar said:
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Click to expand...
Click to collapse
Hi Leapinlar,
thanks for your feedback: Rather surprising (& unfortunate) behaviour but still better than a rootkit
I guess so my option are only to install/boot CM from an sdcard (or getting a new device)?
-michael-
BTW: to run CM from sdcard i guess i need a no-emmc ROM (even though my emmc still works read-only and i can boot recovery from it)? If so, the latest one i found is https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/ which is rather dated. Is there anywhere a new one or some pointers one what all has to be changed to make a emmc ROM turn into a no-emmc ROM so i could try changing a ROM myself? Thanks!