Develop Bugs

[Q] Constant Bootloops ARRGHHHH

Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!

it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?

xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.

Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.

If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App

hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.

http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App

same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.

No good man I hope you got insurance
Sent from my PC36100 using XDA App

Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App

same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?

These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App

dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...

xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.

[Q] Think Ive Bricked my DHD

I recently installed pyramid 1.1 on my DHD after the full ace wipe from this thread http://forum.xda-developers.com/showthread.php?t=1281894.
I then found a file on page 23 (UOT-10-07-12-33-1.zip) which i think installs a bat icon i was looking for, i then went to reboot but got stuck on white t-mobile screen. I took bat and tried to boot into recovery to correct it, which worked, reapplied wipe and pyramid 1.1 but half way through installing the rom my phone freaked out - 5 short battery vibrations and solid green light - screen off. Now any time i try to power on this is what happens. Even when trying to vol down/power on to get into recovery. Is there anyway to get my phone into recovery from Off using my PC? Is my phone dead for good? PLEASE HELP!!
PS the same 5 vibration thing happens when I plug into PC from phone switched off. Pretty worried now.

Weeeeew.
Damn, what recovery were you using?
Sounds like a HardWare failure..
Sent from HydrOG3N MOD DHD.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.

do you have adb?
use
Code:
adb reboot recovery
Check to see if the rom you downloaded was corrupted or not and retry downloading it.
From there i suggest you do a complete wipe and clear cache within recovery.
Then flash a new rom.
Edit: I'm going to move this to QA thread.

zadok1873 said:
I recently installed pyramid 1.1 on my DHD after the full ace wipe from this thread http://forum.xda-developers.com/showthread.php?t=1281894.
I then found a file on page 23 (UOT-10-07-12-33-1.zip) which i think installs a bat icon i was looking for, i then went to reboot but got stuck on white t-mobile screen. I took bat and tried to boot into recovery to correct it, which worked, reapplied wipe and pyramid 1.1 but half way through installing the rom my phone freaked out - 5 short battery vibrations and solid green light - screen off. Now any time i try to power on this is what happens. Even when trying to vol down/power on to get into recovery. Is there anyway to get my phone into recovery from Off using my PC? Is my phone dead for good? PLEASE HELP!!
PS the same 5 vibration thing happens when I plug into PC from phone switched off. Pretty worried now.
Click to expand...
Click to collapse
Try pulling battery out for a few minutes, then try to go into recovery or as the post below suggests try going in via your PC using adb shell command
Sent from my HTC Desire HD using xda premium

Thanks for the help guys. Phone is now functioning but only in SAFE MODE. Please see this thread:
http://forum.xda-developers.com/showthread.php?t=1296698

Phone restarts and won't turn on

For the past several months my phone would restart randomly when I used 3G, GPS or sometime just from heavy usage. It would turn off, boot to the white HTC screen but then the screen went black and it would vibrate 3 times and a led would blink. At that point the only way to turn it back on was to pull the battery and power on (although that usually didn't work until after a few tries or letting it sit for a while).
It has done this with both CM7.1 and decks 1.3 and with the Tiamat 3.3.7 & 4.1 kernels. I flashed Mason .14 on Tuesday hoping it might fix the problem. It did at first but after 24 hours it was back to restarting randomly, only this time it was worse. I was also getting a lot of force closes and it would restart even it was sitting unused. It would take hours until I could get it to successfully boot again. I attempted to do a full wipe and install CM7.2 yesterday only to find out I can not boot into recovery, attempting to do so causes the phone to turn off (I tried both through holding the power button and selecting recovery and through the bootloader).
As of right now my phone will not turn back on at all (going on 4 hours), I've had it successfully boot twice only to immediately turn off, other times it gets stuck on the white HTC screen.
I am still able to access the bootloader so I'm thinking my best option may be to place a PC36IMG.zip on my sdcard and see if I can't flash back to stock and then load CM7.2. My concerns are a) not sure if that will even work b) if the phone were to turn off in the middle of that would it completely brick my phone?
Sorry for the long post but I just wanted to provide as much info as possible. Any thoughts/suggestions would be greatly appreciated.

Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium

scottspa74 said:
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Unfortunately that doesn't work. Flashes the recovery just fine but I still can't access it. I did manage to get my phone to boot into android after trying, not sure if that's a coincidence or not.
So I'm left with my original option, flashing a stock PC36IMG.zip. Also this might be a dumb question but can I rename anything PC36IMG.zip and flash? If so I could just rename Calkulin's format all, flash that and then repeat the process with CM7.2. Anyone know if this will work?
Edit: Should probably also ask if anyone knows what is causing this, is it a kernel issue?

Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium

imheroldman said:
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I was able to flash back to stock and it is still having similar problems. Turns off during any sort of data usage both 3g and Wifi. The fact that it has happened on multiple ROMs, multiple kernels, and multiple radios makes me think it is something hardware related. I guess I will talk to sprint and see what they can do.
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.

mcotter said:
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
Click to expand...
Click to collapse
Well after going back to stock but still being S-Off I decided to try reflashing Amon_RA and I eventually got it to boot into recovery. It was similar to booting into the OS, I just had to pull the battery and wait 30+ mins before trying and then boot into bootloader and select recovery. It was a PITA since I needed flash a couple things but it worked. Got it back to S-On and took it to Sprint. Of course they didn't bother checking for any of that haha but I was able to get a replacement EVO.

[Q] BRICKED! Bootloop VZW HELP!

Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.

seanrobot said:
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
Click to expand...
Click to collapse
Fastboot seems the best solution to me. What exactly went wrong? Also you could try a OMAP flash.
Sent from my Galaxy Nexus using XDA Premium HD app

To be honest I have no idea what happened. It happened out of no where didn't flash a new rom or anything. OMAP flash? Never heard of it but I'll definitely look into it and try it. I've tried fastboot method and still got the same problem sadly

Really hoping this isn't a hardware issue

I just tried an OMAP Flash and still have the same problem. Ive moved on to a new phone but I still want to get this one working. Any other ideas to fix this problem?

Got into the same problem as yours. I googled around, and most people fix this problem by flashing stock image. Basically wipe your phone clean, e.g system,data,cache etc. and then flash in the stock image u downloaded from google website throught fastboot mode. I tried that method, but my phone is still stuck in bootloop. You can give it a try and see if it works

[Q] Phone is going nuts!!! Help!! PLEASE!!!

Ok so, I have been running Hyperdrive RLS16 for quite sometime now with no issues, going on approx 6 months now. Love the rom. Just today out of nowhere my phone started timing out. By timing out I mean, screen started going black as if I was closing it when I was in the middle of using it. This proceeded to happen for at least 15 minutes meanwhile it was constantly rebooting itself as well. After about 15 mins of reboots and screen timeouts, it got to where the phone would not stay on. it would boot up, then when i started using it it would reboot again. So after a battery pull, sd card pull and sim card pull I restarted it and since it seems to be doing ok for the moment. I immediately backed up my rom in clockword mod recovery through rom manager, backed up all my apps and created an update.zip in titanium backup. I downloaded the stockmod slim rom t999 4.3 v3 and the uvuemj4 modem that it requires for data and was gunna try and flash it and everytime i boot into recovery and try to select an option to pick, it randomly starts selecting things and jumping all over the place and then reboots. wont let me wipe data factory reset, or wipe dalvick or cache. wont even let me choose the rom or modem to flash. I tried to update my version of clockwork mod, and nothing. Tried to download goo manager and try twrp but it wont go into twrp it stays in clockwork mod and does the same. Im so confused on what to do to fix this and would like to flash a new rom to see if it will fix my screen timeouts and reboots but I cant get recovery to cooperate in order to do that. Can anyone help me? PLEASE!!!! I thought maybe if i try clockwork mod touch that it may fix the problem, but even if i download it how can i flash it if recovery isint cooperating?:crying::crying::crying:

kbeezy2686 said:
Ok so, I have been running Hyperdrive RLS16 for quite sometime now with no issues, going on approx 6 months now. Love the rom. Just today out of nowhere my phone started timing out. By timing out I mean, screen started going black as if I was closing it when I was in the middle of using it. This proceeded to happen for at least 15 minutes meanwhile it was constantly rebooting itself as well. After about 15 mins of reboots and screen timeouts, it got to where the phone would not stay on. it would boot up, then when i started using it it would reboot again. So after a battery pull, sd card pull and sim card pull I restarted it and since it seems to be doing ok for the moment. I immediately backed up my rom in clockword mod recovery through rom manager, backed up all my apps and created an update.zip in titanium backup. I downloaded the stockmod slim rom t999 4.3 v3 and the uvuemj4 modem that it requires for data and was gunna try and flash it and everytime i boot into recovery and try to select an option to pick, it randomly starts selecting things and jumping all over the place and then reboots. wont let me wipe data factory reset, or wipe dalvick or cache. wont even let me choose the rom or modem to flash. I tried to update my version of clockwork mod, and nothing. Tried to download goo manager and try twrp but it wont go into twrp it stays in clockwork mod and does the same. Im so confused on what to do to fix this and would like to flash a new rom to see if it will fix my screen timeouts and reboots but I cant get recovery to cooperate in order to do that. Can anyone help me? PLEASE!!!! I thought maybe if i try clockwork mod touch that it may fix the problem, but even if i download it how can i flash it if recovery isint cooperating?:crying::crying::crying:
Click to expand...
Click to collapse
It sounds like there would be a problem with your digitizer. Or motherboard. Either way it sounds expensive to fix.
Sent from my Galaxy NexusL using Tapatalk

The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
jmcoffey said:
It sounds like there would be a problem with your digitizer. Or motherboard. Either way it sounds expensive to fix.
Sent from my Galaxy NexusL using Tapatalk
Click to expand...
Click to collapse

kbeezy2686 said:
The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
Click to expand...
Click to collapse
I don't use cwm so I wouldn't know. But your didgitizer could still act like its working fully and still be broken. Idk man.
Sent from my Galaxy Nexus using Tapatalk

ok well thanks man for your help. Would the digitizer be causing the random reboots as well?
jmcoffey said:
I don't use cwm so I wouldn't know. But your didgitizer could still act like its working fully and still be broken. Idk man.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse

kbeezy2686 said:
ok well thanks man for your help. Would the digitizer be causing the random reboots as well?
Click to expand...
Click to collapse
If it's malfunctioning is possible. But there's no telling.
Sent from my Galaxy Nexus using Tapatalk

Can you boot download mode? Odin flash stock firmware. If it continues then it may be a hardware problem.

i havent tried to do that. But i did do a factory reset from my settings instead of through recovery. I did lose quite a bit of stuff because it deleted my backups in titanium and etc but my recovery is working now. No more ghost mode selecting everything. But my phone is still doing the random reboots
DocHoliday77 said:
Can you boot download mode? Odin flash stock firmware. If it continues then it may be a hardware problem.
Click to expand...
Click to collapse

kbeezy2686 said:
i havent tried to do that. But i did do a factory reset from my settings instead of through recovery. I did lose quite a bit of stuff because it deleted my backups in titanium and etc but my recovery is working now. No more ghost mode selecting everything. But my phone is still doing the random reboots
Click to expand...
Click to collapse
Did you flash another ROM and its still rebooting?
Sent from my SGH-T999 using Tapatalk

kbeezy2686 said:
The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
Click to expand...
Click to collapse
Earlier I too felt this type of auto touch in my other device and I figured out that this was happening due to some radio interference at some particular time and particular place which was near a radio station
Whenever I go away or that station time was over it will be working correctly
May be something like this happening just for your information to make sure
Sent from my SGH-T999 using Tapatalk