Tonight, my HTC One ran out of battery so I hooked it up to a charger. I wanted to use it but it keeps rebooting every 45 seconds.
It has been over an hour (11:25 pm here) and I don't know what to do, I need my phone and its data tomorrow.
I'm on MaximusHD 30.0 and I didn't do anything weird or out of the ordinary.
Already tried wiping cache and Dalvik, but no cigar.
herbivoor said:
Tonight, my HTC One ran out of battery so I hooked it up to a charger. I wanted to use it but it keeps rebooting every 45 seconds.
It has been over an hour (11:25 pm here) and I don't know what to do, I need my phone and its data tomorrow.
I'm on MaximusHD 30.0 and I didn't do anything weird or out of the ordinary.
Already tried wiping cache and Dalvik, but no cigar.
Click to expand...
Click to collapse
make a /data backup and try deleting the data parition... its possible that the data partition is corrupted throught the instant reboot after the battery ran out. And this would also explane why it reboots that late. And resetting the /data partition (without /data/meida - that's automatically set this way in TWRP and CWM) isn't dangerous if you previously made a bakup
Worst case, flash a different rom
Sent from my HTC One using xda app-developers app
LibertyMarine said:
make a /data backup and try deleting the data parition... its possible that the data partition is corrupted throught the instant reboot after the battery ran out. And this would also explane why it reboots that late. And resetting the /data partition (without /data/meida - that's automatically set this way in TWRP and CWM) isn't dangerous if you previously made a bakup
Click to expand...
Click to collapse
BadAzDB said:
Worst case, flash a different rom
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks guys!
I was able to get into recovery and adb push my rom (took 4000 seconds!). I did a dirty flash and backed up all my info, now I will wipe
everything.
Thanks for the help!
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.
hey everyone, i'm new here. Sorry if this has been posted before, but i'm having a bit of a problem right now.. I rooted my CDMA hero last night. I made a nandroid backup of my phone before i flashed any roms. I flashed a rom and did something wrong, so i tried to restore my nandroid backup... and i got stuck at the "htc - quietly brilliant" screen. i then found out i'm supposed to wipe all data, so i did, and flashed the nandroid backup again.. same problem. so i flashed a different ROM and it loaded up.. so, again, i wiped all data and tried to restore my stock ROM (google didn't back up contacts when it said they were, so i'm trying to restore to get them back)... and i'm STILL getting the quietly brilliant screen. Any help? Thanks!
When you restore - it does take a while to boot up. How much time did you wait on the white screen? Also, did you get any errors during the nand restore?
no, no errors.. and i waited a pretty long time. Enough to allow the "Quietly Brilliant" screen to flash black, then come back up a few times... i'll do another nandroid restore though and watch for errors. But when i did it before, I didn't see any.
this can happen if you don't have enough space on your sd card during the backup. it has been my experience that nand will not give you an error when it runs out of space, everything appears to have completed as it should, but when you go to restore not everything is there, thus causing the phone not to boot.
also as someone else stated the first boot after a wipe can take a very very long time. 10-15+ mins. (this is not always the case)
my advice (for what it is worth) try a full wipe, and load a new rom. another thing to consider is that most (should be all) roms do not come with gapps built in. once you flash the new rom, before you try and boot it, you should also flash gapps. for instance aospCMod will not load without it.
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
daveishere911 said:
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
Click to expand...
Click to collapse
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
aqualls said:
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
no
Sent from my HERO200 using XDA Premium App
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App
BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.
Hi all,
My battery got drained yesterday night and i charged the phone when it was off.
When I'm starting the phone everything looks OK but after a minute its restarting.
I'm using TEAMWIN recovery, so i tried to clear cache and dalvik cache, which did not resolved the issue.
I restored an old backup and that backup works just fine with no restarts what so ever.
What can be the issue? how can i load my phone? even just for 20 minutes so i can backup properly.
Please help!
Could not find a way around it - pushed new rom
get2guy said:
Hi all,
My battery got drained yesterday night and i charged the phone when it was off.
When I'm starting the phone everything looks OK but after a minute its restarting.
I'm using TEAMWIN recovery, so i tried to clear cache and dalvik cache, which did not resolved the issue.
I restored an old backup and that backup works just fine with no restarts what so ever.
What can be the issue? how can i load my phone? even just for 20 minutes so i can backup properly.
Please help!
Click to expand...
Click to collapse
Could not find a way around the issue but i think the cause was an air update (on a rooted phone+TeamWin recovery)
I pushed a "reset rom" (from htc1guru) without deleting data. did all the setup and app downloading during Germany-Ghanan 2-2, so it wasn't that bad .
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Apoplectic1 said:
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Click to expand...
Click to collapse
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
mikeprius said:
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
Click to expand...
Click to collapse
Wiping and then restoring didn't work, stalled in the same place. Wiping, reflashing the ROM and then restoring did for whatever reason.
Thanks for tip!