yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] markvarvel:
Root Problems

OK, I had lots of problems getting root on my ND7 as well.

I finely was able to get it by doing the following.

1. Wipe Cache, Then do data factory wipe 2 times.

2. You may need to try different USB cords or USB port, "Important" remove all Samsung USB drivers and turn off computer.

3. Now, the hardest part is to get a new RSA key between the phone and computer. Without this it will not work.

4. Turn off the phone and plug it into the computer. Turn on computer and wait for it to completely boot up.

5. Install the latest USB drivers and reboot computer.

6. Turn on phone, you should see USB drivers being installed, and it should ask you to Authorize a new RSA key.

Be sure to check the little box to always allow

If you can't get this far without errors, start over and try different USB cords or USB port until you get the RSA key.

7. I am including a modified GhettoRoot folder with everything in it you should need to root the phone. I did not create any of the files or scripts, I only assembled the files need to root my phone.

8. Extract file to your desktop, and run GhettoRoot.bat

I hope this will help.

https://www.dropbox.com/s/ts02qate3wuqyee/GhettoRoot.rar?dl=0
[Verizon Samsung Galaxy Note II] Telemachus:
Worked like a charm.

just an FYI: The RSA certificate request doesn't just "pop up" when you plug the phone in. In my case, it wasn't until I clicked on the ghetoroot.bat file that it requested certificates. I accepted, but root failed the first time. Second time, golden!
[Verizon Samsung Galaxy Note II] pmally:
IT WORKED!

I followed your instructions I completely removed any Samsung drivers then used the universal driver

installerdownload. clockworkmod. com/test/UniversalAdbDriverSetup.msi

skipsoft .net /?wpdmpro=uat-v143

before running the GhettoRoot script I used SkipSoft Android toolkit to confirm that the phone was talking to the computer.

option [ i ] display connected devices

At that point the phone also prompted me for permission.

I wiped it 4x and cleared the cache 4x just in case that might help.

I had to switch USB ports a few times, restart my computer, disable USB debugging then re-enable it finally it prompted me for permission using SkipSoft toolkit.

It had a some errors in the script but it worked perfectly.

It rebooted and I was very happy to see superSU installed

installed busybox from google play and ran root checker.

Root checker verified it as rooted.

Thank you so much for the script I'm pretty sure this is the only working root for the Verizon note 2 :cool::good:
[Verizon Samsung Galaxy Note II] Roozter:
Better late than never!!

THANK YOU, THANK YOU...IT WORKED:D!

I really appreciate the hard work that was put into this - you are geniuses!! :good:

Now on to Safestrap...
[Verizon Samsung Galaxy Note II] ZackFearheart:
I can't seem to get this to work at all, SuperSU isn't installing or installed, I've reset the phone 3 times, cleared cache, changed USB ports... I have to switch between MTP to camera mode to get the key thing to pop-up, I push allow and then it will connect in the installer, it does it's thing and reboots the phone, but no SuperSU. I ran Root checker and it said Root Access is not properly installed on this device.

I followed the directions to a tee... Not sure why it won't work. Device is on 4.4.2...

EDIT: Nevermind! Used the Ghettoroot all-in-one and that worked.
[Verizon Samsung Galaxy Note II] gee1000:
My workaround for getting root

Just for the record, I thought I would post my experience getting rooted. I just upgraded to 4.4.2 from being at 4.3 bootlocked for a long time. Now that my Verizon Note 2 is now only used as my primary Android device, I decided to upgrade to 4.4.2 to get ChromeCast screen mirroring, etc. and, of course, root.

I used a Microsoft Surface Pro 1 with Win 10 and I had the damnedest time trying to get ghettoroot to work. My device would authorize fine, but root just wouldn't work. Followed all the instructions, got everything seemingly good to go, but would still throw errors like YOU ARE A SCARY DEVICE and no root. Really? lol

I ended up finding the GhettoRoot All-in-One/Networking Pro thread here: http://xdaforums.com/showpost.php?p=55210343. Once I downloaded it, I tried many times to get the device to authorize but no dice.

Anyway, here's my workaround that finally got me rooted:

1) Start Command Prompt

2) Run ghettoroot_v3.2 INSTALL script

3) Get your device to authorize

4) Once it does, hit Ctrl-C and terminate the batch job. You should go back to the command prompt.

5) Run GhettoRoot All-in-One. Your device will still be authorized! Everything should work.

I don't know why I had to go all this but I would assume that, once you authorize the device, you lose it when GhettoRoot closes and adb stops. But, if you run it within a command prompt so it doesn't automatically exit, the authorization obviously stays active until you close the command session.

Anyway, if you get stuck like I did, try it and see if it works for you! The All-in-One definitely worked for me.
[Verizon Samsung Galaxy Note II] kilolima:
Thank you! That worked for me. For some reason Ghettoroot kept failing and the all-in-one could not detect the phone. However, I did not Ctr-C Ghettoroot, just left it running.

Note: For reference, this was in a virtual Windows 7 machine via VirtualBox on an Ubuntu host.
[Verizon Samsung Galaxy Note II] Alcamtar:
Success!

Thank you everyone for all the info on this thread! I finally managed to root my Note 2 using the all in one method. I tried many times and ran into a few false starts, which I will try to describe for the benefit of anyone else that runs into them.

I first tried using just the v0.3.2 ghetto root INSTALL script. It saw the device and seemed to run ok and said it was successful, but there was an error message about a missing newline in root.sh, and afterward Root Checker said I did not have root access. I could not find the 0.2.2 to download, but started messing around with adb.

(The reason you have to type "adb devices" in a command window is that "devices" is an argument to adb.exe. If you type "adb /?" in a command window you can see it has a lot of command line options. This cannot be done just by clicking in a window.)

Anyway I ran adb devices, but the INSTALL still didn't work. So I tried again in an Administrative shell, but still no luck. I then downloaded the all-in-one GhettoRoot.zip (see links above) but this could not see my device. I started playing with the adb devices command but it was giving me "List of devices" and nothing in the list. After much rebooting my phone, trying various options, and searching forums, it occurred to me that maybe adb.exe was already running. I checked Task Manager and found it was indeed running, so I used End Process and killed it. That was when everything started working.

I suspect if you run adb and it DOESN'T find anything it stays resident in memory unless you reboot the computer or use task manager to kill it. Maybe I messed it up when I reinstalled drivers or changed options or revoked and reenabled debug access. I don't know, but it wasn't seeing the phone, no matter how many times I ran it. I think it saved the info from when it started and never tried to update it. Killing and restarting it forced a reset. Maybe it sounds like I am belaboring this, but it had me confused and frustrated for a couple of hours, and maybe this will save someone some trouble.

Here are the steps I followed successfully:

1. install the Samsung drivers

2. ensure the phone is booted with debugging enabled, in media mode, etc. You'll know the computer sees the phone if autorun tries to open a window to browse the phone when you plug it in.

3. start a command window as Administrator, and go to the GhettoRoot directory

4. run "adb devices" and verify that your phone serial number is listed. If it is not, the root installer will fail and you first need to make sure adb sees it before proceeding.

5. run GhettoRoot.bat. When I ran it it complained about missing files and such. I ignored these messages and just tested to see if it worked anyway.

6. install Root Checker and SuperSU. Use root checker to verify that you have root access.

Done!

Bottom line is the GhettoRoot.zip all-in-one worked, the ghettoroot-v0.3.2 did not, and typing "adb devices" on the command line has hidden gotchas. I suspect if I had not tried the 0.3.2 and adb first, the all-in-one would have worked on the first try.

Again thanks everyone.
[Verizon Samsung Galaxy Note II] vey9:
I don't see DM mentioned anywhere, so I thought I would. The only way I could get ADB to see the phone was to turn on DM Mode. Following the instructions, I dialed ##366633# and enabled DM Mode. After that, there was no more notification about connecting installer business and ADB would connect. Then I used the method g1000 mentioned to root the phone. SuperSU was not in the app drawer, but it was installed and could be updated after downloading the SuperSU app from the play store.

I don't know what DM is, but I disabled it again after the root.
[Verizon Samsung Galaxy Note II] fallen00sniper:
i keep getting Unfortunately, SysScope has stopped.

didn't even root, this did manage to root, then used post 611 and it did root, but the even after a factory reset (vol+ power and home) i still have this popping up...

any ideas?

my config

./root.sh --root --deknox --deota --desurveillance --debloat --disable-ota --really-remove

only seems to show up after a reboot a few times and then stops, no worries i guess.

My phone has been up for hours, sys scope has stopped continues to show up, any way to disable it?
[Verizon Samsung Galaxy Note II] choder:
Awesome! My Verizon Note 2 is now rooted. I actually had it sitting in a drawer because it was no use to me without root. Now its a great phablet for the kids! I don't know how anyone can handle an unrooted phone!
[Verizon Samsung Galaxy Note II] coderodent:
GhettoRoot 0.3.2 & All-In_one Combo Worked!

I used 0.3.2 to establish connection and then all in one worked fine!
[Verizon Samsung Galaxy Note II] Xereph:
Won't budge

I noticed that in Ghetto 3.2 in THIS directory :

...\ghettoroot-v0.3.2\tools\win\adb

theres a file that is needed BY adb.exe --> the AdbWinUsbApi.dll , which the normal GhettoRoot lacks, thus explaining it's inability to detect phones.

I also noticed that the acb there was newer.

I tried all the above methods , such as running INSTALL first then using ghetto.bat, I tried copying over the newer acb and all its files from 3.2 to GhettoRoot, also tried copying over only the Usb api from 3.2 while leaving the original acb.exe and win api of GhettoRoot intact.

ALL of the above leave me in the same situation: It hangs at Exit wake_actionthread (675). Up to there it's all good.

I'll post an example, skipping to the problem part (lots of text even before this part, also - this is not from my own phone, taken of http://xdaforums.com/note-2-verizon/general/root-note-2-i605-4-4-2-nd7-using-ubuntu-t2897654 where and example of what it looks like is posted):

=================================================

native ghettoroot, aka cube-towel, aka towelroot

running with pid 15545

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 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)

===========================================

Here it hangs indefinitely. Tried toggling Dev.USB and revoking and re-Instating Auth.

Is this normal? waited ages.

EDIT: Also using a Note 2 N7100
[Verizon Samsung Galaxy Note II] Xereph:
I copied the 3.2 ghettoroot file the the other GhettoRoot (all in one they seem to call it) and got the same result as I did after fixing 3.2 so that it would work.

I found that in 3.2 the command screen would at some point during the attempt give me the command for adb instead of doing what it is supposed to do, I looked and found that the Push was being done incorrectly and fixed that - to no avail , as I said above.

So issue is with the ghettoroot file, so likely my Note 2 isn't supported (kernal?), either that or 3.2 has yet another flaw of something that it references incorrectly that all-in-one also does not have thus the same issue. The reason I believe it may be so is that last line. (see below)

Here is my Copy-Paste of what my CMD window looks like and here it hangs perma:

************************************************

native ghettoroot, aka cube-towel, aka towelroot

running with pid 18289

Kernel version: Linux version 3.0.31-3569041 (dpi@SWDD5607) (gc

T Fri Dec 12 20:16:40 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 thr

[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 thr

[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
[Verizon Samsung Galaxy Note II] shallmann:
I had the same thing with syscope, just freeze it with Titanium Backup. I have no idea what it does but I haven't noticed any trouble.
[Verizon Samsung Galaxy Note II] JMSlate32:
This worked for me:

Download GhettoRoot - All-In-One from HERE

Edit GhettoRoot.bat, delete everything and paste the following:

Save

Right click and run as admin.

The problem I kept running into was adb running. I added taskkill to the .bat file and also added "adb devices" so you can see if your phone is being detected. SuperSU did not load but I just downloaded it from the Play store. Good luck.
[Verizon Samsung Galaxy Note II] walkman4321:
I am trying to toot lenovo P70-A with kernal version :Linux version : 3.10.48

But It hangs "search goodnum 907:loop waiting for Other thread ".

Help me why this happen
[Verizon Samsung Galaxy Note II] b00.f0087:
Anyway, here's my workaround that finally got me rooted:

1) Start Command Prompt

2) Run ghettoroot_v3.2 INSTALL script

3) Get your device to authorize

4) Once it does, hit Ctrl-C and terminate the batch job. You should go back to the command prompt.

5) Run GhettoRoot All-in-One. Your device will still be authorized! Everything should work.

I don't know why I had to go all this but I would assume that, once you authorize the device, you lose it when GhettoRoot closes and adb stops. But, if you run it within a command prompt so it doesn't automatically exit, the authorization obviously stays active until you close the command session.

Anyway, if you get stuck like I did, try it and see if it works for you! The All-in-One definitely worked for me.[/QUOTE]

This is what worked for me thank you finally after 2 days of trying i was finally rooted.

After step 4 i ran ghetto all in one with other cmd window open still and it went threw the process and rebooted phone. i had to download SuperSu from playstore. It asked me to update binary and to reboot phone after it was completed.
[Verizon Samsung Galaxy Note II] Mejud:
My Note 4 died the other day (prolly buying a used one soon, I love the removable battery concept) Anyhow, dug out the old reliable rooted Note 2. The thing as at 4.3, and even Pandora wont run unless you're at 5. Unfroze everything, but it still won't take an OTA to 4.4.2...I'm not sure there's any method of upgrading the Android version at this point--I might try factory reset after I get another phone
[Verizon Samsung Galaxy Note II] locolbd:
Hey,

My phone is recognized by the my computer. I am running windows 8.1 update 1. I also looked under Device manager and it is also there. I uninstalled the driver and install Koush universal drivers but still no luck rooting.

I might be mistaken but i dont think i see a download for ghetto root .0.2.2
[Verizon Samsung Galaxy Note II] jollybluehornet:
Hi Guys,

So I toyed with this for almost 2 hours before I finally figured this out. It was not a driver problem but a ADB issue even if it says ADB is available.

I was having trouble getting my phone to prompt for the RSA key accept for my PC

I would hit the revoke authorization but it would never prompt me again.

The final solution was as follows:

Run "ADB devices" from CMD once it was pointed to the ADB folder to verify the device is connected (ADB was not initialized for me without doing this step). Once initialized my phone would prompt me to accept the RSA Key from my computer. That part is very important.

Then double click install.cmd in the ghettoroot folder. (It would still fail the first time)

Close that window and run it again and it would work right away running the script. Now I'm rooted!!!!

Hope this helps you guys.
[Verizon Samsung Galaxy Note II] makbomb:
Unfortunately that doesn't help me, because I'm using a Mac, but thanks :)
[Verizon Samsung Galaxy Note II] jollybluehornet:
I have a mac too I can test with. You should be able to install the android sdk and run the same command from terminal for ADB in the folder it was installed to. Then run the script.
[Verizon Samsung Galaxy Note II] makbomb:
I'm in terminal, pointing to ADB folder.

All I need to know is what exactly to do. Thanks
[Verizon Samsung Galaxy Note II] Mzratm:
Now that we are rooted can we flash new roms?
[Verizon Samsung Galaxy Note II] jollybluehornet:
Type in the command "adb devices"

It should initialize ADB if its not already and show that your phone is connected

If you have never seen the prompt on your phone to accept the RSA Key then it should show now, accept. (Must have USB debugging enabled under "developer options" on your phone.

Once it shows there, run the install.sh file either by double clicking on it or running it from terminal. Essentially the same process as windows. The script should run. If it is unsuccessful the first time close it and run it again, I had to run it twice for it to take.

Let me know how it goes.
[Verizon Samsung Galaxy Note II] makbomb:
When I double click on the INSTALL.sh file, all it does is copy the text into Terminal
[Verizon Samsung Galaxy Note II] jollybluehornet:
Then point to the ghettoroot folder and run it through terminal
[Verizon Samsung Galaxy Note II] makbomb:
I attached a screenshot of Terminal after I attempted to run the INSTALL.sh file after pointing to the GhettoRoot folder.

Maybe I'm not using the right command?
[Verizon Samsung Galaxy Note II] jollybluehornet:
You only need to type

INSTALL.sh
[Verizon Samsung Galaxy Note II] makbomb:
Tried that, first just how you described, no luck.

Then added ./ to the beginning, still no luck.

Check the screenshots for file location and also for Terminal's response to my commands that I tried to run.

Thanks :)
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Sorry all. The upload must have failed last night. What a drag... It's actually uploaded now.

makbomb, try v0.2.2, but note that OS X isn't official supported... Also, the bundled ADB binary is for Windows *only*. You will need to install the Android SDK *or* try out this link, but I can't verify its effectiveness or vouch for the site: http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/

./INSTALL.sh is the correct syntax, yes, though you might need to do a chmod +x on INSTALL.sh first if it says permission denied.

(P.S. It sucks getting the second-class citizen treatment with post edits, etc. :-/ have to wait a bit before making edits)
[Verizon Samsung Galaxy Note II] jollybluehornet:
Looks like ADB is not running.

Check out this link

https://code.google.com/p/adb-fastboot-install/

Do that and try again, see if it helps. Sounds like ADB isnt installed/running.
[Verizon Samsung Galaxy Note II] makbomb:
Thanks, installed ADB via your link.

Now, when I run INSTALL. sh, ADB starts(hallelujah), but the phone is not seen. What's weird about that is that when I run ./ADB devices, the phone shows up properly.
[Verizon Samsung Galaxy Note II] jollybluehornet:
Just to make sure you have USB debugging enabled?

Might want to try revoking USB authorization on your phone and running ADB devices command again to get the rsa key prompt again. Then run the script two times in a row if it fails the first time.

Another thought that may help is to drop the ADB files in the ghetto root folder and try running the script again. Kinda running out of ideas lol.
[Verizon Samsung Galaxy Note II] joeasaurus:
Help

I can't get it to detect my phone. I don't know much about Koush, but i downloaded it anyway. I don't know anything about ADB. When i've rooted in the past it's been through odin. please help me.
[Verizon Samsung Galaxy Note II] makbomb:
USB debugging is enabled.

Tried the revoke thing many times.

I did drop ADB file in the "tools" folder within the GR folder. No dice.

Thanks so much though so far for all the help brother!
[Verizon Samsung Galaxy Note II] Mzratm:
With this root can custom roms be installed
[Verizon Samsung Galaxy Note II] jollybluehornet:
No custom roms until bootloader is unlocked. If you try it will show there is unauthorized software and you will have to restore via Odin to stock 4.4.2
[Verizon Samsung Galaxy Note II] doctor-cool:
Root Verizon Note 2 running stock Android 4.4.2

Not sure what finally made it work. I reinstall the parts several times in different orders, authorized and unauthorized and reauthorized several times. Thanks to ALL who made ROOT possible on the Verizon Note 2 running stock Android 4.4.2 Thanks again. IT WORKS!

Precise instruction would be helpful. I can tell you what I downloaded .

1.adt-bundle-windows-x86_64-20140702

2.UniversalAdbDriverSetup

3.GhettoRoot

-----------------------------------------------------------------------------

EDIT: I rooted a second note 2. I tried for 2 hours without success until I decide to do a factory restore and data and partition wipe. Then another unauthorized and reauthorized then it Worked again.