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?
Related
I have an Evo 3d with HBOOT 1.5 and S-OFF. I want to get to 1.4 S-OFF but I can't find how I can set S-OFF back to S-ON, so I can proceed with the downgrade instructions located here... http://forum.xda-developers.com/showthread.php?t=1547695
Search and google are not helping too much as there is too much noise talking about getting to s-off and not trying to get to s-on.
Can you please point me toward a solution to change from HBOOT 1.5 S-OFF to HBOOT 1.5 S-ON?
Thank you.
JDogHerman said:
I have an Evo 3d with HBOOT 1.5 and S-OFF. I want to get to 1.4 S-OFF but I can't find how I can set S-OFF back to S-ON, so I can proceed with the downgrade instructions located here... http://forum.xda-developers.com/showthread.php?t=1547695
Search and google are not helping too much as there is too much noise talking about getting to s-off and not trying to get to s-on.
Can you please point me toward a solution to change from HBOOT 1.5 S-OFF to HBOOT 1.5 S-ON?
Thank you.
Click to expand...
Click to collapse
You can brick your device!
Forgive my ignorance, but if you are s-off, why would you want to do this? I thought 1.5 s-off was just as good as1.4 s-off.
Sent from my PG86100
When set at 1.5 you cant change the splash screen or radio. or other settings.
Also Bricking it is what I need to do to convert it to 1.4 BUT I cant to that until I have S-ON. Correct?
You are s-off so no need to brick, just download this copy it to sd card and flash via bootloader.
Also I could be mistaken, but I believe hboot 1.5 is perfectly ok as long as you are S-off, I am pretty sure you can flash whatever you want.
BTW the download link is taken from OP in this thread, you might want to read through it.
birddog_61 said:
You are s-off so no need to brick, just download this copy it to sd card and flash via bootloader.
Also I could be mistaken, but I believe hboot 1.5 is perfectly ok as long as you are S-off, I am pretty sure you can flash whatever you want.
BTW the download link is taken from OP in this thread, you might want to read through it.
Click to expand...
Click to collapse
^Exactly this. If you read the first post of that thread (especially the gigantic red letters and what is under that), it will tell you to NOT brick an S-off phone as it will permanently brick it. You just need to flash the 1.4 bootloader.
birddog_61 said:
You are s-off so no need to brick, just download this copy it to sd card and flash via bootloader.
Also I could be mistaken, but I believe hboot 1.5 is perfectly ok as long as you are S-off, I am pretty sure you can flash whatever you want.
BTW the download link is taken from OP in this thread, you might want to read through it.
Click to expand...
Click to collapse
i had the same problem as OP. i think the issue with 1.5 is even though its s-off, the bootloader is still locked and therefore a recovery cant be flashed and root cant be gained.
Ive been looking for the standalone hboot 1.4 ruu so i didnt have to do what op originally suggested
You have all of my thanks
alexjzim said:
i had the same problem as OP. i think the issue with 1.5 is even though its s-off, the bootloader is still locked and therefore a recovery cant be flashed and root cant be gained.
Ive been looking for the standalone hboot 1.4 ruu so i didnt have to do what op originally suggested
You have all of my thanks
Click to expand...
Click to collapse
Ya I didn't even think about revolutionary only working with 1.4 or below that must be the problem. You are welcome for the help, I just figured most of this out about a week ago when I had to do the downgrade after unlocking with htc method.
I would fastboot oem lock then do HTC's unlock again.
Sent from my PG86100 using XDA
kiewee3 said:
I would fastboot oem lock then do HTC's unlock again.
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
You have to HTC Unlock the device first, then do the fastboot oem lock (if you don't it will say "Device was already locked!" message)
JDogHerman said:
I have an Evo 3d with HBOOT 1.5 and S-OFF. I want to get to 1.4 S-OFF but I can't find how I can set S-OFF back to S-ON, so I can proceed with the downgrade instructions located here... http://forum.xda-developers.com/showthread.php?t=1547695
Search and google are not helping too much as there is too much noise talking about getting to s-off and not trying to get to s-on.
Can you please point me toward a solution to change from HBOOT 1.5 S-OFF to HBOOT 1.5 S-ON?
Thank you.
Click to expand...
Click to collapse
If you are S-OFF you can flash any bootloader you want...no need to go back to S-on....I found a few bootloader versions on here and flashed them back and forth when trying different roms.....once your S-OFF you should never return...lol
I was thinking of taking it to Sprint for a replacement cuz of 4G not working, but then I thought, WHEN ON EARTH do I use 4G??? LOL It's always off...
this is what my hboot says and im not sure why
LOCKED
VIGOR PVT SHIP S-OFF RL
HBOOT-2.11.0000
why is there a "RL" at the end of s-off
I don't know what the rl stands for and I'd like to know as well, but that is perfectly normal. I recommended the dev hboot if you intend to modify from here on out as unlocking with the htcdev will make it a pain to return to stock. (Relock, s-on, s-off then s-on again)
Sent from my ADR6425LVW using XDA
Kennnny1 said:
I don't know what the rl stands for and I'd like to know as well, but that is perfectly normal. I recommended the dev hboot if you intend to modify from here on out as unlocking with the htcdev will make it a pain to return to stock. (Relock, s-on, s-off then s-on again)
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
ive been s-off for a while now and i was on a modifided hboot with ics firmware and ics rom. i decided to downgrade my firmware to the 2.11 GB. after that is when the RL showed up at the end of s-off.
i never unlocked after s-offing and now its is acting like im locked and s-on.
i even had to flash recovery with fastboot as no other method would work.
i am going to unlock and s-off again. i just thought it was weird how it happend
nevermind, i just looked at a pic i had and the "RL" is there. i guess i just never noticed it before
Are you still s-off'd? Did you unlock yet? It's as easy as flashing a patched 2.11 hboot via ph98img to get fastboot commands to work again.
Do not bother to unlock once you have S-off. Trust me, just unwanted trouble.
Just flash a JuopunutBear hboot.
Edit: to elaborate just a bit, if you did need to do a warranty exchange or repair and wanted the bootloader to look stock by saying Locked/S-on:
Coming from Locked/S-off you'd just run a GB RUU and do a few fastboot commands to achieve S-on.
Coming from Unlocked/S-off, you'll need to do the RUU, relock bootloader, and do fastboot commands for S-on... then the whole S-off procedure again... then repeat RUU and fastboot S-on.
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