Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Assuming you have a custom recovery flashed (I hope you do) reboot into it and wipe data and cache. It should then reboot just fine into your new ROM. Worked twice before for me.
SandmanGTP said:
Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Click to expand...
Click to collapse
I'll be adding "whipe data/clear cache" to the instruction set of that post.
Related
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
I rebooted my phone to install a font and now it continues to turn on (HTC logo) and then restart. Tried to get into recovery and it just exits...
I had my phone off at night and turned it on - read a few text messages - and went to replace the ****ty font I installed yesterday.
Just looping.
Any help?
Can't even turn it off lol - I would need to go into bootloader and click power down. It is odd - I didn't do anything and it started up perfectly before 5 minutes I did the fonts.
flash the boot and/or recovery?
pwr2wh8 said:
flash the boot and/or recovery?
Click to expand...
Click to collapse
I flashed the recovery with CWM and installed Android Revolution HD 6.1
I was just wondering if it was safe to re-flash the recovery again to see if it would work. I don't want to screw up this phone lol.
EDIT: Got it. Reflashed the recovery and had to reflash the ROM.
I don't know why a simple font change would screw ALL of that up. I don't want to keep flashing this ROM lol it has been about 4 times now.
rowebil said:
I flashed the recovery with CWM and installed Android Revolution HD 6.1
I was just wondering if it was safe to re-flash the recovery again to see if it would work. I don't want to screw up this phone lol.
EDIT: Got it. Reflashed the recovery and had to reflash the ROM.
I don't know why a simple font change would screw ALL of that up. I don't want to keep flashing this ROM lol it has been about 4 times now.
Click to expand...
Click to collapse
The ROMS this phone and everything is new. Give it a little time unless you want to guinea pig for use :cyclops:
I had the same thing when I flashed a power menu mod made for this phone but not for my OTA. Really weird thing is when I cleared the cache android booted did its upgrading thing and then restarted and went back to stuck at HTC logo.
nullkill said:
The ROMS this phone and everything is new. Give it a little time unless you want to guinea pig for use :cyclops:
I had the same thing when I flashed a power menu mod made for this phone but not for my OTA. Really weird thing is when I cleared the cache android booted did its upgrading thing and then restarted and went back to stuck at HTC logo.
Click to expand...
Click to collapse
I have the same...
What ca I do?
Reflash recovery doesn't help.
It keeps restarting...
:crying:
DannySchaukens said:
I have the same...
What ca I do?
Reflash recovery doesn't help.
It keeps restarting...
:crying:
Click to expand...
Click to collapse
You need to reflash what ever was on it. Hopefully you made a backup if not and were on stock find the correct nandroid back or RUU for your phone and flash that. You can also try doing a factory reset that may bring it back.
agreed...try to re-flash everything to stock than go from there to find what is causing 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 cannot get my phone to boot. It started when I was installing updates from the Play Store. It suddenly rebooted in the middle and it hasn't made it past the boot animation since.
When I try to turn it on, it will go through the boot animation and then end with the Verizon logo. The screen turns off afterwards. If I leave it alone, it eventually reboots itself again.
I've had this happen a couple times in the past but it always recovered after a couple of reboots.
This is an unrooted phone. The only sideloaded app installed is SwiftKey Beta. It has that latest 4.4.2 update. The battery was ~50% when it rebooted the first time. It's set to use ART runtime. I've tried clearing the cache from the bootloader AND from fastboot. Neither helped. I really don't want to restore to factory defaults if I don't have to. Advice?
SOLVED: My solution in 3rd post.
TL;DR: Reflashed stock system partition. Turned on and plugged in overnight. Hard reboot via holding down power button for 7-10 seconds. YMMV
You mention Unrooted, does that mean you've never used SlapMyMoto/RockMyMoto/etc or MotoWpNoMo?
If so, and you don't mind re-writing your /system partition (putting it back to stock), you can try option 2 or 3 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . Option 2 will definitely not touch your data/apps. Option 3, if you follow EXACTLY will also not touch your data/apps.
KidJoe said:
You mention Unrooted, does that mean you've never used SlapMyMoto/RockMyMoto/etc or MotoWpNoMo?
If so, and you don't mind re-writing your /system partition (putting it back to stock), you can try option 2 or 3 on -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html . Option 2 will definitely not touch your data/apps. Option 3, if you follow EXACTLY will also not touch your data/apps.
Click to expand...
Click to collapse
Thanks for the reply, Mark.
I actually tried flashing the stock system partition last night shortly after I posted here but it didn't work.
However, I left it plugged in and turned it on once before I went to bed. In the morning, it was still stuck after the boot animation so I held down the power button for about 10 seconds to hard reboot it. I went to brush my teeth and get ready for work and when I came back, the phone had booted up all the way! Reflashing the stock system partition may have helped but I can't be sure.
I've seen this happen before but I think it was after I switched to ART and my sister's Dalvik Moto X doesn't do it. I'll be switching back to Dalvik after this scare.
thebrianiac;52700161I've seen this happen before but I think it was after I switched to ART and my sister's Dalvik Moto X doesn't do it. I'll be switching back to Dalvik after this scare. ;)[/QUOTE said:
Art is still "experimental" and not all apps work with Art.. so.. Its best to stick with Dalvik for now.
Click to expand...
Click to collapse
Hi there
So last night I downloaded android 5.1. I was on 5.0.1.
After it downloaded I didn't install as I had to go out. At dinner I checked my phone and it was stuck on the google boot screen and wouldn't go any further. I went into recovery, wiped cache, but no luck. I went and wiped data/factory reset.. But no luck. It still won't go passed the google logo.
Where do I go from here? My phone is stock everything. Thanks
darrenwo said:
Hi there
So last night I downloaded android 5.1. I was on 5.0.1.
After it downloaded I didn't install as I had to go out. At dinner I checked my phone and it was stuck on the google boot screen and wouldn't go any further. I went into recovery, wiped cache, but no luck. I went and wiped data/factory reset.. But no luck. It still won't go passed the google logo.
Where do I go from here? My phone is stock everything. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked? Can you get into bootloader mode?
darrenwo said:
Hi there
So last night I downloaded android 5.1. I was on 5.0.1.
After it downloaded I didn't install as I had to go out. At dinner I checked my phone and it was stuck on the google boot screen and wouldn't go any further. I went into recovery, wiped cache, but no luck. I went and wiped data/factory reset.. But no luck. It still won't go passed the google logo.
Where do I go from here? My phone is stock everything. Thanks
Click to expand...
Click to collapse
Are you unlocked? Do you have custom recovery.
I haven't touched my phone out of the box. It's completely stock. I can get into that mode by holding "power + volume down," then I can choose recovery, and then I press "power + volume" up to get into the place where you can wipe cache etc.
What's the best option to take from here? Thanks
If it's brand new then you may want to get it swapped out. That shouldn't be happening on a completely stock device. However you might have some luck with the nexus root tool kit. You can fine it here. There may be a way to flash the images on a locked bootloader.
http://forum.xda-developers.com/showthread.php?t=2947452
toknitup420 said:
If it's brand new then you may want to get it swapped out. That shouldn't be happening on a completely stock device. However you might have some luck with the nexus root tool kit. You can fine it here. There may be a way to flash the images on a locked bootloader.
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
I have a feeling the phone got turned off during the install of android 5.1?
I'm really not sure, as I put it in my pocket, and when I took it out an hour later, it was stuck on the Boot screen.
Maybe I pocket dialed into the Android updater.. who knows. This phone does crazy **** in my pocket.
But thanks for that, ill try put unlock + root + custom recovery
Thanks guys for the help.
I ended up taking it back to the store and got it instantly replaced. It was literally on its last day of immediate replacement. Very lucky!
darrenwo said:
Thanks guys for the help.
I ended up taking it back to the store and got it instantly replaced. It was literally on its last day of immediate replacement. Very lucky!
Click to expand...
Click to collapse
Glad you it replaced. It's so weird that that happened on a stock device. Maybe you some how shut it down mid way through the update. Although it's very possible you had a defective unit.