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.
Related
Long story short I've got a Rogers Dream, 32B, 2005 SPL that up until recently I had only rooted. When I'd press power and home it reported Cyanogen JF 1.2 I believe.
I was trying to update my ROM, long story short I renamed the signed-dream_devphone_userdebug-ota-14721.zip to update.zip, (because I didn't have any option to select which file I wanted to use to update) loaded it, then realized I was unable to access the SDcard in any way (card reader, etc) to replace that file with the latest cyanogen rom.
So now my phone is stuck at the Rogers boot logo, and I can't get into fastboot or the loader screen.
How effed am I? As effed as I suspect? Anyway to recover this thing, or did I just dumbass myself into a $350 paperweight?
unfortunately I think I am running into a problem just like yours.. I'm running AmonRA 1.5.0 recovery. For a few days it was working fine. I basically did a wipe on the phone and restarted the phone hoping to get the command list to come back up but now I don't get anything but a HTC recovery logo on my phone. I've been pressing a combination of all kinds of buttons to see if there is a way to bypass the recovery console but I'm getting nothing but that HTC logo (which should be something like the Android mascot for some of you), yet I am also not getting to see the T-Mobile G1 boot screen (US Phone) anymore, I assume you don't see your carrier on your screen neither..
Anyways, if anyone can give us any advice, your support will be greatly valuable.
Pull the battery, once the device is off replace the battery. Hold down the camera button and press the power button. If you get to a rainbow colored screen, or a white screen with Androids on skateboards you are not bricked. If you are unable to get to one of these screens I am afraid you have a paperweight, or at least until someone figures out the JTAG pins to manually re-write the startup code back to the phone.
If you can get to one of those screens, you are in good hands! If you have a T-Mobile G1 then simply download this and extract the file within (DREAIMG.nbh) to the ROOT directory of a freshly formatted (FAT format) SD card.
Just reboot the phone with the camera button pressed and follow the directions.
This will get you back to Android 1.0, please follow guides from that point forward.
Last year(late 2010, maybe mid November), I rooted my phone and flashed recovery with no problem s at all. Some time after that I added Apps2SD and that went smoothly with no problems for about a week. I purchased an 8 GB SD Card for more storage room and after I partitioned it and switched the cards my phone started acting up so i rebooted it. After that I was stuck in a boot loop, so i tried to flash it back to stock but it wouldn't take to it no matter how I tried, whether it be through recovery or SW Update. So then I tried Odin Multi loader(cant remember which version but at the time I made sure it was the one meant for the Intercept) after I flashed it with the Stock through Odin, the phone bricked. Now it will not turn on in any way(recovery or other) the only thing it does do is vibrate when I plug it in to a computer, and it will occasionally show battery life through the touch screen and keyboard buttons by lighting them, but as soon as the it is unplugged it is a brick. I see the little bit of functionality as a little bit of to be able to fix this phone whether through ADB or another function but I desperately need help with this. Can someone please help me fix this phone?
note: I currently have a Samsung Transform as my main phone so if the Intercept can't be helped then it's not that big of a problem.
I have the same problem! Please help!
When you root a phone you put the rom, and recovery onto the sd card. changing sd cards disrupts this process. Put the old sd card in and tell me what happens.
The phone doesnt come on at all
see if you can get it into download mode with the battery out.
Pull battery
connect to computer with usb
vol down + camera + end
If you get into download mode this way flash the stock.tar using SWUpdater.
Nope, it doesnt work, thx though
Ok I've got the same problem with my intercept as well, So i just like to add (maybe its just me) that when i plug my phone to the computer the phone shows that its still functions right (without the screen on), I'm able to make calls, and receive them as well (with the touch of the answer button) but just the screen doesn't turn on, AT ALL!, so KJON i don't know if your having the same problem as me but I'm just a noob and i wouldn't know what to do. But there's some ammo if you need it.
I HAVE THE SAME PROBLEM! i dont even know where /sdcard/sdx/zip/ is!
My phone is also a samsung transform and not and intercept and whenever i press vol down+ Power, only the function buttons at the bottoms light up but not the screen
i am a noob.
help?
noooooob here...i didnt wanna start another thread since i have this same problem, so i hope someone reads this..
couple days ago i bricked my sprint intercept i was using SWu and forgot to take the Binary files for the Moment out so now i cant get my phone to DL mode, ive been searching since saturday night and have tried every Button combo posted and nothing, my phone will not turn on and ofcourse it isnt recognized by my pc BUT, ive noticed that only when its plugged in to the computer after trying to power it up several times it´ll vibrate then the 4 touch buttons will react to either the call or end button, also it makes the low battery sound and if i press the camera button it makes the volume sound but i CANT get to download mode, can i bring my phone back or is it done with? help please! and thanks in advance...
well, i would say boot into rrecovery by making the phone off either power button, or remove and replace battery.
next, you will need to press and hold in order: power/end call, call, and volume down.. this should boot recovery mode.
lastly, use the red scroll device to go to reset facory defaults or factory recovery, use common sense while looking. select with clicking and use arrow back button to go back to recovery main, then reboot to system. easy as pie.
Have you tried ODIN or ADB?
I have flashed the Intercept numerous times, soft bricked more than once, I was always able to recover using either the stock bootloader, CWM recovery, or flashing the ROM/Kernel directly using ODIN or ADB.
If you are still having these issues drop me a line and I'll gather some links together that should get you back up and running.
If the phone will not boot at all, even with a charged battery, I would definately try contacting Virgin Mobile and escalating the issue. I've had plenty of luck replacing devices claiming that the device just dropped dead without notice. They are usually good about sending out a replacement phone, and on rare occasions even giving you an upgraded unit if they are out of stock.
Good luck!
Did you use Odin or the swupdater?
Bug difference. Sounds like there's a missing boot loader.
Sent from my SPH-L710 using xda app-developers app
Hi, did you guys fix your bricked phones? Today I have bricked my Samsung transform (bad flash went with SW upgrade.
Only vibrates sometimes and the buttons flash a little, but no boot at all. Is there any chance to fix it? even with Jtag?
regards
Hello all.
I have my old T-Mobile HD2 with the NAND rom you can see in my signature.
Everything was fine for 6 months till today, when my wife (I've given to her) couldn't open it and thought it was run-out from juice.
She plugged it on the PC and wait, while she was dealing with our baby-daughter. When I came back late in evening, I saw the phone with the led still orange, the screen black and the hard buttons flashed. I pressed them, but nothing happen.
I removed the battery, plugged it back again and... since then, the phone stops in the splash animated video (keep continues endless), without the led to flash (orange or whatever) and of course I never getting the Android rom's lockscreen!!!
What's going on???
I've read somewhere to press the red button and plug the battery back. I did and the root menu came up. I pressed the "12" (PowerDown) but the phone started-up again and of course... freezed on the animated splash screen!
Please, help me on this.
I did also hard-reset, by pressing both volume up/down and the red button...
After I pressed the red button (for 30 sec) and then plugged the battery back, I came into the black boot screen and I choose the "AD Recovery".
In the next screen I've seen, that the battery was 95% full!!!!
So, I just pressed the first choice (boot) and... nothing happen, again.
So, what am I suppose to press, in the "Recovery" screen?
Update
-----------
I went again to Recovery screen and I choose to re-install the rom from the SD card (zip file); I did it, the process began and finished, the dialogue wrote to press the "Next" to boot and... still freezed on the animated splash screen!!!!!!
So, what's going on? Is the rom damaged and also I have a problematic SD card and the problem can't be solved?
search how to logcat on google. download necessary files.
make a logcat and post here.
OR
download qtadb (search for it and download) and when in bootanimation, connect phone to qtadb and after it's connected, go to phone info. is system and data partition or any one of them full?
also try wiping cache/dalvik-cache in recovery
Did you checked battery pins if they aren't bent?
Sent from my PIXELDROID HD2 using XDA
I succeed it; made it working!
I did wipeout/format everything except sd and reinstalled the rom and worked! (With NAND option).
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.
So, yesterday my father said his S4 had just shut itself down and that now it only reboots itself and he can't boot the phone.
He asked me to see if I can get it working again and if not try to get the internal data of it, and we tried all evening to see if I could get it working with no success, we tried everything from changing to his second battery and I can't remember what made it work, but all of a sudden it was alive again and it worked for about 3 mins before restarting itself over and over again.
So now he has a phone that is stuck on the first logo screen (The screen that says "Samsung Galaxy S4") and I've tried to flash TWRP to see if I could get MTP to work for moving the files from the /data partition to my PC with no sucess.
He had decided to use his phone for a few more months before he would get a new phone but because of this he have now bought a S8.
So I want some help to see if anyone knows how I can get the files from the hard-bricked phone.
The phone was and is on stock Lollipop 5.0.1 and he hasn't touched the system in anyway until I tried to flash TWRP which did pass in Odin but it got stuck on the "Booting Recovery" until it restarted itself again. The weird thing is that the phone stays on in Download mode and doesn't restart itself there which leads me to think there isn't any hardware error.
Any help is much appreciated!
Just tried to reflash the system, got a little further but then it got into the same problem. It boots which is good, but after a a few seconds it restarts itself, I will attempt to move the files in this short period. But if anyone got a better idea, please tell me.
*Edit: It restarts way too often, sometimes (About 1/10 times) it manages to boot into the OS but then almost immediatly restarts. I've read that it might be the power button that has some dust inside it or something. Seems like after all it must be the hardware? But the weird thing is that it still can stay on inside the download mode, and when I'm holding the button there it shuts down, but not automaticly. I can get into the stock recovery but installing TWRP doesn't work.
If you tried installing TWRP 3.2.0-0 it has an issue with the S4. Use 3.1.1-0 or 3.1.1-1 instead. From there, you should be able to get the data off the internal storage. Once you do, give the side with the power button a firm whack on a table. If there's any grit in the power button, that may loosen it and restore the button to operating condition. Of course, you could get a replacement button but it may not be worth it despite the button being inexpensive and relatively easy to replace.
Strephon Alkhalikoi said:
If you tried installing TWRP 3.2.0-0 it has an issue with the S4. Use 3.1.1-0 or 3.1.1-1 instead. From there, you should be able to get the data off the internal storage. Once you do, give the side with the power button a firm whack on a table. If there's any grit in the power button, that may loosen it and restore the button to operating condition. Of course, you could get a replacement button but it may not be worth it despite the button being inexpensive and relatively easy to replace.
Click to expand...
Click to collapse
Not sure how I feel about whacking the phone (Even if it's firmly) on a table. But yes, I tried TWRP 3.2.0-0 so I'll try 3.1.1-1 later today. Thank you for the tip!
Well, I'm not saying you should bash it hard enough to break the phone, but it can't be a light tap either.
I didn't originally come up with the idea. I just promote it as a quick fix. A more permanent solution is to replace the button.