EDIT: Great news! We have an on-device one-click root again!
Simply download VISIONary from (edit: used to be in the Market) Modaco. I tried it on FRG83 stock. It works. No ADB, no external computer required, no fuss. Thanks to the developers!
EDIT again: Sorry, the FRG83D build no longer works with VISIONary - BUT - the overall rageagainstthecage method still works via ADB. I also hear that SuperOneClick works but it requires a Windows machine.
----
Ok it's been established that Universal Androot / exploid / freenexus no longer works on FRG33/FRG83 etc. And it's been established that "rageagainstthecage" does still work. So far I'm not aware of a one-click method to implement the latter exploit.
So I'm starting this thread to centralize everyone's experiences. I don't personally need these instructions but other folks apparently do. I've quoted a rooting guide in post #2. If you think any refinements are necessary or you have a better way of writing it out, please feel free to add to this thread.
Thanks to efrant for pointing the way to this guide. Based on comments below, I'm quoting another revised version.
hmanxx said:
Hi OP,
You may want to edit your post #2, I have inserted the mounting commands in the thread i posted previously. this will help novice users to get thing right out of box without figuring why permission denied.
I have just tried out the additional mounting steps..things are working fine..
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/showpost.php?p=8120790&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}
[*] Searching for adb ...
[+] Found adb as PID 64
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
exit
Click to expand...
Click to collapse
And below are the previous contents of this post, prior to editing.
-------------
Many respondents on this thread have indicated that the instructions don't work the first time. If you get to the step where you are supposed to get a root shell (#) but you instead get a non-root shell ($), start from the top and try the exploit once or twice more. Apparently if you are persistent it will work.
I'm also told these instructions are missing adb remount before the steps where you push busybox, su and so forth.
hmanxx said:
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/showpost.php?p=8120790&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}
[*] Searching for adb ...
[+] Found adb as PID 64
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
# exit
exit
Click to expand...
Click to collapse
I too am interested in this info. Looking forward to any info provided....
There is detailed step-by-step info in many threads as to how to use the rageagainstthecage exploit to root your device, e.g.: http://forum.xda-developers.com/showpost.php?p=8300203&postcount=55
Why start a new thread?
efrant said:
There is detailed step-by-step info in many threads as to how to use the rageagainstthecage exploit to root your device, e.g.: http://forum.xda-developers.com/showpost.php?p=8300203&postcount=55
Why start a new thread?
Click to expand...
Click to collapse
Actually that's perfect, thanks.
I started a new thread because the step-by-step info is buried in other threads and many folks post questions asking about it because they can't find said guides. I figured if I could start a new thread with a proper title, it would be located more easily.
All the info is located in Nexus One Wiki, under "Guides" / "Rooting". Direct link to the post with complete data. So I still don't see any need for the post, that will be buried in forum depths. My signature..
But since you posted it, and it's more detailed - I'll change the link to point to it.
[edit 2] The Wiki is damn slow after the forum crash...
[edit 3] It refuses to accept the submit, complaining about "session data loss". Time to complain to admins..
Heh well if the Wiki is crashy at the moment, all the more reason to have a redundant post here.
If you look back to the linked posts, I was the one who suggested which instructions for ali3nfr3ak to follow after a successful push of rageagainstthecage, and then ali3nfr3ak reported success on FRG33, and then hmanxx seems to have stripped out the irrelevant/unnecessary lines. So it's teamwork =)
One thing I'm not sure of - I see the original "exploid"/"freenexus" instructions included a cleanup by removing /system/bin/rootshell. Should something similar be done after rageagainstthecage to clean up?
@ cmstlst This is a good idea, because when I did this I had like 3 different pages open as all the information was spread everywhere, hopefully this will make it easier for everyone to follow, good one
I used the steps posted here to restore root access to a Nexus One which had been previously rooted with 1-click. It was running stock FRF91. It was a fairly smooth process, especially since the update to FRG83 did not delete my Superuser.apk, su, or busybox files. The permissions had just been turned down, so with the RageAgainstTheCage exploit active, I was able to change the permissions as indicated and was off and running.
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
for the read/write mount and was then able to turn up the permissions. And, in the interests of completeness, to mount /system read-only again afterward:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Thanks much for consolidating the procedure where it was easy to find.
anyway to re-lock the Bootloader
highvista said:
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
It's mtdblock3, not mtdblock4, though for some reason the mount worked for me even on 6. But in any case, much better and easier done using ADB command:
adb remount
Finally the Wiki is also back to work, the "Rooting FRG83" link is updated to point to this thread.
Here, the rageagainstthecage didn't work.
I followed these steps:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#
Click to expand...
Click to collapse
But, I didn't get root shell (#), when I typed "adb shell" I still got ($).
I'm in FRG83, Android 2.2.1.
Any ideas?
cmstlist said:
Thanks to efrant for pointing the way to this guide.
Click to expand...
Click to collapse
Thank you for posting this. It was a big help. I lost my root after 2.2.1 and this worked great. I did have to execute the .bin file 3 times. The first time, I got $, and the second time as well. It was only on the 3rd execute that I got the # prompt. I read that others had the same problem, that it only worked after a few times.
highvista said:
I used the steps posted here to restore root access to a Nexus One which had been previously rooted with 1-click. It was running stock FRF91. It was a fairly smooth process, especially since the update to FRG83 did not delete my Superuser.apk, su, or busybox files. The permissions had just been turned down, so with the RageAgainstTheCage exploit active, I was able to change the permissions as indicated and was off and running.
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
for the read/write mount and was then able to turn up the permissions. And, in the interests of completeness, to mount /system read-only again afterward:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Thanks much for consolidating the procedure where it was easy to find.
Click to expand...
Click to collapse
Thank you for this. I was in the same situation and I was not able to set the premissions. Then I saw your post. I am not a Linux/Unix guy, so it was step-by-step for me. Curiously, why is it necessary to change the premission for su, busybox, etc.?
Thanks guys.
Atento said:
Here, the rageagainstthecage didn't work.
I followed these steps:
But, I didn't get root shell (#), when I typed "adb shell" I still got ($).
I'm in FRG83, Android 2.2.1.
Any ideas?
Click to expand...
Click to collapse
I had this, too. Like the above poster said, I got # after several tries. However something went wrong midway through the other steps from efrant, and I went back and lost #, only had $.
Also looking for ideas.
Xel'Naga said:
I had this, too. Like the above poster said, I got # after several tries. However something went wrong midway through the other steps from efrant, and I went back and lost #, only had $.
Also looking for ideas.
Click to expand...
Click to collapse
I would try the process over again from the beginning. Once you get the #, follow highvista's information to mount the file system as RW, and do the chmods. After you are done, re-mount as RO.
snovvman said:
I would try the process over again from the beginning. Once you get the #, follow highvista's information to mount the file system as RW, and do the chmods. After you are done, re-mount as RO.
Click to expand...
Click to collapse
Yup, had to reboot the device and try again about four times and then it finally all stuck. Now rooted on 2.2.1.
snovvman said:
Thank you for posting this. It was a big help. I lost my root after 2.2.1 and this worked great. I did have to execute the .bin file 3 times. The first time, I got $, and the second time as well. It was only on the 3rd execute that I got the # prompt. I read that others had the same problem, that it only worked after a few times.
Thank you for this. I was in the same situation and I was not able to set the premissions. Then I saw your post. I am not a Linux/Unix guy, so it was step-by-step for me. Curiously, why is it necessary to change the premission for su, busybox, etc.?
Thanks guys.
Click to expand...
Click to collapse
Thanks for your replies! I'm rooted now.
Thanks for all!!!
Hi OP,
You may want to edit your post #2, I have inserted the mounting commands in the thread i posted previously. this will help novice users to get thing right out of box without figuring why permission denied.
I have just tried out the additional mounting steps..things are working fine..
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/...nstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/show...&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
exit
Thanks, I'll fix it up when I'm at a desktop computer again and less occupied by the Masters thesis I'm defending in just over 2 weeks
Sent from my Nexus One using XDA App
hehe oh noes. I gave the cage file a go 3 times, failed, so I got pissed and unlocked the bootloader, then now I read about the remounting of the file system.. didn't think about that.
well.. now I can't undo the unlocking :/
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 everyone, first all I apologize for my English a bit "strange", being French, I do not mania Shakespeare's language as well as you.
I post here to request your help: I have a low cost tablet brand "Boulanger" visible in google with the next words : "Tablette multimédia android ESSENTIELB Smart'TAB 8002 16Go "
Despite several attempts on my part, I can not get to the rooter, whether with tools like "UnlockRoot" or line by line with this procedure:
"First, here are the commands that run the psneuter exploit and gain a root shell.
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
"
I can not make CHMOD do not have sufficient rights.
Here is the information I have on the shelf:
"Device detected: ST8002 (V2.0.1.JRO03C.user.root.20130503)"
Thank you for your help.
@ +
toniodu7666 said:
Hi everyone, first all I apologize for my English a bit "strange", being French, I do not mania Shakespeare's language as well as you.
I post here to request your help: I have a low cost tablet brand "Boulanger" visible in google with the next words : "Tablette multimédia android ESSENTIELB Smart'TAB 8002 16Go "
Despite several attempts on my part, I can not get to the rooter, whether with tools like "UnlockRoot" or line by line with this procedure:
"First, here are the commands that run the psneuter exploit and gain a root shell.
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
"
I can not make CHMOD do not have sufficient rights.
Here is the information I have on the shelf:
"Device detected: ST8002 (V2.0.1.JRO03C.user.root.20130503)"
Thank you for your help.
@ +
Click to expand...
Click to collapse
Hello
At jiun 2013 i buy 2 smart tab 8002
first, started at 21/7/2013
blanc laqué
133938
13_21_1003117
st8002
v 4.1.1
v3.0.8
v2.0.1.JRO03C.user.root.201303503
at september, start
rouge
133940
13_03_1003117
v 4.0.4
3.0.8
v2.0.5.IMM76I.user.20121210
= 2 st8002 but 2 android version !
My 2 kids can't play at same game.....
Nobody have tips to upgrade the oldest ?