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

wolfballz · Sep 11, 2015 at 3:29 PM

RBEmerson said:
Oh, jumpin' jeebus, I've gone back and given myself the VZW Yellow Triangle of Death (YTD) again.

Let's stop here for a sanity check - I'm sure I'm seriously OT so if someone wants to shift this post to a better place, at least tell me where the thread went. Alright... onwards.

For whatever reason, trying to install TWRP (any recent rev.) brings out the YTD. TWRP Manager says TWRP installed but VZW hands out the YTD whether trying reach recovery or simply reboot.

I've gotten too good at restoring ND7: Under Odin, use a sch-i605.pit, included in a distro of MC3, and an md5 of ND7, and ND7 is back. Use the Networking Pro version of GhettoRoot and the phone is rooted. Re-install SuperSU (curiously, it goes away during the GhettoRoot run, but SuperSU Pro remains, although Pro is a dead loss without SuperSU installed), open SuperSU, load the binary, reboot, and open BusyBox Pro, install it, and all is well. Even the home page(s) remain the same. ~~Use TI to re-freeze stuff that was frozen before ("freeze" goes away during re-installing ND7 and being rootless).~~ Anyway...

Going to 4.4.4 means moving to CM11. Will SafeStrap (which uses an earlier TWRP) let me do that? Or, getting stupidly bold, will it let me use the CM12 Lollipop? I assume that of CM11 won't work, CM12 won't either. But ya never know...

ADDED: I mistakenly wrote that frozen items "defrost" during restoring to ND7. That's simply wrong. I had a brain burp after seeing NFL Mobile try to update for some reason. Odd, as I'd deleted, not frozen, the app. The take-away is "don't sweat frozen apps thawing out".

Nothing other than safestrap is going to work. The bootloader is locked... so therefore won't allow a custom recovery like TWRP or CWM. Trying to flash any form of CM on a ND7 note 2 won't work either as the kernels are different and since the bootloader is locked won't allow other kernels to run.

---------- Post added at 07:29 AM ---------- Previous post was at 07:26 AM ----------

cory733 said:
thanks wolf. isnt the stock rom touchwiz? are you saying you can only run the stock rom from the stock rom slot or install other stock roms that are basically the same?

in a boot loop will the phone make it to the safestrap screen? and then be able to run recovery?

if it didnt you would just go into odin mode and flash a copy of the stock rom correct?

now that my phone is rooted can i do a factory reset if i wanted? (found alot of mixed info about this)

besides that im about to download and install safestrap. i have busybox and supersu. i was going to clear cache and run it from the download link in this thread that you recommended in an earlier post

does it look like im ready to go?

There's a couple custom ROMS in the forum for the note 2 that will work with safestrap. I don't think you need to do a factory reset. I would go get titanium backup and delete unwanted bloatware. Odin should get you back to good if you do something that bootloops the phone and you can't access safestrap. Clearing cache never hurts.

RBEmerson · Sep 11, 2015 at 4:02 PM

A couple of final (I think) questions: Why would a .pit file magically get me past the instances of "NAND write failed" when using Odin?

What's up with the inability to get SuperSU and BusyBox to install during GhettoRoot.bat's run? The log showed both couldn't load from curl downloads. I had to install them from Play Store instead.

In all of this loading and reloading, I've flipped the KNOX counter. I assume that once it's 0x1, that's where it stays. It's not a real problem, but it'd be nice to clear it if possible.

---------- Post added at 11:02 AM ---------- Previous post was at 10:55 AM ----------

Hmmm... I seem to have lost a quick reply post. OK, trying again...

If I read the comments correctly, they say that there is no way to move past 4.4.2 to 4.4.4 or 5.n.n. The locked bootloader makes that impossible. The only way to move the Note 2 to something other than 4.4.2 is with a custom ROM.
If that's right, then I've hit the wall with the Note 2. This phone is intended to be a "daily driver" for my wife, who'd rather stay with her flip phone (ain't gonna happen thanks to the new VZW plans). Trying to talk her through any custom ROM's oddities doesn't bear thinking about. [/shudder]

wolfballz · Sep 11, 2015 at 7:31 PM

RBEmerson said:
A couple of final (I think) questions: Why would a .pit file magically get me past the instances of "NAND write failed" when using Odin?

What's up with the inability to get SuperSU and BusyBox to install during GhettoRoot.bat's run? The log showed both couldn't load from curl downloads. I had to install them from Play Store instead.

In all of this loading and reloading, I've flipped the KNOX counter. I assume that once it's 0x1, that's where it stays. It's not a real problem, but it'd be nice to clear it if possible.

---------- Post added at 11:02 AM ---------- Previous post was at 10:55 AM ----------

Hmmm... I seem to have lost a quick reply post. OK, trying again...

If I read the comments correctly, they say that there is no way to move past 4.4.2 to 4.4.4 or 5.n.n. The locked bootloader makes that impossible. The only way to move the Note 2 to something other than 4.4.2 is with a custom ROM.
If that's right, then I've hit the wall with the Note 2. This phone is intended to be a "daily driver" for my wife, who'd rather stay with her flip phone (ain't gonna happen thanks to the new VZW plans). Trying to talk her through any custom ROM's oddities doesn't bear thinking about. [/shudder]

Even the custom ROM has to be 4.4.2. If the Note 2 you have didn't take the last few updates and get to ND7 you would be able to still have an unlocked bootloader and could get 4.4.4 or 5.x.x. It's just unfortunate...

RBEmerson · Sep 11, 2015 at 8:51 PM

I'm guessing that going back to MC3 doesn't fix the locked bootloader problem. I received the phone with 4.4.2, so I think I'm well and truly SOL.

55rebel · Sep 12, 2015

Stuck.... still not able to root

I was originally rooted @ 4.2 [stock rom] for quite awhile. Due to bug issues creeping in, I decided to: un-root, do a full factory reset, and a full upgrade to 4.4.2--before doing the research. If I had known it was going to be this difficult to get my phone re-rooted, I wouldn't have upgraded to the latest :/
Maybe someone can see something that I'm doing, or not doing?
Thanks

OS: Windows 10
Phone/pda:
Model# - SCH-I605
Version - 4.4.2
Baseband version - i605VRUFND7
Kernel version - 3.0.31
Build# - KOT49H.I605VRUFND7

After several other attempts, this was the last...
SuperSU installed via google play store

My procedure-chain::

Checked - "Allow Unknown sources"
Activated - "Developer options"
Checked - "USB debugging"
Entered - "adb devices" @ command prompt, resulting in...

Code:

.......
.......
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
43005987b490a067        unauthorized

So, as suggested in this thread:
Unchecked and then rechecked "USB debugging"
Hit "Revoke USB debugging authority"
Reentered "adb devices" @ command prompt, resulting in...

Code:

.......
.......
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
43005987b490a067        device

Ran as administrator - "GhettoRoot.bat" as suggested by NetworkingPro @ post #27 in this thread.
Resulting in...

Code:

Welcome to GhettoRoot for the Samsung Galaxy Note 2 - 4.4.2 ND7
Please confirm you have turned on USB debugging and authorized your device.

- Press any key to continue -

Press any key to continue . . .
The rooting process is about to begin. Please do not interrupt the process once it has started.

Removing old root files.
drwxrwxrwx shell    shell             2015-09-10 10:24 ghetto
-rwxr-xr-x shell    shell       34208 2015-09-10 10:50 ghettoroot

Pushing necessary files to your phone.
cannot stat 'libs/armeabi/ghettoroot': No such file or directory
cannot stat 'data/local/tmp': No such file or directory

Starting root exploit.
cannot stat 'libs/armeabi/ghettoroot': No such file or directory
************************************************
native ghettoroot, aka cube-towel, aka towelroot
running with pid 13016
kernel version: Linux version 3.0.31-1496113 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Thu May 8 01:19:38 KST 2014

found matching phone: Linux version 3.0.31-
modstring: 1337 0 1 0 4 0
************************************************

Enter send_magicmsg (722)
Enter make_socket (681)
Enter search_goodnum (842)
Enter accept_socket (1072)
Socket tastefully accepted.
Exit  make_socket (709)
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
starting the dangerous things
Enter setup_exploit (817)
Exit  setup_exploit (824)
Enter setup_exploit (817)
Exit  setup_exploit (824)
search_goodnum 908
MAGIC: a0000800
MAGIC_ALT: 00100800
magicval: a0000820
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
MAGIC = MAGIC_ALT;
search_goodnum 920
Enter setup_exploit (817)
Exit  setup_exploit (824)
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
0xe94d6000 is a good number
Enter get_root (310; tid: 32df)
get_root 315
cpid1 resumed
   In get_root(329): HACKS_fdm = 7 [/dev/pts/1]
   In get_root(349): ph->limit_offset == 0
Enter setup_exploit (817)
Exit  setup_exploit (824)
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
0xe7235d5c is also a good number
Enter setup_exploit (817)
Exit  setup_exploit (824)
Enter wake_actionthread (622)
Enter make_sigaction (579)
Exit  wake_actionthread (675)
Enter get_root (310; tid: 32e1)
GOING
   In get_root(358): read(HACKS_fdm, readbuf, sizeof readbuf);
get_root 361
   In write_pipe(258) dest:e4b7c008 src:00011000 count:4
get_root 364
get_root 367
get_root 315
cpid3 resumed
WOOT
Enter read_pipe (233)
read_pipe(236) src:e4b7c000 dest:41289a4c count:16
Exit  read_pipe(248): len:16
ti.task=e807c400 .flags=00000200 .preempt_count=1 .addr_limit=ffffffff
Enter read_pipe (233)
read_pipe(236) src:e807c400 dest:4128964c count:1024
Exit  read_pipe(248): len:1024
00000000 e4b7c000 00000002 00400040 00000000 00000000 00000001 00000001 00000082 00000082 00000082 00000000 c065fae0 00000000 0000006e 0253c825 00000001 ca88ea80 00000000 c316b5a0 ca88ea8c 00000001 1bf14a19 000002d9 0002e14e 00000000 ffb41050 00000f00 0002e14e 00000000 00000000 00000000 00000000 00000000 0056178d 00000000 0000000c 00000000 005aba12 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000275b9 00000000 000275b9 00000000 00000000 00000000 00000000 00000000 0000f353 00000000 00001388 00000000 00000000 00000000 00000005 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000c 00000000 00000000 00000000 00000000 00000000 0000000b 00000000 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 c316b570 00000000 00000000 e807c568 e807c568 00000000 000000c8 00000001 00000000 00000000 c316b610 00000000 00000000 00000000 00000000 00000001 00000000 00000000 e807c5a4 e807c5a4 00000000 0000000b 00000000 005aa68a 00000000 1bf14a19 000002d9 00000000 00000000 c0acfb40 e807c190 0000008c e807c5dc e807c5dc e807c5e4 e807c5e4 e8513860 e8513860 00000001 00000001 00000000 00000001 00000000 00000000 00000000 ffffffff 00000000 00000000 00800000 00000000 000032e1 000032d8 e807bfc0 e807bfc0 e807c634 e807c634 e807c63c e807c63c c46b4400 e807c648 e807c648 e807c650 e807c650 00000000 e8f1d108 e8f1d100 e807c224 e8a6d58c e8a6d580 e807c230 e8a6d590 e8a6d580 c46b467c e807937c 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001 00000009 00000c3b 1d6578b9 00002569 0b8ac58e 00000001 00000000 00000000 00000000 00000000 00000000 00000000 e807c6e0
Supposedly found credential at taskbuf[184]: db051380
Enter read_pipe (233)
read_pipe(236) src:db051380 dest:412895f0 count:92
Exit  read_pipe(248): len:92
Enter read_pipe (233)
read_pipe(236) src:e4769500 dest:412895d8 count:24
Exit  read_pipe(248): len:24
YOU ARE A SCARY PHONE
   In write_pipe(258) dest:e4769500 src:412895d8 count:24
   In write_pipe(258) dest:db051380 src:412895f0 count:92
   In write_pipe(258) dest:e807c624 src:00011004 count:4
-rw-rw-rw- root     root            0 2015-09-11 13:01 rooted
Package com.sec.knox.seandroid new state: disabled
Disabling Knox: Success
Disabling SEAndroid: Success
Package com.sec.knox.seandroid new state: disabled
Disabling Knox (again): Success
Package com.policydm new state: disabled
Disabling Policy Updater: Success
Disabling Local OTA Updates: Success
Package com.sec.android.fwupgrade new state: disabled
Disabling FWUpgrade: Success
Disabling Samsung Data Migration tool: Success
Remounting /system: Success
Remounting /: Success
Unable to chmod /data/local/tmp/busybox: No such file or directory
sh: /data/local/tmp/busybox: not found
Could not find/unzip SuperSU: Success
Please place an UPDATE-SuperSU-*.zip file in the main folder before running the install script

Your device will reboot in 10 seconds.
This is normal. Thanks for waiting.

10 seconds...

5 seconds...

Rebooting...       [it did]

Your phone should now be rooted. Press any key to exit.
Press any key to continue . . .

Then verifying root using Root Checker Basic, resulted in...
"Sorry! Root access is not properly installed on this device"

Any suggestions would be greatly appreciated.

Thanks,
Mark

RBEmerson · Sep 11, 2015

You may well have gotten further along than you think.

Try this:
Disconnect the USB cable.

Boot to Recovery, wipe the cache, boot to the system.

Verify that you still have USB debugging checked. Revoke USB debugging authorizations. Return to the home screen.

Connect the USB cable to the phone and laptop - ignore the Verizon CD "request", just close the popup. Do not let the screen go dark. Wait until you see the request to accept your PC. Check the box and accept the connection. Since you've seen the handshake between the phone and PC, you're almost certainly no longer in installation mode, but check it anyway. If you're still there, remove the cable, clear USB debugging, clear the authorizations. Enable USB debugging again, plug in the cable, and wait for the authorization request. Proceed as above - Wash, Rinse, Repeat.

Open Windows Explorer and go to the subdirectory holding GhettoRoot.bat. Do a <SHIFT-RIGHT CLICK> in a blank spot in the window. Click on "Open command window here".

Enter GhettoRoot<ENTER> and watch the magic happen. Follow the instructions to the point where you hit the <ANY> key and the script ends. Enter "exit" to close the command window. Remove the USB cable and reboot the phone.

Open Play Store and install SuperSU. Install BusyBox (BusyBox Pro and SuperSU Pro recommended, ditto for Root Checker). Open SuperSU and follow the "install binary" prompt with the "normal" option. Reboot.

Open Root Checker and verify root. You should be golden. If so, open and install BusyBox from inside BusyBox (follow the BB prompts).

If things go sour, repeat the process. If it still doesn't work, do a Factory Data Reset, get the phone running again, open Developer, enable USB Debugging and... Wash, Rinse, Repeat.

DISCLAIMER: I don't know jack. Follow the above and you'll almost certainly brick your phone. Follow the above at your peril. For sure you've violated any warranty for your phone. You'll probably trip the KNOX counter. In short: Abandon all hope, ye that enter within.

Don't say I didn't warn you.

Have a nice day.

cory733 · Sep 8, 2015 233 21 0

I know you said I can do a factory reset but will it still be rooted? Will safestrap still be there? Any difference between doing it from settings and doing it from recovery? Not that I want to now. But I like to every once in a while.

Has anyone gotten past the locked bootloaders on these phones? Is samsung even able to during an ota update?

Edit: also does factory reset affect anything sub-root? Does it affect things like supersu if supersu is installed in system apps? What about anything left over from uninstalled root only apps?

55rebel · Sep 10, 2015 4 0 0

Awesome!!!

RBEmerson said:
You may well have gotten further along than you think.

Try this:
Disconnect the USB cable.

Boot to Recovery, wipe the cache, boot to the system.

Verify that you still have USB debugging checked. Revoke USB debugging authorizations. Return to the home screen.

Connect the USB cable to the phone and laptop - ignore the Verizon CD "request", just close the popup. Do not let the screen go dark. Wait until you see the request to accept your PC. Check the box and accept the connection. Since you've seen the handshake between the phone and PC, you're almost certainly no longer in installation mode, but check it anyway. If you're still there, remove the cable, clear USB debugging, clear the authorizations. Enable USB debugging again, plug in the cable, and wait for the authorization request. Proceed as above - Wash, Rinse, Repeat.

Open Windows Explorer and go to the subdirectory holding GhettoRoot.bat. Do a <SHIFT-RIGHT CLICK> in a blank spot in the window. Click on "Open command window here".

Enter GhettoRoot<ENTER> and watch the magic happen. Follow the instructions to the point where you hit the <ANY> key and the script ends. Enter "exit" to close the command window. Remove the USB cable and reboot the phone.

Open Play Store and install SuperSU. Install BusyBox (BusyBox Pro and SuperSU Pro recommended, ditto for Root Checker). Open SuperSU and follow the "install binary" prompt with the "normal" option. Reboot.

Open Root Checker and verify root. You should be golden. If so, open and install BusyBox from inside BusyBox (follow the BB prompts).

If things go sour, repeat the process. If it still doesn't work, do a Factory Data Reset, get the phone running again, open Developer, enable USB Debugging and... Wash, Rinse, Repeat.

DISCLAIMER: I don't know jack. Follow the above and you'll almost certainly brick your phone. Follow the above at your peril. For sure you've violated any warranty for your phone. You'll probably trip the KNOX counter. In short: Abandon all hope, ye that enter within.

Don't say I didn't warn you.

Have a nice day.

Thanks, that worked!!
Nothing like scaring me half to death with that disclaimer, though

.... lol!

Actually I never unplugged the phone; i just used "adb reboot recovery"--everything went smoooooth.

Again, THANKS!

Mark

RBEmerson · Sep 12, 2015 at 2:17 AM

cory733 said:
I know you said I can do a factory reset but will it still be rooted? Will safestrap still be there? Any difference between doing it from settings and doing it from recovery? Not that I want to now. But I like to every once in a while.

Has anyone gotten past the locked bootloaders on these phones? Is samsung even able to during an ota update?

Edit: also does factory reset affect anything sub-root? Does it affect things like supersu if supersu is installed in system apps? What about anything left over from uninstalled root only apps?

FDR means all apps go away. You're effectively back to the "out of the box" state. The basic load comes from the phone. Apps such as SuperSU are not part of that. The start-up process should eventually bring them back if they came from Play Store. I avoid FDR's as much as possible. I can't say whether root totally goes away or needs SuperSU to make it accessible.

As to SafeStrap, the app goes away, too,. after an FDR. My guess is SafeStrap's splash screen (sad robot) will show up at bootup, but I've been wrong before.

AFAIK, VZW locked up the bootloader for the Note 2 when 4.4.2 was released. Samsung isn't about to annoy VZW by releasing a work-around or new bootloader. The phone is now old enough that even if VZW didn't care, there's the Note 3 and S6 and a host of other, newer products that Samsung is going to spend its time on. The only hope to get out of this mess is if someone gets creative and conjures up an unlocked bootloader. Don't hold your breath while waiting for that to happen.

Unless less you have a phone that's at 4.3 or earlier and has never, ever been to 4.4.2, you can work with the bootloader. If your phone took the 4.4.2 OTA, what you see is what you've got. The party's over.

Again, I have been known to get things wrong. What you've got is my best guess.

---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------

55rebel said:
Thanks, that worked!!
Nothing like scaring me half to death with that disclaimer, though .... lol!

Actually I never unplugged the phone; i just used "adb reboot recovery"--everything went smoooooth.
Again, THANKS!

Mark

Hey, glad to help you raise your pulse rate! [/GRIN]

In all seriousness, this process can hurt a phone. Some folks are rather casual about that, but I figure it's better to underline there really is some risk in rooting.

IMHO, you may have gotten lucky with the adb reboot and not unplugging. Once you've run adb, a daemon process continues to run on the PC (use Task Manager to look at the processes - you'll see adb.exe in the list). Your phone rebooted but the adb daemon is still there on the PC, remembering what it saw before the reboot. At the very least, I would use (and have used) Task Manager to kill the process before doing something new with adb. For example, after doing adb devices and before running GhettoRoot.bat, I killed adb.exe.

55rebel · Sep 10, 2015 4 0 0

Question...

I hear that to get rid of the knox-nag after GhettoRoot, that it was suggested to remove knox. Is it safe to uninstall ALL the files associated with knox listed in titanium backup? I've read that some in the past--rom 4.3, have lost network connectivity by removing knox.

Thanks,
Mark

RBEmerson · Sep 12, 2015

The KNOX app can be frozen by TI (Titanium Backup app - root required) without a problem (BTDT). The same applies for SysScope, the other common nag. TI can also be used to delete the apps but I left them as just frozen, which gives the same result but doesn't free up storage.

55rebel · Sep 10, 2015 4 0 0

RBEmerson said:
The KNOX app can be frozen by TI (Titanium Backup app - root required) without a problem (BTDT). The same applies for SysScope, the other common nag. TI can also be used to delete the apps but I left them as just frozen, which gives the same result but doesn't free up storage.

I may do just the freezing also then.

Thanks,
Mark

RBEmerson · Sep 12, 2015 at 10:01 PM

Da nada.

At some point I'll probably review what's frozen and uninstall these apps if nobody's complaining about their absence.

wolfballz · Sep 15, 2015 at 3:03 PM

RBEmerson said:
I'm guessing that going back to MC3 doesn't fix the locked bootloader problem. I received the phone with 4.4.2, so I think I'm well and truly SOL.

Nope...

---------- Post added at 07:03 AM ---------- Previous post was at 06:57 AM ----------

55rebel said:
I hear that to get rid of the knox-nag after GhettoRoot, that it was suggested to remove knox. Is it safe to uninstall ALL the files associated with knox listed in titanium backup? I've read that some in the past--rom 4.3, have lost network connectivity by removing knox.

Thanks,
Mark

I've had my note 2 rooted for a while now and completely uninstalled everything Knox related with Titanium Backup and have had no ill results. Also removed that Syscope with no problems.

RBEmerson · Sep 15, 2015 at 8:10 PM

wolfballz said:
Nope...

---------- Post added at 07:03 AM ---------- Previous post was at 06:57 AM ----------

I've had my note 2 rooted for a while now and completely uninstalled everything Knox related with Titanium Backup and have had no ill results. Also removed that Syscope with no problems.

The "Nope" refers to going back to MC3 not freeing up the bootloader?

+1 on no KNOX and no Syscope - doesn't hurt a thing.

wolfballz · Sep 16, 2015 at 3:24 PM

RBEmerson said:
The "Nope" refers to going back to MC3 not freeing up the bootloader?

+1 on no KNOX and no Syscope - doesn't hurt a thing.

Correct.

RBEmerson · Sep 16, 2015 at 3:43 PM

Once again, great thanks for your help, wolfballz

economicist · Aug 6, 2015 5 0 0

Tried again... no hope, apparently.

So, about 7 weeks later I've decided to give this another shot. Apparently there is no hope for rooting this particular phone in my case. I've tried on a Windows PC this time. I went through the trouble of installing Eclipse and the ADT SDK. Still nothing. debug.txt is still full of "no such file or directory" and "not found" errors. I swear I've read this thread from top to bottom and can't find any answers.

I've also tried the GhettoRoot.bat method posted in #27. That doesn't even acknowledge my device's existence.

Any more ideas? Or is this just the end of my relationships with Samsung and Verizon? I've grown weary of their user-hostile philosophies.
Here is the output of GhettoRoot v0.3.2

Code:

* Cleaned! 
push: C:\Users\blb6667\Downloads\ghettoroot-v0.3.2\scripts\\..\files/UPDATE-SuperSU.zip -> /data/local/tmp/ghetto/UPDATE-SuperSU.zip
push: C:\Users\blb6667\Downloads\ghettoroot-v0.3.2\scripts\\..\files/root.sh -> /data/local/tmp/ghetto/root.sh
push: C:\Users\blb6667\Downloads\ghettoroot-v0.3.2\scripts\\..\files/ghettoroot -> /data/local/tmp/ghetto/ghettoroot
push: C:\Users\blb6667\Downloads\ghettoroot-v0.3.2\scripts\\..\files/busybox -> /data/local/tmp/ghetto/busybox
4 files pushed. 0 files skipped.
3627 KB/s (2429248 bytes in 0.654s)

*** Necessary files pushed and chmod'd.
    Give it a brief moment or your device will be overwhelmed.
 
 * Preparation files transferred! 

************************************************
native ghettoroot, aka cube-towel, aka towelroot
running with pid 9342
Kernel version: Linux version 3.0.31-1496113 ([email protected]) (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: 0xc6b4c000 is a good number
[DEBUG] get_root:428: thread ID: 9349
[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: 0xc6b4fd5c 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] get_root:428: thread ID: 9351
[DEBUG] search_goodnum:1095: Writing to HACKS_fdm...
[DEBUG] get_root:476: Writing new addr_limit to thread...
[DEBUG] write_pipe:325: dest:c68e0008 src:0001300c count:4
[DEBUG] get_root:486: cpid3 resumed
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:4133ba44 src:c68e0000 count:16
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:492: ti.task=e4e72200 .flags=00000200 .preempt_count=1 .addr_limit=ffffffff
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:4133b644 src:e4e72200 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 c68e0000 00000002 00400040 00000000 00000000 00000001 00000001 00000082 00000082 00000082 00000000 c065fae0 00000000 0000006e 0253c825 00000001 cd8dc880 00000000 c316b5a0 cd8dc88c 00000001 e1607756 000002ea 00024ff6 00000000 8bfb1049 0000114c 00024ff6 00000000 00000000 00000000 00000000 00000000 00559199 00000000 0000000e 00000000 005a027a 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0002889a 00000000 0002889a 00000000 00000000 00000000 00000000 00000000 00006b6c 00000000 0000109a 00000000 00000000 00000000 00000002 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000b 00000000 00000000 00000000 00000000 00000000 0000000b 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 c316b570 00000000 00000000 e4e72368 e4e72368 00000000 000000c8 00000001 00000000 00000000 c316b610 00000000 00000000 00000000 00000000 00000001 00000000 00000000 e4e723a4 e4e723a4 00000000 0000000d 00000000 0059c479 00000000 e1607756 000002ea 00000000 00000000 c0acfb40 e4e70a50 0000008c e4e723dc e4e723dc e4e723e4 e4e723e4 ea6f1a00 ea6f1a00 00000001 00000001 00000000 00000001 00000000 00000000 00000000 ffffffff 00000000 00000000 00800000 00000000 00002487 0000247e e4e70880 e4e70880 e4e72434 e4e72434 e4e7243c e4e7243c e3d3c840 e4e72448 e4e72448 e4e72450 e4e72450 00000000 ea34c708 ea34c700 e4e70ae4 e7ae3c4c e7ae3c40 e4e70af0 e7ae3c50 e7ae3c40 e3d3cabc e4e7643c 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001 0000000b 00000c87 30e8eb99 00000c87 30e8eb99 00000001 00000000 00000000 00000000 00000000 00000000 00000000 e4e724e0 
[INFO] get_root:512: Supposedly found credential at taskbuf[184]: e5074880
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:4133b5e8 src:e5074880 count:92
[DEBUG] read_pipe:316: function exit
[DEBUG] read_pipe:299: function start
[DEBUG] read_pipe:303: dest:4133b5d0 src:c50e8b20 count:24
[DEBUG] read_pipe:316: function exit
[DEBUG] get_root:535: YOU ARE A SCARY DEVICE
[DEBUG] write_pipe:325: dest:c50e8b20 src:4133b5d0 count:24
[DEBUG] write_pipe:325: dest:e5074880 src:4133b5e8 count:92
[DEBUG] write_pipe:325: dest:e4e72424 src:00013010 count:4
[DEBUG] postroot:394: Going to execute custom command.
[INFO] postroot:404: chmod 0755 ./root.sh >/dev/null 2>&1 succeeded
[INFO] run_custom_command:382: Going to execute: ./root.sh '--root' '--deknox' '--deota' '--desurveillance'
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: not 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/supersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[73]: /tmp/supersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[74]: /tmp/supersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[75]: /tmp/supersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[76]: /tmp/supersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[77]: /tmp/supersu/arm/chattr.pie: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[78]: /tmp/supersu/arm/chattr: not found
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[79]: /tmp/supersu/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 u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/bin/.ext/.su with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/xbin/su with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/xbin/su with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/xbin/sugote with u:object_r:zygote_exec:s0:  No such file or directory
chcon:  Could not label /system/xbin/sugote with u:object_r:zygote_exec:s0:  No such file or directory
chcon:  Could not label /system/xbin/daemonsu with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/xbin/daemonsu with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/etc/install-recovery.sh with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/etc/install-recovery.sh with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/etc/init.d/99SuperSUDaemon with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/etc/init.d/99SuperSUDaemon with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/app/Superuser.apk with u:object_r:system_file:s0:  No such file or directory
chcon:  Could not label /system/app/Superuser.apk with u:object_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
Removing Knox...
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: find: not found
./root.sh[399]: find: not found
./root.sh[399]: find: not found
./root.sh[399]: find: not found
./root.sh[399]: find: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
./root.sh[399]: dirname: not found
./root.sh[399]: basename: not found
Removing OTA stuff...
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
./root.sh[438]: dirname: not found
./root.sh[438]: basename: not found
Remove some surveillance...
./root.sh[510]: dirname: not found
./root.sh[510]: basename: not found
./root.sh[510]: find: not found
Completion summary:
  Successful tasks: Install SuperSU, Deknox, De-OTA, Remove some surveillance
[INFO] postroot:407: 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...

GhettoRoot.bat output:

Code:

Welcome to GhettoRoot for the Samsung Galaxy Note 2 - 4.4.2 ND7
Please confirm you have turned on USB debugging and authorized your device.

- Press any key to continue -

Press any key to continue . . .
The rooting process is about to begin. Please do not interrupt the process once
it has started.

Removing old root files.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found

Pushing necessary files to your phone.
error: device not found
error: device not found

Starting root exploit.
error: device not found
error: device not found

Your phone should now be rooted. Press any key to exit.
Press any key to continue . . .

RBEmerson · Sep 19, 2015 at 11:43 PM

If the device isn't recognized either the drivers on the PC are missing or in some way not what should be there. Or the phone isn't in one of the file sharing modes. Did you create the Developer options and enable USB Debugging? (tap Build number in about phone until it says you're a developer.)

The easiest way to confirm that the PC and phone are ready to run GhettoRoot is to use adb.exe.

Code:

o Open Windows Explorer and go to the folder created by unzipping GhettoRoot
o Look in the GhettoRoot folder for adb.exe
o <SHIFT><RIGHT-CLICK> in a blank space in the WE window showing adb.exe and chose Open command window here
o Make sure your phone is connected to the PC; look at the notice line (top of the screen) for the USB symbol
o Look for Connected as a media device in the list of notices when you pull down the top of the screen. You may need to unplug and plug in the phone a couple of times. Try rebooting it. If you see the Verizon "cd" show up shortly after plugging in the phone, it's reasonable to expect to see the rest of the phone data become available after a minute or two. If you see nothing, try another USB cable, another USB port, and update the USB drives on the PC. 
o If you see your phone in Windows Explorer, enter [code]adb devices

o You should see

Code:

G:\Samsung\Note II\GhettoRoot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
2b179a09        unauthorized
G:\Samsung\Note II\GhettoRoot>

Don't worry about "unauthorized".
o If you've gotten this far, GhettoRoot has a good chance of running.
o Close the cmd window
o Use <CTRL><ALT><DEL> to start Task Manager.
o Select processes and terminate adb.exe -close Task Manager
o Follow the GhettoRoot instructions - Use the trick shown above to create a new command window to execute GhettoRoot.bat
[/code]
There is more than one GhettoRoot available. Use the one created by NetworkPro and available here. This is the only version of GhettoRoot that worked for me. YMMV

economicist · Aug 6, 2015 5 0 0

RBEmerson said:
If the device isn't recognized either the drivers on the PC are missing or in some way not what should be there. Or the phone isn't in one of the file sharing modes. Did you create the Developer options and enable USB Debugging? (tap Build number in about phone until it says you're a developer.)

The easiest way to confirm that the PC and phone are ready to run GhettoRoot is to use adb.exe.

I did enable the USB debugging, and did wait until the phone was in "media" mode before proceeding. When asked by my phone I did allow USB debugging access. If the drivers are missing on the PC I'd be very surprised. I installed both the official Samsung USB drivers and the Koush Universal ADB drivers. I'm at a loss, honestly

RBEmerson said:
There is more than one GhettoRoot available. Use the one created by NetworkPro and available here. This is the only version of GhettoRoot that worked for me. YMMV

If you mean the one posted by NetworkPro in Post #27 here, I tried that as well. That's the short "GhettoRoot.bat" output I posted. I also tried the earlier versions of GhettoRoot posted in the OP but with no luck there either. I'll try again to get their output and post those later.

Thanks for such a prompt reply, RBEmerson. But it looks like my phone is some kind of exception to the rule here. Even with a factory reset before these recent attempts, these same errors continue to hound me.

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

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member