I purchased a nook color the other day and successfully rooted and used it for a few days. My youtube would not open so I reinstalled, it ran once and then failed to open again so I gave up on that issue. In reading about youtube app I found that you could get the new market app. I could not get it to install...and in trying multiple things I accidentally deleted my original market app.
I could not get it back so I whiped my nook color and reflashed autonooter. I got all my apps back but I get a connection error when trying to access the market now. I added my account via youtube which again opened once to allow me to sign in and now fails to open.
So I decided to try to reset it back to the way it was out of the box and start from scratch.
I tried the adb 8x reboot method.....it just reboots the nook as it normally would. No bootloader or install screen.
I tried the button method. It works once or twice then it goes through the entire boot. I did it for a half hour and used counts to verify I was doing the process correctly and no matter what I did I could get it to fail boot once and one the second or third it would always bypass and go through with boot even with my finger on the button.
I also am running windows 7 64bit and I cannot get my computer to see "nook" in the device manager for more than a second and it auto installs as a storage device. I've tried to "uninstall" the different devices and last night I was able to catch the "nook" in time to install usb drivers manually but when I reset the nook today my PC no longer see's it again. I was wondering if there is an easier way to install the adb device.
Thanks
UPDATE: Somehow the ADB way to reflash worked the second time I tried it. I also changed some settings in the development menu to fix the device manager issue. I'll update again if I can use youtube and the market.
I don't know what to tell you about everything else but for ADB I would highly recommend adbWireless... it works great on my NC and I never had to install any drivers.
To reset I used the button and counted slow to 15 after the screen gose off each time it worked for me. Good luck
Related
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Do a factory reset, install the update, then use the new autonooter.
how to do a factory reset? thanks, I am a newbie to this area!
Not sure how much I can help-
Just how "bricked" is it?
A truly bricked device will do nothing. It will not start or do anything whatsoever.
A machine that is thoroughly HOSED may get stuck in a boot loop, or try to start and fail every time you press the power button.
When I forced the update manually it took a few minutes to take and reboot; how long ago did it do the update?
Have you tried connecting with adb yet?
Have you tried booting it with a nooter or auto-nooter sd card yet?
http://nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC
Instructions for manually updating.
Here is my situation:
Around 9:30, my NC started updated itself, it reboot in about 15 minutes, and takes a very long time get to the "nook color" screen, then took another 10 minutes letting me select "home or zeam", after that, it has no response.
I tried to reboot, it got up to the "Nook Color" welcome screen, no further response!
I tried to factory reset, not working through adb, it did appear on the adb devices command!
Do a factory reset and start over.
I ran into a similar problem, but here is what happened to me:
1. I reset the device to factory settings.
2. I rebooted the nook 8 times, stopping the boot process. This took my NC back to factory version and no rooting at all.
3. Installed NC update 1.01 per B&N instructions.
4. Used AutoNooter (latest version for 1.01). AutoNooter rebooted the device as it is supposed to.
5. After AutoNooter reboot, I installed Astro File Manager and then after that the NC stopped responding to screen touch.
6. I held the power button to shut the device down. Strangely, the screen shut off and it appeared to be shut down, but I think it did not truly shut down.
7. I could not turn the NC back on. I tried to reset to factory settings 2-3 times and no response.
8. I plugged in my NC as if to charge, and it went through the boot process.
and it has worked just fine since then. To be honest it kind of scared me, because I love this thing to death, but I remained calm and kept at it and it was not bricked. I guess what I'm trying to say is that before you post here that the new update bricks the NC, you should be absolutely sure it is bricked and not just frozen like mine was.
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Brick, like you can't do anything at all anymore, might as well lay it on papers, use it as a door stop and pour cement to build a house?
That's what bricked means... If you still can access it via ADB, run recovery, etc.. it is far from "BRICKED"...
-CC
I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
Hello,
My Nook is completely rooted. I wanted to start from a clean slate. During the wiping and upgrading to 1.0.1 I was prompted to go through the setup which it did. The root happened successfully, however when I look at the device info ==> About your Nook it is currently showing the "Owner" as unavailable. I tried the erase and degregister my nook but it comes up with an error Deregister device failed with error: User Not registered (e_not_registered) Reset device was not attempted. Also, I'm unable to ADB into my nook after I flashed the update for some reason. Any idea would be appreciated, thanks.
The three finger data reset will take you back to the Register screen. Just be very sure you are using the correct login info.
Sent from my Droid using Tapatalk
Which three keys are used, or are you referring to rebooting it 8 times? thanks!
takef0cusin said:
Which three keys are used, or are you referring to rebooting it 8 times? thanks!
Click to expand...
Click to collapse
I was having similar issue as well getting the E_NOT_REGISTERED error. That was the result of trying to upgrade the NookColor firmware to 1.0.1 without deregister the unit first.
The problem was eventually solved after poking around the "NookColor Tools" after rooting. Select that NookColor Tools, then select "Development", then "Deregister & Erase Device". Try one of the option to see which one works for you. The Deregister Only option doesn't work for me, but Master Clear Only worked and after reboot it let me register again and this time I got access back to the Nook Shop.
However it seems there is something wrong with the root as I can't connect to Gmail anymore. Perhaps I need to properly deregister it again before I do any upgrade....
Hope this help.
I too have been having trouble registering my NC to my bn account since i unboxed it. I tried using the method above and ran master reset now my NC won't boot any more...
It seems completely unresponsive :/ Ideas?
EDIT: Removed SD card and it booted up. Cant get past the LogicPD Screen, going to try select "quick setup" this time...
Boots ok, though still getting deregister device failed message :-(
So I selected the other option at boot and got the normal setup screen YAY! when through and selected my wifi etc and hit continue with setup only to be greeted by the familiar error "sorry we're having trouble setting up your nookcolor. Please shutdown the device and try again. it says "BAD1221" at the bottom in grey letters....error code?
So frustrating
Hi all,
I am trying to build a car headunit system using the Asus memo pad 7 ME176CX (k013). I got everything sorted out and the last thing I had to do was to kill the player when the ignition of the car is off.
For that reason I installed llama and made an event to kill the player when on battery. This did not work so I decided to root the tablet so I could force-kill the app.
I downloaded the one-click zenfone root from and followed the instructions. Everything worked just fine and I got the Super SU icon and so on.
Unfortunately, llama still could not kill the process, so I decided I did something wrong and started the un-root.bat file. The process ended with success, but.......I got stuck to the ASUS logo with the loading
indicator below (just before the home screen loads) . I could still connect to the tablet and performed the CheckBeforeAction.bat - it worked just fine. For some reason decided that it would be a good idea to root again and did it - again successfully (or so says the shell).
However, I could not go pass that ASUS logo. So (as if I haven't created a big mess already) I entered into fastboot mode and performed factory reset. That did not help at all.
I followed the instructions and downloaded the stock 182 ROM (I saw the WW version from the fastboot screen), put it in the root of my external 16GB SD card and renamed it.
Well.....when I enter fastboot mode I do not see an option involving SD card. All options I have are droid reboot, something I can not remember but has nothing to do with SD, recovery, power off.
When I go to recovery there I see
- reboot
- apply update from ADB
- wipe data
- wipe cache
Strangely, I can no longer connect to the tablet via USB, so I do not know how to make use of the CWM.
I downloaded ADB_driver.zip and ASUS_Android_USB_drivers_for_Windows_20140325.zip, but for some reason these do not work - I get ERROR 10 when starting the driver.
Well, after all the things (probably really stupid) I did, now I am still not able to boot, but it also looks like I have no more USB access to the device and do not know how to take advantage of the
procedures that I have seen in the different threads.
Is there a way to still recover the device?
Hi, I tried to uninstall YouTube today (yes, I know it's a stupid idea) from my LG V40. All with root. First time using com.jumobile.manager.systemapp, then using Lucky Patcher. Using the LP I remember that I also used the option to replace the factory application (I don't really remember the exact name of this option, but it sounded like it was supposed to replace the application that appears after uninstalling the system application update). It seems that since then uninstalling did a quick reboot, but always successfully. After installing YouTube, I manually rebooted. Unfortunately, the system wakes up only to the inscription with the phone logo. Is there any way to restore the phone? I care most about the data in the form of photos and video - the rest can eventually be wiped. I can't turn off my phone because it's in bootloop all the time. I'm waiting for it to discharge and do it on its own
EDIT
I can go to fastboot mode and EDL mode, but can't see any adb devices from cmd. Anyone know how to see device?