Hi, phone was working fine, been rooted and S-OFF'd for awhile but all of a sudden after a reboot it just takes ages, talking about 5 minutes to boot into recovery (It takes about 5 minutes to get past the initial HTC splash screen, it does start loading the main rom but it takes so long I'm not sure if it'll boot into the rom).
Any ideas? I've wiped everything and nand restored some backups I have at various stages, wiped dalvik etc pretty much anything I can think of.
Haven't tried the RUU method yet as the download is going very slowly, any suggestions?
Have access to recovery and fastboot.
What happens if you are going back to the HTC Desire stock rom. And after that rooting your device back again and see what happens.
Or maybe there is something wrong with your phone (Hardware)
Rednasman said:
What happens if you are going back to the HTC Desire stock rom. And after that rooting your device back again and see what happens.
Or maybe there is something wrong with your phone (Hardware)
Click to expand...
Click to collapse
I have to assume it's hardware. Used an .RUU to go back to stock which worked, but even then I have the same issues. Takes about 5 minutes to get past the splash screen, then the Rom takes about 10 minutes to load, and when it does it's just a black screen with 'CONNECT CHARGER' and an unusable slider/touchscreen.
Looks like it'll have to be sent back, shame.
Yes, I think you should send it back. You should use the stock rom if you are going to send it back, I think HTC isn't happy if they see you are using custom roms etc. ^^
Just send it in for warranty, I had something like the same issue (mine was malfunctioning / crashing / no gps etc.) They did a mainboard-swap
Charlesnasi said:
Just send it in for warranty, I had something like the same issue (mine was malfunctioning / crashing / no gps etc.) They did a mainboard-swap
Click to expand...
Click to collapse
Yeah sending it back tomorrow. Just needed to make sure it was hardware
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!
Got a HTC One X a while back and decided to keep it stock as long as I dont find a stable recovery. So my HOX was completely stock. Had no issuses with it for the time I have used it which should be around 15days. I did experience some random reboots. Overheating was a problem too.
Last night was using gameboid to play while watching soccer. After match, I tried to use inbuilt browser but it could not be launched. Everytime I started it, a menu opened with sending a report or not. Then tried google play store to download another browser, but that failed too. Even apps did not upadate. got a error. Dont remember exactly but most probably that was error 492.
Then i decided to reboot. After the HTC quietly brilliant screen, came the HTC ONE screen with some sound, and then hung up there. Tried a hard reboot but same thing happened but this time onwards sound vanished.
So what should I do?
Thought of going to bootloader and then factory reset but I have some important data in HOX and then doing factory reset might not solve the problem.
What should I do?
Just to tell you, Now when I went to bootloader and turned off and back on while plugged to laptop, its still on the same screen but this time its charging.
It does not charge while turned off.
Again,
Im unrooted - completely stock and not unlocked via htcdev.
Edit: The phone is charging now with the power adapter.
Edit2: Just did a factory reset via bootloader , back to normal now.
When still completely on stock and haven`t done anything.
I would say return it..
There would be answers and suggestions but why void warranty.
while my phone hangs up at htc one screen, is there any way the data can be restored? Im assuming running ruu erases everything since its virtual sd card.
I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
liranh said:
I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
Click to expand...
Click to collapse
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
nlooooo said:
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
Click to expand...
Click to collapse
You are quite right, I have dropped it hard and got it wet several times, so it probably is indeed a hardware fault.
I'll try your suggestions, but it seems to me like I will probably have to refund the buyer.
Thanks for your help.
Liran
Try with disassembling and cleaning of all connectors.
I've just refunded the buyer.
Thank you both for your help
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
xdaaccount123 said:
Hi guys
I seem to have an incredibly weird issue on my HTC. It is rooted and running DU 6.0.1.
For some reason, despite the battery being 60%+, whenever I unplug my phone from power it just switches off. If I try to reboot it/go to recovery, it starts up for a second and goes off. However, it seems to function normally when it is plugged in via usb. I can access recovery as well. I have tried to reflash as well as a full wipe, but nothing seems to work.
Im thinking something went wrong with the boot.img maybe ?
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe its a stupid inquiry but does battery work as it should in stock rom? so that you can be absolutely sure its not faulty battery that's creating issues.because two things happen(in my experience when something goes wrong with boot.img) either its stuck at splash screen (hboot) with red text OR it goes blank but not off, just blank
Definitely isnt the battery. I am not experiencing any drain and it functions completely normally when plugged it. When I unplug, it works fine for a few min and then switches off. It will then not turn on, despite it showing 90%+ when I plug it in
but it happens in stock rom also? thats what i wanted to know .if you can full wipe and phone works when connected to usb,maybe you can run ruu and confirm that as well . If you can go to recovery ,make a nandroid backup.and try a ruu.
Yup, happens on stock as well.
Also, I think the recovery is messed up as well since it just crashes now when trying to flash something. It's having issues doing a nanroid backup as well
And no love for exe ruu as well?