Related
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
Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks
just a little baby sized pump...
This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?
Do you have a link for the method you described about? That would be really helpful!
An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!