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.
Related
[ROOT][ICS] Root Razr ICS 4.0.3 and 4.0.4 [updated]
This is first post for Razr Root ICS 4.0.4 on XDA Developers
Tested on my Razr xt910 no errors...
This method run in CDMA and GSM Razr...
This method run in all versions ICS 4.0.4 for Razr
This method run in all versions ICS BRAZIL and ICS Leaks
This method run in all versions ICS CHINA / 4.0.3 and 4.0.4
This method run and confirmed on ICS Leaks english.en.Eu 4.0.4
Credit to Rick#2 for this great post and Exploit
Credit to miloj for this new technique on ASUS Transformer
Only Run the script and wait end process
Remenber this method has been fully tested on my Razr and i succeeded
[REQUIREMENTS]
Check if your USB computer connection is "Mass Storage".
It shouldn't be. Change it to "media device" MTP mode.
Check if your configuration of android is set to "debug mode".
[AUTOMATIC]
1. Download exploits or scripts
2. Unpack files on any folder
3. Install motorola drivers
4. Connect your Razr with USB cable
5. Check if your configuration of android is set to "debug mode".
6. Check your Usb connection and change to "media device"
7. Run the exploit in the bottom of the page
[SCRIPT] Fully tested only run in prompt and wait process
Mod Edit:Removed links
[MANUAL]
1. Download the following files: su and debugfs
2. Save the two files on /sdcard
(ie: mount your sdcard in windows and copy them over, or "adb push" them to /sdcard).
3. In a linux terminal/Windows command prompt:
commands at the prompt is started after the symbol #
4. Run all commands and if reboot not run open new prompt and enter adb "reboot"
5. Run sequence commands and reboot with "adb reboot" or with shutdown
6. Install superuser.apk from market or google play
7. Install OTA ROOT KEEPER and backup your ROOT
8. Install ROOT CHECKER BASIC and test your ROOT access
9. if fails one first test, reboot and restart ...
10. Run all commands and no reboot... yes run all comands again...
11. Reboot only with finish all commands...
12. if fails with second test run script on the end of this page
[COMMANDS]
Code:
adb shell
[email protected]_maserati:/ # cd /sdcard
[email protected]_maserati:/ # cp su /data/local/12m/
[email protected]_maserati:/ # cp debugfs /data/local/12m/
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # chmod 755 su
[email protected]_maserati:/ # chmod 755 debugfs
[email protected]_maserati:/ # mv batch batch.bak
[email protected]_maserati:/ # ln -s /dev/block/mmcblk1p20 batch
[email protected]_maserati:/ # exit
adb reboot
The Razor reboots, after restart enter new commands...=>
Code:
adb wait-for-device shell
Wait android shell:
Code:
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # rm batch
[email protected]_maserati:/ # mv batch.bak batch
[email protected]_maserati:/ # /data/local/12m/debugfs -w /dev/block/mmcblk1p20
(Enter this commands at the "debugfs:" prompt)
debugfs: # cd xbin
debugfs: # write /data/local/12m/su su
debugfs: # set_inode_field su mode 0104755
debugfs: # set_inode_field su uid 0
debugfs: # set_inode_field su gid 0
debugfs: # quit
[email protected]_maserati:/ # cd /data/local/12m
[email protected]_maserati:/ # rm su
[email protected]_maserati:/ # rm debugfs
[email protected]_maserati:/ # cd /
[email protected]_maserati:/ # reboot
[email protected]_maserati:/ # exit
adb reboot
if fails one first test, reboot and restart ...
run all commands and no reboot... yes run all comands again...
reboot only with finish all commands...
After install - open market and Download superuser.apk
https://play.google.com/store/apps/...wsMSwyLDEsImNvbS5ub3NodWZvdS5hbmRyb2lkLnN1Il0.
Download the Superuser app from the google play and install.
[THANKS]
If this post help you click Thanks
[SCRIPT] Exploit Script Updated
I rooted my razr with commands only ok... and I succeeded
[EXPLOIT]
ICS.4.0.4.ROOT.zip - [ROOT-ICS] (1.133 KB, 50.898.976 views)
Mod Edit:Removed links
[FILES]
Mod Edit:Removed links
[ABOUT THIS PAGE]
I'm here to help people around the world
is not what you do that makes you extraordinary
but it is the way that we give that says who we are
it can not be measured with thanks or views
Jesus is the Lord
About this Root method - Thank You XDA for this page
http://www.xda-developers.com/androi...razr/#comments
About this Root method - Thank You Droid Life for this page
http://www.droid-life.com/2012/06/1...rooted-before-official-release/#disqus_thread
{
"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"
}
amazing, thanks for this i will try it out tomorrow morning and post root confirmation on my latam ota 404.
Sent from my XT910 using XDA
drolgnir said:
amazing, thanks for this i will try it out tomorrow morning and post root confirmation on my latam ota 404.
Sent from my XT910 using XDA
Click to expand...
Click to collapse
FrAsErTaG Thank you
Thanks for confirmation drolgnir
i´m happy for you... and for all my friends on XDA
The secret of my success is Jesus
I strongly recommend you to send this file to Mediafire
4shared cannot download anything without its account
shiwuye12 said:
I strongly recommend you to send this file to Mediafire
4shared cannot download anything without its account
Click to expand...
Click to collapse
Ok, thanks for sugestion...
I have not tested this script...
I rooted my razr with commands only ok...
[SCRIPT] Exploit with script by Hacker812c
http://www.4shared.com/rar/0BKsZ-Uw/ROOTICS404_2.html
http://www.mediafire.com/download.php?cbh4kpdeeizjc8j
First correction...
in the line 6 i insert new command [chmod]
[email protected]_maserati:/ # chmod 755 su
the commands failed on mine.(rom is 651.167.26.XT910.Retail.en.EU OTA 672.180.17.XT910.Retail.en.EU )
i tried it for many times.
i got error just on this lines:
Code:
[email protected]_spyder:/data/local/12m $ /data/local/12m/debugfs -w /dev/block/mmcblk
1p20
fs -w /dev/block/mmcblk1p20 <
debugfs 1.42 (29-Nov-2011)
/dev/block/mmcblk1p20: Permission denied while opening filesystem
debugfs: cd xbin
cd xbin
cd: Filesystem not open
debugfs: write /data/local/12m/su su
write /data/local/12m/su su
write: Filesystem not open
debugfs: set_inode_field su mode 0104755
set_inode_field su mode 0104755
set_inode_field: Filesystem not open
debugfs: set_inode_field su uid 0
set_inode_field su uid 0
set_inode_field: Filesystem not open
debugfs: set_inode_field su gid 0
set_inode_field su gid 0
set_inode_field: Filesystem not open
solved:
device needs reboot while process.
even it fail on first time
in manual command i have this message:
cp su /data/local/12m/
cp: su: No such file or directory
1|[email protected]_spyder:/sdcard $
pls help me
thanks
Everything's cool! Everything is working. Thank you very much. (RAZR GSM, Blur_Version.651.167.3370.XT910.Brasil.en.BR)
i just did everything manually without errors and nothing
the only issue i saw was the reboot command was not allowed. i had to do that manually, problem?
markceri2000 said:
in manual command i have this message:
cp su /data/local/12m/
cp: su: No such file or directory
1|[email protected]_spyder:/sdcard $
pls help me
thanks
Click to expand...
Click to collapse
ok, found my mistake: the 2 files are copied into internal memory. I was copying them into the external sd.
I did the manual procedure and everything went well!! Now I again have the root on my razr!
4.0.4 ICS 672.180.17 en eu
Thanks to those who have allowed this!!!!!!!
you are great at helping us "earthlings"
bye
This method/idea is almost the same as how to root the Transformer TF300T. @Rooting the TF300T
Thanks to @miloj who found this technique
works perfectly with manual method on my razr on 4.0.4 ICS 672.180.17!THANKS!
GREAT!!!!
Worked flawlessly on my LATAM GSM RAZR, Blur_Version.651.167.3370.XT910.Brasil.en.BR, only tip, if you do the "rebooot" line and get a "not permitted operation" just shut down the phone and turn it back on, it won't affect nothing.
Thank you a lot OP
This is great! Much better than our root method which needs to wipe and restore the CID partition. It wasn't published because many users would have to boot via BP Tools because they would have tried it without having a p18 backup. Thx!
Gesendet von meinem XT910 mit Tapatalk 2
Rooted!
I've nearly bricked my Razr when trying to fastboot back to 2.3.6 just for rooting my phone (I'm currently on "official" ICS leak 651.167.26.XT910.Retail.en.EU OTA 2.180.17.XT910.Retail.en.EU, it cannot be fastboot back)
Thank you very much!
By the way, the 2 reboot lines should be "adb reboot" right? I wasn't able to reboot directly (permission denied) so I exit and type adb reboot instead.
But ... I need backup root with ota rootkeeper ... Right?
I dont open shell from terminal without root permissions ...
Enviado desde mi XT910 usando Tapatalk 2
build: 6.7.2-180_SPU-19-TA-5 (updated from t-mobile to this one http://forum.xda-developers.com/showthread.php?t=1688241 , lost root
worked flawlessly! thanks
p.s. in manual mode
whirleyes said:
This method/idea is almost the same as how to root the Transformer TF300T. @Rooting the TF300T
Thanks to @miloj who found this technique
Click to expand...
Click to collapse
It's a copy n paste work http://forum.xda-developers.com/showthread.php?t=1707214
P.S. And why didn't you wait releasing it until the official ICS will be released? Now Moto is able to patch it...
Gesendet von meinem XT910 mit Tapatalk 2
dtrail1 said:
P.S. And why didn't you wait releasing it until the official ICS will be released? Now Moto is able to patch it...
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
I think we should save ours in case this happen. meanwhile, lets spread the root @Rick made work.
Hello,
I've not posted on here for a bit.
Basically I'm wanting to put my HTC Flyer WiFi back to Gingerbread as Honeycomb is no where near as stable.
Not used the Flyer for a while because of this.
I have thought about this for a while and looked at rooting the Flyer but everytime I look into it and find instructions I have more questions and seem to hit a brick wall at various stages.
As I am a complete noob and never rooted a device, can anyone help in a basic way.
Is the HTC dev root a good place to start?
Thanks, any help appreciated.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
/banned
Banned?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Wrong section. Development if for developers to post their work (ROMs, mods, etc.). Development is not for posting of questions, or seeking basic help.
Post in Q&A.
JB1971 said:
As I am a complete noob and never rooted a device, can anyone help in a basic way.
Is the HTC dev root a good place to start?
Thanks, any help appreciated.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Because I just root it recently, I can help you:-
Required downloads
1.First download the Gingerbread RUU.
2.If you don't have adb and fastboot on your PC
◦Get fastboot and adb tool for windows
3.Download universal misc_version and unzip to obtain the misc_version file.
4.Download tacoroot
5.Place both the misc_version and tacoroot.bin files in the same directory as adb
Procedure
1.Check the version number for your gingerbread RUU
RUU_Flyer_hTC_Asia_WWE_2.27.707.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204905_signed
3.The version is 2.27.707.1
4.Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
5.Run the following adb commands (in DOS prompt after install adb tools)
6.Code:
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
7.At this point your device will reboot to recovery
8.Simultaneously press Volume Down and Power
9.Reboot your device
10.Run the following command
11.Code:
adb shell /data/local/tacoroot.bin --root
12.Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
13.Run the following command:
14.Code:
adb shell /data/local/misc_version -s 2.27.707.1
15.Note that the number in RED is the version number retrieved in step 1.
16.Reboot to fastboot:
17.Code:
adb reboot bootloader
Relock the bootloader:
18.Code:
fastboot oem lock
19.Go back to fastboot mode ( lock causes the device to reboot )
20.Run your RUU ( if on linux or mac, see other similar threads from me on how to RUU on those OSes )
This is what happened in the command prompt:-
What is happened in real case:-
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\>cd download
D:\Download>cd flyer
D:\Download\Flyer>cd fastboot
D:\Download\Flyer\fastboot>adb push tacoroot.bin /data/local/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
614 KB/s (14475 bytes in 0.023s)
D:\Download\Flyer\fastboot>adb push misc_version /data/local/
2489 KB/s (367096 bytes in 0.144s)
D:\Download\Flyer\fastboot>adb shell chmod 755 /data/local/tacoroot.bin
D:\Download\Flyer\fastboot>adb shell chmod 755 /data/local/misc_version
D:\Download\Flyer\fastboot>adb shell /data/local/tacoroot.bin --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
D:\Download\Flyer\fastboot>adb shell /data/local/tacoroot.bin --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
D:\Download\Flyer\fastboot>adb shell /data/local/misc_version -s 2.27.707.1
--set_version set. VERSION will be changed to: 2.27.707.1
Patching and backing up misc partition...
D:\Download\Flyer\fastboot>adb shell /data/local/misc_version -s 2.27.707.1
--set_version set. VERSION will be changed to: 2.27.707.1
Patching and backing up misc partition...
D:\Download\Flyer\fastboot>adb reboot bootloader
error: device not found
D:\Download\Flyer\fastboot>adb reboot bootloader
error: device not found
D:\Download\Flyer\fastboot>adb reboot bootloader
error: device not found
D:\Download\Flyer\fastboot>adb reboot bootloader
error: device not found
D:\Download\Flyer\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.004s]
finished. total time: 0.005s
D:\Download\Flyer\fastboot>
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Then I just run the RUU
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
This version of revone has been successfully tested on Droid DNA 2.04 / 2.06 and Butterfly J 1.29.
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.dna
Instructions
Use any operating system you like, you only need adb.
1. Download revone (above) and push it to your device: adb push revone.dna /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.dna -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.dna -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.dna -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.
(reserved)
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.
* Remove the random reboot feature.
* Vastly reduce the error -6 probability.
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: revone.dna-0.2.1
Use as per OP instructions renaming or name substituting as appropriate.
Reverting to S-ON (updated)
* ./revone -l
* fastboot oem writesecureflag 3
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.
I'm just going to wait for a video tutorial before I attempt this. Don't want a brick. Thanks
Sent from my HTC6435LVW using xda premium
DELETED
thx~!! revteam!!!
HTC J butterfly 1.29.970.1 S-OFF succsess!!
{
"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"
}
Reserved
Sent from my LG-LS970 using xda app-developers app
AWESOME! going to do this right now and let you know if there were any problems
Yep. Worked great. S-off 2.06 firmware. thankyou guys
Great work! I am running into the following.
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
Success.
revone failed (error code = 2
As I proceed from here, everything shows success, but I am not unlocked. I am running a Droid DNA with
Software Number: 2.06.605.1.710RD
HBOOT-1.33.0001
Let me know if you want anything from my phone.
Works great. Thank you. You have increased the value of DNA to me.
itsmikeyj said:
Great work! I am running into the following.
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
Success.
revone failed (error code = 2
As I proceed from here, everything shows success, but I am not unlocked. I am running a Droid DNA with
Software Number: 2.06.605.1.710RD
HBOOT-1.33.0001
Let me know if you want anything from my phone.
Click to expand...
Click to collapse
Looks like removing the existing script and waiting 2 minutes then repeating worked just fine. Thanks guys!
nice work guys!
Great work!
I'm already s-off but whoooohooooo boy hell yeah good stuff guys very good to see a new method in case I have to replace my phone lol!!!!!
Sent from my HTC6435LVW using Tapatalk 2
Awesome work.. after s-off. What's needed for root?
Sent from my HTC6435LVW using xda app-developers app
Didn't work for me. I didn't get any errors, everything says success but I'm still S-On at the end ....
Stickboy46 said:
Didn't work for me. I didn't get any errors, everything says success but I'm still S-On at the end ....
Click to expand...
Click to collapse
Out of interest - how are you rebooting the device after the prepare stage (-P) ?
kmdm said:
Out of interest - how are you rebooting the device after the prepare stage (-P) ?
Click to expand...
Click to collapse
The Device auto rebooted
Stickboy46 said:
The Device auto rebooted
Click to expand...
Click to collapse
That is not a "success" state for "-P". Sadly. (It is very much an error/hard-crash though.)
Can you try
adb reboot
wait approx 2-3mins (2 mins seemed best for me once the adb wait-for-device returned)
then do ./revone -P ?
auto-reboot = bad.
i have followed the instructions mentioned in the below link to lock it back
http://forum.xda-developers.com/show....php?t=2314582
but the problem is i am stuck at step 4
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone-0.2.1 -P
./revone-0.2.1 -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Bus error
135|[email protected]:/data/local/tmp $
i couldnt understand about this bus error , can anyone help me in locking my device please.. i have only time till OCT 10th to submit my phone for warranty. please please help me
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.