Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
cawaller said:
Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
Click to expand...
Click to collapse
I was in your same state two days ago I just downloaded and ran the global ruu twice and everything went fine. Just make sure after you run the ruu twice before the first boot of the phone make a factory reset from within hboot
No you wont get s on after the global ruu. You stay s off but locked but all you have to do is flash the jbear hboot and you are unlocked and s off.
Related
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
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
1. You can flash kernels in recovery and not HBOOT, you can also install a different splash screen logo (downside. you can brick the phone because there is zero security now. "S" in on or off means security)
2. you can update the HBOOT to 2.27 without any problems by downloading one from the develop section and it wont hurt the phone. link
3. HBOOT 2.27 was meant for the global update. if you dont plan on leaving the U.S. or use the phone for gsm then there isnt a need to update.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
I would run newest ruu with 2.27 hboot and flash a custom rom.
Damasterjj said:
I would run newest ruu with 2.27 hboot and flash a custom rom.
Click to expand...
Click to collapse
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
You can't ever brick your phone running an ruu unless its a bad ruu. To ruu though.. your phone must be relocked using fastboot. What you're thinking of is if you s-on with a modified hboot then you brick. You're good though.
1. Relock with fastboot oem lock
2. Run RUU
3. Honestly there's not much reason to unlock again
Sent from my ADR6425LVW using Tapatalk 2
polarEskimo said:
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
Click to expand...
Click to collapse
OK so unlocked and locked boot loaders mean you can use fast boot commands. If you ruu to the newest you will loose fast boot commands unless you unlock or flash an engineering hboot.
If you ever wanted to update after you have unlocked, you must relock the boot loader before updating. Ie never ruu on an unlocked hboot
Sent from my iPhone...
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Snuzzo said:
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Click to expand...
Click to collapse
Learned something new. Thanks.
Sent from my iPhone...
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
I was on HBOOT 1.58 which has problems with most roms so I wanted to downgrade my HBOOT. I used JuopunutBear to gain S-OFF and then downgraded my HBOOT to 1.50 and my radio is 1.06.00.1216. I then installed CM10. I could not get any data. I checked APNs and the APN is there. I then ran the retail RUU to see if it fixed the issue and it did not. I tried installing several different HBOOTS with no change. I tried a PRL update on the official OTA and the issue still exists. Any ideas?
hanzohittori said:
I was on HBOOT 1.58 which has problems with most roms so I wanted to downgrade my HBOOT. I used JuopunutBear to gain S-OFF and then downgraded my HBOOT to 1.50 and my radio is 1.06.00.1216. I then installed CM10. I could not get any data. I checked APNs and the APN is there. I then ran the retail RUU to see if it fixed the issue and it did not. I tried installing several different HBOOTS with no change. I tried a PRL update on the official OTA and the issue still exists. Any ideas?
Click to expand...
Click to collapse
If you flashed the RUU before doing the wire trick per the instructions on the unlimited.io website you should be on firmware (baseband level) 1.09.00.0706. My phone automatically reactivated after doing the wire trick and gaining S-OFF. If yours hasn't done that you should probably call Sprint and ask them to reactivate it for you.
ramjet73
Hey all,
so I've been running ARHD on firmware 127.538.8 for awhile. I saw the RUU come out for 4.3 on Tmob, so obviously I was all like, **** yeah! So I flashed a stock ROM (based on 127.538.11) and then tried to run the RUU. Unlocked, S-OFF. For some reason, the RUU flashed Hboot (I'm currently stuck at 1.55.00) and then decided to throw an error 155 at me. So I tried relocking the bootloader, with a command I found browsing the forums that sets the status to Locked. Flashing the RUU here didn't work either. Re-unlocked the bootloader (I have no user data at all... it's sad). I realized, okay, I'm Unlocked and have a custom recovery installed (TWRP). Even if I relock, the RUU doesn't flash. My idea right now is to flash the 127.538.11 RUU to get Hboot 1.44, as well as a working non-hacked firmware. I'm not sure if that RUU will work, though I'm hoping it does. If it does, then I can OTA update without a problem.
Do any of you have any ideas as to how to do this? I can RUU to 127.538.11, then downgrade to x.8 and use revone to lock my bootloader and attempt an OTA. I'm not sure what to do here... I can also reflash ARHD 30 and stick with that for awhile. I can do basically anything recommended, as I have S-OFF and TWRP.
Thanks!
I don't mind being stuck on stock, however I do want to be able to warranty my phone in the future -- will having hboot 1.55.00 with 127.538.8 firmware be a problem? Can I downgrade my hboot since I'm S-Off? Any help here would be absolutely wonderful...