Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,810,846 Members 37,470 Now Online
XDA Developers Android and Mobile Development Forum

[Root][4.4.2 ND7]GhettoRoot (Towelroot port) v0.3.2

Tip us?
 
Ezrae19
Old
(Last edited by Ezrae19; Today at 12:05 AM.) Reason: Highlighting my output to make the problem areas a little more obvious..
#191  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Sep 2014
I can connect to my phone with adb just fine, there is no problem with adb.

I tried to manually step through the root process, using adb and typing each command along the way and still get the same errors from the ghettoroot binary and the root.sh script.




C:\Users\me\Downloads\ghettoroot-v0.3.2>adb devices
List of devices attached
42f7881ee5729f87 device



C:\Users\me\Downloads\ghettoroot-v0.3.2>adb -s 42f7881ee5729f87 shell
shell@t0ltevzw:/ $ pwd
pwd
/
shell@t0ltevzw:/ $ cd /data/local/tmp/ghetto
cd /data/local/tmp/ghetto
shell@t0ltevzw:/data/local/tmp/ghetto $ ls
ls
META-INF
UPDATE-SuperSU.zip
busybox
ghettoroot
root.sh
supersu

shell@t0ltevzw:/data/local/tmp/ghetto $ ./ghettoroot
./ghettoroot
************************************************
native ghettoroot, aka cube-towel, aka towelroot
running with pid 7614
Kernel version: Linux version 3.0.31-1496113 (dpi@SWDD5710) (gcc version 4.4.3 (
GCC) ) #1 SMP PREEMPT Thu May 8 01:19:38 KST 2014
Found matching device: Linux version 3.0.31-

modstring: 1337 0 1 0 4 0
************************************************

[DEBUG] init_exploit:1153: function start
[DEBUG] send_magicmsg:762: function start
[DEBUG] make_socket:726: function start
[DEBUG] search_goodnum:883: function start
[DEBUG] search_goodnum:886: loop FUTEX_CMP_REQUEUE_PI
[DEBUG] accept_socket:1118: function start
[DEBUG] accept_socket:1140: Socket tastefully accepted.
[DEBUG] make_socket:749: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:902: single FUTEX_CMP_REQUEUE_PI
[DEBUG] search_goodnum:905: loop while waiting for other thread
[DEBUG] send_magicmsg:803: loop while waiting for other thread
[DEBUG] send_magicmsg:812: perform selected method
[INFO] search_goodnum:948: starting the dangerous things
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] search_goodnum:952: MAGIC: a0000800
[DEBUG] search_goodnum:953: MAGIC_ALT: 00100800
[DEBUG] search_goodnum:956: magicval: a0000820
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:961: MAGIC = MAGIC_ALT;
[DEBUG] search_goodnum:965: Entering while loop...
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:976: 0xd5b2a000 is a good number
[DEBUG] get_root:428: thread ID: 7621
[DEBUG] get_root:440: cpid1 resumed
[DEBUG] get_root:448: HACKS_fdm = 7 [/dev/pts/1]
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:1078: 0xe70bfd5c is also a good number
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] get_root:428: thread ID: 7624
[DEBUG] search_goodnum:1095: Writing to HACKS_fdm...
[DEBUG] get_root:486: cpid3 resumed
[DEBUG] get_root:476: Writing new addr_limit to thread...
[DEBUG] write_pipe:325: dest:daddc008 src:0001300c count:4
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc1a44 src:daddc000 count:16
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:492: ti.task=e508b300 .flags=00000200 .preempt_count=1 .addr_li
mit=ffffffff
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc1644 src:e508b300 count:1024
[DEBUG] read_pipe:316: function exit
[INFO] get_root:496: Address limit successfully extended, seemingly
[DEBUG] get_root:502: Contents of taskbuf:
00000000 daddc000 00000002 00400040 00000000 00000000 00000001 00000001 00000082
00000082 00000082 00000000 c065fae0 00000000 0000006e 0253c825 00000001 e7aaea8
0 00000000 e7aaea8c c316b5a0 00000001 0b32a172 000000b1 0002d63d 00000000 1c77fb
58 00000573 0002d63d 00000000 00000000 00000000 00000000 00000000 0048fc92 00000
000 0000000f 00000000 0052f236 00000000 00000000 00000000 00000000 00000000 0000
0000 00000000 001c575f 00000000 001f48ca 00000000 00000000 00000000 00000000 000
00000 00007b60 00000000 00005f8a 00000000 00000000 00000000 00000000 00000000 00
000000 00000000 00000000 00000000 00000000 00000000 0000000c 00000000 00000000 0
0000000 00000000 00000000 0000000c 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 c316b570 00000000
00000000 e508b468 e508b468 00000000 000000c8 00000001 00000000 00000000 c316b61
0 00000000 00000000 00000000 00000000 00000001 00000000 00000000 e508b4a4 e508b4
a4 00000000 0000000e 00000000 0052a87b 00000000 0b32a172 000000b1 00000000 00000
000 c0acfb40 eb44ca10 0000008c e508b4dc e508b4dc e508b4e4 e508b4e4 e5ad3ba0 e5ad
3ba0 00000001 00000001 00000000 00000001 00000000 00000000 00000000 ffffffff 000
00000 00000000 00800000 00000000 00001dc8 00001dbe e7aafb40 e7aafb40 e508b534 e5
08b534 e508b53c e508b53c eb44a640 e508b548 e508b548 e508b550 e508b550 00000000 e
83e0988 e83e0980 00000000 e50d308c e50d3080 e7aafdb0 e99ee590 e99ee580 eb44a8bc
eb44e43c 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000002 0000000b 000002f8 1735be85 000002f8 1735be85 0000000
1 00000000 00000000 00000000 00000000 00000000 00000000 e508b5e0
[INFO] get_root:512: Supposedly found credential at taskbuf[184]: db936580
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc15e8 src:db936580 count:92
[DEBUG] read_pipe:316: function exit
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc15d0 src:e7fb1180 count:24
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:535: YOU ARE A SCARY DEVICE
[DEBUG] write_pipe:325: dest:e7fb1180 src:40dc15d0 count:24
[DEBUG] write_pipe:325: dest:db936580 src:40dc15e8 count:92
[DEBUG] write_pipe:325: dest:e508b524 src:00013010 count:4
[INFO] postroot:404: chmod 0755 ./root.sh succeeded
Remounting filesystems
Setting SE Permissive
Installing SuperSU...
Archive: /data/local/tmp/ghetto/UPDATE-SuperSU.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script

About to run SuperSU install script
ui_print *********************
ui_print
ui_print SuperSU installer ZIP
ui_print
ui_print *********************
ui_print
ui_print - Mounting /system, /data and rootfs
ui_print
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
skip reached end of input
skip reached end of input
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
ui_print - Extracting files
ui_print
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[64]: unzip: n
ot found

ui_print - Disabling OTA survival
ui_print
Unable to chmod /tmp/supersu/arm/chattr: No such file or directory
Unable to chmod /tmp/supersu/arm/chattr.pie: No such file or directory
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[72]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[73]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[74]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[75]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[76]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[77]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[78]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[79]: /tmp/sup
ersu/arm/chattr.pie: not found
ui_print - Removing old files
ui_print
ui_print - Creating space
ui_print
ui_print - Placing files
ui_print
mkdir failed for /system/bin/.ext, File exists
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/common/Superuser.apk: No such file or directory
cp: /tmp/supersu/common/install-recovery.sh: No such file or directory
cp: /tmp/supersu/common/99SuperSUDaemon: No such file or directory
ui_print - Restoring files
ui_print
ui_print - Setting permissions
ui_print
Unable to chown /system/bin/.ext/.su: No such file or directory
Unable to chown /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chown /system/xbin/su: No such file or directory
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chown /system/xbin/sugote: No such file or directory
Unable to chown /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chown /system/xbin/daemonsu: No such file or directory
Unable to chown /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chown /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chown /system/app/Superuser.apk: No such file or directory
Unable to chown /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/daemonsu with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/daemonsu with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/etc/install-recovery.sh with ubject_r:system_f
ile:s0: No such file or directory
chcon: Could not label /system/etc/install-recovery.sh with ubject_r:system_f
ile:s0: No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/app/Superuser.apk with ubject_r:system_file:s0
: No such file or directory
chcon: Could not label /system/app/Superuser.apk with ubject_r:system_file:s0
: No such file or directory
ui_print - Post-installation script
ui_print
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[166]: /system
/xbin/su: not found
ui_print - Unmounting /system and /data
ui_print
failed: Device or resource busy
failed: Device or resource busy
ui_print - Done !
ui_print
Completion summary:
Successful tasks: Install SuperSU
[INFO] postroot:410: Executing ./root.sh succeeded

*** Thank you for choosing ghettoroot. Please enjoy your stay.

Your device will reboot in 10 seconds.
This is normal. Thanks for waiting.
Please make sure all programs are closed to avoid losing data.

10 seconds...

5 seconds...

Rebooting...


etc. etc. My phone does reboot. After boot it's not rooted. The errors and output of the scripts are the same as if I just run the scripts from the Windows or OSX command line.
 
larry_thagr81
Old
#192  
larry_thagr81's Avatar
Senior Member
Thanks Meter 64
Posts: 256
Join Date: Dec 2012
Ok, so if the super user isn't listed in your app drawer, download root checker by joeykrim and run that program. If it says that it has successfully gained access to the root of your phone, then you're rooted. You'll just need to download an updated super user program like the program offered by chainfire.
Samsung Galaxy Note II (rooted+unlocked bootloader) "Game Changer"
HTC Rezound (rooted) "potential but FAIL"
Motorola Droid 3 (stock) "a joke"
HTC Thunderbolt (rooted+unlocked bootloader) "The first 4G/LTE phone but FAIL"
Motorola Droid X (rooted+unlocked bootloader) "FAIL"
Motorola Droid (rooted+unlocked bootloader) "The phone that put Android on the map"
 
Ezrae19
Old
#193  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Sep 2014
Quote:
Originally Posted by larry_thagr81 View Post
Ok, so if the super user isn't listed in your app drawer, download root checker by joeykrim and run that program. If it says that it has successfully gained access to the root of your phone, then you're rooted. You'll just need to download an updated super user program like the program offered by chainfire.
It's not rooted. See screenshot and all of the errors I previously posted.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2014-09-20-11-51-33.png
Views:	24
Size:	149.5 KB
ID:	2944288  
 
wheeless
Old
#194  
Junior Member
Thanks Meter 2
Posts: 28
Join Date: Dec 2010
Default ADB and Path Not Issue - Maybe Permissions????

I've really appreciated the advice to changing the environment path to try and resolve my issue of my I605 not getting root.

I did that and verified that adb was recognized by my Windows 8.1 system. Also ran the adb device command and verified the device was recognized. Ran GhettoRoot again. Got exactly the same result - GhettoRoot does something to the Note II device (I get the Knox and Syscope error messages again) but doesn't root.

So I think maybe there is a issue on the Windows machine - so I move AndroidSKD and GhettoRoot_v0.3.2 to the C:root on my windows machine (had them on the desktop). Again, change the path variable, verify that adb is recognized by windows and recognizes my device. Run GhettoRoot again. Same result - the same massive list of "unable to chmod," "no such file or directory," and "unable to chown." And I did run Root Checker - it confirmed what I knew SU-not found; Root Access - no access.

I'm about to the point of saying this isn't worth it since I now have to do my third ODIN back to stock to get rid of the "Knox stopped" and "Syscope stopped" error messages - but since I hate unsolved puzzles, could the problem be one of permissions on my Windows machine or on my I605 device? Just doesn't make any sense that adb is recognized on the windows machine and adb recognizes the I605 device and does something to it (creating error messages with Knox and Syscope) - yet the adb process cannot find files and take ownership.

Any other puzzle solvers who want to take a final shot (for me at least) at this?



"ADKQUOTE=doctor-cool;55558607]<iframe width="560" height="315" src="//www.youtube.com/embed/yjutSsQn2Ic" frameborder="0" allowfullscreen></iframe>
Thanks for the answer !
I thought the problems might be related to the path. Any ideas why some of us were able to run GhettoRoot "out of the box" and some of us can not.
I think if they install SDK ADT Bundle For Windows properly and run adb.exe at least once afterwards their computer will be able to find the path on it's own.
Check this out.
How To Download & Install SDK ADT Bundle For Windows-

https://www.youtube.COM/watch?v=PKY5bbytBGE
I recommend the whole video but at 16:36 he tells you how to open the adb command window. Once you have it open type in "adb devices" hit enter and it will show you a list of devices connected. Your phone should be there.[/QUOTE]
 
larry_thagr81
Old
#195  
larry_thagr81's Avatar
Senior Member
Thanks Meter 64
Posts: 256
Join Date: Dec 2012
Quote:
Originally Posted by Ezrae19 View Post
I already had the environment variables set on both Windows and OSX to allow the OS to find adb, so unfortunately that video does not help.

Thanks!
Are you running the program with administrative privileges? Which version of the latest towelroot are you running? There are two out there and one is completely automated while the other ask you 3 or 4 yes or no questions before it attempts to root your device. Does the program tell you that it's can communicate with your device? Did you store the towelroot file within the platform-tools folder of the SDK folder? If necessary, PM me and I can send you the files that I used, which would include everything you need to get your phone rooted.
Samsung Galaxy Note II (rooted+unlocked bootloader) "Game Changer"
HTC Rezound (rooted) "potential but FAIL"
Motorola Droid 3 (stock) "a joke"
HTC Thunderbolt (rooted+unlocked bootloader) "The first 4G/LTE phone but FAIL"
Motorola Droid X (rooted+unlocked bootloader) "FAIL"
Motorola Droid (rooted+unlocked bootloader) "The phone that put Android on the map"
 
Ezrae19
Old
#196  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Sep 2014
Quote:
Originally Posted by larry_thagr81 View Post
Are you running the program with administrative privileges? Which version of the latest towelroot are you running? There are two out there and one is completely automated while the other ask you 3 or 4 yes or no questions before it attempts to root your device. Does the program tell you that it's can communicate with your device? Did you store the towelroot file within the platform-tools folder of the SDK folder? If necessary, PM me and I can send you the files that I used, which would include everything you need to get your phone rooted.
Yes, I'm running as root and/or Administrator, depending on which computer I try this with. I get the same thing from OSX Mavericks and Win7 64 bit.

I'm using ghettoroot version 0.3.2. If I run the scripts included in the zip I do get the yes/no prompts.

Yes adb can see and communicate with my device without issues - take a look at my previous posts with the command line outputs for details there. I'm able to use adb (from both OSX and Windows) to communicate with my device, transfer files back and forth, etc. I don't think there's a problem there.

Thanks!
 
larry_thagr81
Old
#197  
larry_thagr81's Avatar
Senior Member
Thanks Meter 64
Posts: 256
Join Date: Dec 2012
Quote:
Originally Posted by wheeless View Post
I've really appreciated the advice to changing the environment path to try and resolve my issue of my I605 not getting root.

I did that and verified that adb was recognized by my Windows 8.1 system. Also ran the adb device command and verified the device was recognized. Ran GhettoRoot again. Got exactly the same result - GhettoRoot does something to the Note II device (I get the Knox and Syscope error messages again) but doesn't root.

So I think maybe there is a issue on the Windows machine - so I move AndroidSKD and GhettoRoot_v0.3.2 to the C:root on my windows machine (had them on the desktop). Again, change the path variable, verify that adb is recognized by windows and recognizes my device. Run GhettoRoot again. Same result - the same massive list of "unable to chmod," "no such file or directory," and "unable to chown." And I did run Root Checker - it confirmed what I knew SU-not found; Root Access - no access.

I'm about to the point of saying this isn't worth it since I now have to do my third ODIN back to stock to get rid of the "Knox stopped" and "Syscope stopped" error messages - but since I hate unsolved puzzles, could the problem be one of permissions on my Windows machine or on my I605 device? Just doesn't make any sense that adb is recognized on the windows machine and adb recognizes the I605 device and does something to it (creating error messages with Knox and Syscope) - yet the adb process cannot find files and take ownership.

Any other puzzle solvers who want to take a final shot (for me at least) at this?



"ADKQUOTE=doctor-cool;55558607]<iframe width="560" height="315" src="//www.youtube.com/embed/yjutSsQn2Ic" frameborder="0" allowfullscreen></iframe>
Thanks for the answer !
I thought the problems might be related to the path. Any ideas why some of us were able to run GhettoRoot "out of the box" and some of us can not.
[/QUOTE]

Yes I have a theory, if you don't have the correct samsung drivers installed ADB won't be able to communicate with the phone. Simply connecting your phone to the computer and having windows install the necessary drivers for your device to be able to transfer files aren't the correct drivers that are needed for the ADB environment. I went to samsung website and downloaded the drivers from there.

If you don't have the correct pathway set ADB won't be able to find the files it needs to access. I went a step further and placed the ghettoroot file into the platform-tools folder of the SDK folder.

I've had my galaxy note 2 rooted with an unlocked bootloader. Unfortunately a corrupted boot file prevented me one day from being able to boot into the OS as well and restore my phone through custom recovery to a previously saved backup. So I had all the necessary files to reroot my phone. The only issue I ran into was that windows wasn't installing the necessary drivers for the ADB environment to be able to communicate with my device and once I realized that was the issue, I was able to root my phone.

---------- Post added at 12:41 PM ---------- Previous post was at 12:32 PM ----------

Quote:
Originally Posted by Ezrae19 View Post
I can connect to my phone with adb just fine, there is no problem with adb.

I tried to manually step through the root process, using adb and typing each command along the way and still get the same errors from the ghettoroot binary and the root.sh script.

The root itself doesn't seem to be working, after ghettoroot runs it does not grant the root permissions that allow the root.sh script to mount the filesystems and install busybox and supersu:



C:\Users\me\Downloads\ghettoroot-v0.3.2>adb devices
List of devices attached
42f7881ee5729f87 device


C:\Users\me\Downloads\ghettoroot-v0.3.2>adb -s 42f7881ee5729f87 shell
shell@t0ltevzw:/ $ pwd
pwd
/
shell@t0ltevzw:/ $ cd /data/local/tmp/ghetto
cd /data/local/tmp/ghetto
shell@t0ltevzw:/data/local/tmp/ghetto $ ls
ls
META-INF
UPDATE-SuperSU.zip
busybox
ghettoroot
root.sh
supersu
shell@t0ltevzw:/data/local/tmp/ghetto $ ./ghettoroot
./ghettoroot
************************************************
native ghettoroot, aka cube-towel, aka towelroot
running with pid 7614
Kernel version: Linux version 3.0.31-1496113 (dpi@SWDD5710) (gcc version 4.4.3 (
GCC) ) #1 SMP PREEMPT Thu May 8 01:19:38 KST 2014
Found matching device: Linux version 3.0.31-

modstring: 1337 0 1 0 4 0
************************************************

[DEBUG] init_exploit:1153: function start
[DEBUG] send_magicmsg:762: function start
[DEBUG] make_socket:726: function start
[DEBUG] search_goodnum:883: function start
[DEBUG] search_goodnum:886: loop FUTEX_CMP_REQUEUE_PI
[DEBUG] accept_socket:1118: function start
[DEBUG] accept_socket:1140: Socket tastefully accepted.
[DEBUG] make_socket:749: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:902: single FUTEX_CMP_REQUEUE_PI
[DEBUG] search_goodnum:905: loop while waiting for other thread
[DEBUG] send_magicmsg:803: loop while waiting for other thread
[DEBUG] send_magicmsg:812: perform selected method
[INFO] search_goodnum:948: starting the dangerous things
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] search_goodnum:952: MAGIC: a0000800
[DEBUG] search_goodnum:953: MAGIC_ALT: 00100800
[DEBUG] search_goodnum:956: magicval: a0000820
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:961: MAGIC = MAGIC_ALT;
[DEBUG] search_goodnum:965: Entering while loop...
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:976: 0xd5b2a000 is a good number
[DEBUG] get_root:428: thread ID: 7621
[DEBUG] get_root:440: cpid1 resumed
[DEBUG] get_root:448: HACKS_fdm = 7 [/dev/pts/1]
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] search_goodnum:1078: 0xe70bfd5c is also a good number
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] setup_exploit:858: function start
[DEBUG] setup_exploit:865: function exit
[DEBUG] wake_actionthread:660: function start
[DEBUG] make_sigaction:614: function start
[DEBUG] wake_actionthread:684: loop while waiting for other thread
[DEBUG] make_sigaction:633: loop while waiting for other thread
[DEBUG] wake_actionthread:712: mutex unlock
[DEBUG] wake_actionthread:715: function exit
[DEBUG] get_root:428: thread ID: 7624
[DEBUG] search_goodnum:1095: Writing to HACKS_fdm...
[DEBUG] get_root:486: cpid3 resumed
[DEBUG] get_root:476: Writing new addr_limit to thread...
[DEBUG] write_pipe:325: dest:daddc008 src:0001300c count:4
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc1a44 src:daddc000 count:16
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:492: ti.task=e508b300 .flags=00000200 .preempt_count=1 .addr_li
mit=ffffffff
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc1644 src:e508b300 count:1024
[DEBUG] read_pipe:316: function exit
[INFO] get_root:496: Address limit successfully extended, seemingly
[DEBUG] get_root:502: Contents of taskbuf:
00000000 daddc000 00000002 00400040 00000000 00000000 00000001 00000001 00000082
00000082 00000082 00000000 c065fae0 00000000 0000006e 0253c825 00000001 e7aaea8
0 00000000 e7aaea8c c316b5a0 00000001 0b32a172 000000b1 0002d63d 00000000 1c77fb
58 00000573 0002d63d 00000000 00000000 00000000 00000000 00000000 0048fc92 00000
000 0000000f 00000000 0052f236 00000000 00000000 00000000 00000000 00000000 0000
0000 00000000 001c575f 00000000 001f48ca 00000000 00000000 00000000 00000000 000
00000 00007b60 00000000 00005f8a 00000000 00000000 00000000 00000000 00000000 00
000000 00000000 00000000 00000000 00000000 00000000 0000000c 00000000 00000000 0
0000000 00000000 00000000 0000000c 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 c316b570 00000000
00000000 e508b468 e508b468 00000000 000000c8 00000001 00000000 00000000 c316b61
0 00000000 00000000 00000000 00000000 00000001 00000000 00000000 e508b4a4 e508b4
a4 00000000 0000000e 00000000 0052a87b 00000000 0b32a172 000000b1 00000000 00000
000 c0acfb40 eb44ca10 0000008c e508b4dc e508b4dc e508b4e4 e508b4e4 e5ad3ba0 e5ad
3ba0 00000001 00000001 00000000 00000001 00000000 00000000 00000000 ffffffff 000
00000 00000000 00800000 00000000 00001dc8 00001dbe e7aafb40 e7aafb40 e508b534 e5
08b534 e508b53c e508b53c eb44a640 e508b548 e508b548 e508b550 e508b550 00000000 e
83e0988 e83e0980 00000000 e50d308c e50d3080 e7aafdb0 e99ee590 e99ee580 eb44a8bc
eb44e43c 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000002 0000000b 000002f8 1735be85 000002f8 1735be85 0000000
1 00000000 00000000 00000000 00000000 00000000 00000000 e508b5e0
[INFO] get_root:512: Supposedly found credential at taskbuf[184]: db936580
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc15e8 src:db936580 count:92
[DEBUG] read_pipe:316: function exit
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:40dc15d0 src:e7fb1180 count:24
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:535: YOU ARE A SCARY DEVICE
[DEBUG] write_pipe:325: dest:e7fb1180 src:40dc15d0 count:24
[DEBUG] write_pipe:325: dest:db936580 src:40dc15e8 count:92
[DEBUG] write_pipe:325: dest:e508b524 src:00013010 count:4
[INFO] postroot:404: chmod 0755 ./root.sh succeeded
Remounting filesystems
Setting SE Permissive
Installing SuperSU...
Archive: /data/local/tmp/ghetto/UPDATE-SuperSU.zip
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script

About to run SuperSU install script
ui_print *********************
ui_print
ui_print SuperSU installer ZIP
ui_print
ui_print *********************
ui_print
ui_print - Mounting /system, /data and rootfs
ui_print
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
skip reached end of input
skip reached end of input
2+0 records in
2+0 records out
2 bytes transferred in 0.001 secs (2000 bytes/sec)
ui_print - Extracting files
ui_print
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[64]: unzip: n
ot found
ui_print - Disabling OTA survival
ui_print
Unable to chmod /tmp/supersu/arm/chattr: No such file or directory
Unable to chmod /tmp/supersu/arm/chattr.pie: No such file or directory
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[72]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[73]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[74]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[75]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[76]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[77]: /tmp/sup
ersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[78]: /tmp/sup
ersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[79]: /tmp/sup
ersu/arm/chattr.pie: not found
ui_print - Removing old files
ui_print
ui_print - Creating space
ui_print
ui_print - Placing files
ui_print
mkdir failed for /system/bin/.ext, File exists
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/arm/su: No such file or directory
cp: /tmp/supersu/common/Superuser.apk: No such file or directory
cp: /tmp/supersu/common/install-recovery.sh: No such file or directory
cp: /tmp/supersu/common/99SuperSUDaemon: No such file or directory
ui_print - Restoring files
ui_print
ui_print - Setting permissions
ui_print
Unable to chown /system/bin/.ext/.su: No such file or directory
Unable to chown /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chown /system/xbin/su: No such file or directory
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chown /system/xbin/sugote: No such file or directory
Unable to chown /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chown /system/xbin/daemonsu: No such file or directory
Unable to chown /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chown /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chown /system/app/Superuser.apk: No such file or directory
Unable to chown /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/daemonsu with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/daemonsu with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/etc/install-recovery.sh with ubject_r:system_f
ile:s0: No such file or directory
chcon: Could not label /system/etc/install-recovery.sh with ubject_r:system_f
ile:s0: No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/app/Superuser.apk with ubject_r:system_file:s0
: No such file or directory
chcon: Could not label /system/app/Superuser.apk with ubject_r:system_file:s0
: No such file or directory
ui_print - Post-installation script
ui_print
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[166]: /system
/xbin/su: not found
ui_print - Unmounting /system and /data
ui_print
failed: Device or resource busy
failed: Device or resource busy
ui_print - Done !
ui_print
Completion summary:
Successful tasks: Install SuperSU
[INFO] postroot:410: Executing ./root.sh succeeded

*** Thank you for choosing ghettoroot. Please enjoy your stay.

Your device will reboot in 10 seconds.
This is normal. Thanks for waiting.
Please make sure all programs are closed to avoid losing data.

10 seconds...

5 seconds...

Rebooting...


etc. etc. My phone does reboot. After boot it's not rooted. The errors and output of the scripts are the same as if I just run the scripts from the Windows or OSX command line.
What have you tried after the restart to know if your phone is rooted or not?
Samsung Galaxy Note II (rooted+unlocked bootloader) "Game Changer"
HTC Rezound (rooted) "potential but FAIL"
Motorola Droid 3 (stock) "a joke"
HTC Thunderbolt (rooted+unlocked bootloader) "The first 4G/LTE phone but FAIL"
Motorola Droid X (rooted+unlocked bootloader) "FAIL"
Motorola Droid (rooted+unlocked bootloader) "The phone that put Android on the map"
 
liftedplane
Old
#198  
liftedplane's Avatar
Member
Thanks Meter 2
Posts: 69
Join Date: Jun 2011
Location: Tacoma
I'm not sure if this can help however I was having problems as well, I used usbdev view and just deleted everything including my keyboard and mouse, i then plugged them back in to reinstall and then plugged my I've in, I was finally able to install the drivers that I had previously installed (samsung drivers that Windows wasn't recognizing) then ran adb WITHOUT admin elevation. I then had to run a command prompt and kill the asb server and restart to have my phone recognized, once I did that it rooted without issue. I've had to root it twice already since I'm an idiot and effed up the system ui.

not sure if this will help but worth a try.

I'm on win7 x64 ultimate as well

Sent from my SCH-I605 using Tapatalk
 
NetworkingPro
Old
#199  
NetworkingPro's Avatar
Senior Member
Thanks Meter 62
Posts: 112
Join Date: May 2014
Location: Central US
Do the following:

adb shell
ls -la /data/local/tmp/ghetto/META-INF/com/google/android/

copy/paste the output here.
 
Ezrae19
Old
#200  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Sep 2014
Quote:
Originally Posted by NetworkingPro View Post
Do the following:

adb shell
ls -la /data/local/tmp/ghetto/META-INF/com/google/android/

copy/paste the output here.
Here it is!

shell@t0ltevzw:/ $ ls -la /data/local/tmp/ghetto/META-INF/com/google/android
ls -la /data/local/tmp/ghetto/META-INF/com/google/android
-rw-rw-rw- root root 5265 2014-09-20 14:54 update-binary
-rw-rw-rw- root root 4693 2014-09-20 14:54 update-binary-2
-rw-rw-rw- root root 78 2014-09-20 14:54 updater-script
shell@t0ltevzw:/ $


Thanks!

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes