Out of the blues yesterday my HTC Evo 3D GSM (S-on) running MIUIV4 (with antrax kernel 3.5) went down with no warnings whatsoever. Now the screen is distorted showing millions of colored dots. All the buttons are working. If I move my hand over the screen in the right direction I can even hear it unlock though I can't see anything but those dots.
Worst part is I am not able to go into the bootloader as well or rather I can't see it in bootloader, the screen is blank. ADB and fastboot commands work properly when connecting to my laptop. Recovery also shows the same colored dots and nothing else.
Ran out of ideas to try fixing it on my own. Before I take it to the service center, would like to have another opinion on what might be the problem. Any inputs appreciated.
I would suggest reflashing an hboot and then reflashing a rom if you are able to.
If after that it is still doing that then its probably a problem with the screen.
Sent from my PG86100 using Tapatalk 2
Anthrax kernels are only to be flashed with s-off I believe
( Don't ask me for help as I couldn't care if your phone explodes, eh! )
Might be a digitizer failure
As a last ditch effort, I would boot into bootloader (even though you can't see it), relock the bootloader (fastboot oem lock) and then run the ruu.exe for your area/carrier. This will completely put you back to stock which hopefully fixes it. If not, your back to stock to take it in for repairs.
Thanks for the input guys.
flashallthetime said:
Anthrax kernels are only to be flashed with s-off I believe
( Don't ask me for help as I couldn't care if your phone explodes, eh! )
Click to expand...
Click to collapse
I am aware of that
But can that affect the screen alone and leave everything else working? Just asking.
coal686 said:
As a last ditch effort, I would boot into bootloader (even though you can't see it), relock the bootloader (fastboot oem lock) and then run the ruu.exe for your area/carrier. This will completely put you back to stock which hopefully fixes it. If not, your back to stock to take it in for repairs.
Click to expand...
Click to collapse
Thanks, will try that out and lets see if that fixes it. Will update soon.
Update: Tried running the RUU but didn't fix the problem.
Took it to the HTC authorized center, they told me that the display needs to be changed. After a week or so they told me there is some motherboard issue and they are trying to fix. And yesterday they gave up and said they can't fix the issue.
When the authorized center itself says it can't fix , finally given hope on my beloved EVO 3D and back to nexus one running CM7 :crying:.
Related
how do i relock my bootloader on my amaze 4g
AndroidKing said:
how do i relock my bootloader on my amaze 4g
Click to expand...
Click to collapse
did you try:
fastboot oem lock
command?
Bootloader "Relocked"
I need to send Amaze in for warranty replacement, but bootloader shows as "Relocked." Do any of the legendary android dev heroes know if its possible to restore the Amaze bootloader to show "Locked" as it originally did. Not sure if the relocked status will void the warranty.
Throatchopper said:
I need to send Amaze in for warranty replacement, but bootloader shows as "Relocked." Do any of the legendary android dev heroes know if its possible to restore the Amaze bootloader to show "Locked" as it originally did. Not sure if the relocked status will void the warranty.
Click to expand...
Click to collapse
Not without s=off... The testers of s=off script I think are able to, but ours (s=on) will say "relocked."
Your warranty is probably still good... As long as it was a hardware issue... And if its a software issue, that can probably be fixed w/o sending it in
Sent from my HTC Ruby running Android Revolution HD
Thanks... I believe its a hardware issue. It was running fine on senseless rom, then all of a sudden it began overheating when charging, and the phone would just continually reboot until the battery was completely drained. It showed battery health was poor so I replaced the battery, but the problem persisted. The phone overheats when charging, and just keeps loading all the way to the home screen, then it auto reboots after less than a minute. I reverted everything back to stock to see if that fixed the problem, but it still does the same thing. T-mobile tech support said the prob sounds hardware related. Has anyone heard of software causing these problems? As far as I can find through searching s-off is still a no go for the average "instruction follower" like me. I dont wan t to jump into trying s-off when its still in the r&d stages and destroy an already limping device. thanks for all the help. There are many geniuses on XDA and I dont think you all get the credit u deserve.
You should be fine with it relocked then...
Sent from my HTC Ruby running Android Revolution HD
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
Hello, I have an EVO 3D, running Cool ICS v7, with the htcdev.com unlocked bootloader, and the juopuonut bear S-Off (Wire Trick). My refurb phone seems to be having issues with all of the 4 touch buttons on the bottom of the screen, and works randomly. I have already tried re-installing the ROM, but it seems to be a hardware issue, since it only started a few days ago. Anyhow, im going to have to go to the sprint store, to get my phone diagnosed again, and have them send me a new phone, but I don't want them to see that my phone has been modded, and have them conclude that that is the cause of the problem. I need to know how I can go back to Stock Rom, Turn my S back to S-ON, and relock my bootloader, so that it won't say Juopuonut bear in the bootloader screen in pink highlighter either. Thanks!
Sent from my PG86100 using xda app-developers app
From everything I've read, you should be fine if you take it as is. The official Sprint policy is to treat rooted customer's phones the same as unrooted. If you are concerned, you could take it in with a rooted stock Rom but leave it unlocked.
Sent from my ICS 3VO with Tapatalk 2
coal686 said:
From everything I've read, you should be fine if you take it as is. The official Sprint policy is to treat rooted customer's phones the same as unrooted. If you are concerned, you could take it in with a rooted stock Rom but leave it unlocked.
Sent from my ICS 3VO with Tapatalk 2
Click to expand...
Click to collapse
Do you have a link to the source of this?
3 weeks ago a friend brought his in, and they wouldn't order a replacement (even though he pays for insurance) until he brought it back fully locked up.
To OP, backup your stuff, run the 2.17 exe while the phone is in FASTBOOT USB mode. Then use HTC's tool to re-lock the device. and then to turn S-ON back on, do fastboot oem writesecureflag 3 while the device is connected in FASTBOOT USB Mode again.
Unknownforce said:
Do you have a link to the source of this?
.
Click to expand...
Click to collapse
I found this link on Pocketables (well goodandevo) originally: http://www.acsyndicate.net/dear-sprint-thanks-for-the-memo/
Now, whether the local Sprint employee follows it :banghead:
Sent from my ICS 3VO with Tapatalk 2
Thanks!
Unknownforce said:
Do you have a link to the source of this?
3 weeks ago a friend brought his in, and they wouldn't order a replacement (even though he pays for insurance) until he brought it back fully locked up.
To OP, backup your stuff, run the 2.17 exe while the phone is in FASTBOOT USB mode. Then use HTC's tool to re-lock the device. and then to turn S-ON back on, do fastboot oem writesecureflag 3 while the device is connected in FASTBOOT USB Mode again.
Click to expand...
Click to collapse
Im going to try doing this method, i hope it works! Ill keep you posted
THANKS!
Thanks For All Your Help Guys! It worked, im back to 100% Stock. Ill now be able to go to he sprint store, and get my replacement evo 3d!
I have an Evo 3d and was working great, but up until recently like 1/4th an inch of the right side of the screen doesnt have any touch capabilities :/
I touch and and nothing happens and it sits right over top of the back button when typing so if i mess up a word i have to reload the app and start again cuz i cant hit the backspace :/
What would cause this? and how can i fix it? I have returned to stock and reflashed everything, nothing seems to work
thanks
Sounds like the Touchscreen got an Defect...
if you had a warranty, go to your next shop and let it Exchange
EnesGTR said:
Sounds like the Touchscreen got an Defect...
if you had a warranty, go to your next shop and let it Exchange
Click to expand...
Click to collapse
Nope no warranty, its been flashed to cricket, but its stock right now back to sprint...
Couldnt i open it up and change the screen?
117micc said:
I have an Evo 3d and was working great, but up until recently like 1/4th an inch of the right side of the screen doesnt have any touch capabilities :/
I touch and and nothing happens and it sits right over top of the back button when typing so if i mess up a word i have to reload the app and start again cuz i cant hit the backspace :/
What would cause this? and how can i fix it? I have returned to stock and reflashed everything, nothing seems to work
thanks
Click to expand...
Click to collapse
Are you s-on or s-off and does your bootloader say unlocked, relocked or locked? If you are locked then it doesn't matter if your s-on or s-off, your good to go. When you take your phone is for service, they check to see if your bootloader says unlocked or relocked. If so then they won't service your phone. Thats the only way they can tell if you flashed anything. Here is a link to a very easy guide that will help you if you are relocked or unlocked. http://forum.xda-developers.com/showthread.php?t=1889438 It will help you get your bootloader backed to locked with s-off using the wire trick. Then after that you would flash a ruu to return everything to complete stock unrooted and stock recovery. Including hboot. Don't forget to hit the thank you button if I helped you. Also don't forget to give credit to the man behind this amazing guide. If you have any questions don't hesitate to ask.
Sent from my HTC EVO 3D X515m using xda app-developers app hiii i also have a problm with my touch but i work well only the 4 button(home,menu,back and search is not work)sometime the work and sometime they dont..pleaaseee can sumone tel mw wat the problm n wat to do????
Digitizer
Your digitizer is messed up.. Best thing is if u can get it replaced by going back to locked bootloader. But if that doesnt work out then buy a new digitizer and replace by watching tutorials(not an easy task, first check videos and then order it).
i have the same issue, i messed up left side of the screen..
Best of luck :good:
Well here's a good one for you xda folk... So here is what happened in a nutshell... I unlocked my bootloader, flashed 4ext and supersu, then booted my phone fine. I didn't want to s-off. So I skipped the jbear process. After messing around and installing some apps I decided to flash a "modified" stock Rom. That booted fine but I didn't want to keep the Rom. I restored back and then I was in a bootloop. So I relocked the bootloader and flashed the RUU through fastboot. It booted fine. Then I reunlocled rerooted and attempted s-off but sadly failed hard at it. The phone was bootlooping from that so I then relocked the bootloader and did the RUU process again. However this didn't fix the boot loop so I ran it twice more. And it booted up. My sd card was unreadable and I formatted it and it works now. Later that night before I went to bed I always change my dead battery with a full one. ( I have a dock battery charger) And when I attempted to power on the phone was yet again, bootlooping. I booted into bootloader and selected recovery. It went to a screen with a triangle and android guy then a loading bar with a picture of the sd card at the end. It fixed and booted but wiped everything. I powered down today and powered back up fine. I am afraid to remove the battery. What can cause the phone to bootloop by removing the battery??? Any help is most gratefully appreciated.
Sent from my PG86100 using xda app-developers app
Nothing?
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Well here's a good one for you xda folk... So here is what happened in a nutshell... I unlocked my bootloader, flashed 4ext and supersu, then booted my phone fine. I didn't want to s-off. So I skipped the jbear process. After messing around and installing some apps I decided to flash a "modified" stock Rom. That booted fine but I didn't want to keep the Rom. I restored back and then I was in a bootloop. So I relocked the bootloader and flashed the RUU through fastboot. It booted fine. Then I reunlocled rerooted and attempted s-off but sadly failed hard at it. The phone was bootlooping from that so I then relocked the bootloader and did the RUU process again. However this didn't fix the boot loop so I ran it twice more. And it booted up. My sd card was unreadable and I formatted it and it works now. Later that night before I went to bed I always change my dead battery with a full one. ( I have a dock battery charger) And when I attempted to power on the phone was yet again, bootlooping. I booted into bootloader and selected recovery. It went to a screen with a triangle and android guy then a loading bar with a picture of the sd card at the end. It fixed and booted but wiped everything. I powered down today and powered back up fine. I am afraid to remove the battery. What can cause the phone to bootloop by removing the battery??? Any help is most gratefully appreciated.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
What a long story
there is good tutorials in the forum to get s-off , follow them , my HBOOT was 1.49.0018 , an i got s-off easily , and bootloops got disappeared
Sajijun said:
What a long story
there is good tutorials in the forum to get s-off , follow them , my HBOOT was 1.49.0018 , an i got s-off easily , and bootloops got disappeared
Click to expand...
Click to collapse
I plan on s-off but I just want to take this back to sprint to get the firmware reinstalled. The front camera is done for as well and that's a hardware problem. My upgrade is in Feb so I'm just getting a new phone but I just wish I knew what is causing bootloop from a battery pull.
Sent from my PG86100 using xda app-developers app
I brought my phone to sprint. Dun dun dunnnn. I explained the problem and they said, "Sorry but your screen is cracked so we can't do anything." I said Dafuq??? I know I have insurance and all. I just wanted them to reflash The firmware but I guess they can't due to a crack in my screen. (They said it could have been when I dropped it. But I bought the whole front faceplate and installed it myself cause my LCD broke. I have a white housing but everything else is black. So maybe they noticed. I don't know. Just gotta wait a month.
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
I brought my phone to sprint. Dun dun dunnnn. I explained the problem and they said, "Sorry but your screen is cracked so we can't do anything." I said Dafuq??? I know I have insurance and all. I just wanted them to reflash The firmware but I guess they can't due to a crack in my screen. (They said it could have been when I dropped it. But I bought the whole front faceplate and installed it myself cause my LCD broke. I have a white housing but everything else is black. So maybe they noticed. I don't know. Just gotta wait a month.
Click to expand...
Click to collapse
Cracked screen. Broken camera. White housing. It's no wonder you are having problems. There's usually more to the story than what we see here.
Why didn't you just get it replaced if you have insurance? Good luck with your new phone when you get it.
ramjet73
Yea I'm just going to wait ramjet. Although now I can pull and switch batteries without bootlopping. Must-have been fixed when I chose recovery.
Sent from my PG86100 using xda app-developers app
EDIT: Nevermind...pulling battery still results in a freaking bootloop. This phone...smh. Never had a problem before i failed the jbear soff. Its to bad how much i love HTC, and i am deffinitly not getting one february. Galaxy Note 2 here i come. Goodbye HTC
AGoogleUser said:
EDIT: Nevermind...pulling battery still results in a freaking bootloop. This phone...smh. Never had a problem before i failed the jbear soff. Its to bad how much i love HTC, and i am deffinitly not getting one february. Galaxy Note 2 here i come. Goodbye HTC
Click to expand...
Click to collapse
There is a lot to be said for the other vendors, but it sounds like you brought all this on yourself. It's not HTC's fault you broke the screen, swapped out hardware, and failed an unsupported hack. Any other phone would act the same way given the circumstances.
As far as your actual problem, I wouldn't be surprised if you shorted out the phone when attempting to ground out to the SD slot. If you accidentally connect the wire a bit above the case, you'll instead short out to some internal phone circuitry. You can see some leads in there if you remove the shell. That's just a guess, so take it with a grain of salt.
Since nothing else seems to be working, I would once again attempt to go for s-off. It's not unheard of to have to try it dozens of times before it works, so just keep at it. Try starting from the beginning. Verify you're still unlocked, reinstall twrp/4ext, do the s-off project, change your hboot, flash the latest Sprint radio firmware if you want, all of it. Don't skip a single step. Treat it as though it's a brand new phone and you're ready to start rooting it.
If that doesn't work, maybe someone else has some other ideas. But I don't think there's anything more that can be done beyond that.