• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Sprint] TWO s off methods!

scotty85

scotty85

Extreme Android User
moonshine has been released:
moonshine xda thread
direct link:
http://moonshine.io/

and also a well known team has released what they are calling a developer early access edition:
revolutionary

i tried revolutionarys method partially becasue it used more commands and was slightly less automated,partially becasue it didnt require linux,and mostly becasue moonshine doesnt list a download for t mobile us yet.

worked like a charm on my first try,casueing much giddy schoolgirl type giggling :D

heres what it looks like,if anyone has the notion to try it:
Code: 
c:\miniadb_m7>[COLOR="Red"]adb push revone /data/local/tmp/[/COLOR]
3272 KB/s (646704 bytes in 0.193s)

c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
shell@android:/ $ [COLOR="red"]cd /data/local/tmp[/COLOR]
cd /data/local/tmp
shell@android:/data/local/tmp $ [COLOR="red"]chmod 755 revone[/COLOR]
chmod 755 revone
shell@android:/data/local/tmp $ [COLOR="red"]su[/COLOR]
su
root@android:/data/local/tmp # [COLOR="red"]./revone -P[/COLOR]
./revone -P
revone successful - please reboot to continue.
root@android:/data/local/tmp #

[COLOR="Blue"]*physically reboot phone(dont use adb reboot)[/COLOR]

c:\miniadb_m7>[COLOR="Red"]adb shell[/COLOR]
shell@android:/ $ [COLOR="red"]cd /data/local/tmp[/COLOR]
cd /data/local/tmp
shell@android:/data/local/tmp $ [COLOR="red"]su[/COLOR]
su
root@android:/data/local/tmp # [COLOR="red"]./revone -s 0 -u[/COLOR]
./revone -s 0 -u
revone successful.
root@android:/data/local/tmp # [COLOR="red"]exit[/COLOR]
exit
shell@android:/data/local/tmp $ [COLOR="red"]exit[/COLOR]
exit

c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off [COLOR="Blue"]<-hooray![/COLOR]
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-60fafa5b0be2807a0ad050f62f94e0010
getvar:all FAILED (unknown status code)
finished. total time: 0.087s
 
Tried revolutionary's method and worked without a hitch. I had a locked bootloader before attempting, and no issues. Now unlocked & S-OFF.

I installed TWRP and obtained root access. I did have a question regarding OTA's, is there an option to not accept OTA's, or will they not be pushed to my device without my consent?
 
I think it's amazing that Team Rev.io has found a way to get us all S-OFF without requiring HTCDev. This is definitely a step in the right direction. Grats to all HTC One users!
 
antonatron said:
I installed TWRP and obtained root access. I did have a question regarding OTA's, is there an option to not accept OTA's, or will they not be pushed to my device without my consent?
Click to expand...

if you stay on the stock rom,they will be pushed without consent. :eek: you will possibly be able to defer the update a few times before it forces itself upon your device. the usual result is a simple failure to install,but in the process i can leave you stuck aat a splash screen or bootloop,and in an extreme situation an unrecoverable state(bricked)

there are several things ive read to defer OTAs:
-modify build.prop rom "fingerprint"
-freeze "updater" file with titanium or equivalent
-delete or rename "OTAcerts.zip" file

the best option,is to run a custom rom(even just a stock one) that will ahve un-needed files and bloat removed. custom roms are in most cases modified to not check for updates.
 
ironman187 said:
Sick! So we can now root without using HTC Dev?
Click to expand...

Quite possibly. Ive Seen quite a few reports of success with stock, locked Sprint phones.

However, If it doesn't work for you, I don't think having to use HTC unlock is too big a deal, since all visual traces of it can be removed afterward.
 
scotty85 said:
Quite possibly. Ive Seen quite a few reports of success with stock, locked Sprint phones.

However, If it doesn't work for you, I don't think having to use HTC unlock is too big a deal, since all visual traces of it can be removed afterward.
Click to expand...

The phone gets registered though, and that is what I want to avoid.
 
ironman187 said:
The phone gets registered though, and that is what I want to avoid.
Click to expand...

you are correct,they prolly know your imie,serial number,and every thing else thats unique to your phone.

however... the likelyhood of them doing something with this info is slim to none. i have taked to someone who works at htc that assures me they really dont care that much. he wasnt even sure they have the ability to look that information up.

when a phone makes it to htc for repair,the check for visual signs of having been rooted(unlocked,relocked bootloader). finding them,it depends on the repairs needed,most phones are still fixed. non booting phones generally just have the motherboard/emmc replaced.

they dont try and find out if youve rooted or messed with a non-booting phone. we like to think that they are out to thwart our actions and patch our exploits,and keep us from getting our phones fixed,but the reality is that we(hackers/modders/rom flashers) are just a very small part of the phone-using community. fixing a few phones that they prolly shouldnt have is likley alot cheaper than the labor/manpower needed to catch the dishonest few.

not trying to make light of the situation,as we certainly cant make any gaurantees about what could happen(or not happen) :)
 
scotty85 said:
you are correct,they prolly know your imie,serial number,and every thing else thats unique to your phone.

however... the likelyhood of them doing something with this info is slim to none. i have taked to someone who works at htc that assures me they really dont care that much. he wasnt even sure they have the ability to look that information up.

when a phone makes it to htc for repair,the check for visual signs of having been rooted(unlocked,relocked bootloader). finding them,it depends on the repairs needed,most phones are still fixed. non booting phones generally just have the motherboard/emmc replaced.

they dont try and find out if youve rooted or messed with a non-booting phone. we like to think that they are out to thwart our actions and patch our exploits,and keep us from getting our phones fixed,but the reality is that we(hackers/modders/rom flashers) are just a very small part of the phone-using community. fixing a few phones that they prolly shouldnt have is likley alot cheaper than the labor/manpower needed to catch the dishonest few.

not trying to make light of the situation,as we certainly cant make any gaurantees about what could happen(or not happen) :)
Click to expand...

Using HTC dev voids certain parts of your warranty, so they do register your meid and cross reference it when you send the phone in for warranty replacement.
 
ironman187 said:
so they do register your meid and cross reference it when you send the phone in for warranty replacement.
Click to expand...

thats contradictory to what ive heard. not arguing they have information on file,just doubting that they do any cross referencing or checking.

again,im not trying to persuade you. warranty discussions are something i typically try and avoid,as there is a fine line between returning to stock for a legitimate reason(say a malfunctioning power button or vol rocker) and trying to fraud a carrier into replacing the phone that the user himself has messed up.

if youre concerned about factory warranty,then dont root,period,wether htcdev is involved or not. android lends itself well to alot of customization with third party launchers,keyboards,etc. lots of folks enjoy a completely stock device until the factory warranty has expired.

if you want to enjoy a rooted device,make sure to carry a third party insurance,since they dont care if your phones rooted,lost,or layed at the bottom of a pool for 3 hours :eek: :D legitimate hardware issues are likely to be taked care of under factory warranty when you remove visual traces,and if you screw it up with firmware,worse case is you pay the deductible for a new phone.
 
scotty85 said:
thats contradictory to what ive heard. not arguing they have information on file,just doubting that they do any cross referencing or checking.

again,im not trying to persuade you. warranty discussions are something i typically try and avoid,as there is a fine line between returning to stock for a legitimate reason(say a malfunctioning power button or vol rocker) and trying to fraud a carrier into replacing the phone that the user himself has messed up.

if youre concerned about factory warranty,then dont root,period,wether htcdev is involved or not. android lends itself well to alot of customization with third party launchers,keyboards,etc. lots of folks enjoy a completely stock device until the factory warranty has expired.

if you want to enjoy a rooted device,make sure to carry a third party insurance,since they dont care if your phones rooted,lost,or layed at the bottom of a pool for 3 hours :eek: :D legitimate hardware issues are likely to be taked care of under factory warranty when you remove visual traces,and if you screw it up with firmware,worse case is you pay the deductible for a new phone.
Click to expand...

They don't specifically say they keep the info on record, but HTC dev has a disclaimer stating that certain things will not be covered under warranty after using HTC dev to root. As for being afraid to root, it's easy to unroot phones and doing so does not leave a trace. As for insurance, it's generally a waste of money.
 
Follow up: I decided to do Moonshine and it works with Windows 8. I had a little bit of difficulty with step 1 "moonshining1" which got the phone stuck on off I rebooted manually and it continued going through the process. I manually restarted once more under "moonshining2" and after the phone automatically rebooted several times I got S-Off. I was glad that I didn't brick my phone. I know the great guys that create these exploits warn us about using it at our own peril but man this process scared me so much that only people with nerves of steel should perform it.
 
thanks for the follow up. one thing to keep in mind for other folks considering using anything not recommended by the team,if you do not follow their specific directions,they may not offer any help on their IRC channel.

welcome to s off! what doesnt kill us makes us stronger :D
 
scotty85 said:
thanks for the follow up. one thing to keep in mind for other folks considering using anything not recommended by the team,if you do not follow their specific directions,they may not offer any help on their IRC channel.

welcome to s off! what doesnt kill us makes us stronger :D
Click to expand...

I know they have step by step instructions but they didn't have a contingency step in case phones wouldn't reboot by themselves. I read their website word for word before I started this process. I really am liking S-off, makes everything easier on me to customize.
 
scotty85 said:
Yes. I will detail it later... Been meaning to put up a post, the real life has been getting in the way lately :mad:
Click to expand...

No problem, I have been doing some research and found plenty of unrooting instructions, but none of them mention getting s-on back, I've been holding out for that before I finally go ahead and root.
 
s on is easy,just use fastboot command:
fastboot oem writesecureflag 3

just make sure youre on a signed hboot(not monshine,etc),and make sure youve done other neccessary changes first.

in a nutshell:
-change lock status flag,if needed
-change cid,if needed
-change mid,if needed (:eek:)
-run factory ruu
-change secure flag to s on

in that order! well,you could mix up the first 4 a little,but s on has to be last thing you do.
 
You must log in or register to reply here.
Back
Top Bottom