Hey guys.
About every 3 days my HTC Desire (Amoled) reboots without any warning and stucks in a loop of the custom boot logo. When this is happening i can only take out the battery and then restart the phone. I already tried two different custom roms (latest Oxygen and latest Modaco) and both have the same problem.
Is there anybody out there having the same problems as me and also having a solution for this annoying bug?
cheers
typie34 said:
Hey guys.
About every 3 days my HTC Desire (Amoled) reboots without any warning and stucks in a loop of the custom boot logo. When this is happening i can only take out the battery and then restart the phone. I already tried two different custom roms (latest Oxygen and latest Modaco) and both have the same problem.
Is there anybody out there having the same problems as me and also having a solution for this annoying bug?
cheers
Click to expand...
Click to collapse
Same my problem
/bump.....
i gotta say this has been happening to me too no idea why
This seems to be a common gingerbread issue. The only workaround I know of is to reboot the phone every day because the chances of getting into a bootloop rise with the uptime of the phone.
Sent from my HTC Desire
Supposed temporary fix found in this thread:
code.google.com/p/oxygen-rom/issues/detail?id=507#c74
I created the script as detailed in that post this morning and gone in to confirm that the permissions were applied on boot as expected, and no reboot yet. Though it's only early days (Just over 12 hours) I was getting the reboots very frequently, and have been using resource intensive stuff today and trying to vary the load in between to try and force it across all the steps that if the explanation of the possible culprit is indeed correct, would have likely resulted in a reboot by now. Will check back in as time goes on and let you know how it goes.
Related
I am having continuous reboot issue when i updates my cell(Desire G2) to Cyanogenmod 7 RC2. I noticed this thing happened first time when i enabled my Wifi and after that its still rebooting again and again... anyone please help. as i have less posts so i am unable to post this in Development forum
arslanshah said:
I am having continuous reboot issue when i updates my cell(Desire G2) to Cyanogenmod 7 RC2. I noticed this thing happened first time when i enabled my Wifi and after that its still rebooting again and again... anyone please help. as i have less posts so i am unable to post this in Development forum
Click to expand...
Click to collapse
1 Power the phone OFF, if you can, or pull the battery and put it back in.
2 Hold down the volume bar and power back on..this should bring you to the fastboot menu.
3 Select the option to reboot into recovery...this should boot you into clockworkmod recovery.
4 try to flash the ROM again.
Yeah, you shouldn't be having such issues. At least, I didn't experience such things. Do as the previous user said and perform a reflash. Good luck!
I had this same issue and flashed back to nightly #12. I've read a reboot/battery pull is all you should need, no need to re-flash till you've tried that first.
Just do a regular old battery pull/reboot. WiFi causes issues on the first boot after flashing. Requires a reboot to get WiFi to work and stop causing problems.
Thanks Everybody simply restarting the cell solved the issue...
Hello,
today I flashed IceColdSandwich 7.0 on my DHD and when I want to shut my phone down it always does a restart. Anyone knows a fix for this?
cheers,
z3xi0n
not sure, but you're probably more likely to get an answer on the support thread for that rom. here:
http://forum.xda-developers.com/showthread.php?p=24364406
Sounds like a clock problem. Strange, I know.
Deselect the time auto-update, and change the time and date to something random.
Turn off, pull the battery before it restarts and leave for a few mins.
Battery back in and restart, reselect time auto update and you should be good to go.
Sent from The App that Time Forgot.
Tried your advice twice, phone reboots again and again ^^ Any other solutions? ^^
cheers ;D
I've been having the same issue since installing 7.x on my device. It got so frustrating that I restored a 6.x image via recovery, but unfortunately the problem still exists. The phone never restarted on shutdown previously, so I'm a bit confused as to what is causing the problem.
I did flash Touch Recovery recently, so might go back to ClockWorkMod Recovery to see if that helps.
So there's some issue with my phone, it started with an issue where my phone would crash, restart, and then go into a booting loop (the samsung logo part). Well after a few retries of installing that rom again (phantom blazer), after that very version of the rom had worked without an issue for 4 months, the crash/boot loop happened again. After this instance, reinstalling the same ROM would not get me into the android OS.
So I moved on to a new rom (paranoid android), which worked for a little while, and then had the exact same issue. After two times in a month of the same crash/boot loop, I moved on to a new rom (wicked sensations). So here I am now with the same issue, but it seems to have gotten worse. Now the crashes happen more often, randomly while in my pocket, and often when trying to place/answer a call, but the frequent crashes are without the boot loop and need to reinstall a rom.
I follow the installation instructions for each rom to the T, all the wiping of dalviks and cache, but the same **** keeps happening. Does this sound like a hardware error in my phone?? Should I return to a stock rom and see if my issue keeps happening? I'm in a rage at this point . Please halp.
I would try this link-http://forum.xda-developers.com/showthread.php?t=1904099. And like you said, see if problems continues. I think any ROM can and will reboot at some point, are you updating your ROMs as developers update them?
Sent from my hybrid GS3
Have you considered your experiencing the 'sudden death syndrome' you may have a faulty power button it's a known issue with the S3. Sprint does repair or exchange the phone for this. It's exactly what you described it powers off and on. It can power up until the splash screen and it powers right down. It just so happens that you start playing with the power button when trying to go into recovery to flash another rom or what not and it clears the issue for a while. Until it sticks again. Just something to consider you can search it here under exactly what I called it 'sudden death syndrome'
Sent from the future via Tapatalk 4
I have been an XDA lurker for years and have never had a need to post since everyone on here is so great about solving issues as they emerge. Anyway I have searched high and low for any answers to my problem with no success. My phone was rooted running a kit kat rom (Dirty Unicorns) when this issue occurred. A couple days ago I sent a mms and noticed my data was off so I turned it on via the power menu and my phone rebooted. Now this is something I have encountered with certain custom roms so I thought nothing of it. The phone went through the reboot process but then it rebooted again after about 3 minutes of normal operation. Since then the time to reboot has gotten worse until now it wont go past the Samsung boot screen. I have tried nandroid restores, cache/data wipes, and finally pushing stock roms via ODIN. None of these change the reboot behavior. Finally, as if everything else wasn't enough, I can no longer flash roms via any custom recovery. This to was something that also degraded over time. At first I was able to flash .zip files for the first few hours but eventually that to would also send my phone into a bootloop. I am clueless what to try next. Any help would be greatly appreciated. Thanks.
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.