yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Aha! Maybe it's just that the scripts aren't all +x? In the ghettoroot folder, try running: chmod +x scripts/*

If that command gives an error, do: chmod 0755 scripts/*

Then, try running ./INSTALL.sh again. Let me know if that works and you can ignore the rest of this post if it does.

If it still fails, it might be a difference in how OS X's bash works compared to Linux. You can try seeing if it works manually.

In a terminal, cd to ghettoroot (the folder where ghettoroot was extracted), and then...

Try the mini-scripts directly:

scripts/prepare.sh

scripts/root.sh

If that doesn't work, try all the commands directly:

In a terminal, cd to ghettoroot (where ghettoroot is extracted folder)

run these commands (but the # ones are just comments, so don't need to run those)

GHETTO=/data/local/tmp/ghetto
adb shell mkdir -p $GHETTO/
adb push files $GHETTO/
adb shell chmod 0755 $GHETTO/ghettoroot
# ghettoroot chmods busybox but just in case you could also do...
adb shell chmod 0755 $GHETTO/busybox
adb shell $GHETTO/ghettoroot
# when done, to clean up...
adb shell rm -rf $GHETTO

Pretty simple, for how big the main script is...

Please let me know what, if anything, works, trying the topmost methods first. I've edited this post a few times so hopefully you haven't started yet, but try the methods from top to bottom. You don't need to try them all once you find one that works.

If running those commands manually produces more informative errors (or, on the other hand, just works), great. I don't have a Mac to test with, unless I used one at work (no thanks), so maybe someone more familiar with scripting for OS X could find out why it's not working in less time, and with less frustration than I'd be feeling.

I suppose I could also add a super simple script, with no error-checking, that just does those things -- hard for that to fail -- and it could be the ghetto Mac script. That's assuming it works like this.

I appreciate your trying this out in advance.
[Verizon Samsung Galaxy Note II] Death.DeaLer:
You can't run a custom rom but...

you can just about any tweak you want

Start with xposed framework...wanam exposed..device controller.. are what I have found so far. Just getting into this stuff myself
[Verizon Samsung Galaxy Note II] locolbd:
Okay so I the device could not be detected on my windows 8.1 laptop so i switched over to my linux box and still no join.

The prompt start adb, finds a device but cannot communicate with the device. It show me the serial and says offline.

Any further final thoughts for me on this one. Anybody:(

Thanks a milli in advanced
[Verizon Samsung Galaxy Note II] lacoursiere18:
When adb stats "offline" there should be a prompt that pops up on the phone that will ask you to grant permission to the computer.. Also make sure usb debugging is on..
[Verizon Samsung Galaxy Note II] Mzratm:
Okay thanks, I'm trying to get teathering to work but no luck. What are the Verizon and Samsung bloat apps to remove
[Verizon Samsung Galaxy Note II] lacoursiere18:
Tethering is pretty easy to do.. I know some xposed modules work.. But to hard code it in, it is an adjustment in services.jar..
[Verizon Samsung Galaxy Note II] doctor-cool:
authorization

On the second phone I rooted I waited for that prompt and it never came that's why I decided to do a factory reset/ wipe to the phone. For some reason it wouldn't check for authorization until I did the factory reset/ wipe..
[Verizon Samsung Galaxy Note II] makbomb:
Can't wait to get to work using your guidance tonight. Very excited, and even more grateful for your help!
[Verizon Samsung Galaxy Note II] Death.DeaLer:
For wifi hotspot tethering install foxfi from the playstore. MODERATOR EDIT - If you want to use a paid app for anything, pay for it, don't be a cheapskate. Follow prompt and your good to go.
[Verizon Samsung Galaxy Note II] Matttrix:
Well maybe im the odd ball but Ive encountered some bugs. I did the original ghettoroot and things were fine.. then i notice some minor issues like apps force closing (which doesnt happen much) then browsing started fail. Play store started getting errors as well. So I Verizon restored my phone and everything was perfectly fine with nothing on the phone but the stock 4.4.2 I ran everything and no problems. I then deleted and reinstalled my java and Android adk set and redid everything on my windows 8.1 x64. I proceeded with the newest ghettoroot 0.2.2. with no problems. I ran some tests and sure enough im getting errors. So I just wonder if anyone else is.
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Prior to my bootloader getting locked, so prior to ghettoroot, I had a lot of problems with forced closes and rebooting, even freezing... I could not get ND7 stable without using AGNi kernel and eventually I found it wasn't stable even with that. My phone was crashing so often that I did everything I could just to get it stable, and in the process I ended up accidentally locking my bootloader: hence working on this root. Actually I went a day and a half with a bricked phone. Took an all-nighter to finally get it to even work. (I had also screwed up my EFS but I had an old backup that I just needed to convert to ODIN format.)

I did notice a few issues after rooting with ghettoroot but only after installing Xposed and some of my typical modules. I removed Xposed and have been stable ever since (for nearly a week now).

I actually just did a fresh ODIN to stock yesterday, including PIT, and factory reset. Like I said above, things were stable, but I didn't want to chance any future issues as a result of running ghettoroot dozens of times for testing, and not always waiting for apps to settle first (which can lead to corruption) because I was impatient.

After ODIN and reset and running ghettoroot again, I did put Xposed back on and have been installing modules in bits and pieces so I can see what has caused the problems.

So far so good. No problems all day, with a limited number of Xposed modules installed: Wanam Xposed, Samsung Multiple Widgets Kitkat, Physical Button Music Control.

As for the issues you are experiencing, there are really only two things that might be causing them: the disabling of knox, or the disabling of various OTA packages.

This won't help you unless you reflashed stock, but executing the install script with --no-disable-knox --no-disable-ota does nothing but install SuperSU, e.g. for Windows

INSTALL.cmd --no-disable-knox --no-disable-ota

or Linux/OS X:

./INSTALL.sh --no-disable-knox --no-disable-ota

OR if you don't want to reflash (why would anyone WANT to?), you can run some commands as root on your phone to re-enable all the packages that ghettoroot disabled, since other than having programs actively running on your phone and writing to disk while rooting (which can cause corruption when the phone reboots after rooting), I cannot think of another explanation for your trouble that involves ghettoroot.

To re-enable Knox and all the other disabled packages, enter these commands in a terminal on your phone, or in adb shell (# are comments and can be excluded):

su # become root
pm enable com.sec.knox.seandroid # re-enable knox
pm enable com.policydm # re-enable Policy Updater
pm enable com.LocalFota # other ota
pm enable com.sec.android.fwupgrade # other ota
pm enable com.samsung.sdm # other ota
[Verizon Samsung Galaxy Note II] Mzratm:
Any other ways of doing teathering. The Foxfi works but how do you do the service . Jar thing
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
What tests did you run, by the way? I could try running them, too. Maybe I just haven't noticed problems yet.
[Verizon Samsung Galaxy Note II] makbomb:
Good Morning!

Please take a look at the screenshot. adb sees the phone, then as soon as I run the command, it doesn't.

Thanks :)
[Verizon Samsung Galaxy Note II] lacoursiere18:
Looks to me like you need to update adb.. Maybe the OP can post the version he uses..
[Verizon Samsung Galaxy Note II] T1mm3r1992:
[Solution] Problem Connecting to ADB

I have had some issues getting ADB to connect to my phone and displaying the Authorization request on my phone. I thought I should share the steps I took to solve this problem. I started out by unplugging my phone from the computer. I had to download the following two things

[cant post links]google ADB-1.0.31.zip there is a hostr link third one down thats what I used would be nice if someone could repost with links, OP?

and

[cant post links]google USBDeview v2.36 go to the nirsoft link 4th one down

I then took adb.exe, adbwinapi.dll and adbwinusbapi.dll from ADB-1.0.31 and placed them in the tools folder of ghettorootv0.2.2

I also used USBDeview to remove any samsung or android related drivers, not only disconnecting or deactivating them but completely uninstalling them.

I also removed any samsung or android related drivers from uninstall a program in control panel.

Following all these steps i finally managed to get a Authorization request from ADB.

I also did a full restore before I started but I do not believe that had any bearing on the results.

I hope this helps someone. Thank you to OP for ghettoroot.

Why is this not a sticky yet???
[Verizon Samsung Galaxy Note II] Stryke_the_Orc:
Warez discussion will not be tolerated to any extent.
[Verizon Samsung Galaxy Note II] T1mm3r1992:
Hope youre not talking about me, because none of what I posted is Warez
[Verizon Samsung Galaxy Note II] makbomb:
So through searching the web for the past 2 hours it appears that my PATH is incorrect.

For the life of me I cannot get a relatively simple set of directions with which to repair this.

I would be more than happy to post screenshots of Terminal for any kind soul who would help me out :)

Thanks everyone.
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
No, makbomb is on a Mac and I don't have a Mac so I don't use or have a compatible binary. From the looks of it, the ADB binary in that handy package linked earlier may be too far old (2012) to work with our 4.4.2 phones. That would certainly match up with the error message you're getting, makbomb, but it's not unusual for development tools to have misleading error messages, so we'll see. As for the PATH variable, that is mainly a Windows issue; I doubt that is the problem you're having.

I'm sorry this has been so much trouble for you, makbomb. I get the feeling when we sort it out, it will have been something embarrassingly simple (embarrassing for me, for not realizing it sooner).

If you'd like to try this first (and haven't already), you can try running the commands directly as shown in my previous post, just to see if that has any effect, but after all the time you've put into trying to get this to work, installing the full Android SDK seems like a lot less of an inconvenience than it once did. When you're ready, let's remove your existing, outdated adb and fastboot files, since they aren't doing you any good anyway:

adb kill-server # ok for this to fail
sudo rm /usr/bin/adb
sudo rm /usr/bin/fastboot

If you ended up following some advice that I edited out shortly after posting, make sure you don't have the adb and/or fastboot files from that Androidv4 package copied into your ghettoroot folder. In fact, it would be safest to just extract ghettoroot again, and then run the chmod again once in the folder in Terminal:

chmod +x INSTALL.sh scripts/*

Now that your ghettoroot folder is freshly-prepared and the obsolete adb and fastboot files are gone (so they can't conflict with anything in the future), here is a link that looks pretty comprehensive for installing the SDK: Installing the Android SDK for Windows, Mac and Linux: A tutorial

Please try that link and see if it works for you. Once installed, relaunch a Terminal window and see if you can list your device with 'adb devices'; also see if you can get a shell with 'adb shell' (if you can, type 'exit' to leave it). Those things being true, you should definitely be ready to root, so anything standing in your way is likely a script issue, which means you should try the advice in my previous post again, now that you've got a working adb installed. :)
[Verizon Samsung Galaxy Note II] mikespe:
Well after about an hour I got it to see my device & the script ran but it said it couldn't push the files over to my phone & my phone never rebooted. It couldn't chmod the ghettoroot folder or busybox....which I am assuming because it didn't push them over....any suggestions? Thanks!!!
[Verizon Samsung Galaxy Note II] camkie:
Did you try unticking usb debugging ? or then turn off developer mode then back again i had same issue on a friends phone it worked for me..
[Verizon Samsung Galaxy Note II] chartli:
It worked great for me on a new replacement phone. Rooted for 24 hrs so far with no problems. Thanks. Glad someone finally figured this one out. I had given up hope.
[Verizon Samsung Galaxy Note II] lifeofanomad:
Finally after many hours of messing with cords and drivers, I figured it out. I uninstalled every driver and restarted my PC. I then downloaded Android SDK, installed and then moved to my phone. I reset my phone to factory and then plugged into the PC. When the drivers didn't install, using the device manager, I pointed to the SDK drivers and then my phone was found. Picked up my phone, accepted the RSA pop up request and the rest was cake. Thanks everyone!
[Verizon Samsung Galaxy Note II] locolbd:
After not being able to root my phone because ADB would detect my device but claim it was offline. Even if I revoked usb debugging authorization i would not get the pop.

After seeing this post, decided to give it once last try before I called it quits and voila with some techniques for other posters I am not rooted.

I factory reset my phone, completed the following steps below, but my device was still not be rooted. So i did the following final steps:

1. Opened device manager and saw that the SCHi605 driver was not being installed

2. Downloaded and installed the driver the samsung provides for the Note 2

3. revoked usb debug... auth...

4. ran the following command: adb kill-server

5. Switched from MTP to PTP

6. ran the following command: adb devices

7. my phone showed up as offline, however i got the adb pop up to authorize usb debugging from my computer

8. the rest is history.

THANK YOU ALL FOR YOU INPUT AND HARD WORK.
[Verizon Samsung Galaxy Note II] makbomb:
Note 2 Successfully Rooted on Mac OSX

Happy Sunday.

Thanks to your taking the time to write such perfect directions, I am now successfully rooted.

I followed everything in order. Worked like a charm on the first try. Thank you ever so much!!
[Verizon Samsung Galaxy Note II] mikespe:
I tried again this morning and again I can see my phone but it says it can't push the files over. Here is the message below. What would cause the files not to be pushed to the phone?
[Verizon Samsung Galaxy Note II] oinop:
I have the same problem. Could someone help us with this?
[Verizon Samsung Galaxy Note II] doctor-cool:
Recovery data wipe/factory reset and wipe cache partition

Try going into recovery and doing a data wipe/factory reset and wipe cache partition.

Reboot and then do the GhettoRoot thing.

That is what worked for me.
[Verizon Samsung Galaxy Note II] OdinsEyepatch:
Great work, but still having a few issues

First, thank you for working on this. I regrettably took the OTA update and have been vigilantly trying to correct that mistake for about a week now. I've been following this thread since its inception, starting with the original Ghettoroot and each revision after. It has come a long way since then, but I'm still having a few issues. Up until the most recent version, ADB connected fine, but Ghettoroot could not find my device. It appears to be finding my device fine now, but encounters an error somewhere toward the midde. My phone never reboots, and the root access is never applied. I'll do my best to relay the details of the error in the hope that perhaps the next version of Ghettoroot can patch it, and myself and the few others still encountering problems may join the ranks of the rooted as well. I only just registered an account on the forums over this issue, so I could not post this in the Development thread. I appreciate any help. The error messages I receive are the following;

*** Could not push files.

*** Could not send preparation files!

/system/bin/sh: ./ghettoroot: not found

*** ghettoroot execution completed! Investigate the results...

Ive installed all necessary drivers, and am having no problem turning on USB debugging, or authorizing the computer. Thanks again for all the help. It appears that you're the only ones working on this matter. I've tried all other recommended routes of rooting, and can confirm that none of them work on the Note 2 after the OTA update.
[Verizon Samsung Galaxy Note II] doctor-cool:
"HOW TO" video

Try using different USB ports and removing your phones drivers from your computers device manager. reboot and reinstall drivers.

I bet most of the problem people are having are due to the computer installing the wrong drivers .

Windows installs different drivers depending on what you are using the phone as. Also you may need to turn off Windows defender or your anti-virus program in order to install GhettoRoot. It may work unless you have defective hardware.

Factory restore/wipe your phone then plug it into a different usb port.

Someone make a "HOW TO" video
[Verizon Samsung Galaxy Note II] OdinsEyepatch:
I've factory reset, wiped data and partition cache, toggled USB debugging, revoked debugging authorization, toggled DM settings through ##366633#, tried all usb ports, deleted both the USB drivers and ADB drivers for my phone, rebooted, and reinstalled both the USB drivers and ADB drivers under device manager, all multiple times. I don't believe it to be a driver issue any longer, because Ghettoroot is now finding and communicating with my phone, which it wasn't before the new release. Also, the error messages I'm receiving lead me to believe that it must be something else. I'm not versed enough in command prompt to determine if ADB is running properly for certain, but the fact that Ghettoroot successfully utilizes ADB leads me to believe that it isn't the problem. I'm curious to see what the OP makes of all of this.
[Verizon Samsung Galaxy Note II] doctor-cool:
OdinsEyepatch
[Verizon Samsung Galaxy Note II] GingerSnapps:
No go

I have done everything including factory reset, wipe cache, turning off firewalls and defender. This is what I've done and the error I'm still getting:

ADB is working:

environmental variables:

ADB_TRACE - Print debug information. A comma separated list

of the following values

1 or all, adb, sockets, packets, rwx, usb, sync

, sysdeps, transport, jdwp

ANDROID_SERIAL - The serial number to connect to. -s takes prior

ity over this if given.

ANDROID_LOG_TAGS - When used with the logcat option, only these de

bug tags are printed.

C:\Users\mine>adb devices

List of devices attached

42f7841a8bb2afe9 unauthorized

C:\Users\mine>adb devices

List of devices attached

42f7841a8bb2afe9 device

Location in Path:

C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Rar$EXa0.657\adt-bundle-windows-x86_64-20140702\sdk\platform-tools

Error:

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.

'adb' is not recognized as an internal or external command,

operable program or batch file.

'adb' is not recognized as an internal or external command,

operable program or batch file.

Pushing necessary files to your phone.

'adb' is not recognized as an internal or external command,

operable program or batch file.

'adb' is not recognized as an internal or external command,

operable program or batch file.

Starting root exploit.

'adb' is not recognized as an internal or external command,

operable program or batch file.

'adb' is not recognized as an internal or external command,

operable program or batch file.

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

Press any key to continue . . .

This girl is in need of some help.
[Verizon Samsung Galaxy Note II] Matttrix:
Good news I solved the app crashing and internet problems. It was "busybox" being missing, for some reason it didn't install on the root install, once I installed that and did things everything is working great.
[Verizon Samsung Galaxy Note II] thunderblaster88:
Few questions, I'm still on 4.3 MJ9 and have been waiting for this for awhile now and have update removed so I'll have to unroot and update right? Of course. Now will safestrap work? Because I'd really like to always have a back of at all times "JUST IN CASE"! Also what about downgrading from this, maybe Odin down to mj9? Before I make the leap I have questions and wanna make sure, one more thing, what about tethering? I'm just using the module from xposed with the stock system app hack and works great from my girl or kid on the go, if any and or all questions could be answered I'd be much appreciated.
[Verizon Samsung Galaxy Note II] OdinsEyepatch:
I had 4.3 MJ9 prior to foolishly accepting the OTA update, and honestly, wish I would have asked the same questions before updating. I had no problems flashing new firmware with Odin when I had MJ9, but now, it appears that is no longer possible with the ND7 update. So no flashing back to MJ9 or any other firmware after the update. Rooting after the update by any of the old means is not possible as far as I know, and I've tried nearly everything. Your best bet is to stay with MJ9 for the time being, but should you choose to accept the OTA update (which I cannot recommend with a clear conscience), Ghettoroot appears to be the only option for gaining root access. Many people have had success using this method, however, not all. I'm still not rooted, and I've tried every version of Ghettoroot except the latest revision. Safestrap with the Ghettoroot exploit is still in the works as far as I know, but is not yet fully functional. I'm not sure about tethering, as I've never used it. Perhaps someone more experienced in the matter could answer that for you. For now, the XDA forums are still your best bet for new information, but I might recommend the new thread in Development, as it appears to be more active than this one at the moment. You can find the link to it in the first post on page 1 of this thread.
[Verizon Samsung Galaxy Note II] mendez91:
This happened to me when I ran the INSTALL.cmd as Administrator.

To fix it all I did was double clicked on it without doing all the "Run as Administrator" thing.

After that, everything worked.

Just make sure that you have debugged mode enabled.
[Verizon Samsung Galaxy Note II] mikespe:
Actually I never ran the script as an administrator...only double clicked it. Maybe if I do the opposite it will work lol

thanks!!
[Verizon Samsung Galaxy Note II] doctor-cool:
incrementally

OdinsEyepatch---I'm sure you have tried a different computer with a different usb cable right.

Just for forensics,

How many times have you flashed your phone with different ROM's. Could it be that some data was left on your phone from other ROM's.

I don't know .Just a thought.

When I took the OTA update from Verizon I started on 4.1.1. They gave me the updates incrementally. 4.1.2 then they sent 4.3 then 4.4.2.

Those may not be the exact numbers but they did not try to update the phone in one flash.

I'm thinking that if you may have missed a step in the upgrade and you may not have got the total package.