Related
Followed the guide from Paul on Modac, while attempting to unlock the bootloader I ran into an error that was resolved by updating fastboot. I successfully rooted,flashed custom rom and booted. I noticed that while in bootloader I went from S-OFF to S-ON. The fast boot error came attempting " 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' " The error 'Locked' the bootloader. After I updated fastboot above command worked, BUT I was now back to S-On.
What part of the process should I redo in order to get S-OFF back?
What are my limitations with S-ON?
Any thoughts, comments, suggestions and especially solutions are appreciated.
Also the haptic buttons ( same row as pen button) do NOT work. They do not light and are not usable
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Gumby63 said:
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Click to expand...
Click to collapse
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
ATownI20 said:
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
Click to expand...
Click to collapse
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Revolutionary does not support the HC bootloader version 1.11.0006.
but after unlock bootloader go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
And flash castom recovery
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' this recovery support all castom Rom based on Honeycomb
S-Off not needed for you.
Sorry my bad English...
Gumby63 said:
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Click to expand...
Click to collapse
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
piramida13 said:
Revolutionary does support the HC bootloader version 1.11.0006.
but only after unlock bootloader , go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img'
Click to expand...
Click to collapse
So I'm not suppose to have S-OFF after running that command?
I think that's what he is saying. My bootloader was a totally different one. So I don't really have any knowledge. What I would do is go into the development forum and do a quick search and see if anyone answered the question or had a similar problem and fixed. It helps out a lot. I don't want to give you knowledge and mess anything up on your end.
ATownI20 said:
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
Click to expand...
Click to collapse
haha the process of going to honeycomb was not supposed to give you s-off, simply an unlocked bootloader. I think i'm following you
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
The only way right now to get S-OFF is with HBOOT versions 1.11.0000 and 1.11.0003. Since you have 1.11.0006, needed for running HC on the Flyer, Revolutionary doesn't support it, so right now you can only have the unlocked boot loader and S-ON. If you run the Revolutionary tool with HBOOT 1.11.0006, it will tell you it is not supported, and won't run.
The only way it would be supported is when the AlphaRev/Unrevoked team update their tool to support it. So running that command listed above does cause this, but it is required in order to run HC on the Flyer. Without it, I don't know if you'd have a $300 brick or what.
Parastie said:
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
Click to expand...
Click to collapse
Thanks chief... I was just a little confused as the guides talked about permanent S-OFF... But if S-ON is how I'm suppose to be right now, then S-ON it is! lol...
I am in the same boat
Just Upgraded and noticed S-on as well...
what am I limited to with S-ON.. and whats the *UNLOCKED* mean?
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
I have exactly the same issue.
is there anyway out of S-ON?
I decided to run the 4.03.605.2 RUU before flashing back to Neo's Adrenaline 2.0...running the RUU reflashed a stock recovery and returned the bootloader to Locked, of course, so I went to the HTC Dev site to try to unlock it. I'm sure it's already a known issue but it appears that HTC's bootloader unlock tool is down and has been for some short time with no apparent efforts on their part to fix it.
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
socal87 said:
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
Click to expand...
Click to collapse
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
nrfitchett4 said:
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
Click to expand...
Click to collapse
That's what I thought too, but I tried to flash recovery after running the RUU...got the "not allowed" error; unlocked, and had no issue.
To my knowledge, all S-off does is "break" the locks on certain partitions, such as boot, so they can be written from recovery...and allow flashing of radios and HBOOT without a valid signature. Recovery itself is what decides what you can flash in terms of ROMs...the stock recovery won't flash anything but an original signed .zip.
Next time just flash the the jupunto bear hboot it makes everything easier and all you need is the s off to flash it. I do it right after running any ruu
I ran the latest ruu,was s-off,locked bootloader,and flashed the recovery without any problems. You can try to push it through adb if anything
Sent from my ADR6425LVW using Tapatalk 2
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
jayochs said:
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Click to expand...
Click to collapse
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
HowardZ said:
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
Click to expand...
Click to collapse
You are wrong in so many ways Howard.please everyone font bother reading this post.
Ok jbear hboot is not meant to fool Verizon. It's meant to provide fastboot commands even while the bootloader is locked.
As for op,I can confirm after running the ruu,you will still have to unlock to flash your recovery, if you still have your unlock code file you can unlock with that just like you did the first time .
Oh and the HTC website always does that just keep trying like every hour or so, if you can't find that unlock file they e mailed you
Sent from my ADR6425LVW using xda app-developers app
I am s-off and locked. And have been able to flash everything under the sun with no problems
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
There's no extra work on flashing jbear hboot. Right after the ruu rename the jhboot.zip to ph98img boot on hboot, flash and done. It seems you don't have a lot of knowledge when it comes into hboot stuffs.(no offense intended) And like the others guys said jbear is not to fool anyone and beside the jbear is an unlocked hboot.
socal87 said:
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
Click to expand...
Click to collapse
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
dassh said:
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
But he does need to be s-off...and I think he said he wasn't.
topgun1953 said:
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
Click to expand...
Click to collapse
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
HowardZ said:
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
Click to expand...
Click to collapse
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
topgun1953 said:
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
Click to expand...
Click to collapse
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
I don't think verizon cares. IMHO
In my case, I'm locked, s-off, stock hboot. I can get what I want in ph98img.zip files so I don't use fastboot. I can write the s-on flag, and flash the lastest ota and my phone will be like stock, out of the box....good for some, doesn't really matter to me.
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
Verizon don't care about s-off because there's some rezound that came out s-off out of the box.
topgun1953 said:
But he does need to be s-off...and I think he said he wasn't.
Click to expand...
Click to collapse
Yes, absolutely needs to be s-off for what i was suggesting. I may have mis-understood the op and subsequent posts. If the op doesn't want to s-off then unlock is a necessity but if s-offed, then the op has a choice to unlock or stay locked.
I chose to stay locked, like Topgun says, it's easier. The only difference is i did install a jbear hboot, but again that was because i think it's easier to use fastboot sometimes instead of trying to repackage something as a ph98.
Sent from my ADR6425LVW using xda app-developers app
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
HowardZ said:
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
Click to expand...
Click to collapse
If you brick, you couldn't change your hboot anyway. Using a jbear hboot is not to be deceptive.
Sent from my ADR6425LVW using xda app-developers app
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 recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind