I'm ready to try a ROM, before the OTA finds it's way on my phone. I'm looking for the best way to unlock this device. I thought I'd give this new tool a try, however, it doesn't appear to work on the HTC Incredible 4G LTE (fireball). The temp-root method seems to work, but not the S-OFF.
Using Windows 7 Enterprise SP1 x64. HTC Driver 4.10.0.0001 and Android SDK 1.16
HBOOT-1.15.0000
RADIO-1.53.06.0919
OpenDSP-v29.1.0.45.0622
Current software: 2.17.605.2 701RD
Here were my results:
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2331 KB/s (4347896 bytes in 1.821s)
C:\Android>adb push temproot /data/local/tmp
2678 KB/s (68576 bytes in 0.025s)
C:\Android>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/temproot
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/temproot
/data/local/tmp/temproot
run_root_shell, thanks fi01 - "can't post external links"
tools/android_r
un_root_shell
[*] Root acquired.
[*] Thanks, HTC, for leaving this exploit open for such a ridiculously
long time
!
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 0.2.0
==============================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for
users
however the authors disclaim any liability for damage to your
phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the
user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever
caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc
networks
support is much faster there vs.posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with
eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
======================================================================
===
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
[email protected]:/ #
FWIW, I wouldn't be messing around with a new S-OFF method that hasn't been tested or verified to work for our device by someone who knows what they are doing. It isn't really a surprise that it doesn't work. Try one of the known working methods if you want to get it done.
The Facepalm method worked great for me.
http://forum.xda-developers.com/showthread.php?t=2214653
DanPFW said:
I'm ready to try a ROM, before the OTA finds it's way on my phone. I'm looking for the best way to unlock this device. I thought I'd give this new tool a try, however, it doesn't appear to work on the HTC Incredible 4G LTE (fireball). The temp-root method seems to work, but not the S-OFF.
Using Windows 7 Enterprise SP1 x64. HTC Driver 4.10.0.0001 and Android SDK 1.16
HBOOT-1.15.0000
RADIO-1.53.06.0919
OpenDSP-v29.1.0.45.0622
Current software: 2.17.605.2 701RD
Here were my results:
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2331 KB/s (4347896 bytes in 1.821s)
C:\Android>adb push temproot /data/local/tmp
2678 KB/s (68576 bytes in 0.025s)
C:\Android>adb shell
[email protected]:/ $ chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/temproot
[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/temproot
/data/local/tmp/temproot
run_root_shell, thanks fi01 - "can't post external links"
tools/android_r
un_root_shell
[*] Root acquired.
[*] Thanks, HTC, for leaving this exploit open for such a ridiculously
long time
!
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 0.2.0
==============================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for
users
however the authors disclaim any liability for damage to your
phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the
user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever
caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc
networks
support is much faster there vs.posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with
eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
======================================================================
===
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
[email protected]:/ #
Click to expand...
Click to collapse
It looks like temproot may have failed. Although it is contusing, because it state success. One of the requirements was a working internet connection. The error "can't post external links" kind of implies it couldn't talk to a site. Any chance that was your problem. I would like to know if this works too. My wife's phone has the latest OTA and can't be rooted by any of the past methods.
tj13 said:
It looks like temproot may have failed. Although it is contusing, because it state success. One of the requirements was a working internet connection. The error "can't post external links" kind of implies it couldn't talk to a site. Any chance that was your problem. I would like to know if this works too. My wife's phone has the latest OTA and can't be rooted by any of the past methods.
Click to expand...
Click to collapse
I replaced a valid link with "can't post external links" when I posted this info, because XDA wouldn't let me post a link.
DanPFW said:
I replaced a valid link with "can't post external links" when I posted this info, because XDA wouldn't let me post a link.
Click to expand...
Click to collapse
I gave it a try on my wife's phone. The temp root part works great. nothing happens for me on the firewater part. I guess we have to wait until someone figures it out, if that ever happens.
Related
i did the htc unlock blootloader.
and downloaded and plate the PH8.... on my sd card
when i go to fastboot it says i have older version faild to flash
then i tried the one click root and i get this
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb push zergRush /data/local/
1328 KB/s (21215 bytes in 0.015s)
C:\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg rush root>adb shell /data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb shell sleep 1
C:\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg rush root>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg rush root>adb install ./androidterm.apk
1936 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb shell sync
C:\Zerg rush root>pause
Press any key to continue . . .
i have the htc drivers aswell on fastboot says unlocked but s-on????
i had tried to do this method with pc and mac. and no luck
what am i doing wrong. please help. i have 3 days trying to root my phone
Do you have USB Debugging checked?
It should say S-On. there is not way to get S-off right now.
when you put the PH85IMG on your sd card and when to hboot did it ask you to update?
did you volume up and hit update?
If it worked then go to Hboot screen and volume down to recovery. Should bring up clockworkmod and you can flash a rom.
thanks for the quick respond. and yes i have Debugging checked on.
i didnt know we couldnt have s-off yet but im trying to root this device just like it says on the thread. and cant seem to have luck
gypsy214 said:
thanks for the quick respond. and yes i have Debugging checked on.
i didnt know we couldnt have s-off yet but im trying to root this device just like it says on the thread. and cant seem to have luck
Click to expand...
Click to collapse
are you using this one?
http://forum.xda-developers.com/showthread.php?t=1324177
never did the one click one..
bmbrad said:
are you using this one?
http://forum.xda-developers.com/showthread.php?t=1324177
never did the one click one..
Click to expand...
Click to collapse
i tried that one first. did that htc unlock and put this PG58IMG on the sd card but fastboot says fail older version
gypsy214 said:
i tried that one first. did that htc unlock and put this PG58IMG on the sd card but fastboot says fail older version
Click to expand...
Click to collapse
hmmmm.... try this one PH85IMG
http://forum.xda-developers.com/attachment.php?attachmentid=814010&d=1323710332
your not extracting it right?
never extracted it. i downloaded it from pc and mac and still. im gonna try this one and report back
bmbrad said:
hmmmm.... try this one PH85IMG
http://forum.xda-developers.com/attachment.php?attachmentid=814010&d=1323710332
your not extracting it right?
Click to expand...
Click to collapse
this one did the work thank you so much... they need to update the file in the op from the guide thread.
gypsy214 said:
this one did the work thank you so much... they need to update the file in the op from the guide thread.
Click to expand...
Click to collapse
It's because the hboot needs to verify the current file. For example in this new file that you just downloaded it has:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.43.531.3
hbootpreupdate:0
DelCache:1
The previous version that you tried earlier:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.36.531.5
hbootpreupdate:0
DelCache:1
See the difference? So all I did was modified the 1.36.531.5 with 1.43.531.3 and replaced the android-info.txt file in the zip file and it worked.
I'm not sure why HTC does this or even if there is a way around it but so far we have three versions for the US PH85IMG.zip files.
1.43.531.3 (newest)
1.36.531.6 (kinda new)
1.36.531.5 (shipped)
Other carriers such as Wind may have a different version so it's kinda difficult to make a universal PH85IMG.zip file. I'm curious if we could just use something as simple as:
modelid: PH8511000
cidnum: T-MOB010
hbootpreupdate:0
DelCache:1
or
modelid: PH8511000
cidnum: T-MOB010
mainver: *
hbootpreupdate:0
DelCache:1
Anyone is welcome to try if you like.
gypsy214 said:
this one did the work thank you so much... they need to update the file in the op from the guide thread.
Click to expand...
Click to collapse
Were you able to do this using your Mac or did you have to use your PC? I am tempted to root, but I have Mac and haven't even been able to temp root successfully so I'm hesitant to unlock bootloader.
sh!mon said:
Were you able to do this using your Mac or did you have to use your PC? I am tempted to root, but I have Mac and haven't even been able to temp root successfully so I'm hesitant to unlock bootloader.
Click to expand...
Click to collapse
You really don't even need a computer. Just place the PH85IMG.zip (with the recovery inside) on the root of your external sdcard once you have an unlocked bootloader then flash it from hboot. Voila! Root!
while i was visiting my uncle i took their computer to unlock the bootloader.
so in another words. i got the new update on the phone that one the includes wifi calling. thats why the old file didnt work and says older version fail.
so now thanks to you i am fool rooted and i have recovery. when s-off comes available is it something i would need?
on my sensation i have to wait for s-off to have perm root
gypsy214 said:
so in another words. i got the new update on the phone that one the includes wifi calling. thats why the old file didnt work and says older version fail.
so now thanks to you i am fool rooted and i have recovery. when s-off comes available is it something i would need?
on my sensation i have to wait for s-off to have perm root
Click to expand...
Click to collapse
we already have perm root with the unlock bootloader. we're able to do everything s-off allows us to do but to update radio hboot bootloader
Oh my god thank you so much! I was having the same problem and I was just about to post asking for help when i came across! Whew! thx guys I have a great and rooted amaze again!
westcoastfishing86 said:
Oh my god thank you so much! I was having the same problem and I was just about to post asking for help when i came across! Whew! thx guys I have a great and rooted amaze again!
Click to expand...
Click to collapse
The wonders of the search feature.
Binary100100 said:
The wonders of the search feature.
Click to expand...
Click to collapse
lol tell me about it.. anywho thx again guys
I've seen the Zerg root for the 4G, but after reading some comments about it there's been speculation that the 1.45.1500.2 is Zerg root proof. It there a way to root the Amaze with 1.45.1500.2 software?
On another note... I'm not able to tether with my phone? i'm able to make a hot spot and all yet, I cannot connect any devices to it. The devices seem to not be able to acquire the IP address.
All tips and suggestions are helpful, so please comment as I'm sure you'll be able to help me with my issues one way or another.
Have you unlocked your bootloader?
Sent from my HTC Amaze 4G using xda premium
*edit
What's the complete process in rooting the device with the 1.45.1500.2 software? I'm going to bootload it as soon as it's fully charged.
To unlock your bootloader:
Go to http://htcdev.com/register/ and register an account with them.
Then select "Begin Unlock bootloader"
Follow the steps. It is easy. Just back up your info because when you unlock it, it will require a hard reset.
To do install ClockWorkMod Recovery (CWM), go to this link.
http://forum.xda-developers.com/showthread.php?t=1316855
Follow the instructions that says "Installation from fastboot (hboot only ||Hard Method||):" (It's actually very easy and it worked on the new ROM update)
Download the ClockworkMOD 5.0.2.7 Amaze 4g and not the ClockworkMOD 5.0.2.0 Amaze 4g.
To root, you can install a prerooted Custom ROM or you can download SuperUser (SU) from here
http://www.multiupload.com/TI14RLNE8A
Just boot into CWM and flash the su-2.3.6.3-ef-signed.zip if you want to root it with your stock ROM.
To get WiFi Tethering working, you need root (duh).
Download WiFi Tether for Root Users 3.1-beta9
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_1-beta9.apk
After you install it, press the menu button. Select "Settings". Change the Device Profile to HTC Amaze / HTC Ruby. You are good to go!
Much appreciated, will try this tonight and will get back to you
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
HTC Bootloader unlock
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
RyanB125 said:
Alright, so I've tried the Bootloader process and I've received an error:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: .
Error Reason: .
That's after I went through the steps and had to paste the coding from the cmd onto the site. What's the problem?
Click to expand...
Click to collapse
Tardango said:
I just read another post that said the HTC bootloader unlock page is broken today. I was trying to unlock my new t-mobile US amaze today and have the same errors as you.
Click to expand...
Click to collapse
Alright, I guess i'll have to try again tomorrow.
The site is down I believe. I tried it for my friend. If it works, let me know!
Zerg not working on my unlocked Amaze
I have unlocked my bootloader and am running 1.43.531.3. I get pretty much the same set of errors every time I run the bat file. I have tried factory resetting it 3 times and trying again, but it always does the same thing. Occasionally it'll also say rm failed: no such file or directory on the adb shell rm /data/local/tmp/*sh command. USB debugging is on.
C:\Zerg>adb wait-for-device
C:\Zerg>adb push zergRush /data/local/
1294 KB/s (21215 bytes in 0.016s)
C:\Zerg>adb shell chmod 777 /data/local/zergRush
C:\Zerg>adb shell rm /data/local/tmp/*sh
C:\Zerg>adb shell /data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sleep 1
C:\Zerg>adb remount
remount failed: Operation not permitted
C:\Zerg>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg>adb install ./androidterm.apk
1969 KB/s (92780 bytes in 0.046s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg>adb wait-for-device
C:\Zerg>adb shell sync
C:\Zerg>pause
Press any key to continue . . .
Have you installed CWM?
Still getting the same errors as before. :/
edit* is there any report as to when the HTCdev page will be fixed?
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
hasoon2000 said:
I tried is an hour ago. The HTCDev site is working. I got my friend's unlock key.
Click to expand...
Click to collapse
I'm still receiving the same error!
PM me the token ID in a text file attachment. I will see what the issue is.
pepsishine said:
its not the HTCdev site, its the way you copied the key over to the box. absolutely no spaces are allowed.
but im gettin the same error for zerg. this is crap, i basically blanked my phone just to unlock it and restore everything.
is this a software version problem?
Click to expand...
Click to collapse
Assuming you are trying to root, you might try this approach. Worked for me. After the wifi update I had to reset to factory and remove CWM to get the update to install. After the update I did this again and all went well except I got an error during the root process using the file I downloaded from that thread. Thought maybe I was out of luck, but after rebooting the phone it was rooted. Been working fine for the past several days.
hasoon2000 said:
PM me the token ID in a text file attachment. I will see what the issue is.
Click to expand...
Click to collapse
Alright, give me a sec, i'll pm you.
Are you on Telus or Wind mobile? I heard that they didn't give HTC permission to allow the customers to unlock their bootloaders
Sent from my HTC_Amaze_4G using xda premium
I'm with Wind.
So I installed the latest ASUS firmware update (build 9.4.2.11) and lost root. I did not have OTA Rootkeeper (like an idiot) so I'm wondering if there is any way of re-rooting/restoring root without having to flash back to an earlier version.
If anyone can figure it out, it would be greatly appreciated.
You'll just have to wait until viperboy finds a way of rooting that firmware most likely. It shouldn't be too long.
I'm an idiot too.
Sent from my Transformer Prime TF201 using Tapatalk
I cringed as soon as I clicked that install button, but there was no way to cancel or stop the update to . . . soon as one of our awesome devs finds a new way to root, if any kind soul could post here to share the joy would be much appreciated.
zeusal said:
I cringed as soon as I clicked that install button....
Click to expand...
Click to collapse
I hang my head in shame also....
Made the same stupid move here
Looks like a lot of us in the same boat. Nothing to do but wait for a new root solution. I wish there was a way I could go back to previous version, root use OTA rootkeeper, then update. Other than that, the update is working great. Wifi signal seems to be a bit better, and I'm getting locks with GPS now.
Sent from my Transformer Prime TF201 using Tapatalk
Same thing here. Tried unrooting then rerooting using the viperboy primetime method and it didnt work. So now i just keep refreshing a bunch of different pages to see if anyone finds another way lol
Mea culpa etiam.
Sent from my Thunderbolt using Tapatalk
i was reading the root keeper as it was verifying the install, i was like NOOOOOOO
and well, you know the rest.
soon enough.
props to viper.
lets hope we have root again soon,
i do notice more stable wifi, it was going NUTS before the update, and now its great, and i already sideloaded my apps when i WAS rooted, so im kinda ok for a bit.
weeee,
loveing my prime, and cant wait for bootloader to be unlocked and get some stellar roms on this beast.
~k
I actually used ota root keeper, updated, and my update rendered it basically useless... I had no choice but to sideload it I guess at least now I have a functional tab again
For those who may have subscribed to this thread, good news if you are comfortable using ADB and shell.
I just used the stripped down version of ADB included with the previous one click root.
Testing that ADB has access
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ exit
exit
Executing commands from [ROOT] Mempodroid root - ICS including 9.4.2.11 I would have posted the below as feedback on actual thread to help those having issues troubleshoot, but I didn't have permission
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push mempodroid /data/l
ocal
568 KB/s (37273 bytes in 0.064s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push su /data/local
642 KB/s (22364 bytes in 0.034s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell chmod 777 /data/l
ocal/mempodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell /data/local/mempo
droid 0xd9ec 0xaf47 mount -o remount,rw '' /system
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
[email protected]:/ $ /data/local/mempodroid 0xd9ec 0xaf47 sh
/data/local/mempodroid 0xd9ec 0xaf47 sh
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/me
mpodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/su
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb reboot
After Reboot
Launch Super User app if you were previously rooted, or else download it from the market
Execute from Options, "Su binary__Tap to check for updates", then update anyway to install busybox etc.
Root complete and functional, thank you very much for posting se1000!
MOD EDIT: In order to prevent undue questions and excessive off-topic I'm making this edit to the op to inform the users revone does not support HBOOT 1.54.
What is "EARLY ACCESS PREVIEW"?
We want to give you S-OFF as soon as practically possible so an early access preview release is not a polished product but it does work (mostly). It will:-
* require knowledge of common android tools like adb and/or fastboot
* be a command line tool
* be rough around the edges
* probably crash sometimes
* fail to work everytime or in all cases or on different carrier ROMs - LET US KNOW if you get repeated failure on carrier variants.
* certainly not look pretty.
* despite being "early access" be very unlikely to brick your device (but naturally, this is possible, it's still a hack).
* give you a very good chance of getting S-OFF. Today. Right now.
Status
* revone has been known to grant S-OFF on the latest WWE & EU RUU, T-Mobile and AT&T versions, as well as Sprint HTC One.
* revone might also work on the Droid DNA 2.04 and 2.06. Awaiting (your) feedback.
Download
* Get the Android SDK for ADB. You may need to update to the latest version of the SDK for jellybean devices.
* Download revone: http://revolutionary.io/revone
Instructions
Use any operating system you like, you only need adb.
1. Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
* cd /data/local/tmp
* chmod 755 revone
3. (optional) If your device is unlocked and rooted please switch to root using su.
4. Prepare to gain S-OFF by running the command: ./revone -P
4a. If revone reports success reboot the device and proceed to step 5)
4b. If revone reboots the device (we'll pretend this isn't an undiagnosed random crash) please wait 2 minutes then try again from step 2.
4c. If revone reports that you need to reboot and try again please reboot and try again from step 2.
5. Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to
the /data/local/tmp directory.
6. Instruct revone to grant you S-OFF and unlock status by running the command: ./revone -s 0 -u
6a. Other optional command arguments:-
* -u - Unlock the device
* -l - Lock the device (as if it was never unlocked)
* -r - Relock the device (mark the device as relocked)
* -t - Reset the device's tamper flag.
7. Presuming revone reported success please reboot the device again, this time to the bootloader (adb reboot bootloader)
8. You should now observe your device is S-OFF (and the lock status changed if you invoked that option).
9. (optional) Re-run revone to remove TAMPERED from your HBOOT screen: ./revone -t
Credits
revone is brought to you by the Revolutionary dev team.
We've been silent, we're back.
Disclaimer
Revolutionary dev team disclaims all responsibility for your use of revone (and any of our tools): If the world ends, it's not our fault. If your device spontaneously ignites, well, that's not our fault either. You make the choice to use our tool, we don't force it upon you.
Support
Please visit #revolutionary on the Freenode IRC network. We will try to support you in the best way possible, but remember, this is early access, and operators might be asleep or not available at the time you join. Just hang around and wait for someone to answer.
ALTERNATE revone binary (v0.2.1-wlj)
Alternate revone binary for the HTC J One (m7_wlj) only, if the main one crashes, reboots or otherwise does not work.
Download: revone-0.2.1-wlj
UPDATED revone binary (v0.2.1)
* Safety update: No longer allows -s 3 since this can lead to bricks with custom HBOOTs, use: fastboot oem writesecureflag 3 (which is safer - and checks such things)
* Fix: delusions of grandeur - revone now no longer reports success when it fails.
* Outside chance some previous failures will now be successful but most likely they will just correctly report failure.
Please note that due to the safety update ALL previous versions have been replaced with v0.2.1 and are hence no longer supported.
YOU WILL NOT RECEIVE SUPPORT FOR A VERSION LESS THAN v0.2.1
Download (and any previous link): revone-0.2.1
UPDATED revone binary (v0.2)
* Remove the random reboot feature.
* Vastly reduce the error -6 probability.
Download: revone-0.2
Use as per OP instructions renaming or name substituting as appropriate.
Reverting to S-ON (updated)
* ./revone -l
* fastboot oem writesecureflag 3
Instructions updated since stating "fastboot oem lock" was a fail - my bad! xD
Stuck with error: -1?
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
Redistribution/Bundling revone
Permission is not given to redistribute and/or bundle revone into "one click" utilities (or similar). Please only obtain revone directly from us, this allows us to ensure the most up to date version is available in case of any critical issues.
Many thanks for your understanding.
Thanks this made my day
I wanted to update my post (Monday) as I have the priviledge of being on the first page.
I did struggled to get this installed, the first two attempts failed and told me to reboot, the third worked but did not S-Off the device.
Eventually, after multiple combinations of "-P" and "-s 0" (with all reporting successes) and my device was suddenly S-Off.
Then of course, locking and removing the tamper were easily done.
Excellent work everyone involved!
My stock HTC One with HTC_001 (purchased from Phones4U UK) on the EE network is now unlocked!
Electronic Punk said:
I am so in.
First attempt failed, rebooting.
Second attempt failed too.
Error code -6
Click to expand...
Click to collapse
Device mainver? I can check it out if there's a RUU/OTA for it.
squirt
T-Mobile USA, Device doesn't get a error, but doesn't reboot on its own either, tried four times. Tried rebooting manually and continuing, no go. No errors, but no S-OFF either.
Worked without a hitch on my One! Thanks!
itzsnookums said:
T-Mobile USA, Device doesn't get a error, but doesn't reboot on its own either, tried four times. Tried rebooting manually and continuing, no go. No errors, but no S-OFF either.
Click to expand...
Click to collapse
What output do you yet?
very thanks revteam!
I use HTC J butterfly. 1.29.970.1 version (DNA 2.06/2.05 same situation)
root method is temproot
c:\adb\DLX_J>adb push revone /data/local/tmp/
2438 KB/s (646704 bytes in 0.258s)
c:\adb\DLX_J>adb shell chmod 755 /data/local/tmp/revone
c:\adb\DLX_J>adb shell
[email protected]:/ $ /data/local/tmp/run_root_shell
/data/local/tmp/run_root_shell
Attempt perf_swevent exploit...
writing address is 8e55
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone failed (error code = 2
error code 2...?
Please advise me...!
thanks
graffixnyc said:
Worked without a hitch on my One! Thanks!
Click to expand...
Click to collapse
You have really S-OFF now?
Worked here. First couple of times it failed after the entering su part, so tried without su and worked fine. Thanks!
kmdm said:
What output do you yet?
Click to expand...
Click to collapse
You mean this??
I:\One>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone successful - please reboot to continue.
[email protected]:/data/local/tmp #
ATT HTC One, All commands report successful however upon reboot after issuing the S-OFF and Tampered command, nothing gets changed.
Okay, this is a good day!
S-OFF worked on the first try, had to rerun with -t to remove TAMPERED.
Many thanks to the guys who made this possible!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: 1BL09825KR231950Y
:highfive: yeah^^
When I ran it I got S-off but it didn't reset the Tampered. I had to run the -t switch alone a second time for it to reset it
itzsnookums said:
You mean this??
I:\One>adb shell
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
chmod 755 revone
[email protected]:/data/local/tmp # su
su
[email protected]:/data/local/tmp # ./revone -P
./revone -P
revone successful - please reboot to continue.
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
At that stage you reboot manually and continue to step 6.
i did no change, ill try again, thank you....
graffixnyc said:
When I ran it I got S-off but it didn't reset the Tampered. I had to run the -t switch alone a second time for it to reset it
Click to expand...
Click to collapse
Same. Sprint HTC One. Otherwise it's reporting s-off.
hi to all can u pls help me to s off my htc one max im desperate to s off my phone i unlock bootloader flash twrp recovery flash viperom 2.0 but when im in cmd to push firewater nothings happn and firewater not run in command heres my log...
Code:
C:\Users\nehj>cd c:\adb
c:\adb>adb reboot
adb server is out of date. killing...
* daemon started successfully *
c:\adb>adb wait-for-device push firewater /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2810 KB/s (4522136 bytes in 1.571s)
c:\adb>adb shell
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]/#
i already try other rom like cm12 pacman rom but when im in command same as in log firewater not run....:crying::crying::crying:
Firewater is dead server side. You'll have to pay for sunshine.apk.
Don't waste your time, only way to do it is called sunshine, it cost 25 usd. It worth it. You will need to flash a pure stock RUU, get root and run sunshine.