Ok so Ive searched for help at phandroid, but, I think I might need some XDA help !
I repair phones at CPR loveland colorado.
Routine digitizer replacement on a Rezound. Turn the phone on. Everything looks great. HTC splash screen comes on nice and bright and then cuts out.
The phone is still on and booted into the Android OS. Its just that the LCD is out.
Replaced LCD and i got the same thing. Even tried changing digitizers. Nothing. LCD only stays on for 5 seconds after booting or in the Bootloader.
If I go into the bootloader, the LCD stays on. If i go into recovery it turns off again!
I have ADB/Fastboot set up. But when i use the command "adb devices" while in fastboot usb mode, nothing is shown. I have the latest HTC drivers and HTC SYNC turned off.
I've tried using the leaked ICS RUU through the sd card. It loaded the img and completed, but, still no LCD after boot.
After no luck, I unlocked the bootloader and flashed Amonra. Still, when i go into recovery, the LCD cuts out again. So I relocked the phone.
Phone is currently TAMPERED/RELOCKED.
If anyone has any ideas, please, throw them at me.
Thanks for reading my post guys. Again, any help would be great. Thanks for providing a great community here at XDA!
Synergy-7 said:
Ok so Ive searched for help at phandroid, but, I think I might need some XDA help !
I repair phones at CPR loveland colorado.
Routine digitizer replacement on a Rezound. Turn the phone on. Everything looks great. HTC splash screen comes on nice and bright and then cuts out.
The phone is still on and booted into the Android OS. Its just that the LCD is out.
Replaced LCD and i got the same thing. Even tried changing digitizers. Nothing. LCD only stays on for 5 seconds after booting or in the Bootloader.
If I go into the bootloader, the LCD stays on. If i go into recovery it turns off again!
I have ADB/Fastboot set up. But when i use the command "adb devices" while in fastboot usb mode, nothing is shown. I have the latest HTC drivers and HTC SYNC turned off.
I've tried using the leaked ICS RUU through the sd card. It loaded the img and completed, but, still no LCD after boot.
After no luck, I unlocked the bootloader and flashed Amonra. Still, when i go into recovery, the LCD cuts out again. So I relocked the phone.
Phone is currently TAMPERED/RELOCKED.
If anyone has any ideas, please, throw them at me.
Thanks for reading my post guys. Again, any help would be great. Thanks for providing a great community here at XDA!
Click to expand...
Click to collapse
just thinking out loud...would a messed up/blocked proximity sensor be involved. At what point in the boot process or even in recovery does the sensor become active?
Looks like bad hardware
Sent from my ADR6425LVW using Tapatalk 2
Yeah there is a problem that probably can't be easily fixed. The proximity sensor is a good thought tho might want to check that out
they proximity sensor should only kill the screen when an application such as the dialer calls upon it to do so. seeing as the screen works when you are booting and fails after boot, have you considered reflashing the phone back to factory?
Or doing a factory reset if u can wing it from hboot
Sent from my ADR6425LVW using xda premium
Kidney Poker said:
Or doing a factory reset if u can wing it from hboot
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Would an exe RUU process be able to run with his screen situation? Con could really provide some good info but I bothered him on gtalk all night the last two nights working on the venom stuff so I'm not messaging him right now lol.
Does the screen work in recovery?
con247 said:
Does the screen work in recovery?
Click to expand...
Click to collapse
Does not work in recovery.
I would love to flash a gingerbread ruu on it. Official.Signed. Any idea where I can find that?
Synergy-7 said:
Does not work in recovery.
I would love to flash a gingerbread ruu on it. Official.Signed. Any idea where I can find that?
Click to expand...
Click to collapse
I think these should do.
http://www.filefactory.com/f/c2e320ee1d5c7886/
Related
okay! so I have a S-on amaze 4g. Unlocked bootloader and have clock work recovery, Im also on tmobile. I was running Bulletproof's rom v2.5
so yesterday I was looking at some roms and I came accross mike 1986's android revolution ROM that was based on tmobile's sense 3.6 and android 4.0. I decided to ditch my current ROM and go for mike's ROM instead
Well last night I followed his instructions. Put the PH85IMG, Rom and Super wipe to my phone's SD card. I booted into bootloader and it loaded the PH85IMG but it didnt seem to have done anything so it loaded back to bootloader. I selected "Recovery" and booted into recovery. I deleted my files and cache using clockwork recovery. Then applied the Superwipe zip then installed the ROM. It said it installed the rom and then I proceeded to reboot my amaze 4g. Ok I rebooted my phone and it got stuck on the HTC screen for some quit time WITHOUT THE QUIETLY BRILLIANT. So i decided to redo this all over again. and again the same problem happened. stuck on the HTC logo. so I took out my batterys and went to bed since i wanted to get some shut eye
now this is where my problem comes from. When ever I turn on my phone it wont turn on! i wanted to boot into bootlader but when ever i press on the power button with the volume rocker down it wont start up. So i plug in my USB cable and the LED that indicates charging comes on. and my computer detects the phone... i click on the search capacitive button and the phone disconnects from my computer and it boots into the HTC screen and the screen turns blank
if anyone can help me please help.
come on 43 views and no help
Leave your phone in the charger overnight. See what happens in the morning.
hasoon2000 said:
Leave your phone in the charger overnight. See what happens in the morning.
Click to expand...
Click to collapse
i dont think thats going to work but ill give it a try
Just curious. What version of CWM was installed?
Sent from my HTC_Amaze_4G using Tapatalk 2
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
jp2dj1 said:
Ok. First don't panic. Can you explain by "I clicked the capactive search button". Have you really try power it on without your computer?
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
what i mean by that is when i touch the search button (the magnifying glass icon on the far right) when its charging it would boot into the HTC screen then the screen would turn off
aj_2423 said:
So you cant get the the phone to turn on, but u were able to turn it on when it was connected to the computer?
Sent from my NRGized amaze
Via XDA premium
Click to expand...
Click to collapse
i cant get the phone to turn on when its connected to the computer or wall charger
i just noticed that my LED would blink when first charging then it boot into the HTC screen on its own then the screen would turn off or go blank. after that the LED wouldnt come on so i dont know if its still charging since the orange light isnt there
any more help it would be greatly appreciated
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
jimczyz said:
I tried the same rom yesterday and it failed for me also. I've seen quite a few fails on it. Mine didn't die like yours, mine just froze on the splash screen. I had to pull the battery and hboot and re install my recovery so I could restore my backup. Does anything happen if you pull the battery and try to get into bootloader?
Click to expand...
Click to collapse
i cant even get my phone to get into hboot when i press down on the power and volume buttons.
it did work yesterday after i failed... but when i woke up today i cant even get into hboot for some reason.
You might have to get an external charger to charge your battery, or if you know anyone to swap batteries with to charge yours and try theirs to see if it's just a dead battery. Sounds like it might be.
Download the latest RUU for your phone. You said the computer detects the device see if the RUU will see it as well. Hoping that it does just run it and it will flash your phone back to stock stock and you may have to unlock and install clockwork again but if it works you'll have a working phone again good luck chief
Sent from my LG-P999 using Tapatalk 2
I believe the Rom u were trying to flash is for s-off only....I might be wrong though...
Sent from my HTC_Amaze_4G using XDA
If i recall, you were supposed to lock the bootloader before you placed the PH85.img, because it wouldn't recognize the file without it on an S-On device. Also, where you using Xboarder's Clockwork recovery touch? or an older version?
Try this and tell me what happens. Change your phone by your computer USB and turn it on by search button and "HOLD THE DOWN VOL BUTTON AT THE SAME TIME" try it a couple of times.
Sent from my HTC_Amaze_4G using XDA
I think it's a problem with the version of cwm installed, it won't charge the battery right if it dies all the way pull the battery then charge it for about 20 mins then battery pull again and charge for a minute or two and try and turn it on
Sent from my HTC_Amaze_4G using XDA
Thread Moved to Q&A. PM sent to OP.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
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
all the sudden i have no display it is blank everything else works meaning i can call my phone it rings even though i have no display if i slide my finger to unlock the ring i can answer all calls i change the display today along with the digitizer but still have no display what else could be bad
Maybe the motherboard? I'd take it to the Sprint store (or whoever your carrier is) for repairs.
1iwilly said:
all the sudden i have no display it is blank everything else works meaning i can call my phone it rings even though i have no display if i slide my finger to unlock the ring i can answer all calls i change the display today along with the digitizer but still have no display what else could be bad
Click to expand...
Click to collapse
If its not the hardware, it can be the kernel problem. Do you see anything in your bootloader (vol down + power while phone is off)?
mnomaanw said:
If its not the hardware, it can be the kernel problem. Do you see anything in your bootloader (vol down + power while phone is off)?
Click to expand...
Click to collapse
no it is all black only the bottom light are on is the there a way i can get into it using sdk even thought display is black.??? thanks
Remove and reinsert the battery then try to boot into bootloader and see If screen lights up. You might have fastboot turned on.
mnomaanw said:
Remove and reinsert the battery then try to boot into bootloader and see If screen lights up. You might have fastboot turned on.
Click to expand...
Click to collapse
no no go still black screen
1iwilly said:
no no go still black screen
Click to expand...
Click to collapse
hmmm..then maybe... what coal said
coal686 said:
Maybe the motherboard? I'd take it to the Sprint store (or whoever your carrier is) for repairs.
Click to expand...
Click to collapse
can't do that the phone is flash to metropcs from my donor phone
1iwilly said:
can't do that the phone is flash to metropcs from my donor phone
Click to expand...
Click to collapse
I've heard the cables in the 3d are very tiny. Maybe the cable that connects the motherboard to the display is broken or has a broken pin.
coal686 said:
I've heard the cables in the 3d are very tiny. Maybe the cable that connects the motherboard to the display is broken or has a broken pin.
Click to expand...
Click to collapse
somebody said maybe a kernel gone bad is there a way using sdk that i can get into the phone to do a wipe and install a fresh different rom.??
what command would i need if possible??
1iwilly said:
somebody said maybe a kernel gone bad is there a way using sdk that i can get into the phone to do a wipe and install a fresh different rom.??
what command would i need if possible??
Click to expand...
Click to collapse
You could always try going back to stock. If you are s-on, bout the phone into fastboot, connect to pc, relock the bootloader and run the ruu.exe. You'll have to HTC unlock again. If you're s-off, just run the ruu. You'll keep s-off, but be completely stock otherwise.
coal686 said:
You could always try going back to stock. If you are s-on, bout the phone into fastboot, connect to pc, relock the bootloader and run the ruu.exe. You'll have to HTC unlock again. If you're s-off, just run the ruu. You'll keep s-off, but be completely stock otherwise.
Click to expand...
Click to collapse
i'm s-off but if the screen is black how do i put it in fastboot.?? with sdk.?? if so what commands do i need to run to do what you are saying i do have a copy of the original stock rom and i do want to stay s-off
If you don't have a light at all(even the "black" one), I suggest to take your phone to service because if that is kernel problem, you would have a bit of light. If that is not possible, open your phone and check if there are any irregularities. If you dropped your phone, cable could detach from motherboard. It is not hard to disassemble..you can find youtube video.
Sent from my shooteru using xda premium
1iwilly said:
i'm s-off but if the screen is black how do i put it in fastboot.?? with sdk.?? if so what commands do i need to run to do what you are saying i do have a copy of the original stock rom and i do want to stay s-off
Click to expand...
Click to collapse
You can use adb. With the phone hooked up to the computer, at the command prompt, type adb reboot bootloader.
1iwilly said:
i change the display today along with the digitizer but still have no display what else could be bad
Click to expand...
Click to collapse
PROleev said:
If you dropped your phone, cable could detach from motherboard. It is not hard to disassemble..you can find youtube video.
Sent from my shooteru using xda premium
Click to expand...
Click to collapse
Unless he's made a habit of dropping his phone in the exact same way, I very much doubt that would help.
If it were a kernel issue your boot loader would have worked all the same (boot loader loads the kernel and is independent of it)
As it's not the screen itself and not a software problem it's probably either the GPU being fried or some other piece of electronics between it and the screen connector ( maybe even the connector itself). As far as I know the "fix" for this is replacing the motherboard or the entire phone. As you've opened the phone I'm going to assume you're not under warranty in which case either repair option is quite expensive... a new PCB is generally over 50% of the phone's value and will most often prevent you from ever unlocking the phone via htcdev;
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.
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated. I can't see anything except the snow. I have gotten it to show my lock screen by kind of tweaking the phone by bending slightly. When I get the lock screen, the touch screen no longer works. I can hit the power button to turn the screen off, and then again to only get the snow. I am thinking it's probably a hardware issue. I haven't dropped it or gotten it wet. Which leads me to my next question. I am rooted and running CM 10.1. I can't get in to recovery mode to restore to a stock ROM. If I take it in to Sprint for repair/replacement will they have a way of seeing I am running a ROM and decide they wont't work on my phone?
thedanpal said:
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated....
Click to expand...
Click to collapse
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
tmwilsoniv said:
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Click to expand...
Click to collapse
That is a very good chance. I will give it a shot tonight. Thanks for the idea.
I pretty much have no idea what to do now. My phone won't mount the SD card on any computer. The phone recognizes the SD card, i just wont mount it. When trying to use RUU i just get the error 170. So, i guess i will be dropping my phone off at sprint and hope for the best.
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
SiGuy11 said:
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
The tech thought it was a connection issue with the display, but he couldn't get it fixed and thinks the motherboard went bad. They are replacing the phone with a new one, but they are backordered so I have to wait a week.
Yeah but what caused all of our phones to have the same issue that doesn't exist on sense roms? Kernel overpowering the motherboard causing it to fry?
Sent from my EVO using xda app-developers app