I decided last night after 10+ years with sprint, I switched to verizon.
I want to sell my LTE
I want to put my evo LTE back to complete stock, including, taking away "tampered" and "unlocked".
I am Son, rooted, with custom ROM.
Question is, will I have to get Soff first to be able take away "tampered" through lazy panda or is there another way?
Thanks
If you have hboot 1.12 you might be better off leaving it rooted and selling it as such.
Sent from my EVO using xda premium
You'll need to relock the bootloader with fastboot ("fastboot oem lock" from command prompt) and then run the RUU for the software version that matches the bootloader you currently have.
But yeah, agree with previous poster...if you're on 1.12 I would leave it and find someone on xda who wants it for s-off. Otherwise, above instructions should work. For more details, do a forum search...there have been multiple threads on the subject.
Sent from my EVO LTE
Thanks for the input. Yes it still has 1.2 hboot.
I guess I can leave it up to the buyer how they want the phone set up.
premo15 said:
You'll need to relock the bootloader with fastboot ("fastboot oem lock" from command prompt) and then run the RUU for the software version that matches the bootloader you currently have.
But yeah, agree with previous poster...if you're on 1.12 I would leave it and find someone on xda who wants it for s-off. Otherwise, above instructions should work. For more details, do a forum search...there have been multiple threads on the subject.
Sent from my EVO LTE
Click to expand...
Click to collapse
Do you know where I can find the RUU? I am definetly 1.12 hboot and the buyer wants completely stock.
rc51rider said:
I decided last night after 10+ years with sprint, I switched to verizon.
I want to sell my LTE
I want to put my evo LTE back to complete stock, including, taking away "tampered" and "unlocked".
I am Son, rooted, with custom ROM.
Question is, will I have to get Soff first to be able take away "tampered" through lazy panda or is there another way?
Thanks
Click to expand...
Click to collapse
Just did this the other night also. My phone was just like yours. I am not sure if S-On could just load the .img from the thread below. So I went the long way and went to S-OFF then followed the thread below.
http://forum.xda-developers.com/showthread.php?t=1744700&highlight=stock
Getting S-Off was SCARY for me. I went straight from MeanROM to try and get S-OFF and my phone was running the utility and then it went black screen and on my PC the number kept increasing in time. I finally stopped after waiting ten mintues. I had to go to my PC and run Ubuntu Live to unbrick the phone.
http://forum.xda-developers.com/showthread.php?t=1737123
Read the Linux part at the beginning of the thread before you start just in case. I am not a Linux user and getting into the right folders was a little tough.
yazyazoo said:
Just did this the other night also. My phone was just like yours. I am not sure if S-On could just load the .img from the thread below. So I went the long way and went to S-OFF then followed the thread below.
http://forum.xda-developers.com/showthread.php?t=1744700&highlight=stock
Getting S-Off was SCARY for me. I went straight from MeanROM to try and get S-OFF and my phone was running the utility and then it went black screen and on my PC the number kept increasing in time. I finally stopped after waiting ten mintues. I had to go to my PC and run Ubuntu Live to unbrick the phone.
http://forum.xda-developers.com/showthread.php?t=1737123
Read the Linux part at the beginning of the thread before you start just in case. I am not a Linux user and getting into the right folders was a little tough.
Click to expand...
Click to collapse
Yeah, I think I'm going to do it the long way too. I've done s-off then back to s-on already, but that was before the OTA's and up dated roms came out.
Thanks for the input!
I too have switched and have 2 Evo LTEs for sale on eBay if anybody is interested. Hboot 1.12 and all!!! Comes with cases and sdcards too!
SUCCESS with Lazy panda!
Worked flawlessly!
Related
EDIT: UPDATE .... i managed to get the phone rebooted .... held the force reboot buttons for literally over a min in desperation.... not i need to fully unroot and start from scratch but am having trouble with that still.... can anyone help me either (A) get s-off ... or (B) get it so that i am completely unrooted so i can start over from scratch to get s-off????
Ok folks, i am officially stuck.... its been quite awhile since i have really asked for help on here but i am stuck in a really bad way!!!
Here is how i got to where i am
Just bought my brand new EVO LTE today and went to root it using "[ROOT] RegawMOD EVO 4G LTE Rooter | Updated 06.13.12" from this section!
everything seemed to work great and it said everything rooted properly.... I love Clockwork mod recovery so i then flashed that and it worked properly to or so i thought! so i went to create an origional Nand but it would not work, so i decided to flash TWRP back instead and do that way. when going into the bootloader it said "Tampered" as expected, but it still said S-on so obviously not a proper and correct root.
So i ran RegaMOD again as it said in the instructions, but it would never get passed the HTCdev part, it would just say "sucessfully logged out" and sit there forever and do nothing. So after a few tries of that i decided to unroot and start over from scratch. I could not find an unroot method for RegaMOD so i then went to the other root method "How to Root HTC Evo 4G LTE! [Windows/Mac/Linux] - by Zedomax" in this section and saw it had an unroot method which i followed to the letter! did full unroot through SuperSU and then downloaded the stock RUU from that section for my phone with the proper version number.
everything seemed to be running fine went to the black "HTC" screen and everything was going smoothly.... then the update failed and my phone stayed on the black HTC screen. my computer prompted me to recover which i could not really do as you can't pull the battery on this phone. So i then tried to update the RUU again except this time it did not list a current software version, only the one i was updating too.... it failed again 2 more times!!
when plugged into the computer my phone displays the black "HTC" screen
when plugged into the charger it displays the following screen info (bootloader look)
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT AO <---- MIGHT BE FASTBOOT AC HARD TO TELL
Update Fail!
when un-plugged it says almost the same thing
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PUT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 26 2012,19:54:01
FASTBOOT <---- THIS IS THE ONLY CHANGE
Update Fail!
no buttons do anything at all, in any combination or holding pattern
PLEASE HELP ME!!!!! THANKS TO ALL IN ADVANCE!!!
just one thing, s-on or s-ff has nothing to do with root
did you relock your bootloader before running the RUU?
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
smw6180 said:
And now we see what happens when we blindly click stuff without an understanding of what we're doing. I hate to be a douche (and I'm not usually) but this is EXACTLY the kind of thing you should NOT do with a brand new phone without intensive study. While the one-click root methods are convenient as hell, their major shortcoming is that they don't allow people to learn what they're DOING when they click that batch file...which leads to problems like yours.
As mentioned above, you need to relock your bootloader before running the RUU.
Also as mentioned s-off and root are completely different...and frankly you don't need s-off with HTC's unlock anymore.
Get your phone back to the bootloader, plugged in via USB to your computer.
Install adb (you should already have it, I hope) and type fastboot oem lock from a dos prompt (command prompt).
That relocks your bootloader. reboot into bootloader and you should see 'relocked'.
THEN run the RUU and start over....and this time please read and understand what you're doing rather than just blindly doing the 'cool root thing'.
Click to expand...
Click to collapse
+1
shootin4aces said:
Sorry I just got excited, I have run root on my last 2 phones (much more research on those) and just kinda fell into a super late night lazy not thinking groove... please dont be offended, the reason a rarely dont ask for help is i usually have not needed it.... no need to get hostile.... thankyou for the responce
Click to expand...
Click to collapse
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
shootin4aces said:
no, i did not re-lock the boot loader.... didnt know you needed to, not used to that on the OG EVO... how do you go about redoing that? I always thought S-OFF was an important part of root..... the main reason i looked and noticed it was since i flashed clockworkmod recovery and wanted to go back to TWRP i read on their page that "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!" I guess that since i used HTC unlock i could flash, but either way, should i need to go back to stock for any reason, could you please tell me the proper steps?
Thanks a million!!!
Click to expand...
Click to collapse
read the post above yours he did tell you how to do it..lol
Oh and before I forget: Don't use CWM. Unless they've fixed it in the last couple of days it breaks your /misc partition, which is quite probably what caused your issues in the first place.
Use TWRP. After you have root/unlocked you can download goomanager from the Play Store...it will install it for you.
smw6180 said:
Wasn't being hostile and I'm not offended. It's just there are entirely too many people who haven't been paying attention to what they're doing and get upset about it when it all blows up in their face.
And for the record every phone is different. I've rooted my last 4 Android phones, 3 evo's and the hero, and root was different on each one, with different potential problems. Being excited is great. But you need to take the time to learn what you're doing, first.
Click to expand...
Click to collapse
+1 and wrong section
This is the method I used on my 4lte without a problem. But you should read entire post before attempting cause it flashes TWRP recovery automatically along with SU. Clockwork still is buggy.
http://forum.xda-developers.com/showthread.php?p=26955832
from my "Beach Watcher" 4LTE
thankyou
all problems have been fixed, thankyou everyone for all your help
again, sry for posting in the wrong forum with this issue, and i am sorry if i came off as a noob! I'm really not, just completely jumped the gun and am very very tired as i have been up for almost 36 hours now
thankyou again for all the help, and as i normally do, i will perform all my research before my next venture.... a lot has changed between this phone and my last one that i rooted and modded, i will be more prepared in the future!
Selders, you're here now?! Good to see ya here
sent from a shining jewel 4g LTE
<MOD EDIT>
THIS IS NOT SAFE FOR REGAINING S-OFF
DO NOT PERFORM THIS METHOD IF YOU WISH TO KEEP S-OFF
</MOD EDIT>
So i didnt want to wait for the devs to update thier roms, and i wanted the radio updates as well. for all those ppl say not to do the OTA you will losew root until a new method is found are not correct. Yes you will lose root, but you can get it back. and its easy. Here are the steps
1. Relock boot loader
2. apply RUU for the same rom version you are running http://forum.xda-developers.com/showthread.php?t=1645890
3. rerun RegawMOD EVO 4G LTE Rooter
3a. It will sucessfully unlock and flash the recovery on your phone, but it will fail to root it.
3b. Download the rooting files http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
4. Extract the contents of the zip file
5. Copy the file CWM-SuperSU-v0.87.zip to your SD card
6. Reboot to recovery
7. Flash CWM-SuperSU-v0.87.zip
8. Reboot to system and Viola you have have a rooted install
But can you still unlock with Lazy Panda?
EDIT: I realize you can unlock with the RegawMod unlock, but I have no doubt HTC's unlock tool will work.
Try to lazy panda your new hboot
{ParanoiA} said:
Try to lazy panda your new hboot
Click to expand...
Click to collapse
This is really the main(only?) concern.
Sent from my LTEvo
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
LiquidSolstice said:
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
Click to expand...
Click to collapse
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Dude, just listen to LiquidSolstice on this one. DO NOT OTA an already S-OFF PHONE! Literally in a few hours we will probably have a stock / rooted ROM posted. Just have patience.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
The compelling reason to S-OFF is the fact that HTC and Sprint are never made aware in the slightest that you have done anything to your phone. The Dev unlock runs and tells HTC and Sprint that you are messing with your device. If done correctly, S-OFF gives you complete unfettered access to your phone, and with the proper tools, you can ensure you don't have to deal with the warning text on the screen that almost criminalizes you for having the audacity to unlock your phone.
People who are S-ON and HTC Dev unlocked ultimately run into strange issues down the road. You just wait until full AOSP comes around. On the Evo 3D, it was a nightmare. Even on the One-X, they're having issues because their boot partition is still locked and they can't use custom kernels (though I don't think that's as much of an issue with our phones).
S-OFF is so easy to perform, and the ONLY type of soft-brick that sometimes happens when performing it can be easily fixed with a dedicated tool. There is literally no downside to being S-OFF.
HseloMein said:
with these phones I can do every thing with S-ON, that you can do with S-OFF
Click to expand...
Click to collapse
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Lol so much fail. Good luck with that bro. I'm keeping my s-off
No one should follow this guy. You better hope it doesn't come back to bite you in the ass.
And you sir are in denial.
Sent from my EVO using xda premium
Rxpert said:
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
Click to expand...
Click to collapse
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
LiquidSolstice said:
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
Click to expand...
Click to collapse
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
While I respect your choice, I must also respectfully disagree with it. Regardless of what I think, you did take the time to explain how to re-root, and for that, I can't fault you. Thanks for your contribution.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
A recognized developer warning us should be enough reason.
OMG pbedard thanking my post? The world has just ended, lol.
Nice to see you again pbedard
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
RoidPusher said:
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Click to expand...
Click to collapse
Nope. Keep your hboot. It can be difficult if not impossible to downgrade hboot.
Sent from an EVO 4G LTE using Tapatalk 2.
HseloMein, would you mind editing the title of this thread (maybe add [S-ON] at the beginning) to indicate that it may affect the ability to get S-OFF in the future.
david279 said:
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Is this fact or assumption on the HBOOT Update? I'm S-off and no damn way am I taking the update BUT I thought I'd ask just for general knowledge. Back on the 3D, while we did get the HBOOT update, at least if you were S-off before the HBOOT update you held on to that and weren't stuck like chuck with HBOOT 1.50.000, what a nightmare. We were able to downgrade the HBOOT as long as you were S-off but why go through all that pain. I guess the saving grace here is that we really do have a pretty good "official" Dev unlock that doensn't totally screw you like the half baked unlock we got from HTC for the EVO 3D.
I need to get the word out to any and all LTE owners I know to not take it before I can S-off their phones.... might be a busy rest of the week! :laugh:
Thanks
I've done a bunch of searching on this and finally gave up and decided to ask it here because I can't find anywhere with actual info on it... I was trying to ruu back to the 2.13 base and then reroot from scratch with the new radios but ended up getting stuck in the bootloader with **TAMPERED** **RELOCKED** and **Security Warning** as the headers. It won't let me reboot, it won't let me into recovery, and I'm getting frustrated ... I still have access to fastboot but I'm useless with commands so I haven't been able to fix it. Any help?
Basically, here's the whole details.
I'm on hboot 1.15 s-on, dev-unlocked using regaw's rooting+unlocking tool. The phone had the 2.13 deodexed running, got it from here http://forum.xda-developers.com/showthread.php?t=1860728
Had twrp 2.X (the version before the latest) installed
I tried running the latest ruu.exe on my computer but it kept failing so I looked it up and assumed it must be because I was dev-unlocked.
Went into the bootloader>fastboot and locked it with fastboot oem lock
The phone rebooted into bootloader with the ** Security Warning** header and now I'm stuck...
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
sparytrainor said:
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Good luck to ya. I hope it works out.. I would still recommend using the hacked upgrades for radios and such.
Sent from my EVO using xda premium
Do you know with the security warning will cause running an RUU to fail?
rubyknight said:
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Click to expand...
Click to collapse
I'm in the same boat as you were - can you point me to where/how you got the RUU to run? I've got exactly the same situation, but my RUU (2.13) won't run, either in fastboot or the bootloader.
Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App
I originally rooted the phone using HTCdev method.
I'm trying to unroot the phone, I have Tampered, Unlocked, S-on
hboot- 1.19.0000
radio 1.12.11.0809
Per the RUU utility, it says Current information about your Android phone: Image Version 2.12.651.1
I followed a video tutorial http://www.youtube.com/watch?v=zC-3XsAoL_U&feature=player_embedded#! to unroot the phone. I was running Stock w/ Goodies 2.21, which I believed was software version 2.13.651.1, and so I downloaded a completely stock RUU and ran it, according to the instructions. It started doing its thing, the phone shows just a black screen with silver "HTC" in the center, nothing else in the corners or anything. it got to a point where it said Erasing Data, and then "sending...." then the RUUwindow came up saying
"Error 155, The ROM Update Utiliyu cannot update your Android Phone. Please get the correct ROM Update utility and try again."
I says to fix it, click next if there are exclaimation points in the corners. But I don't have excalinmation points in the corners.
Anyways, no matter what I try, the phone is stuck either at a black screen with HTC in the center, or if i pull the cable out, it goes to the boot loader and shows RUU failed. If I plug the cable back in, it goes back the the black screen.
Please help me!
Pretty sure this belongs in Q&A, not Development.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
Pretty sure this belongs in Q&A, not Development.
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
Sorry man, it just seemed like a development-type question. Just a wee bit stressed
dont you have to relock to run ruu?
if you watch his video you can see his evo is locked. i remember on a 3d i was having problem running the ruu until i relocked it..
maybe someone else can help you to get it back on.
stang04 said:
dont you have to relock to run ruu?
if you watch his video you can see his evo is locked. i remember on a 3d i was having problem running the ruu until i relocked it..
Click to expand...
Click to collapse
yeah, this is what im starting to see as I'm looking. It just didnt make sense to me that the phone has to be locked in order to do something like that, you would think it would need to be unlocked. So I'm going to figure out how to lock it.
Oh, and I just had to take the cable out and hold the power button for 10 seconds. rebooted fine, I'm almost wondering if I should just leave it.
if you wanna unroot i would first relock it, i am sure thats your problem since i had that happen to me before. at least you got it back on.:good:
stang04 said:
if you wanna unroot i would first relock it, i am sure thats your problem since i had that happen to me before. at least you got it back on.:good:
Click to expand...
Click to collapse
my heart is slowly returning to normal rhythm lol. looking for how to lock it back up now
jasongthang said:
my heart is slowly returning to normal rhythm lol. looking for how to lock it back up now
Click to expand...
Click to collapse
there is a way i think command "fastboot oem lock"
qbking77 has a great tutorial
http://www.youtube.com/watch?v=5yS7yy4XVA4
if you dont have Android SDK, qbking77 also has a tut how to install it.
http://www.youtube.com/watch?v=oaNM-lt_aHw