So last night I was shooting some videos with my MT4G, in the rain. When I got home, my phone was working fine. Then it rebooted and went straight to HBOOT. The message I have now is:
"Parsing...[SD ZIP]
[1] Radio_V2"
My volume keys won't work, I can't boot into recovery, can't connect to adb. Is there any way I can factory reset this or anything? My moisture stickers are still white but it is entirely possible that water may have gotten under the buttons...
Should I try taking it apart?
JeffyLube0 said:
So last night I was shooting some videos with my MT4G, in the rain. When I got home, my phone was working fine. Then it rebooted and went straight to HBOOT. The message I have now is:
"Parsing...[SD ZIP]
[1] Radio_V2"
My volume keys won't work, I can't boot into recovery, can't connect to adb. Is there any way I can factory reset this or anything? My moisture stickers are still white but it is entirely possible that water may have gotten under the buttons...
Should I try taking it apart?
Click to expand...
Click to collapse
remove your sd card you have the XXXXXX.img that automatically flashes your phone thats what it seems like... that should fix your problem just boot into recovery and flash a rom or nandroid normally
Related
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Hold power and volume when turning on phone, then select fastboot and have the selection for bootloader highlighted, then start the RUU it should work then.
OK, so I tried the volume down + power btn deal, but still no dice. I really don't undestand wtf happened, cause before doing the 2nd part of root, I was able to load Damage ROM, now anything I load besides the PC36IMG.zip from part 1 just bootloops. Crazy
control_logic said:
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Click to expand...
Click to collapse
ive seen this answered in the RUU threads. they mentioned the RUU doesn't automatically reboot the phone into the correct mode, i think it was bootloader? manually booting it into the correct mode, then connecting the USB, resolved the issue.
you might want to search/reference the RUU threads for more details as i never had the issue and am only recalling off the top of my head what ive read, which cant be 100% accurate!
When RUU stops/freezes and your phone has the black screen with "HTC" on it.... do not restart your phone or anything leave it the way it is. What you do is exit out of the RUU program by clicking "exit" when it freezes up. Then without doing anything to the phone, just restart the RUU program and it should pick up where it left off and complete the process. I found this fix in "Q and A" part of the Evo forum and it worked for me.
Sent from my PC36100 using Tapatalk
You need to format the phone rest and format cashe then install the rooted image and it will boot. I had the same problem.
Thanks for the responses, it is working again, YEAH!
Apologies in advance for my newbie-ism with the Hero/HTC android devices... I'm trying to get my father's Hero running for him.
The story is that a small amount of water was spilled on the phone and now it won't boot past the "htc" boot screen. My experience with phones + water is that either they dry out and they're fine or they refuse to ever boot at all ever again so I'm hoping the fact that I can get the boot screen at all is a good sign.
I've tried the home-back-end call clear storage and the volumedown-action-end call fastboot. Everything I've tried just gets me back to the htc boot screen. When I plug into USB a mass storage drive pops up in windows explorer but when I try to click into it it gives me the "please insert a disc" message.
The diagnostic screen at the top states:
"HERO XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-fail
RADIO-1.04.01.01.21"
The touch panel fail message scares me, but is there any hope of getting this thing running again?
Thanks,
Kevin
Try asking the Impaler on his thread he might b able to help you
Root-Hack-Mod-Always™
Is the phone rooted? If so, try booting into recovery. May be a coincidence that water got to the phone and something with the phone's software got broken.
pull battery from phone, reinstall, then hold the volume down button and the power on button at the same time. hold until you see recovery screen pop up, this will work with or without root
The phone is 100% stock.
When I boot into the recovery mode (volume down + power on), I would hit the home button for "Recovery", correct? When I do that the phone restarts and goes back to the "htc" boot screen and hangs there.
Any ideas?
Holding the Volume down and powering on the phone will boot you into hboot. You can boot into recovery from hboot but you can boot directly to recovery as well. Hold the Home button and power on the device. However, to be honest I don't know if you can boot into recovery with a stock (unrooted) phone but it's worth a shot.
Looks like a direct boot into recovery is a no-go...
I downloaded the ROM update utility from the HTC website and was able to get the upgrade to load through FastBoot USB. The phone booted up and actually loaded past the boot screen into the Android setup screens, but the touch screen was completely non-responsive and every second or so an "acore" something or other error kept popping up. I wasn't able to get past the setup since I couldn't access the keyboard so I tried to restart and now I'm stuck at the (now updated) htc boot screen again.
It seems to me that the touch screen is fried and that the phone is probably no good... someone tell me if I'm wrong
Thanks for all of your help!
That's rotten luck. Hopefully you can get it fixed or replaced.
ok so i am hoping i have not bricked phone but i think i did. i booted to recovery console by holding the home+power and ran the danger spl and when i reboot it just goes to black screnn with white g1 screen and stays. cant even get back into recovery by holding home+power or holding camera+power. so am i done?
i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.
androidcues said:
i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.
Click to expand...
Click to collapse
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.
jcdeuce said:
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.
Click to expand...
Click to collapse
Yip your bricked, you'll need to jtag it im afraid or buy a new one.
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
The same thing just happened to me! Someone please help us! IS there a solution to this?
dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|
jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.
LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.
A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
TheGentleShark said:
A couple days ago, my volume buttons were not working so I thought a quick restart would fix it. But when I restarted it, it went into bootloader. Its stuck on the 'Restart bootloader' option and I can't select it with my power button nor can I select other options with my volume keys. I try and hold down the power button and it restarts into bootloader again. I booted into recovery and tried to restore it with a nandroid I made that had everything stock but that didn't work. I also did a factory reset, but every time I try to boot into system it goes to bootloader instead. The only problem I can think of was that I held my phone when my hands were wet so maybe water went inside? I'm tempted to get rice to get the water out but I want to be certain that this is the result of water damage. If it helps, I had TWRP and a very early version of Lineage OS on the device before it happened.
Click to expand...
Click to collapse
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
5.1 said:
Hi... How did you manage to boot into recovery without the volume rocker?
Have you tried a simple:
fastboot format cache
fastboot format userdata
fastboot reboot
From bootloader?
Is your bootloader unlocked? If yes, try loading a factory image from Google if none of the above work.
Click to expand...
Click to collapse
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
TheGentleShark said:
I used 'fastboot boot recovery.img' to get to recovery. I tried to format the cache and userdata again, but still didn't normally boot. I also tried flashing the stock images from Google's website but still it won't boot.
Click to expand...
Click to collapse
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
5.1 said:
I never seen this before. If you type fastboot reboot, it reboots directly into bootloader, right? I first thought avout the bootloop issue many currently report. But if you can boot a recovery.img or if your phone only reboot into bootloader, I think this scenario can be excluded.
Hmm you said you touched you phone with your hand wet?!
Could it be the moisture that oxidized the volume down contact inside of the phone? I don't have another idea. Wait for other people to chime in. Hopefully it's another (easy to solve) issue which I am unaware of.
Good luck.
Click to expand...
Click to collapse
Ah well. Thanks anyways.
TheGentleShark said:
Ah well. Thanks anyways.
Click to expand...
Click to collapse
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
5.1 said:
Did factory image flash without error?
Last try: did you try pressing power button till it reboots?
Good luck...
Click to expand...
Click to collapse
No error came up when I flashed it and holding power button at bootloader restarts the phone back into bootloader. I might just stick it into some rice and use my old Nexus for now unless another solution presents itself.
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Hi. In order to get the attention of @TheGentleShark you should either reply directly to one of his posts, or put an ampersand in front of his name so he gets a notification. Otherwise he will never know (or see) your question. Hopefully he has some useful feedback for you.
WRDD said:
Hi TheGentleShark, did you manage to resolve this? Stuck in a similar situation
Click to expand...
Click to collapse
Sorry for late reply, but I did manage to get if fixed. I sent it back to my phone company to get fixed since it was still under warranty (even though its rooted with unlocked bootloader). Though, they didn't really tell me what went wrong. I assumed it was a hardware problem (a piece of rice was stuck in the speaker hole and was impossible to remove but was gone when I got the phone back).