Two lines of my digitizer are dead, so I am sending my unit back to Best Buy for repairs. They don't care about rooting, etc, since it is a clear hardware issue. I plan to send it in with S-Off on the most up-to-date Sprint rom in factory reset state.
My question is this: What is the maximum precautions I can take to prevent an update to HBoot 1.5?
Edit: Would installing the eng hboot prevent any sort of automatic update from reapplying S-ON?
Din65 said:
Two lines of my digitizer are dead, so I am sending my unit back to Best Buy for repairs. They don't care about rooting, etc, since it is a clear hardware issue. I plan to send it in with S-Off on the most up-to-date Sprint rom in factory reset state.
My question is this: What is the maximum precautions I can take to prevent an update to HBoot 1.5?
Click to expand...
Click to collapse
Updating to HBOOT 1.50 does not turn the phone S-On. You can still flash a different HBOOT if you are S-off and 1.50. As long as they give you back your phone (and not a different one), you should be fine.
It seems I am asking the wrong question. Without pushing the "fastboot oem writesecureflag 3" command on purpose, is there any way I could lose S-Off? I haven't heard of anyone having full S-Off and HBoot 1.5
Din65 said:
It seems I am asking the wrong question. Without pushing the "fastboot oem writesecureflag 3" command on purpose, is there any way I could lose S-Off? I haven't heard of anyone having full S-Off and HBoot 1.5
Click to expand...
Click to collapse
No, there is no way to lose s-off by applying any current HTC updates. I updated to HBOOT 1.50 from an S-off phone and it just said LOCKED at the top of the screen while in bootloader. I could still flash things like normal (if I remember correctly). I downgraded my HBOOT to the ENG version using the PG86IMG.zip method. It flashes fine (unlike an S-on HBoot 1.50 device), but I don't think the fastboot method of writing the HBOOT worked for me.
I just want to confirm, flashing the most up-to-date RUU will NOT turn on S-ON, nor will any other update besides a firmware level, targeted command?
Din65 said:
I just want to confirm, flashing the most up-to-date RUU will NOT turn on S-ON, nor will any other update besides a firmware level, targeted command?
Click to expand...
Click to collapse
Was I that unclear? I've flashed both of the ruu's containing hboot 1.50 and am still s-off. I even did HTC's unlock while on 1.50 just for fun. I'm now on the eng hboot. No current update does anything to reset the security flag.
Sent from my PG86100 using xda premium
i unrooted running the 2.13 RUU and i ended up with s-off and the 1.19 bootloader. When i run the s-on program it says wrong bootloader...what can i do?
i just need to take my phone back to best buy to exchange
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
vega312 said:
I need to relock my cell to S-ON as I need to send my cell to HTC for repairs as my GPS stopped working. How do I do that if I accomplished S-OFF with jbear and HTCDev method.
Thanks!
Click to expand...
Click to collapse
You need to start by flashing the 2.89.651.2 RUU, either using the RUU.exe from Windows or an RUU.zip renamed to PG86IMG.zip from the bootloader. If you didn't do the htcdev unlock again after the wire trick, the stock bootloader should show ***LOCKED*** with a version of 1.58. Since you are only getting the phone serviced, it's probably OK to leave it S-OFF, but if you want it 100% stock you need to issue the following command after you have verified that the bootloader is 1.58:
fastboot oem writesecureflag 3
Once you have issued this command your phone will be S-ON and you will have to do the wire trick again after you get it back to be S-OFF. My understanding is that most repair facilities, including Sprint, don't mind if you give it to them S-OFF. However, if you are sending it back to HTC it might be worth doing since with stock software, a locked bootloader and S-ON it will look "factory fresh" to them.
You might also want to test your GPS again once everything is back to stock, just to make sure it's not a ROM problem.
ramjet73
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
jb14813 said:
where can i get the ruu i ran the one on htcdev.com but it didnt change my rom
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?p=19089387
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
In an effort to upgrade bootloader and software to be compatible with cm11.. I used vipeRUU to go from 1.12 bootloader to 2.09 bootloader with the 3.17.651.471 software, whats confusing me is bootloader still says ..Unlocked ..and S-off after running ruu ..bootloader has changed and so has the software... (i was Previously s-off via Lazy panda).. i was under the impression that this would un root and lock bootloader again.. i know that i now have lost root i know how to check that .. question is , is bootloader locked now as well?..tried rumrunner and moonshine to no avail, to get S-OFF .. and it needs to be unlocked for those exploits to work.. any ideas?
It will lock your bootloader and return the phone S-on if you chose those options in the menu when you first ran VipeRUU. If you're still S-off, then all you need to do is unlock the bootloader again unless it's showing unlocked. An easier route than what you chose would have been to update your Hboot to the Rumrunner Hboot, which takes less than a minute to do. You'll still need to update your firmware, since VipeRUU is a version behind what's currently out there. If you're S-on now, you'll need to unlock the bootloader and run Moonshine.
Sent from my HTC EVO 4G LTE
ok .. i see what you're saying .... i just ran rum runner... and it seemed to do the trick im currently S-OFF hboot 2.09 with the 3.17.651.4 71 software.. was able to install twrp>>>..I think im good to go!?..>>>>> i shall now...FOAF..lol...btw Thanks!!!
Yep, you should be good to go now. Just make sure that you have Superuser privileges and all should be right with the world:thumbup:
Sent from my HTC EVO 4G LTE