Develop Bugs

[Q] Unrooted: Why still S-OFF?

I just unrooted my phone by running the RUU update for 3.29.xxx and at bootloader screen, it is still showing S-OFF. Shouldn't it be S-ON? I'd appreciate some feedback as I am heading back to the sprint store and want to be sure the phone is completely unrooted. I recall the other time I ran this same procedure, it went back to S-ON.
TIA

You need to flash the Unrevoked s-on tool. It can be found in several unrooting threads.
Sent from my PC36100 using XDA App

TheMagicalSock said:
You need to flash the Unrevoked s-on tool. It can be found in several unrooting threads.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I suspect it was the tool I used to root that had the Unrevoked component (never had this problem first time around); should've read the fine print...
Sent from my PC36100 using XDA App

so you need to re-root (maybe with unrevoked even) and then flash the s-on tool through recovery. it can be found in the unrevoked wiki. after that, then run the ruu.

dkdude36 said:
so you need to re-root (maybe with unrevoked even) and then flash the s-on tool through recovery. it can be found in the unrevoked wiki. after that, then run the ruu.
Click to expand...
Click to collapse
Yup.... exactly. Thanks.....highly appreciated. I guess this explains why most prefer not to use the Unrevoked method.
Sent from my PC36100 using XDA App

glad i could help. another reason people dont like unrevoked is it is now outdated. if you run it with the new protected hboot 2.02, you will get screwed pretty bad.
it used to save people hours of struggle, now it kills ruthlessly (haha)

Just flash this as PC36IMG.zip:
http://goo-inside.me/evo/stock/RUU_...0.09.01_NV_1.77_003_release_154209_signed.zip

drmacinyasha said:
Just flash this as PC36IMG.zip:
http://goo-inside.me/evo/stock/RUU_...0.09.01_NV_1.77_003_release_154209_signed.zip
Click to expand...
Click to collapse
Does this downgrade HBOOT to .76.2000? If not, please list the exact steps + files to use. I have copies of Hboot_0.76.2000.zip and Hboot_2.02.0001-Patch but not sure of the other in which to flash them.
Thanks.
EDIT: I was able to get back S-ON, although I observed that bootloader doesn't show the updated value after flashing the unrevoked-s-on zip; not until you attempt to flash the stock PC36IMG file. The above RUU allowed me complete the unrooting process (now with hboot 2.02).
I guess the other pressing question is why do I need hboot 2.02 and not .93 or .76.2000?

[Q] Very important Question

Please guide me how to check if i have desire z hboot or g2? just saw the tweet by rmk, he said next unity release will require desire z hboot and i am not sure which one i have, i am also sure it will also help other noobs like me
Vision Pvt S-off
Hboot: 0.82.0000
Radio: 26.03.02.26_emmc

quickest way is to check internal storage.... (if you have 1.28GB you got G2 less you got DZ)

master.peterm said:
quickest way is to check internal storage.... (if you have 1.28GB you got G2 less you got DZ)
Click to expand...
Click to collapse
ok it means i have g2 hboot, bro i dont have computer, can i change my hboot with the one posted by rmk on his site and without using computer? i mean putting that pc10img.zip file on root of my sdcard, and than reboot to hboot which its read automaticaly, and let it update?

Yea you could, just when it tells you to do adb recovery just go to the recovery through the bootloader...just after you are done flashing the bootloader replace the sdcard (temporaraly) with another one so the bootloader doesn't try to reflash itsel
Although... I wouldn't do this because you need your comp to. Check the md5 sum of the PC10IMG.zip... which just makes sure that there were no download errors....
Sent from my HTC Vision

master.peterm said:
Yea you could, just when it tells you to do adb recovery just go to the recovery through the bootloader...just after you are done flashing the bootloader replace the sdcard (temporaraly) with another one so the bootloader doesn't try to reflash itsel
Although... I wouldn't do this because you need your comp to. Check the md5 sum of the PC10IMG.zip... which just makes sure that there were no download errors....
Sent from my HTC Vision
Click to expand...
Click to collapse
Thanks Bro for Your help...and when it tell me to do adb recovery, will i go into clockwork mod? i am very sorry if its a stupid question, also i saw that rmk has included radio, hboot, clockworkwork etc in 1 pc10img.zip file

yea you will

master.peterm said:
yea you will
Click to expand...
Click to collapse
Thanks Bro, I am on dz hboot now, really after I did that, I felt it was indeed simple than I was expected...

Revolutionary Rooted but Not???

First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.

to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.

As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.

Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.

oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.

I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!

Anyone have any ideas?
Sent from my PC36100 using xda premium

So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk

revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly

tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.

z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?

Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.

2.16
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.

Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?

z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.

Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.

IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.

I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.

[Q] Alpharev Hboots on latest hboot?

My Dad wants to root his unlocked Desire (That used to be mine FYI) and install CM7, but when I gave it to him I installed the leaked GB RUU which un-rooted it because he didn't want root at the time. I can re-root the device with revolutionary.io but what about a custom Hboot once it's s-off'd and rooted? (more specifically CM7r2)

Matty Matt said:
My Dad wants to root his unlocked Desire (That used to be mine FYI) and install CM7, but when I gave it to him I installed the leaked GB RUU which un-rooted it because he didn't want root at the time. I can re-root the device with revolutionary.io but what about a custom Hboot once it's s-off'd and rooted? (more specifically CM7r2)
Click to expand...
Click to collapse
alpharev.nl
download from there, instructions on how to flash using fastboot or zip from hboot are given there too.
alternatively programs like android flasher can do the same thing, though not used it myself.

Yes I'm on cm7r2 hboot now and everything works, plus if you plan to install cm7 rom it's even better 'cause you avoid wasting space in /system and get more space in /data, right where you need it
Sent from my HTC Desire using XDA App

Right, but this won't downgrade or brick the Desire right? it will just partition it?

Matty Matt said:
Right, but this won't downgrade or brick the Desire right? it will just partition it?
Click to expand...
Click to collapse
Wrong. If you flash a corrupted hboot file, you can brick it.

stankyou said:
Wrong. If you flash a corrupted hboot file, you can brick it.
Click to expand...
Click to collapse
IMHO in this case there is no "can". If one flashes corrupted, the phone WILL be bricked.
Sent from dGB using Transparent XDA App

stankyou said:
Wrong. If you flash a corrupted hboot file, you can brick it.
Click to expand...
Click to collapse
Sure if it is corrupted, if it's a correct hboot taken straight from alpharev there will be less risks. Still, there is always a risk involved when you play with hboots but my experience so far was good
Sent from my HTC Desire using XDA App

Matty Matt said:
Right, but this won't downgrade or brick the Desire right? it will just partition it?
Click to expand...
Click to collapse
just make sure you check the md5 sums provided before you flash them, with some tool on the net somewhere. it's possible to do so directly on the phone but i dunno how.
virtually eliminates the chances of a bad flash. i've never had any problems flashing hboots

eddiehk6 said:
just make sure you check the md5 sums provided before you flash them, with some tool on the net somewhere. it's possible to do so directly on the phone but i dunno how.
virtually eliminates the chances of a bad flash. i've never had any problems flashing hboots
Click to expand...
Click to collapse
Windows tool for checking md5sums:
http://www.softpedia.com/get/System/File-Management/MD5-Check.shtml
Linux:
Open terminal, change to directory of the file and type (assuming the filename is hboot.img:
Code:
md5sum hboot.img
Android:
MD5 Checker: https://market.android.com/details?id=com.fab.md5&feature=search_result

[HOW-TO] (S-OFF REQUIRED!) Downgrade to HBOOT 1.44

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.