Related
Sup guys. I gotta bring my phone in and I need to unroot. Ive used unrevoked forever. I keep trying to flash the s-on tool but it doesnt take.
I have the eng .76 bootloader. Would that make a difference. And if it is how do I upgrade it for the s-on to work??
Thanx
-storm
What radio are you on?
2.15.00.07.28
-storm
r.storm85 said:
2.15.00.07.28
-storm
Click to expand...
Click to collapse
You need to flash 2.15.00.11.19 radio first in recovery.
teh roxxorz said:
You need to flash 2.15.00.11.19 radio first in recovery.
Click to expand...
Click to collapse
Ok I will try.
Thanx
-storm
Well let me know.
teh roxxorz said:
Well let me know.
Click to expand...
Click to collapse
It says unsupported radio version now.
It would install on the old radio. But wouldnt turn s-on
-storm
Never mind the newest s-on tool worked, but still no s-on. I really think its the eng hboot. I need to find a newer one...i think
-storm
r.storm85 said:
It says unsupported radio version now.
It would install on the old radio. But wouldnt turn s-on
-storm
Click to expand...
Click to collapse
That should be the correct one...hold on.
r.storm85 said:
It says unsupported radio version now.
It would install on the old radio. But wouldnt turn s-on
-storm
Click to expand...
Click to collapse
Try upgrading your bootloader (Hboot). You can go to
http://www.mediafire.com/?ff1duqhahwf23w8
and try that. Then go to
http://www.mediafire.com/?2pjq2dhjv6ntxnh
to download and then flash the radio. Then flash the S-ON tool if it is necessary.
See does that help.
Hey guys sorry took so long.
It was the hboot. I thought I remembered reading that eng bootloaders are always s-off. And they are.
So I upgraded to .93 and it went right to s-on.
Thanx for the help guys
Sent from my VM670 using XDA App
Can someone please tell me how to turn S ON on my HTC Desire? I ran the RUU for my phone (US Cellular desire) and it put me back to stock, I just still have S OFF Alpharev. I've searched for a while and can't find anything. Any help will be appreciated.
What is your current HBOOT version?
I think you need to flash the hboot downgraded from the alpharev site. I would search first as I've seen this question asked before buy I'm not 100% on the outcome
Sent from my HTC Desire using XDA App
Is it possible to go S-OFF without loosing anything on the desire ?
matt.xx said:
I think you need to flash the hboot downgraded from the alpharev site. I would search first as I've seen this question asked before buy I'm not 100% on the outcome
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Not sure on that as this is the CDMA desire. unrevoked S-offs this on the older Hboots. Not sure how it works on 1.02 with Alpharevx but the standard hboots dont work I believe
qbking77 said:
Can someone please tell me how to turn S ON on my HTC Desire? I ran the RUU for my phone (US Cellular desire) and it put me back to stock, I just still have S OFF Alpharev. I've searched for a while and can't find anything. Any help will be appreciated.
Click to expand...
Click to collapse
Flash Downgrader first to unlock the hboot protection, then use corresponding RUU.
c0de1 said:
Is it possible to go S-OFF without loosing anything on the desire ?
Click to expand...
Click to collapse
Yes, but you need a Rooted ROM with no a2sd/d2ext scripts.
k3lcior said:
Flash Downgrader first to unlock the hboot protection, then use corresponding RUU.
Click to expand...
Click to collapse
Are you sure? Could you comment on my post please?
OP, what is your hboot version? How did you root? We need to know this please.
rootSU said:
Are you sure? Could you comment on my post please?
OP, what is your hboot version? How did you root? We need to know this please.
Click to expand...
Click to collapse
i agree, we need to know how u root/s-offed ur cdma desire (bravoc), as the apharev hboots are only for desire gsm (bravo)..so u can't use the alpharev downgrader i think
post here ur bootloader hboot infos
Yeah exactly.
The S-on security flag is in Radio's NVRAM. Obviously the radio is different between GSM and CDMA devices.
Historically on GSM, Alpharev S-off (1.8 and lower) flashed a special hboot which ignored this flag.
On CDMA Unrevoked forever did something different and didnt change the hboot
Thanks for the replies everyone. My HBOOT version is 6.06.1002 ... hope this helps...
qbking77 said:
Thanks for the replies everyone. My HBOOT version is 6.06.1002 ... hope this helps...
Click to expand...
Click to collapse
It is a start, so looks like you definitely used revolutionary to s-off your desire. Is it CDMA?
rootSU said:
It is a start, so looks like you definitely used revolutionary to s-off your desire. Is it CDMA?
Click to expand...
Click to collapse
Well I didn't. Previous owner did. Its the us cellular desire. I think us cellular is cdma?
Sent from my Nexus S 4G using XDA App
qbking77 said:
Well I didn't. Previous owner did. Its the us cellular desire. I think us cellular is cdma?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
if u don't have a simcard in it, is cdma...if u have a simcard in it is gsm
Okay, so My HBOOT version is 6.06.1002 and I have a CDMA Us Cell Desire.
qbking77 said:
Okay, so My HBOOT version is 6.06.1002 and I have a CDMA Us Cell Desire.
Click to expand...
Click to collapse
unfortunally, i think there is no way to go back to s-on with that hboot 6.x on the desire cdma
that hboot have a downgrade protection, so the ruu can't overwrite it
maybe you can try to change it manually, doing a "fastboot flash hboot hboot.img" using the hboot img file that you can extract from your ruu exe on your pc
Doesn't work needless to say. With unrevoked we could flash the h-boot and stay s-off with alpha-rev you can't. I was just trying this as I was bored using the uscc eclair ruu.
Fastboot doesn't work either gives error can not flash h-boot on the phone. Hopefully that helps you out.
Edit: By the way qb what you doing with a uscc desire anyway? You venturing away from the photon or something I seen you over there but at this time there is no way to flash it I have found. Making img files does nothing and neither does fastboot. I am tempted to try the downgrader for the bravo for the heck of it as I don't care to brick it. Cept the woman would shoot me.
Hi guys,
I'm helping a friend root his EVO 4G. I asked for some help doing this on another friends phone a while back as it was shortly after 2.3.3 was released OTA. Well that worked well, and so I run into this issue.
This EVO, the one I'm helping my friend with now, is also running 2.3.3. There are a number of new ROMS out there now and I was looking towards maybe flashing a Sense 3.0 ROM.
But I'm unsure as to which rooting method to use. It was a bit more complex the first time as 2.3.3 was new and you could not S-OFF then. But if I can I would like to S-OFF this EVO.
Can you guys post some links to the threads where I can find the help that I need? Does UnrEVOked support 2.3.3 now???
Any help would be much appreciated...
Regards,
PAinguINx
Revolutionary.io is the only way to root the phone
Sent from my PC36100 using XDA App
Thanks evo4gnoob. I've never heard of that but I'll check into it. Thank you for the post!
If the phone has 2.18 hboot, then just give revolutionary.io some time to update...
Not Sent
PAingulNx, that would be dependent on what Hboot the phone has, to what method of rooting you would use. As {ParanoiA} stated, you can wait for revolutionary.io to update for Hboot 2.18 (if that's what the phone is on) or try unlocking the bootloader via HTCDEV method. Which I try to explain here, not sure if I did a good job, http://forum.xda-developers.com/showpost.php?p=21680991&postcount=1.
HBOOT Version
Thanks guys...
It's been a minute since I've rooted an EVO. Can I check the HBOOT version in "Software Information" or do I need to boot in to Recovery?
In software information I have two numbers that resemble the HBOOT version.
The first is "Baseband Version" which is 2.15.00.0808. The other is the PRI Version which is 2.15_003.
Are either of these the HBOOT version?
Thanks again and sorry for the newb question...
Regards,
PAinguINx
PAinguINx said:
Thanks guys...
It's been a minute since I've rooted an EVO. Can I check the HBOOT version in "Software Information" or do I need to boot in to Recovery?
In software information I have two numbers that resemble the HBOOT version.
The first is "Baseband Version" which is 2.15.00.0808. The other is the PRI Version which is 2.15_003.
Are either of these the HBOOT version?
Thanks again and sorry for the newb question...
Regards,
PAinguINx
Click to expand...
Click to collapse
Neither of those are the hboot. To check hboot pull battery out power button+ volume down at the same time
Sent from my PC36100 using XDA App
Ok, it's 2.16.0001.
PAinguINx said:
Ok, it's 2.16.0001.
Click to expand...
Click to collapse
So that means revolutionary.io is your only way
Sent from my PC36100 using XDA App
{ParanoiA} said:
If the phone has 2.18 hboot, then just give revolutionary.io some time to update...
Not Sent
Click to expand...
Click to collapse
Rumor has it HTCdev and the super tool can unlock 2.18 idk for sure I'm on 0.97 I think haven't looked in a while I know its either 0.97 or 0.76 and I'm unr3voked forever no s-on for me without my own intervention oh how do I hate when something changes and I didn't do it myself lol
Success!
Hey guys,
Revolutionary worked beautifully! My friend's EVO now has S-OFF and ROOT...
All I need to do now is determine which ROM to use. I still have Myn's Warm TwoPointTwo and I see now that 3.5 is out. So I will be flashing that soon. But for my friend's EVO I'm still not sure.
Any suggestions?
PAinguINx said:
Hey guys,
Revolutionary worked beautifully! My friend's EVO now has S-OFF and ROOT...
All I need to do now is determine which ROM to use. I still have Myn's Warm TwoPointTwo and I see now that 3.5 is out. So I will be flashing that soon. But for my friend's EVO I'm still not sure.
Any suggestions?
Click to expand...
Click to collapse
For a starter rom I recommend classic and mikg
Sent from my PC36100 using XDA App
Hello everyone, my Incredible 2 is stuck on the white screen with htc logo and try to recover it booloader PG32IMG but get this error can not roll back HBOOT version please help
Note: I have the HBOOT 6.13.1002
No you don't. 6.13.1002 isn't an hboot number, it's your radio number
Plus we need more info such as if you are rooted, s-off, htcdev unlock, etc.
nitsua98 said:
No you don't. 6.13.1002 isn't an hboot number, it's your radio number
Click to expand...
Click to collapse
And you're going to have to give more info such as what you were trying to do, whether you are s-on or s-off, whether you are rooted at all, etc...
gtdtm said:
And you're going to have to give more info such as what you were trying to do, whether you are s-on or s-off, whether you are rooted at all, etc...
Click to expand...
Click to collapse
Omg u ninja'd me I literally just added that to my post o.0
nitsua98 said:
Omg u ninja'd me I literally just added that to my post o.0
Click to expand...
Click to collapse
BAM!
nitsua98 said:
No you don't. 6.13.1002 isn't an hboot number, it's your radio number
Plus we need more info such as if you are rooted, s-off, htcdev unlock, etc.
Click to expand...
Click to collapse
-Revolucionary-
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-BOOT
Aprl 1 2011, 18:34:39
if already root
Your hboot is broken
nitsua98 said:
Your hboot is broken
Click to expand...
Click to collapse
uff any guide it back?
nitsua98 said:
Your hboot is broken
Click to expand...
Click to collapse
Guess mine is too then. My HBOOT is the same as his,
Glad my phone is working fine.
Rooted, S-off and currently running Kangdemnation.
Isn't your hboot supposed to be 0.97?
nitsua98 said:
Isn't your hboot supposed to be 0.97?
Click to expand...
Click to collapse
That's what I thought. I bought the phone used and I honestly don't remember if it was 0.97 when I got it. I know it wasn't 0.98.
I used Revolutionary the day I got it,with no problems, and have been flashing ever since.
All I know is I happened to be in bootloader for something when I noticed it was 6.13.1002.
riker147 said:
Guess mine is too then. My HBOOT is the same as his,
Glad my phone is working fine.
Rooted, S-off and currently running Kangdemnation.
Click to expand...
Click to collapse
rom that I have installed? I work maybe ami
aiyoros02 said:
-Revolucionary-
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-BOOT
Aprl 1 2011, 18:34:39
if already root
Click to expand...
Click to collapse
And your phone is a Verizon dinc2?
gtdtm said:
And your phone is a Verizon dinc2?
Click to expand...
Click to collapse
Yes
I would suggest going into recovery, doing a wipe, flash a backup, wiping again and then rebooting.
Note: I like to wipe.
Sent from my Incredible 2 using xda app-developers app
Jasonp0 said:
I would suggest going into recovery, doing a wipe, flash a backup, wiping again and then rebooting.
Note: I like to wipe.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
That's one of my problems I have no backup
Hmm well I thought I saw a bonestock ROM somewhere. You might try searching for it then flashing that ROM and see if that does it for you.
Or just wipe and see if it loads.
Sent from my Incredible 2 using xda app-developers app
Jasonp0 said:
Hmm well I thought I saw a bonestock ROM somewhere. You might try searching for it then flashing that ROM and see if that does it for you.
Or just wipe and see if it loads.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Thank start looking
So exactly did you do before you got the white screen? And by exactly what I mean just that. Give us details. Were you flashing a ROM? If so what ROM and what method were you using to flash it? Did you sneeze, did you stand on one foot?
Sent from my Incredible 2 using xda app-developers app
Jasonp0 said:
So exactly did you do before you got the white screen? And by exactly what I mean just that. Give us details. Were you flashing a ROM? If so what ROM and what method were you using to flash it? Did you sneeze, did you stand on one foot?
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I have tried various methods and RUU.exe PG32IMG
when use ruu.exe stays and does nothing and when I pulled PG32IMG use this error can not roll back HBOOT version
Found a copy of HBOOT 1.44 that can still be hit by revone lying around online. Figured this would be useful to anyone who was super paranoid about their phone randomly S-ON'ing.
Download the zip Here and reboot to RUU (fastboot oem rebootRUU)
Flash the zip (fastboot flash zip zipname.zip)
Done.
Edit: You're going to have to edit the android-info.txt to match your device info.
So, basically this gives us s-off people a plan-B if we accidentally do something wrong?
HECK YES!!!!!
I will flash this, then go S-On to protect my sweet sweet phone from bad flashes.
Edit:
Have you actually tried this?
GrayTheWolf said:
So, basically this gives us s-off people a plan-B if we accidentally do something wrong?
F*** YES!!!!!
I will flash this, then go S-On to protect my sweet sweet phone from bad flashes.
Edit:
Have you actually tried this?
Click to expand...
Click to collapse
It flashed no problem. I couldn't get revone to kick to me to S-ON. However whatever it uses to lock/unlock the bootloader works and the hboot version is just 1.44.0000 so I'm assuming its revone'able. Fastboot wouldn't do it either due to hboot signature checks. Do you know another way to get S-ON?
Sonic2756 said:
It flashed no problem. I couldn't get revone to kick to me to S-ON. Fastboot wouldn't do it either due to hboot signature checks. Do you know another way to get S-ON?
Click to expand...
Click to collapse
Oh, that's a problem isn't it?
How would we go about getting back on 1.44 then?
GrayTheWolf said:
Oh, that's a problem isn't it?
How would we go about getting back on 1.44 then?
Click to expand...
Click to collapse
fastboot oem writesecureflag 1 works.
fastboot oem writesecureflag 3 fails due to hboot check.
I'm not sure if revone offers the ability to turn S-ON actually, I'll keep looking into it after my homework is done.
Sonic2756 said:
fastboot oem writesecureflag 1 works.
fastboot oem writesecureflag 3 fails due to hboot check.
I'm not sure if revone offers the ability to turn S-ON actually, I'll keep looking into it after my homework is done.
Click to expand...
Click to collapse
After your homework, go s-on, and then try to s-off again with revone to humor me and make sure it works.
What is the date on that 1.44 iirc anything after july can not be revone'd
GrayTheWolf said:
After your homework, go s-on, and then try to s-off again with revone to humor me and make sure it works.
Click to expand...
Click to collapse
Probably due to my GPE RUU. Gonna flash back to stock and try again.
Kraizk said:
What is the date on that 1.44 iirc anything after july can not be revone'd
Click to expand...
Click to collapse
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
GrayTheWolf said:
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
Click to expand...
Click to collapse
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
123421342 said:
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry, I had myself confused.
GrayTheWolf said:
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
Click to expand...
Click to collapse
I'm pretty sure 1.45 is the on that was patched.
Sent from my HTC One
123421342 said:
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
This one says May 3, 2013. Also even after flashing back to stock, trying to S-ON with 1.44 flashed, fastboot gives me the hboot verification error.
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
Sonic2756 said:
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
Click to expand...
Click to collapse
Very nice bro, this will help keep many people feel safer that don't know entirely the full risks involved with S-OFF
Sonic2756 said:
This one says May 3, 2013. Also even after flashing back to stock, trying to S-ON with 1.44 flashed, fastboot gives me the hboot verification error.
Click to expand...
Click to collapse
So, when I get my phone back with S-Off I should flash this file to downgrade bootloader to 1.44? Do I keep it 1.44 and flash roms as usual? Sorry for the dumb questions... Just don't want to mess up my phone.
lluke04 said:
So, when I get my phone back with S-Off I should flash this file to downgrade bootloader to 1.44? Do I keep it 1.44 and flash roms as usual? Sorry for the dumb questions... Just don't want to mess up my phone.
Click to expand...
Click to collapse
messing with hboot is a perfect way to do just that actually.
wrong hboot file.,
hboot file not downloaded fully (corrupted)
it is (Was) back on the inc4 you'd have a bricked phone with no way to fix it, except maybe jtag
but if Sonic confirms it safe, I'd trust him and just double check that md5
andybones said:
messing with hboot is a perfect way to do just that actually.
wrong hboot file.,
hboot file not downloaded fully (corrupted)
it is (Was) back on the inc4 you'd have a bricked phone with no way to fix it, except maybe jtag
but if Sonic confirms it safe, I'd trust him and just double check that md5
Click to expand...
Click to collapse
Please bare with me... I don't understand what you are say. Is the file Sonic posted HBOOT 1.44 good or bad and should I should I not flash it? I don't want to mess with anything I don't have to. I must have misread his post earlier. I thought he said to be on the safe side flash 1.44.
EDIT:
Originally Posted by Sonic2756 View Post
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
lluke04 said:
Please bare with me... I don't understand what you are say. Is the file Sonic posted HBOOT 1.44 good or bad and should I should I not flash it? I don't want to mess with anything I don't have to. I must have misread his post earlier. I thought he said to be on the safe side flash 1.44.
Click to expand...
Click to collapse
I flashed it and everything's fine for me. I never post things without testing them first.
Sent from my M7 using XDA Premium 4 mobile app
Sonic2756 said:
I flashed it and everything's fine for me. I never post things without testing them first.
Sent from my M7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply. I figured you wouldn't. I am just new and don't want to mess up my phone.