Hi everyone,
I've got a problem. My rooted desire running ReflexTSenseHD v1.8. Last night the battery went dead or so I thought then. Anyway when I got home and I tried to charge it nothing happened. Tried a few things (battery out, battery in) and finally got it charging.
The next morning I tried to boot it and but it hangs on the white HTC screen. Took the battery out, tried it again still the same screen. Took the battery out again and tried it one last time. I booted it in the bootloader and cleared storage. This time it booted, but when it finaly got to the lock screen it said: connect charger but couldn't get it off the lockscreen. Took the battery again and this time it booted normally and worked like nothing happend.
After a few hours I got curious if it would boot normally right away. But unfortunately, the whole thing started over again.
I searched the web, but couldn't find anything like this. The white htc screen freeze is known, but that is usually due to a broken/ faulty bootchip which in my case is not likely because I can boot (sometimes).
I haven't got a clue what to do next but hope any of you do.
Thanks for reading this, and hope that somebody has a solution.
Robit
ps sometimes I can boot in recovery but most of the times it will hang on the white htc screen.
Try boot into recovery and wipe the boot, cache, system, data, dalvik cache and do a factory reset too. What on a fresh rom. If you can't be bothered with that, use an ruu which will do a fresh everything, even the bootloader. If things still are messing up, talk to HTC it your carrier.
Sent from CM7
Thanks somehow I got into recovery and wiped it all, and so far so good
Sent from my HTC Desire using XDA App
unfortunately the issue has returned. So far I figured out that if I wait long enough, it will boot but then hangs onto the lockscreen, show the empty battery and says connect charger. I can't unlock it so the only way of rebooting is to take out the battery and start it again.
I just don't get it. It can't be a faulty bootchip, I suppose it wouldn't boot at all then.
I already tried the steps above from meaple but this time I hadn't so much luck. In booting it again.
I'm getting a little desperate by now so any help would again be appreciated.
Robit
ps: I'm on a new rom the RCMixHD v3.6 which at first worked like a charm.
I went for a run yesterday with my phone and it got a little damp. Really only a little. I'm really surprised I'm having issues as it has gotten more wet than this in the past.
When I got back I need to charge the phone but when I plugged it in it wouldn't start charging. I've had that issue before so I pulled the battery, put it back in plugged in the charger to charge while powered off. Needed it to charge fast. Anyway, Tried to boot it again, (running CM9, 0522 nightly) and it was hanging on the boot animation indefinitely.. Tried clearing cache, davlik, battery stats, everything and it wouldn't work. I tried a nandroid backup and it took forever and gave an error while backing up data. I tried again and it threw an error instantly while backing up the bootloader.
I gave up and did a full wipe and tried to reinstall CM9. No luck.
I wiped it again and luckily had a copy of HDRevolution still on the phone so I installed that after running the "super wipe" app for it. It booted to that just fine.
Tried CM9 again and it didn't boot. Freakin frustrating.
Any ideas on what to do here?
If you booted to a useable state, then you don't need to worry about water damage. Download cm9 again and reinstall
Hey guys, so I have this big problem I have never seen before.
My Verizon Galaxy Nexus keeps turning itself off after about 1-2 minutes of turning on. The only way to turn it back on is to do a battery pull. This started when I upgraded the Franco Kernel to the latest version which I think is #350 I believe. I thought it was the kernel at first so I booted into recovery and flashed Tinys Kernel. Needless to say it turned off again. It would make a weird flash transition as the screen would shut off. I then wiped data, wiped cache, wiped dalvik, flashed Muzzys latest ROM, and booted. Then it said the process for Setup was unable to process. I booted into recovery, flashed the zip for SuperWipe, flashed Muzzy's again and it worked. But after 3 minutes right when it was logging into my Google Account through setup, it turned off again.
Does anybody know how to fix this? What a horrible way to start Christmas...ugh
Thanks everyone.
Nevermind. I found the problem. Apparently it seems that the OEM Samsung Extended 2100 mAh battery is shot. It came with my phone at Verizon when I bought it from them the day this phone launched. I put my girlfriend's GNex battery in my phone and it is running no problem. I put the OEM Extended into hers and her phone shut off after 1 minute of being powered on. The battery has about 3/4 full charge. Not sure what happened but it seems the battery is done and I got to get a new one.
Hope this helps out people who have the same issue!
Hi all,
yesterday my phone ran out of battery. I plugged it in(original accessory) and started charging.
After some minutes it started it self( as usual I guess). However it got stuck on bootscreen( boot animation) and restarted.
I left it plugged in over night, but nothing changed. This morning I tried to do a factory reset via hardware buttons and it got stuck there as well.
It restarted itself and nothing changed.
Is there anybody who has an idea what to do?
Thanks in advance.
have a look at this thread :
http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
I saw that, since I already returned the phone to LG it is obsolete now. Thanks anyway
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.