Related
I tried to turn it on and all I get is a vertical line that fades from gray to blue to red. It buzzes like it's coming on and then... nothing. Anyone else had this problem?
edit: I also can't get into the recovery menu
First. What did you do or try to do to it?
Sent from my PG86100 using XDA Premium App
Sorry, I'm having a borderline panic attack...
I wasn't doing anything to it at the time - It had gone dead and I plugged it in to charge when I got home. After maybe 10 min I tried to power it up and I got the weird vertical line on the right side of the screen. I have tried battery pulls, I tried charging it fully then turning it on. I can't boot into the hboot menu. It is 100% stock, s-on. I haven't even tried temp-root on it. I'm trying to run an RUU but it keeps giving a usb error
don't try fixing this yourself! Take it back to an authorized Sprint repair store ASAP.
First of all relax, most bricks are reversible - but indeed some are not and hence you are panicking. Well if you followed the instructions as mentioned in the thread 99.9% things should have not gone wrong. But now that they have - you either need to figure out at what step did they go wrong - and what step before that step you did something wrong.
If nothing works - then run to your operator.
I took it in to Sprint. The rep was literally outraged that my phone was broke. Said it was ridiculous that I should have to come down there after only having my phone 2 weeks. Gave me a brand new one in the box, no questions asked. FYI - they said they hadn't had any other reports of similar issues and hadn't seen it before. It was just a white line down the right side of the screen and wouldn't do anything else.
Glad to hear Sprint is keeping the a good face...especially in this locked hboot era...just try not to break this one
Good to know that, and good on Sprint's part as well. Please read well before doing something tothis one.
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
austontatious said:
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
Click to expand...
Click to collapse
Anyways now that it's okay - cool down and read around before messing with your EVO
austontatious said:
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
Click to expand...
Click to collapse
Too much 3d porn is never good for any phone
You know, it is possible for the OP to be telling you guys the truth about not doing anything to his phone, and his phone just had some kinda software/hardware defect, from running the battery too low..
Sent from my PG86100 using XDA Premium App
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
Alright so long story short I tried to rush through rooting my new phone here without checking everything out too much (complete fail on my part...but I wanted it rooted before I went out to the bars to save some battery life haha...ironic, now I'll have no phone tonight).
I went to root it and it somehow got screwed up...the sense launcher wasn't showing up along with the fact that when I pulled down the notification bar and hit settings, it crashed, so I went to unroot it with the RUU 1.13.651.1 and when I got to the comparison screen it said I had 1.13.651.1_R2...and being already frustraited at this point, decided how worse could it get? Tried it out, not my brand new phone is stuck at the black htc screen....fail.
Anyone have any suggestions on what to do? I tried running it again to no avail...I'm about to try the other RUU to just see if it works, but I'm running out of other ideas. Anyone that can help, it would be greatly appreciated.
Thanks!
awesome first post and congrats on your new paperweight
How do you brick a phone using one click root?
shook187 said:
How do you brick a phone using one click root?
Click to expand...
Click to collapse
Sent from my EVO using xda premium
just smashed on the floor and go the Sprint store and pay $100.00 with the insurance.
But, how did you bricked? is only one click!!
shook187 said:
How do you brick a phone using one click root?
Click to expand...
Click to collapse
sorry i dont mean to laugh
but hahahahaha lol
i couldnt help it lol
one click root bricking. im sorry man
tough luck and congrats on your first post
will it turn on, what can you get it to do?... geez guy at least attempt to help evern though this was an idiot move to rush thru it...
he could try to unlock his bootloader, manually flash the recovery and flash a rom thru there ^_^
but since he even failed at one click root, how will he do all that?
can u get to the bootloader?
does ur comp recognize it when u plug it in? even if it's still stuck
flex360 said:
he could try to unlock his bootloader, manually flash the recovery and flash a rom thru there ^_^
but since he even failed at one click root, how will he do all that?
Click to expand...
Click to collapse
Not that hard if he actually takes his time and reads before doing anything. If he can unlock the bootloader with htcdev and flash a recovery he should be ok
Albaholic said:
Not that hard if he actually takes his time and reads before doing anything. If he can unlock the bootloader with htcdev and flash a recovery he should be ok
Click to expand...
Click to collapse
you quoted me and repeated the same thing i said lol
Easy. Hold the volume buttons down while you turn the phone on then choose to reformat or restore or whatever the option is.
Sent from my EVO using xda premium
Weird, my HTC screen is white
Sent from my EVO using xda premium
HixVAC said:
Alright so long story short I tried to rush through rooting my new phone here without checking everything out too much (complete fail on my part...but I wanted it rooted before I went out to the bars to save some battery life haha...ironic, now I'll have no phone tonight).
I went to root it and it somehow got screwed up...the sense launcher wasn't showing up along with the fact that when I pulled down the notification bar and hit settings, it crashed, so I went to unroot it with the RUU 1.13.651.1 and when I got to the comparison screen it said I had 1.13.651.1_R2...and being already frustraited at this point, decided how worse could it get? Tried it out, not my brand new phone is stuck at the black htc screen....fail.
Anyone have any suggestions on what to do? I tried running it again to no avail...I'm about to try the other RUU to just see if it works, but I'm running out of other ideas. Anyone that can help, it would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Well, the good news is the phone is not hard bricked, it has a soft brick and is recoverable. Redownload the RUU and try again, but make sure you have the correct one. If that doesn't work you'll have to unlock with htcdev, flash a recovery and flash a ROM. Then try the RUU again if you no longer want root.
Like others have said...it sounds like there is hope for your phone yet. Take your time and CAREFULLY follow instructions for whichever process you choose. Hopefully you post again later saying you were able to fix it.
apparently he doesn't care that much... he hasn't checked back recently...
ticklemepinks said:
apparently he doesn't care that much... he hasn't checked back recently...
Click to expand...
Click to collapse
I think he was going out to the bars...without a phone
Come on guys you scared him away. We were all noobies at one point. I done stupid moves and spent countless hours fixing my mess with the help on here. Give the guy a break. Op if u want hit me with pm and we can work together on this I am welling to help
Sent from my EVO using XDA
HixVAC said:
Alright so long story short I tried to rush through rooting my new phone here without checking everything out too much (complete fail on my part...but I wanted it rooted before I went out to the bars to save some battery life haha...ironic, now I'll have no phone tonight).
I went to root it and it somehow got screwed up...the sense launcher wasn't showing up along with the fact that when I pulled down the notification bar and hit settings, it crashed, so I went to unroot it with the RUU 1.13.651.1 and when I got to the comparison screen it said I had 1.13.651.1_R2...and being already frustraited at this point, decided how worse could it get? Tried it out, not my brand new phone is stuck at the black htc screen....fail.
Anyone have any suggestions on what to do? I tried running it again to no avail...I'm about to try the other RUU to just see if it works, but I'm running out of other ideas. Anyone that can help, it would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
First off don't feel too bad, No matter how sure you know what your doing we all make mistakes. I paperweighted mine while manually installing some mods last night. If you would of watched the how to RUU the evo lte you would of seen that that the black HTC screen is perfectly normal. The phone will sit on that screen for like 10 minutes sometimes it will reboot and sometimes you will get differnt screens. The key is to have the drivers handy and install them if ur PC ever calls the device android 1.0.
The RUU version 1.13.651.1_R2 is the one you should be using. As scary as it is you just need to be patient, and let the RUU run it may look like nothing is happening but something is.
fearbasel04 said:
Come on guys you scared him away. We were all noobies at one point. I done stupid moves and spent countless hours fixing my mess with the help on here. Give the guy a break. Op if u want hit me with pm and we can work together on this I am welling to help
Sent from my EVO using XDA
Click to expand...
Click to collapse
Nice! Who said there are no more Good Samaritans?
Props,
Doc
I tried to root my phone using the regawmod process on my PC. i followed the steps until the first reboot…i put the debugging option on the phone when it rebooted because everything got wiped as it said it would and then the phone went completely black as if it was rebooting as it should..but never reloaded..i cant turn my phone on or anything..phone was charged to 65%..so i know it couldn’t have died that quick..What happened?? please help!
hmmmm....
not sure what to tell you man.
hold power button for a while, until you see it reboot... IF you see it reboot. should happen within ten seconds....
if you have root access..... download quickboot and try to boot into recovery.
we'll go from there.
also, plug device into comp and see if it detects it.
assuming you installed all drivers necessary and software packages from that thread, correct?
I did everything to the T...I tried to connect to the PC again and it did not detect the phone, and still wouldn't turn on..so i took it as a loss and took the phone back to the store and they gave me a new one because it wouldn't turn on...I appreciate the reply back.:good:
probably wasn't bricked, btw
This kind of makes me worry..... with what everybody has used, which would be considered the "best" to use? This is my work phone and I'm ok to root it and what-not; heck, I root my co-workers phones all the time so I'm no noob at all to this. Thanks!
I don't know what happened but I tried again, started with fresh files and it worked..I'm thinking one of the files got corrupted our wasnt being recognized by my PC...but now I'm enjoying my rooted phone!
Sent from my EVO using xda app-developers app
pogibry said:
This kind of makes me worry..... with what everybody has used, which would be considered the "best" to use? This is my work phone and I'm ok to root it and what-not; heck, I root my co-workers phones all the time so I'm no noob at all to this. Thanks!
Click to expand...
Click to collapse
Regaw is the best to use, I would say. This is the only case of this I've heard and I've followed the thread from day 1. A few did have it fail part way thru, but then just reran it and all went fine.
If you want S-off, there is the lazy panda method now. But I've seen way to many bricks on that thread to recommend it to anyone. But I guess they're also working constantly on a fix for those bricks and have had measured success (from what I've read).
Sent from my EVO using xda premium
Every one of your 4 posts have been negative on regaw's process and your experience...
Here is a little tip of advice for you that MIGHT lead you to getting actual valuable answers to your problem...
PM Regaw....I'd say post in his thread but you dont have 10 posts...
Regardless I can promise you that creating a new thread each time you try is NOT going to help your situation at all.
OK. I just wanna say that this has got to be the MOST difficult device to unlock & root. I just spent the past 2+hrs trying! I was trying to unlock & root my girlfriend's phone but it is just not happening. I watched a million videos on youtube and even read all the tutorials. Its just not working. I am stuck at the part where my command says "waiting for device"...I would LOVE for someone to help me with this...message me...or whatever. I know this thread will probably be deleted anyway..so send me a message because I am SUPER frustrated!
I have a Galaxy Nexus and it took 5 minutes to do everything I wanted to do!
Fix you install the drivers onto the computer?
Read, Search, Read again, ... Then Ask with Tapatalk 2
If U read my post.. I said I have read everything and watched every YouTube video about it and I cannot do it. That is why I made this post to get answers. If not, that's fine... Not my phone anyway.
Thanks for your "help"... NOT.
filmusikat said:
Thanks for your "help"... NOT.
Click to expand...
Click to collapse
This attitude won't get you far in this community so if you would really like help from others start behaving like a decent man and not just like some "too cool gangsta for this forum".
Try unlocking and rooting your girlfriend's phone on some other computer available to you.
I followed this tutorial and i unlocked mine in matter of minutes.
http://androidforums.com/3892643-post2.html
Good luck.
So you tried a couple of hours...
I actually tried for days. Weeks went by and still could not get the wire trick to work. Same thing... it said: "Waiting for device".
Finally, I read in a forum to try a different computer and that's what I did. Made sure that HTC Sync and stuff like Double Twist were not installed. Re-installed the adb and usb drivers. And still did not work the first time I tried it. So, I went into Device Manager and deleted the Android Phone entry. The computer then re-installed adb by itself. After that, I finally got the "Do the wire trick" message!!!!
It took me three or four tries before finally getting it.
Now I am S-Off and downgraded to Eng hboot. Installed Team Dirt's AOKP Rom and could not be happier. It is so smooth that I have kept it as my daily driver, even though it is still missing a couple of things.
So, definitely try using another computer. Even better if it has never been connected to an android phone and you can install the drivers from scratch.
Hope that helps.
So as you can see, others agree that it might be a driver issue since "waiting for device" usually means the phone is not being seen by the computer due to the drivers not being installed.
But I don't know what I'm talking about because it took me only one hour to root and s-off my phone just by reading the directions. I must be a moron. :banghead:
Read, Search, Read again, ... Then Ask with Tapatalk 2
I had that "waiting for device" problem before (am using Desire S tho), and to my surprise, the solution to that was to change my data cable. I used the one from HTC, and solved by using a generic one.
and yeah, that attitude needs a chmod..
coal686 said:
So as you can see, others agree that it might be a driver issue since "waiting for device" usually means the phone is not being seen by the computer due to the drivers not being installed.
But I don't know what I'm talking about because it took me only one hour to root and s-off my phone just by reading the directions. I must be a moron. :banghead:
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Or USB debugging might be disabled.