So I have mac osx and windows. I've tried rooting on both. I can follow a tutorial, that is how I've rooted my thunderbolt when it first came out. But my new thunderbolt won't root using the methods that are working for others. So I request someone to help me out as to writing a step by step setup for required prerequisites programs... Thank you. Something isnt working. I just want to enjoy perks of root again.
Sent from my ADR6400L using XDA App
Which instructions are you trying to follow, JCase's or Cap's? Also, where is the root procedure failing for you? I only ask because there is no one here who could write better step by step instructions than the ones already included in both rooting methods.
Have to agree. Any information at all regarding how its failing would be most helpful.
Okay. For windows I used the script that is a batch file because I've heard it is super easy to use... When I first was running the script it would not find the device. Now it will find it with debugging on. But when debugging is on my device won't be listed in my computer. With debugging off it will show up on my computer. Anyways with the script it says it pushes all the files then when my phone is to reboot it won't.
Sent from my ADR6400L using XDA App
Make sure that your ADB is set up properly before you start using the batch file.
A great set of instructions can be found here:
http://www.droidforums.net/forum/droid-hacks/10924-how-adb-windows-made-easy.html
The batch file is also old and some of the files included in it might be too dated to use. Try using JCase's method.
Last login: Fri Jul 29 16:53:34 on ttys000
scott-roccas-macbook:~ scott87$ cd ..
scott-roccas-macbook:Users scott87$ cd ..
scott-roccas-macbook:/ scott87$ cd and*
scott-roccas-macbook:androidsdk scott87$ cd tools
scott-roccas-macbook:tools scott87$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT14RS010885 device
scott-roccas-macbook:tools scott87$ ./adb push busybox /data/local/
1867 KB/s (1062992 bytes in 0.555s)
scott-roccas-macbook:tools scott87$ ./adb push psneuter /data/local/
1764 KB/s (585731 bytes in 0.324s)
scott-roccas-macbook:tools scott87$ ./adb push misc.img /data/local/
1943 KB/s (262144 bytes in 0.131s)
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/busybox
scott-roccas-macbook:tools scott87$ ./adb shell chmod 777 /data/local/psneuter
scott-roccas-macbook:tools scott87$ ./adb shell /data/local/psneuter
mmap() failed. Operation not permitted
scott-roccas-macbook:tools scott87$
following this tutorial for my mac... http://forums.androidcentral.com/th...9-mac-procedure-how-root-htc-thunderbolt.html I have rooted my orignal TB over 6 times. Now I cannot use the same method on my new TB. Wtf. It wont let me go past the step of ./adb shell /data/local/psneuter
what is wrong?
Where did you get the exploits file that contained the psneuter file and such? Try downloading the files from http://www.multiupload.com/K4BZ22SIT5 and verify the md5 is 3b359efd76aac456ba7fb0d6972de3af and try again.
I'm kinda clueless without firmware versions and what exploits exactly are being used.
My exploits folder matches the MD5 checksum... I am on the newest possible firm. Someone please help me solve this issue...
http://forum.xda-developers.com/showthread.php?p=12785644#post12785644
http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/73211-rooting-issues.html#post782824
Both of those links showed ppl having similar problems. Try their fixes of restoring to factory defaults and trying again or re-formatting your card.
Thank you for your help. Doing a factory reset made the difference. I greatly appreciate it.
Dueces.
Sent from my ADR6400L using XDA App
Check out these videos, they helped me go through all the steps. The second time I rooted this thing was harder because I thought I had everything setup, and I did but I had to redo everything to get it to work. Start fresh by doing the drivers again, then put the contents of the exploits zip in sdk tool, (all the files but one were correct on mine, I think it was just an outdated version and that was one of my hold ups)
http://www.youtube.com/watch?v=oKPSe12YDxQ
http://www.youtube.com/watch?v=mc6EMdPpF6o
This is why you should manually root, and not do the auto crap... problems
Related
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
Hi!
My phone is LG Optimus One. The version is v10e.
I am new at this. This is my first android phone. I want to move the applications to SD Card. Because phone memory is not enough. So, i am trying to root my phone. Aldready 4 days. I aldready tried to root with different ways approximately 100 times. Every time the problem is same.
I am trying to root with Android SDK, OptimusRoot, then opening CMD window. I heard, everyone rooting with this way and the way with z4root. I can't root with z4root because its not working on the version v10e.
There was some guides "about rooting with opening CMD" on some website forums. I can't post the the links because, posting outside links not permitted for new users. I did everything on their guides. Every prerequisites fulfilled. Than opened a CMD window. Then, this...
C:\Users\Seyhan>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push rageagainstthecage-arm5.bin /data
/local/tmp/rageagainstthecage
43 KB/s (5392 bytes in 0.120s)
c:\android-sdk-windows\platform-tools>adb push su /data/local/tmp/
641 KB/s (26264 bytes in 0.040s)
c:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
1710 KB/s (1926944 bytes in 1.100s)
c:\android-sdk-windows\platform-tools>adb shell
$ chmod 4755 /data/local/tmp/rageagainstthecage
chmod 4755 /data/local/tmp/rageagainstthecage
$ chmod 4755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/busybox
$ 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={3341, 3341}
[*] Searching for adb ...
[+] Found adb as PID 1927
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 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.
$
c:\android-sdk-windows\platform-tools>adb shell
error: device not found
c:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
it's coming to here;
[*] adb connection will be reset. restart adb server on desktop and re-login.
then nothing happens. Its killing adb but never restart. I waited 20 minutes but nothing changed. Just 2 times its reconnected but once reconnected its still "$". I couldn't get the "#". Every time same problem. If anyone knows something about this, please help me. This is already a death battle for me. If anybody can help me with root my phone, i can't explain how i will be thankful.
Thanks for your interests.
Z4 root?
for someone new to this, you seem to doing it the hardest way?
/edit just seen it wont let you use it?
Tried superoneclick method?
If that "v10e" that you have is an Android v2.2.1 or v2.2.2 (check in Settings - About Phone - Android version), then your effort is in vain. You must downgrade to v2.2 in order to be able to root. This thread gives you a lot to read about how to flash an original ROM (which you will make sure is 2.2, that means "v10a") using KDZ.
Is this the german V10E? As far as i know, thats is the android 2.2.2 version which isn't rootable using z4 or rageagainstthecage.
I have the same version, and I did it like this:
1. flashed back to V10A
2. rooted using Z4
3. installed custom recovery
4. downloaded the V10E
5. built a custom rom from this (with root, deleted some stuff and some tweaks)
6. installed that rom using custom recovery
That way, I got a rooted V10E without that LG crap.
I found all neccessary links in this forum, basically I just followed this instructions:
[HOWTO] Cook your custom rom for LG P500: http://forum.xda-developers.com/showthread.php?t=901417
Takes some time, but is worth the effort!
Try to downgrade to 2.2 via KDZ tool .... (10B I think)
I recommend you to stick with 2.2 as it not only provides easy root access
but, it has some tweaks such as volume button swap in landscape mode, etc.
which 2.2.1 or above breaks...
Most roms are built on 2.2 -> see megatron rom
Having successfully semi-rooting my device through pauls root i was trying to install the SDE, i followed all steps correctly and ran the batch file but when rebooting into recovery mode no such menu appeared, i have confirmed root shell access so now i'm wondering if anyone else has had a problem? really would want to get the menu installed. It just seems not to work at all and i've ran the script from both my pc and from the internal device memory but this seems not to have worked, any ideas? Thanks
I followed all paul's instruction but I can't root my 101, I tried SDE script too but I can't see any differcence in recovery
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
@letama i'll pm you those tomorrow and thanks for the help!
letama said:
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
Click to expand...
Click to collapse
If u explain to me how do it, with pleasure
Sent from my ARCHOS 101G9 using Tapatalk
Moskiller said:
If u explain to me how do it, with pleasure
Click to expand...
Click to collapse
I need all the text in the cmd window with the adb commands and the results.
you can do the copy/paste the same way I explained to Nadrian.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>enable_sde
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push zimage /data/
local/tmp
306 KB/s (2655004 bytes in 8.450s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push initrd.cpio.l
zma /data/local/tmp
314 KB/s (398045 bytes in 1.236s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push abcbox /data/
local/tmp
323 KB/s (277204 bytes in 0.838s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 755 /d
ata/local/tmp/abcbox
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /data/local/
tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.l
zma
Generating KD...
Updating KD (3053305 bytes)...
0
100
It worked when i executed the script through command prompt, but here's the execution log anyway, thanks for the tool and for all help!
My log (Windows XP SP3):
C:\android-sdk-windows\platform-tools>enable_sde.bat
C:\android-sdk-windows\platform-tools>adb push zimage /data/local/tmp
1999 KB/s (2655004 bytes in 1.296s)
C:\android-sdk-windows\platform-tools>adb push initrd.cpio.lzma /data/local/tmp
1776 KB/s (398045 bytes in 0.218s)
C:\android-sdk-windows\platform-tools>adb push abcbox /data/local/tmp
1925 KB/s (277204 bytes in 0.140s)
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/abcbox
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/abcbox kd_flashe
r -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
Generating KD...
Updating KD (3053305 bytes)...
0
100
C:\android-sdk-windows\platform-tools>
Even for me, SDE doesn't work (archos 101 G9 8gb)
EDIT: WORKS!
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
hitman72 said:
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
Click to expand...
Click to collapse
Weird!
I guess a couple of md5sum could help pinpointing adb push or flash issue.
I'll add that someday.
Thanks for the report!
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
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
cpiercew said:
Worked once, now no more. I had to re-flash using heimdall, successfully recovered but now can't re-root my phone. Originally had safestrap running like a charm and cant get back to it now.
adb shell confirmed, phone reboots but looks like saferoot is trying to remove temporary files when the phone is rebooting.... see below
Any thoughts? Suggestions?
Thanks - cpiercew
usermbp:saferoot user$ adb shell
[email protected]:/ $ exit
usermbp:saferoot user$ sh ./install.sh
--- Samsung i545 VRUEMJ7 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
Waiting for device...
Watch your phone. Unlock it and give permission for the install to run.
Sending files to your device...
2363 KB/s (17804 bytes in 0.007s)
3412 KB/s (104800 bytes in 0.029s)
2208 KB/s (13592 bytes in 0.006s)
3248 KB/s (2139595 bytes in 0.643s)
4732 KB/s (1109128 bytes in 0.228s)
293 KB/s (629 bytes in 0.002s)
Starting rooting program.
ro.build.product=jfltevzw
ro.build.id=JSS15J
selinux enforcing known.
Succeeded in getroot!
Remount success!
Copying files..
Removing temporary files...
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
/system/bin/sh: /system/xbin/su: not found
--- All Finished ---
usermbp:saferoot user$
Click to expand...
Click to collapse
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked? Also, what happens when you type "adb shell" ? Because from reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands).
Click to expand...
Click to collapse
I included the adb shell output, I verified it could connect to the device first. Prior to installing ADB I first installed Kies and drivers, then put adb in my path to ensure it would run properly.
I haven't check the tmp directory, I will but not sure if this would matter as it seems something else is going on. I have a total of three errors that seem to be happening:
1) Removing temporary files
Removing temporary files...
error: device not found
2) When the phone reboots I unlock it immediately but dont get prompted to allow ADB shell to run
Rebooting...Please wait.
error: device not found
Waiting for device to re-appear...
Unlock your phone, and when prompted, give SuperSU permission for
'ADB shell' to run.
/system/bin/sh: /system/xbin/su: not found
3) Installing busybox seems to fail, "su" is not found
Installing busybox
/system/bin/sh: /system/xbin/su: not found
I also get the "all finished" prompt before the phone is finished booting up.
gnubian said:
I'm assuming the files copied to the tmp directory because of the adb output, but have you checked?
Edit: derp, you said adb shell confirmed.
From reading the install script your phones state shouldn't change before the device is first not recognized (it should still be on and responding to adb commands). So if you can successfully start an adb shell there is no reason the script shouldn't work. Maybe try running the commands manually?
Click to expand...
Click to collapse
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
- just realized looking in install.sh shows the source. However, still noob'd and don't know how to translate some of the basic shell scripting
cpiercew said:
Good idea, I didn't know that was an option, is there a list of commands I can find somewhere?
Click to expand...
Click to collapse
Edit: i was assuming that was a linux error, not an error in adb shell. It seems the files did not properly copy. Did you check if they are in the tmp folder?
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
[/COLOR]If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
gnubian said:
I believe you need to install the package that has the su command (not sure about mac, I use linux). Just open the .sh file rather than run it and the commands are in there. Obviously just ignore the echos and such.
---------- Post added at 08:50 PM ---------- Previous post was at 08:46 PM ----------
If you give me a minute I can post the commands without the unnecessary scripting that should allow for manual installation. Google your errors about system/bin/sh and su to find the appropriate package you need for your mac distribution in the meantime.
Edit: don't know why I assumed mac, thought I read it in your post. What are you running?
Click to expand...
Click to collapse
Correct, using a mac
The following are the individual commands. Should let you know exactly when your problems are starting if you enter them manually. I believe the repeated system/xbin/su command is repeated incase the device isn't responding/rebooted yet. So you may only need to enter it once. Sorry the .sh worked for me so I didn't do it this way. Hopefully this sheds more light on your problem.
Remember to run these from the folder that contains the "file" folder.
adb wait-for-device
adb push files/getroot /data/local/tmp/
adb push files/su /data/local/tmp/
adb push files/selinuxoff /data/local/tmp/
adb push files/Superuser.apk /data/local/tmp/
adb push files/busybox /data/local/tmp/
adb push files/install-recovery.sh /data/local/tmp/
adb shell "chmod 0755 /data/local/tmp/getroot"
adb shell "chmod 0755 /data/local/tmp/busybox"
adb shell /data/local/tmp/getroot
adb shell "rm /data/local/tmp/getroot"
adb shell "rm /data/local/tmp/su"
adb shell "rm /data/local/tmp/selinuxoff"
adb shell "rm /data/local/tmp/Superuser.apk"
adb shell "rm /data/local/tmp/busybox"
adb shell "rm /data/local/tmp/install-recovery.sh"
adb reboot
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb shell "/system/xbin/su -c mount -o remount,rw /system"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/su"
adb shell "/system/xbin/su -c chmod 6755 /system/xbin/daemonsu"
adb shell "/system/xbin/su -c /system/xbin/busybox --install -s /system/xbin"
adb wait-for-device
adb shell "/system/xbin/su -c mount -o remount,ro /system"
gnubian said:
adb wait-for-device
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
adb wait-for-device
adb shell "/system/xbin/su -c sleep 1"
Click to expand...
Click to collapse
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
k1mu said:
Please note that all of that is to give the user a chance to notice the SuperSU prompt asking them to give permissions for adb shell.
Click to expand...
Click to collapse
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
gnubian said:
Thanks for clearing that up. As I said I did not root by manually issuing the commands.
Click to expand...
Click to collapse
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
cpiercew said:
Ok, I resolved the issue after going with my hunch the stock verizon GS4 VRUEMK2 build from Surge1223 I had previously recovered from may have been the issue.
I went back into Kies backed up apps, settings and performed a firmware recovery to MK2. Once rebooted and reconfigured - it worked as designed.
For what it's worth, the build I would suggest avoiding if you want to use saferoot or root your phone at all is what I found from Surge1223 on androidforum: SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip
Not a dig on Surge1223, as with anything I use all downloads at my own risk.
Thanks again for the responses, any info I can provide from this that will help anyone else trying to use Saferoot please let me know.
Click to expand...
Click to collapse
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
FWIW, I don't have an androidforums account. Also, my upload is fine, otherwise it wouldn't flash in Odin. Next time come tell me or comment in my thread about the issues your having with my upload.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure - there could have been a few reasons it didn't work.