this is my first htc and so far i am missing my samsung and motos
the phone is now completely non responsive and is stalled at the HTC boot screen with the text "this build is for development purposes only " i have the verizon htc one m8 ive tried removing the sd and sim holding power holding volume and power nothing makes a difference.
rooted with s off twrp is my custom recovery
started by putting slimrom on for a change of pace i had horrible signal strength and decided to try another rom somewhere in the process of flashing venom one my sd lost its backups the phone had stayed on the same screen for a while but eventually booted to a stable seeming venom rom and had 3g but no 4g service i ended up rebooting the phone today around 11 am and its been in this loop / screen since. i let the battery die down and was able to get to recovery and searched for my back ups but they were gone i ended up rebooting and now am stuck on the same screen as before. even after trying to enter recovery twrp it goes back to htc and not twrp
i tried every combination of buttons the few times and have drained the battery twice and now it just boots to this screen and is non responsive. hope that i can manage to find a way to push something to it or enter recovery and go back to stock using ruu's
anyone with input or advice would be a blessing at this point id be happy to make a donation for any useful help / anything to get me out of this screen even so i can push another rom or ruu to get me to stock
im afraid ive ruined a perfectly awesome phone
update got back to twrp and tried to re flash the venom one rom after full wipe but used their option for "stock" install said 100% and sucessful but upon the reboot is now seems to be stuck in the same screen.
got into the recover after battery died re flashed venom
after about 15 minutes on the htc screen it went to set up ....still very buggy more so than last time the phone was actually working but it is at least from what i can tell working ... going to try to get back to square one somehow
screen wont turn on and acts very buggy only time it stays on is holding power and gives reboot options... i done f ' ed this phone up.
How long are you waiting after I restarts when the install is finished? It will take a long time on that first boot. I have seen them take more than 5 minutes and if you interrupt it it can cause problems.
Related
I recently installed this ROM and I thought it was working fine. I did a restart of the device and now I seem stuck at a android screen that it doesn't see to be going pass. The android word just display as a light goes across the screen and then it seems to cycle again.
I can't seem to boot into recovery either to put restore the back up I made, because when I get to the white fast boot screen the selection won't scroll down to recovery when I hit the down volume button. It just stays there and then tries to install a patch for a radio I believe.
Any thoughts on why this is stuck at the android word screen or how I can get back to my back up and restore that. Thanks
verseman said:
I recently installed this ROM and I thought it was working fine. I did a restart of the device and now I seem stuck at a android screen that it doesn't see to be going pass. The android word just display as a light goes across the screen and then it seems to cycle again.
I can't seem to boot into recovery either to put restore the back up I made, because when I get to the white fast boot screen the selection won't scroll down to recovery when I hit the down volume button. It just stays there and then tries to install a patch for a radio I believe.
Any thoughts on why this is stuck at the android word screen or how I can get back to my back up and restore that. Thanks
Click to expand...
Click to collapse
Try removing your sd card and then vol down and power. Then once you're past fastboot white page pop it back in in time for recovery, and do your thing. Try clearing caches first. If not then restore a backup.
Sent from my Inspire 4G using Tapatalk
Yup I think I seen that in another forum to a similar type problem, I removed the SD card and was able to get back into clockwork recovery. I wipes all data/settings, cache partition and then loaded the rom again.
First thing I did was do a reboot so. So far it didn't get stuck and booted back up. Will do another reboot later tonight to see if it holds. Thanks for the tip
I'd reccomenf going to the dhd forum and getting the latest version (new one coming out soon)
Sent from my Desire HD using XDA App
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
I have a rooted and bootloader-unlocked Inspire 4G. A few months ago, I had been using the MoKee 4.2.2 ROM for some time, and one day, my phone's screen simply froze. I thought I shouldn't be worried about it, so I pulled the battery off, slapped it back in and tried turning on the phone again. It never got past the MoKee loading screen. I tried charging it, leaving it to boot for hours but nothing.
Next, I tried rebooting into CWMrecovery to try different stable backups I had from some time before that happened. The backups restored successfully, but again, the phone stayed stuck in the loading screen. I tried the same with 4EXT Touch Recovery and wiping all the data before the backup, but still nothing worked.
Since I was too busy at the time to install a new ROM and flash a new boot image, I decided to put the phone away and use my backup Galaxy Ace. Today, a few months after that happened, I tried to boot the phone into bootloader and I can't even achieve that. Holding the volume down rocket and power buttons, the phone still boots normally and stays stuck on the loading screen.
What weirds me out the most is that this was all random--I did not drop the phone or did things to it that could break it.
I feel if I could get into recovery I'd be able to do something else about it.
Any ideas?
Me too
Weird, mine just did the same thing today. Crashed, had to pull battery, now stuck at Mokee. Tried clearing DC, cache, factory reset. No luck.
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
Sadly that is because of a hardware issue. Been happening. A lot lately.
hyelton said:
Sadly that is because of a hardware issue. Been happening. A lot lately.
Click to expand...
Click to collapse
Alright, that's what I had read. Just seemed like a software issue so I was hoping for the best. I went ahead and ordered a new device. Im guessing a full motherboard replacement would be required to fix the device?
Recurring Issue
Hello,
The same problem happened to me a few days ago so this is trully a recurring issue.
I also tried to fix my rom by reinstalling it, then tried to install multiple new rom, and finally flashed the original stock rom. I also am stuck on the bootloop issue.
I'm going to contact LG to see if they can do anything to repaire it but my hope are very low.
I'll try to update this message if I find a solution.
Mine just started bootlooping and no wifi and today it just died. Battery pulls didnt work either no power at all. Probably going to switch to the V30 when its released.
Sent from my One using Tapatalk
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
It's probably to late but theres another method returning to stock KitKat dont know the link off hand in development forums. Sucks you couldnt try no adb methods. Still have the Phone want to sell it i need a cheap screen ?
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.