Title says most of it. I have just rooted via Nooter 3 and installed CWM 3.0.0.5 via rom manager (possible cause?). I attempted to do a backup, which worked flawlessly, and I then did a reboot, which caused it just reboot back into recovery. Known issue, I know. After that, though, I prepared to do the update to 3.0.1.0 and...I discovered its completely frozen. Like, 100% stuck in recovery, buttons do nothing, no navigation, nada.
Is there any way to get out of this, or am I basically stuck waiting for it to run out of juice?
EDIT: never mind! Holding down both volume buttons and power fixed it.
Related
Hi Folks,
I had a CyanogenMod-6.1 for Nexus One :: V6.1.0-RC1 (10/28/2010) installed on my Nexus 1.
Prior to that i was using CM6.0 RC1 stable release. Did an upgrade (with full void and nandroid backup) to try out the new features.
However this afternoon, out of nowhere, my volume buttons and trackball started to malfunction.
i.e to say : I cannot adjust volumes in any part of the apps/phone and i can't select/click stuffs with the Trackball.
Hence, I thought of removing CM6.1. Here's the problem started.
#1. I can't boot into recovery. The phone itself will be stuck at the big "X" screen. After 5mins, it will boot into CM6.1
- Using ROM Manager i tried to reflash Clockwork Mod 2.5.1.0 for a couple of times but i still cannot get into Recovery.
Be it powering up with trackball held down, booting into recovery up via Rom Manager. Surprisingly, volume down was working together with power down was able to go into Bootloader
for me to select "Recovery", however, i still can't access Recovery.
#2. I tried using ./fastboot-mac flash recovery updatedclockwork.img also can't.
#3. I tried using Amon-RA. ./fastboot-mac flash recovery Amon-RA.img also to no avail.
#4. i used ./fastboot-mac update to load a StockFRF91 Froyo also can't get into recovery.
As of now, my phone is stuck continuously in bootloop, cannot access Recovery. I've tried almost 30+ fixes on XDA and other Android Forums but i still can't fix it.
Is there anyway, i can wipe everything inclusive of the "Corrupted Recovery" files and restore back my Nexus One?
Thank you all please save my phone! :'(
Dude I feel your pain. I have the exact same problem. I wonder if it is a CM6 issue?
ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.
Hi, I rooted my nook some time ago, and ever since then I noticed that when my battery goes completely dead, and I recharge it, my Nook will hang up on boot. It doesn't matter how long I leave it on the charger, but when I boot up, it just hangs on "Touch the future of reading." My solution so far is restore a nandroid with clockwork recovery, and that always works, but of course, it's not ideal. Does anyone have any suggestions?
Also #2 question: Will updating to 1.1.0 software on the B&N site mess up my nook if it's already rooted? I was hoping to update it without having to reinstall everything.
Thx.
issue solved...
The problem with my nook booting after power discharge is solved by booting into clockwork recovery, going to "advanced" and selecting the first option... I think it's called "fix boot" or something.
So the system restore was unnecessary, being as that solves the issue.
Just had this happen to me this morning, the option is "Reboot Recovery". Thanks!
Had to remove SD card
I was having the same problem, but I couldn't even boot into recovery. Once I tried this a couple times, I removed the SD card and tried again, and it booted normally.
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.
Hello all. First of all, the issue I have is not major, just an annoyance that I want to get rid of.
So, I decided to flash 6.0 stock zip/update through the stock recovery but at some point it got stuck. At that moment, I was in a hurry so I had to unplug the phone and quickly flashed TWRP. I did a 5.1.1 AOSP nandroid backup before so I was all safe. But I noticed that, after successfully restoring the backup, it would boot me back into recovery whenever I tried to boot directly into system.
So basically, the only ways I found out I can boot into Android is through the bootloader and choosing Normal Powerup or doing fast reboots. And, based on what I think, everything that uses the "reboot" command, like in terminal, will kick me directly into the recovery (holding the power button and rebooting normally, doing a hard reboot, rebooting through apps or terminal, booting when phone is off or starting to charge from a depleted battery).
How can I fix this problem? Did anybody else encounter this as well? Thanks in advance!