Develop Bugs

[Q] Bizarre reboot, boot loop issue

Hi all,
So the history is I had CyanogenMod6 on my Desire and was using OsmAnd in the car with the car charger plugged in. The phone reset so I started it again, reopened OsmAnd, then it crashed again. It stopped on the HTC white logo so I removed the charger and weirdly it then booted. When it crashed a third time then it stopped on the white HTC logo and wouldn't go further, regardless of whether the charger was in or out.
I've tried removing the battery etc, but that made no difference.
I've now flashed back to the 2.29 RUU using PB99IMG.zip on the goldcard. This loads fine and all is well, but then every now and again it resets and sticks on the HTC screen again. Also I turned it off once to put my normal SD card back in, and restarting it gave me the white HTC screen. Huh??
Can anyone help please? I need this phone for work and having it die on me and needing an RUU reset (so ALL my data is wiped) is a proper pita.
Thanks.

If its only doing it using osmand then don't use it. Use something else. If its doing it without using it do a full factory wipe, then format the system and boot mounts then reflash. You should be alright. If your still having issues, you might need to use an ruu but you would need to root again.
Sent from CM7

Meaple said:
If its only doing it using osmand then don't use it. Use something else. If its doing it without using it do a full factory wipe, then format the system and boot mounts then reflash. You should be alright. If your still having issues, you might need to use an ruu but you would need to root again.
Sent from CM7
Click to expand...
Click to collapse
It first reset using OsmAnd and Google Navigator but now I have reflashed back to the stock HTC 2.29.405 RUU using PB99IMG.zip and it's still doing it during normal use.
I'm also getting the HTC white screen when I just turn off and back on.
When I flash the stock RUU, does that reformat the system and boot mounts? I know the phone feels like everything is gone since I have to reenter my google acc details.

Yeh, an RUU will completely wipe the whole phone, the boot, system, data, recovery, hboot, cache and what ever else there is, all gets replaced. Yes it is a pain but it will return your phone back to stock and if your still getting errors, then most likely it will be a hardware issue, specifically, the motherboard. Tbh, it's a small price to pay instead of having to send it off.

Random Restarts

Hello every one,
I am new to the forums and have been looking around for some time. I have a major issue that I need some assistance with if possible.
I am running, well was running, gingerbread 2.3.3 on my HTC Evo 4g phone until yesterday night. Here is some info about what happened. I rooted my phone with revolutionary and everything was going good til I tried to install a new ROM on the phone. The ROM I was downloading was CyanogenMod7, When it finished downloading, the phone booted itself into recovery to install the ROM. Well this is when the problem started, it just sat at the install screen and when it got down with the install it just continued to boot itself into a loop.
I turned the phone off and tried to boot it into recovery, which it did by the way. I did a complete restore of the stock ROM and rebooted the phone, when the phone turned back on is when the phone just continued to restart itself over and over again. So, I did a complete wipe: Recovery, Clear storage etc and nothing seemed to work but instead of it restarting itself, it just sits at the recovery screen and wont go any further. Just like it doesn't have any OS installed to boot from.
I would like some help and see what I can do to fix this problem.
When I go to recovery and boot from the fastboot-bootloader it says:
SD checking "No Image" Loading...
No Image,
loading.....
No image,
Loading....
No image or wrong image....
Click to expand...
Click to collapse
on top of that the sd card well not mount to the phone. I am so lost right now.

Some one pelase help or point me in the right direction.

Which recovery are you using for this? Maybe you can actually get it together by doing a complete wipe and cleaning cache/dalvik and then do the recovery.

I am using the clockwork recovery v3.0.0.5.
Every time I try to wipe the Dalvik Cache it tells me
E:unknown volume for path [/sd-ext] Dalvik Cache wiped
Click to expand...
Click to collapse
I still get the same thing. The one issue that I have encountered was that the sd card is not mounted to the phone. I have android sdk tools installed but the program can't seem to find my phone when I run the command prompt. The other things is now my phone just randomly shuts down and the the battery light just blinks, like its in stand by mode or something. The only thing I can do is take the battery out and what, then replace the battery and see if it works.

Try to charge the battery without using the phone that way you can work with it. My suggestion is to use Amon-RA recovery. Works a whole lot better that Clockwork. And try from there if you can install the ROM right.
It might be problems with your SD card. If is not reading it then that would be the message.

I tried that and nothing, I gave up on trying to save the phone that I went and got a replacement for it.

Did I just BRICK my G Nexus?

So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.

Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom

My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..

i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).

i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk

The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.

Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?

i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium

And that might fix this charging bootloop? Because the LCD doesn't even turn off..

i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium

+1 for the new battery thought.

Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.

GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.

Galaxy nexus keeps rebooting

I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??

There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)

....

FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.

I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.

I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.

Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.

630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.

So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.

That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.

I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....

I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]

Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.

I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.

2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?

after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone

I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.

I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!

[Q] JellyTime gets stuck on bootanimation

Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.

You could try dirty flashing, but if that doesn't work you'll have to reflash.

bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime

Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3

GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.

910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!

Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.