Develop Bugs

[Q] New ROM keeps re-booting

Hi,
I rooted my DHD today and tried to flash the CyanogenMod-7 for Desire HD & Inspire. It seemed to work but now keeps re-booting every couple of seconds. It won't actually stay on long enough to put another ROM on. Can anyone help? This is the first time I've done something like this and it seemed to be going so well!
Thanks!

Pull the battery for about 10 seconds. Then hold the vol- button down and power your device on. Now you should see a white screen with some text on it. Navigate to recovery and press the power button. Now it should boot into recovery.
In the recovery choose wipe data/factory reset ald let it finish. Once its finished choose wipe cache partition.
Then go to install .zip from sd and then choose zip from sd. Now search for your rom and reinstall it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.

This is common. Simply wait for it to boot and power off or use the power button to select reboot. You only have to do it once.
The instructions for installing CM7 all say to install ROM then reboot after first complete start up. Shouldn't need to reinstall anything.

Having been left alone for a few hours it seems to have sorted itself out. Thanks! I just wasn't expecting it to spend quite so long re-booting.

I guess you have enabled wi-fi just after flash cm7. Seems like there is a bug or whatever, all you need is re-boot device after first boot.
And about the re-boot loop, just remove battery to turn off you device then turn it on, enter recovery and flash cm7 again WITHOUT do wipe operation. OK, In this time remember to re-boot after first boot.

I got a bit trigger happy and tried to flash Android Revolution HD 3.3. I did a full wipe from ClockworkMod Recovery and tried to install the zip, exactly like I did for the previous ROM. That kept aborting the installation so I mounted the phone and re-downloaded and copied it onto the SD card again. Same problem. I then tried to re-install cm7 and that also kept aborting.
I now have the message "Back menu button disabled" and if I use the power button to select anything it goes straight to a white triangle with an explanation and the Droid, which I think is stock recovery? I'm getting there from what I think is Clockwork though. Is this recoverable or have I managed to brick it?

I had a similar issue a few days ago - it turned out that the battery stats were screwed up so a fix for me was to boot into recovery and then wiping the battery stats.
Everything was fine after that.

How do I do that? I don't want to reboot out of Clockwork as I'm not 100% sure I actually have a ROM at the moment.

Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.

mdaigt said:
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
Click to expand...
Click to collapse
open recovery, goto advanced and wipe battery stats

Going to leave battery out for the night as read in other posts. Fixes the problem of not totally shutting down for some. Thanks.

Well leaving battery out didn't help. Continuous boot loop. Put on charger after turning off orange light came on and didn't go to green after 10 hours. Restarted when I got home and boot loop again. Had CoreDroid ROM installed. Working fine than tried to load Kalagas Mixed Theme and that is where I am now. Looping.

Even a blind squirrel will find a nut now and then. During HTC Hboot menu, noticed it was looking for PD98IMG zip. So I shut phone down. Inserted card with it on it and it restored to original firmware. PHEW. Hope this might help someone else.

[Q] Nexus AOKP flash

Hi all,
New to forums and to android in general. Wanted to ask a quick question about flashing through CWM. I am on a Galaxy Nexus, running 4.0.1 (ITL41F), on Telus, in Canada.
I used the Gnex toolkit for root/cwm flash. Initially I had tried 5.4 but I couldnt get into recovery mode; the device would briefly show the (unlocked) google screen, and then hang at what I can only assume is an android error screen (android on its back, front panel open with red arrow pointing up?) before rebooting. After that initial CWM install and recovery mode issue, I was experiencing some random restarts and some freezes on my unlock screen. I resolved to try Gnex 5.5, installing that version of CWM and it allowed a problem free boot into recovery.
I have since flashed AOKP (Milestone 3/Maguro) and the install was smooth. However, after rebooting out of recovery mode my device is hanging on the team kang boot logo screen. It's still animated and I assume the first boot after an install will take a considerable amount of time for configuration/etc....but its been about 25min.
My question, then, is should I wait longer? Or does this length of time indicate a problem with the install?
Thank you in advance for any help.

Go back into cwr and wipe all data, wipe cache and advanced - wipe dalvic. Then reboot
Sent from my Galaxy Nexus using xda premium

Should I be pulling battery to boot? or will holding power turn it off without causing issues from this boot screen?

Hi and welcome
wrongOne said:
Hi all,
New to forums and to android in general. Wanted to ask a quick question about flashing through CWM. I am on a Galaxy Nexus, running 4.0.1 (ITL41F), on Telus, in Canada.
I used the Gnex toolkit for root/cwm flash. Initially I had tried 5.4 but I couldnt get into recovery mode; the device would briefly show the (unlocked) google screen, and then hang at what I can only assume is an android error screen (android on its back, front panel open with red arrow pointing up?) before rebooting.
Click to expand...
Click to collapse
That is no error screen but the stock recovery screen. If you push vol up + vol down +power button again you see the options of stock recovery.
After that initial CWM install and recovery mode issue, I was experiencing some random restarts and some freezes on my unlock screen. I resolved to try Gnex 5.5, installing that version of CWM and it allowed a problem free boot into recovery.
I have since flashed AOKP (Milestone 3/Maguro) and the install was smooth. However, after rebooting out of recovery mode my device is hanging on the team kang boot logo screen. It's still animated and I assume the first boot after an install will take a considerable amount of time for configuration/etc....but its been about 25min.
My question, then, is should I wait longer? Or does this length of time indicate a problem with the install?
Thank you in advance for any help.
Click to expand...
Click to collapse
25 minutes is way to long. Dit you wipe data cache and dalvic cache before flashing the AOKP ROM?
GR36 beat me to it
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
wrongOne said:
Should I be pulling battery to boot? or will holding power turn it off without causing issues from this boot screen?
Click to expand...
Click to collapse
None of the above. Scroll through the options with your volume buttons and choose the right one with the power button (in recovery that is)

Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!

wrongOne said:
Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!
Click to expand...
Click to collapse
Try holding the power button for a few secs. If that doesn't work: yeah... a battery pull will do the trick

wrongOne said:
Sorry, I wasn't particularly clear about my current status.
The device is currently hanging at the team kang loading screen with the animated logo. In order to get into fastboot/recovery I will need to shut down. Is this best accomplished by pulling the battery at this point?
Thanks for the quick responses!
Click to expand...
Click to collapse
Pretty much pull the battery you are boot looping
Sent from my Galaxy Nexus using xda premium

Just wanted to extend a more personal thanks to all for the help. AOKP 4 running perfect now.

CM10 Boot Loop? Help!

I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.

Flightfreak said:
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Click to expand...
Click to collapse
Download mode couldnt get any simpler bud
Edit: just incase if you dont know its down home power button to get to it, find your galaxy s3 firnware (ATT/Bell etc...) and your back stock nonrooted. And then you can root againif you wanna

While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.

mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
Did you read the question bro.. he said he CAN'T go to recovery mode only other option is download mode

No, the option is to boot into recovery and perform a factory reset (which may fix his problem). IF that doesn't fix his problem, he can flash a different ROM from recovery, provided he had custom recovery.
The only difference in getting to download as opposed to recovery is which volume button you use. Chances are if he can't 3 button into recovery, download will be the same result.

Thanks
Got it fixed guys, thanks for the help, now I'm back at Stock Rooted 4.1.1, but am still on the quest for a deodexed rom!

Excellent suggestion - it worked for me
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
I got a Galaxy S III on 23rd Dec 2012 with Ice Cream Sandwich installed. A couple of weeks later it updated itself with a little help from me to the latest Jelly Bean. Since then it's gone into the reboot loop 3 times without any provocation; i.e. I get it out of my pocket and it's in a reboot loop but it had been fine the last time I used it. I tried pressing various buttons alone and in combination and eventually it came out of the loop. At no time did I have to remove the battery. The only mod I've made to it is the addition of a 64GByte SD card, apart from the upgrade to Jelly Bean. I've seen many posts on this problem but yours is the first that confirms my solution for getting out of it. It's obviously a common problem so somewhere there must be a description of what causes it and, hopefully, how to prevent it as it's a real nuisance when you want to use your phone and it's in a reboot loop. If and when I find a definitive article I'll post here again.
Thanks MrHaley.

[Q] Bricked Samsung Galaxy Nexus I9250

i seem to have hard bricked the device and i have been attempting to find a way i can fix it for hours.. i seem to be stuck. Its stuck on the boot animation cyanogenMod logo. I am unable to get into the recovery mode, as well as fast boot mode. i let it sit on that boot logo for hours without anything at all happening. No progress what so ever. Now the biggest thing i am trying to figure out is how i even managed to get this to happen. there was a software update notification that i received, so i figured it may have been the Android L update or something, so without taking into considering what exactly i was agreeing to i accepted, and continued. Let it reboot, and thats how i got to come across this issue. Any suggestions.

So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.

efrant said:
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
Click to expand...
Click to collapse
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.

Jewelzxo said:
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Click to expand...
Click to collapse
What I find strange is that it boots to the boot animation -- that means the bootloader has loaded up the kernel and Android is attempting to start. The bootloader loads up before anything, so it is obviously working. Don't know why you can't access its menu though with the 3-key press. Maybe one of your volumes keys is not working properly? By holding those three keys down, it should not boot to the boot animation...
Can you get into download mode? Hold only volume down and press and hold power. If so, then you can use Odin and flash a stock ROM as per this thread.
In any case, if you can't get into the bootloader or download mode, then your only option is using OMAPFlash (as per this thread). That will re-flash your bootloader. If you still can't get into the bootloader menu after that, then there is a hardware issue.

CM 13 stuck at Reboot animation. Help please!

It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC. It always rebooted perfectly until I flashed the 5.0 version of ElementalX. Then this happened. Hope to hear some input asap as I'm trying my best not to panic. No other kernels are on here except for micro gapp and CM 13. I would remove the battery pack, but might as well get a new phone at that point. I would post a picture but I'm a new user so I'm restricted. Thanks!

legitbeans said:
It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC.
would remove the battery pack, but might as well get a new phone at that point.
Click to expand...
Click to collapse
No need to do a battery pull on this phone, as you know is not really feasible. HTC has already thought that out, and built-in a hardwired button combo that does the same thing. Hold power button+ vol up until the phone reboots (may take a minute or so in the current condition). The moment the screen goes dark to reboot, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and don't let go until the bootloader screen appears. From there, you can boot recovery, connect fastboot, etc.
If the button sequence above fails, its virtually always due to getting the timing wrong, either not pressing vol down soon enough, or letting go too early. Either of which, will result in trying to boot normally (not bootloader) which in your case puts you back stuck on the loading screen. Just repeat until you get it right.
Although, at this point, your battery may have just run out. In which case, you should be able to charge, and just hold power+vol down to boot directly into bootloader.
legitbeans said:
It always rebooted perfectly until I flashed the 5.0 version of ElementalX.
Click to expand...
Click to collapse
Here was your mistake. ElementalX is only for Sense and GPE ROMs, it doesn't work on AOSP ROMs like CM13.
Once you get booted into recovery, you should be able to dirty flash CM13 to re-install the CM kernel, then reboot. Or at the worst, wipe, flash CM13 and gapps again.