Database Info

[Q] Help! bootlooping

So i installed latest cm7 nightly 55 and it started normally waited about a minute on the cyanogen mod bootscreen then started looping. any ideas?? i have cwm recovery installed (non nvflash version) if i hold down vol up it goes into a S/W upgrade screen then goes black. holding Vol Up and Down doesn't do anything on a virtual windows 7 pc.

Couple of questions: Which rom were you using before you flashed the nightly? Are you sure it was looping? Sometimes the initial boot after a flash takes a minute or 2.
Needless to say you need to NVflash recovery. Do that for sure whether you're looping or not.

phburks said:
Couple of questions: Which rom were you using before you flashed the nightly? Are you sure it was looping? Sometimes the initial boot after a flash takes a minute or 2.
Needless to say you need to NVflash recovery. Do that for sure whether you're looping or not.
Click to expand...
Click to collapse
Ditto on the above - plus what did you wipe before you flashed? Alos, you might try pulling the battery and starting up again.
You amy not be able to do anything if that does not work until you flash a real recovery. Follow the one-click method on the dev thread - NVflash and recovery all in one package.

Thanks for the input guys, I tried using nvflash but it doesn't pick up the device when I try to install the apex drivers. I am using a virtual machine so I'll try on a regular one.
Sent from my HTC Sensation 4G using XDA App

Actually guys I got a sensation so ill sell the g2x if anyone is interested. I'm gonna include an 8gb sdcard.
Sent from my HTC Sensation 4G using XDA App

You needed to clear the cache and then reinstall the rom. That was my problem.
Sent from my LG-P999 using XDA App

No Boot, No Led light

I had installed Vipers and after a few hours not using it i cant open now my phone. This happened twice. First I got it to boot to fastboot and dont know what I did and now its still not booting up

chev said:
I had installed Vipers and after a few hours not using it i cant open now my phone. This happened twice. First I got it to boot to fastboot and dont know what I did and now its still not booting up
Click to expand...
Click to collapse
Remove battery, reinsert it then try again and see if that works. My guess is that your max screen off frequency is too low so your phone couldnt wake up from deep sleep

I did that a million times. and still not working

Are you under volted at all? If so could be under volted too much.
Have you tried a fresh download and install with a full wipe? Assuming you can access recovery, it might be worth a try. Also out of curiosity have you tried a different battery? Once I had no life, no boot, no led and I switched out my battery and bam it booted back up. That's also worth a try. Best of luck and I hope you get it sorted out soon. Best wishes .
Sent from my HTC Sensation 4G using xda premium

realsis said:
Are you under volted at all? If so could be under volted too much.
Have you tried a fresh download and install with a full wipe? Assuming you can access recovery, it might be worth a try. Also out of curiosity have you tried a different battery? Once I had no life, no boot, no led and I switched out my battery and bam it booted back up. That's also worth a try. Best of luck and I hope you get it sorted out soon. Best wishes .
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Dont have any spare battery to use If only this could go to fastboot it would be easy

chev said:
Dont have any spare battery to use If only this could go to fastboot it would be easy
Click to expand...
Click to collapse
Maybe you left the battery die. It doesnt even show the charging light You should try charging it for an hour remove the battery and charge again, than try to boot. Sesation are known for not booting if the battery dies

Thanks all for the advices, I had my phone sent to the service center for repair or hopefully will get replaced since it was only a week old.

Odd behavior when upgrading to cm10.0.0 on HTC one s

I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?

OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app

CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.

Try TWRP...it will be better
Sent whit HTC ONE S

That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app

Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app

boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.

I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app

jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209

N5 keeps shutting down when rebooting

Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app

Listen like the kernel is the problem. So flash another one (easy way) or go back to stock.
If it's working fine then, it was the kernel which made this happens.
Much success
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app

Ack-nak said:
Phone is rooted with latest TWRP, Cataclysm rom, and Franco kernel. It started happening when I flashed r11 Franco kernel and when I reboot the phone, it shuts down instead. I couldn't start the phone holding down the power button and I held it for over 20 seconds. I thought I bricked my phone. After few minutes fussing with the buttons, it finally booted up. However, every time I reboot my phone, it'll do the same and I had to fuss around the buttons keeping them press down for several minutes before it'll boot up to system or boot loader. As far as I can see, it can boot to recovery & system with no issue. I'm wondering if I need to flash to stock and reflash it again. Anyone knows anything about this or had same issue, please help. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?

abaaaabbbb63 said:
This is what happens: it gets stuck in the rebooting process. It doesn't properly shut down, it just hangs with the screen turned off.
Try flashing the stock kernel. Does it do the same?
Click to expand...
Click to collapse
Flashed with stock kernel and it's still doing the same thing. I also restore back to stock 4.4 with stock kernel and it's still doing the same. Do I need to unroot and root again then flash rom, kernel, and etc? Don't really want to do that if I don't have to but guess I have no choice? Thanks again.

Yep, do a factory reset and see if it's working fine again... I'm thinking so.
CHEERS
Sent from my ME301T using XDA Premium 4 mobile app

Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app

Ack-nak said:
Update: I've decided to just wipe it all and start over by unroot and root again which solved the problem. It's rebooting correctly and not stuck in that awful black screen boot loop. Thanks.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
what do you mean unroot and root again?

biggiephat said:
what do you mean unroot and root again?
Click to expand...
Click to collapse
This means, going back on to the stock firmware. This will remove the root for sure.
After that starting with rooting again.
Hope this answers your question
CHEERS
Sent from my Nexus 5 using XDA Premium 4 mobile app

Bricked my phone?

Hi guys.
I have a problem. My phone is bricked ( I think ). The phone was running, then i got into recovery wiped cache and dalvik chache. Then I clicked reboot and the phone neved booted. What could have happend? Sometimes when the phone gets laggy i do this and neved had the problem.
ps: I have a problem with the battery. Sometimes it show wrong % of battery status. It recharges by it self oO . Could it be the battery?

Have you tried flashing a new ROM? Are you able to boot into recovery by any chance?
Sent from my Nexus S using xda app-developers app

superng888 said:
Have you tried flashing a new ROM? Are you able to boot into recovery by any chance?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
No. Nothing. I already sent it for repear.
Thanks anyway.