Related
So today while following a tutorial, not sure which one. I managed to completely erase my system partition from my phone, leaving me without anything, including s-off. So now im stuck at S-ON, no system software, and no custom recovery. What gives? Is there anyway to put atleast SOME software on the phone. I'd love to use my EVO that i just purchased today, and spent countless hours trying to get permanent root. Even a stock ruu or something would be nice. Anything is appreciated. Thanks.
Try a stock ruu..
apristel said:
Try a stock ruu..
Click to expand...
Click to collapse
I've googled, tried the HTC site, somewhat searched xda, found a lot of rooted stock roms, could you point me in the direction of an ACTUAL stock ruu? My phone came with 2.2 and 2.02 bootloader, if that helps any.
https://bit.ly/f9Jx0f
Only has up to 3.30 though.
But I think thats the one that shipped on phones with that booloader version.
The RUU won't recognize my phone, but the software itself has a few typo's and asks for an adb device with an odd looking string after it. Would it be possible to find the update.zip from the ruu and install it using fastboot? because thats about the only thing that works on my phone.
You have bootloader right? How about this one?
OTA_supersonic_3.70 + full RUU
ICEReaction said:
You have bootloader right? How about this one?
OTA_supersonic_3.70 + full RUU
Click to expand...
Click to collapse
Yes I have bootloader, call me ignorant, but what do I do with the zip files? I the exe link is broken, and i've never had to use the bootloader before, i came from an htc hero with a custom recovery.
Here's the RUU link posted by TMartin03: RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe
From here page 7, post #67
Mirror by teshxx
If you need to PC36IMG file, its located here in this post by TMartin03. I assume you would have to rename this to PC36IMG.zip for it to work in bootloader.
Fixed, flashed that pc36img file, THANK YOU!!!!!
Awesome...glad to help and hear that it worked out for you.
i flashed my htc evo phone, still stuck on htc evo 4g screen. cant get into bootloader though im stuck
godzilladad said:
i flashed my htc evo phone, still stuck on htc evo 4g screen. cant get into bootloader though im stuck
Click to expand...
Click to collapse
Pulling the battery, putting it back in, holding the power and vol down button simultaneously (dont release) doesn't get you to the bootloader?
I have a unique problem, and I think I will need someone with some patience to help if its even possible to get my phone back to stock. Recently my EVO screen backlight completely stopped working yet when I turn on the phone I know that it still boots up because i still get notification sounds and alarms and in direct sunlight i can still use the phone. My phone has a custom flash screen unrevoked, and it has an old stock rom 3.70 and hboot 2.10 with custom boot animation not to mention a custom kernal. What I need to know, is it possible to do a push or something to flash the radio to s-on and reset it all back to "stock"? I only have until 8-18-2011 to return my phone to sprint and to
get this done so please someone that knows what they are doing please reply. Thank you so much in advance. I have tried to flash the unrevoked s-on tool but it does not work with hboot 2.10 it seems and there must not be a recovery cause I get the triangle ! when i try to goto it. Please help!
Is your screen blank the entire time, from when you first turn on the phone? If so, then it is a hardware problem and I don't think Sprint will know the difference anyway until they've taken it apart and repaired it, and you'll have shiny new refurb by that time. But, still, if the phone really is booting up, it might be possible to run an RUU (the latest one) if you have usb debugging enabled already, or to flash a stock image. However, neither of those things will set the phone back to S-On. You would have to blindly go into the recovery and flash the S-On tool, which would be really hard. And I don't think it's necessary. I'll post some links to the RUU and/or PC36IMG instructions in a minute, but if you do some searching, you can find them.
Edit: Here's the link to a number of RUU's and PC36IMG files to flash back to stock. I would use the 3.70 version, because the 4.24 version installs an hboot which is locked down (although you would still have s-off). The RUU needs to be run with the HTC drivers installed, USB debugging on, and the phone actually booted up and running and connected to your computer. The PC36IMG file would need to be placed on the root of the SD card and named PC36IMG.zip. The bootloader would automatically recognize that file and after about 1-2 minutes of checking it, it would give you the option to hit volume-up to start the update (even though you can't see it). Good luck...
http://forum.xda-developers.com/showthread.php?t=884060
soldierforchrist2 said:
Is your screen blank the entire time, from when you first turn on the phone? If so, then it is a hardware problem and I don't think Sprint will know the difference anyway until they've taken it apart and repaired it, and you'll have shiny new refurb by that time. But, still, if the phone really is booting up, it might be possible to run an RUU (the latest one) if you have usb debugging enabled already, or to flash a stock image. However, neither of those things will set the phone back to S-On. You would have to blindly go into the recovery and flash the S-On tool, which would be really hard. And I don't think it's necessary. I'll post some links to the RUU and/or PC36IMG instructions in a minute, but if you do some searching, you can find them.
Click to expand...
Click to collapse
Yes the screen is just black when you turn it on, yet the phone will still vibrate and gives sound notifications of texts/email/alarms ect. I know the RUU will flash the rom back to stock but will flashing the latest RUU replace my kernal or is it possible to put that back to stock and what can i do about the splash screen/boot animation? Thank you for your time in this matter. I just want to do everything that is possible to get it back to stock before I send it off to avoid getting charged for my refurb.
z143 said:
Yes the screen is just black when you turn it on, yet the phone will still vibrate and gives sound notifications of texts/email/alarms ect. I know the RUU will flash the rom back to stock but will flashing the latest RUU replace my kernal or is it possible to put that back to stock and what can i do about the splash screen/boot animation? Thank you for your time in this matter. I just want to do everything that is possible to get it back to stock before I send it off to avoid getting charged for my refurb.
Click to expand...
Click to collapse
I understand. I don't know all of that for sure, but I'm pretty sure the RUU will replace your ROM, splash screen/boot animation, radio, hboot, recovery, etc. It wipes everything out and sets it back to stock. I think the only thing it won't do is set it back to S-ON. If you know what kind of recovery you have and how to use it, you can try to blindly flash the S-On tool from Unrevoked.... But I really don't think Sprint will know the difference, or even care when your screen is totally shot.
Edit: If you really really want to try to flash the S-On tool, do that first before you run the RUU. It will wipe out your custom recovery.
soldierforchrist2 said:
I understand. I don't know all of that for sure, but I'm pretty sure the RUU will replace your ROM, splash screen/boot animation, radio, hboot, recovery, etc. It wipes everything out and sets it back to stock. I think the only thing it won't do is set it back to S-ON. If you know what kind of recovery you have and how to use it, you can try to blindly flash the S-On tool from Unrevoked.... But I really don't think Sprint will know the difference, or even care when your screen is totally shot.
Edit: If you really really want to try to flash the S-On tool, do that first before you run the RUU. It will wipe out your custom recovery.
Click to expand...
Click to collapse
I have been looking for a video that might show me how to flash the s-on tool with clockworkmod 3.0.0.5 so i can try and follow the video blindly before i flash the RUU. Would you happen to know of a video that I can follow along with to maybe get s-on back? I would rather try and do it blindly than just sending it in.
z143 said:
I have been looking for a video that might show me how to flash the s-on tool with clockworkmod 3.0.0.5 so i can try and follow the video blindly before i flash the RUU. Would you happen to know of a video that I can follow along with to maybe get s-on back? I would rather try and do it blindly than just sending it in.
Click to expand...
Click to collapse
Makes sense. I don't know of a video off hand but I bet it's out there. I'll help you look. The hardest part is going to be finding the s-on zip on the SD card blindly. I think you can name it "update.zip" and select the option "flash update.zip".
http://www.youtube.com/watch?v=RyulgnaVW_w
Not the best video, but I think it will show you how to get there. You would need to select "apply update from sd card" instead of choose zip from sd card like they did. Pay careful attention to the parts that say "no, no, no.... yes - .... no, no" I don't know for sure if it's the same on every phone and version . Hopefully it is. You might find a better video, but this is the best I can do for you.
I'm not 100% sure what happens after you press "apply update from sd card" I think it will give you the "no no no... yes... no no no" option again.
Actually, I just realized something. Since there are videos that show you specifically how to flash an arbitrarily named zip file. You could just wipe your SD card clean and put the zip on there so that it is the only thing on the card. That might work too...
So, that being said. Here's a much better video that will show you how to flash the S-On tool. Hope this works for you.
http://www.youtube.com/watch?v=guHo_FbSy8Y
WEll as you can see i am stuck on the bootloader screen adn i cant see to get out as i tried to s-off and relocked my phone i cant factory reset becasue it just bring me back up to the bootloader and i cant even unlock it again becasue it will just hang on unlocking tried to flash an RUU file and it just checks but doesnt flash at all i am in serious need of help so anyone please help? i am hboot .98 6.01.605.05 radio 1.09.01.0312
I am not an expert as I just rooted my phone for the first time this week. However I have had the issue where a rom didn't install correctly and I was able to boot into recovery and install a backup. Not sure if this will help you but thought I would mention it. Hope someone can get you lined out asap.
Well I can't really do that since I'm relocked
Hey guys,
fairly new to this all and it seems I have messed up at some point...
I managed to root my phone and i do have TWRP on it and wanted to install a rom (blade elite 1.1). went into bootloader and flashed the boot.img with the tool, then went into recovery, cleared all the caches/factory reset/system and flashed the rom which i had previously copied onto my sd card. then i pressed reboot. It didnt start up for a few minutes so i kind of panicked and went into recovery again. I had made a backup previously, which I then restored. But it's still stuck on the screen where it sais htc one on the white screen with the beats audio thing on the bottom... Waited for around 20 mins. I can still get into recovery, so I'm hoping not all hope is lost.
What do I do now? :/ Do I have to flash the stock kernel or something first before I can restore with twrp?
Please help :/ I kinda really need my phone...
Oh yeah I forgot one thing. The tool said "error: device not found" in the first cmd window when I flashed the kerel, but when I clicked it away a second one popped up and it said it flashed correctly. It did the same thing when I flashed twrp and thats definitely on my phone, so Im guessing it has flashed the kernel correctly. Just thought I'd mention that.
fastboot getvar version-main
gave me:
2.17.401.2
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Your hboot is to low, you need to update. Since you used the ruu, go into settings - about menu and update the phone with the software update utility.
You are still on ICS and need to update to JB.
You can also update your Hboot yourself by check your cid number using this app
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Finding the Hboot to match your cid number here
http://forum.xda-developers.com/showthread.php?t=1957376
And upgrade your Hboot manually or by using a tool like this one here (you'll need to put the correct Hboot in the relevent folder of the app first!)
http://forum.xda-developers.com/showthread.php?t=1924003
Read through the full guide and comments first before proceeding!
Hope this helps.
Easiest is to update with the official ota now as he already installed the ruu
And yes you can use the old unlock code again
StreamOfLife said:
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Click to expand...
Click to collapse
You can use the original Token they sent you. No need to go through the whole HTCDev process again :good:
You guuuuuys, it worked !!
Thanks a bunch! Was totally easy with the ota update too, very smart!
Good ! Enjoy
CASE CLOSED !
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!