yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] RBEmerson:
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]
[Verizon Samsung Galaxy Note II] wolfballz:
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...
[Verizon Samsung Galaxy Note II] RBEmerson:
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.
[Verizon Samsung Galaxy Note II] RBEmerson:
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. :)
[Verizon Samsung Galaxy Note II] cory733:
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?
[Verizon Samsung Galaxy Note II] 55rebel:
Awesome!!!

Thanks, that worked!!

Nothing like scaring me half to death with that disclaimer, though :confused:.... lol!

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

Again, THANKS!

Mark
[Verizon Samsung Galaxy Note II] RBEmerson:
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 ----------

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.
[Verizon Samsung Galaxy Note II] 55rebel:
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
[Verizon Samsung Galaxy Note II] RBEmerson:
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.
[Verizon Samsung Galaxy Note II] 55rebel:
I may do just the freezing also then.

Thanks,

Mark
[Verizon Samsung Galaxy Note II] RBEmerson:
Da nada.

At some point I'll probably review what's frozen and uninstall these apps if nobody's complaining about their absence.
[Verizon Samsung Galaxy Note II] wolfballz:
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.
[Verizon Samsung Galaxy Note II] RBEmerson:
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.
[Verizon Samsung Galaxy Note II] wolfballz:
Correct.
[Verizon Samsung Galaxy Note II] RBEmerson:
Once again, great thanks for your help, wolfballz
[Verizon Samsung Galaxy Note II] RBEmerson:
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.

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

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
[Verizon Samsung Galaxy Note II] economicist:
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 :confused:

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.
[Verizon Samsung Galaxy Note II] makbomb:
Thank you so much for your hard work.

Will I have to install supersu myself after running the zip?

Also, is this considered a temporary root?

Again, many thanks.
[Verizon Samsung Galaxy Note II] TCPDump:
No, this will install SuperSU as part of the root. The root is not temporary. It will persist through reboot, etc. When an OTA comes out it may or may not lose root. Traditionally speaking, it probably will.
[Verizon Samsung Galaxy Note II] lifeofanomad:
I'm in the same boat with locolbd. Tried everything and no go.... Thanks for any help!
[Verizon Samsung Galaxy Note II] shatteringlass:
Thank you so much! This helped rooting my international Note II (GT-N7100) while keeping KNOX 0x0!
[Verizon Samsung Galaxy Note II] makbomb:
I'm on a PC without admin privileges. The PC sees the phone as a mtp device but when running ghetto root, I get "device not found". Please help if possible?

I have a Mac at home :(
[Verizon Samsung Galaxy Note II] TCPDump:
You will have to have the device drivers for your phone, or at minimum the ADB Universal Drivers by Koush. Also, make sure that you hit the "MTP" notification and select "Internet Connection > Modem", or almost anything but MTP. :P
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
NetworkingPro, do you know if it is OK (and legal, etc.) if we were to bundle those drivers? Would we just have to ask Koush and, if it were OK with them, provide a link/credits entry? If you think this could happen and wouldn't mind helping set that into motion I would :victory:
[Verizon Samsung Galaxy Note II] TCPDump:
I don't think he cares, but I will ask.
[Verizon Samsung Galaxy Note II] geneb:
I only have two options when I connect to my pc, MTP and PTP. How do I get the other two?:confused:
[Verizon Samsung Galaxy Note II] mendez91:
After following the steps in the READ ME file. I was able to successfully root the phone!

THANKS 25yvdgpo06 and NetworkingPro

I had major issues when I downgraded to 4.3 but now being able to have root on 4.4.2 is EPIC.

Word of advice to those who might get an error that the "files" folder is not found.

Just make sure NOT to right click and run as Administrator the "INSTALL.cmd"

If you run it as admin, you will get that error.

That got fixed by just double clicking on the INSTALL.cmd without doing anything else.
[Verizon Samsung Galaxy Note II] Droc1983:
Anybody having any luck with safestrap?
[Verizon Samsung Galaxy Note II] mia2973:
thank you so much 25yvdgpo06 !!! i thought i was a goner without root on KK. i would get stuck when it would say communicated with device, and i almost cried because how close root was, but when i moved adb items from tools folder to were the INSTALL.cmd and worked like a charm!! many thanks again. :D
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Aha, mia... Interesting information. I have the script set ADB to the path (temporarily), but maybe it doesn't work with spaces? I'm going to take a look.
[Verizon Samsung Galaxy Note II] mia2973:
yea i would try to just click install.cmd and it would stop at "Can a device be found?" and just stays there. if i try to run as admin, it would show that "Can we communicate with device?: NO!" and would do that over and over. i tried with my adb folder and checked and did adb install an apk and worked so just moved adb files to the root of folder and worked.
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Ah, thank you for reporting this. I was able to verify this problem and have fixed it for the next upload (soon).

No need to run any of this as an admin from my experience, except driver installation, but I added a workaround for the admin issue. As for the admin problem, it might be a "bug" with the way Windows launches batch files as Administrator... one which I've grown accustomed to. It does not maintain the working directory (changes it to %SYSTEMROOT%\system32 if I recall correctly) which breaks most batch scripts that expect to be executing in their own directory. It looks like they work OK out of the box in 8.1 if they have the .cmd extension, but I may have fixed it myself already and forgot.

Way off-topic, but if you want to actually fix that Windows problem so other scripts will also work OK running as admin, you can navigate in regedit to HKEY_CLASSES_ROOT\batfile\shell\runas\command (and later cmdfile, too) and change the (Default) value...

from: %SystemRoot%\System32\cmd.exe /C "%1" %*
to: %SystemRoot%\System32\cmd.exe /s /c pushd "%w" && "%1" %* && popd
[Verizon Samsung Galaxy Note II] mia2973:
Glad I could help. and thank you for the tip to fix my windows, always had a problem running as admin, never occurred to me that i only needed to change something so simple. definitely going to download next upload and keep in files in case i ever need to factory reset or flash stock again. was so hard not having root for a couple months haha. :good:
[Verizon Samsung Galaxy Note II] locolbd:
Thanks for your help, I have but still no Joy
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
What version of Windows do you have, and is it 32-bit or 64-bit? Try Koush's drivers now linked in the opening post. They work for me...

Is your device even detected in Device Manager at all?

v0.2.2 (just uploaded) has some better troubleshooting steps inside, so you might want to try all that it recommends when you run it.
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
No, no luck with Safestrap, here. It might be because we can't even flash Recovery with this new locked bootloader. Wish I knew more about how people find the exploits (and about the exploits that worked previously).
[Verizon Samsung Galaxy Note II] makbomb:
Hi again, so I've got the phone recognized in terminal on my Mac. I also have adb installed, and I pointed Terminal to the adb folder.

I also moved the GhettoRoot folder with the GR .bat file there as well. Can I make this happen? Thanks in advance.
[Verizon Samsung Galaxy Note II] RBEmerson:
[...]

Da nada.

To start with

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

This says your phone and PC aren't talking to each other at all. Why?

It could be bad or missing drivers, a bad cable, a bad port, the phone doesn't have USB debugging enabled and if it's enabled the phone is not in media mode. I'm sure there are more possibilities but these are some easy explanations. Until you can do "adb devices" and get a result very close to the one I posted earlier, anything else is a waste of time. The PC and phone must be on talking terms. If they're not, nothing else in GhettoRoot, odin, adb, etc. is going to work. Ever.

As in life in general, and certainly in troubleshooting, "assume is the mother of all feck-ups". So assume nothing about the phone or PC unless the proof is clear and in front of you.
[Verizon Samsung Galaxy Note II] economicist:
That's what's confusing me. The other versions of ghettoroot at least acknowledged the device, so doesn't that mean I *do* have all the drivers installed and it's something wrong with my phone? Does the version posted by NetworkingPro require some different set of drivers?
[Verizon Samsung Galaxy Note II] RBEmerson:
First, did you do the "adb devices" as I suggested? Do that and report what happens. Add to that "adb version" to see which version of adb you're using. It's possible one version of adb works and another doesn't. I think, however, that's extremely unlikely.

Second, before running any version of adb or any version of GhettoRoot, use Task Manager to be certain that the adb daemon isn't running. If adb.exe shows up in the processes list, kill it. Then try either adb devices or ghettoroot.bat. Once you run adb, again terminate it after you're done.
[Verizon Samsung Galaxy Note II] wolfballz:
I've heard of some people needing to run ghettoroot as administrator on a PC in order for it to work also. Have you tried that?
[Verizon Samsung Galaxy Note II] RBEmerson:
Before messing with ghettoroot.bat,

establish a connection between the PC and Note 2

! If there's no connection between the phone and PC, anything else is a waste of time.

Once again, follow this example:

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>

---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------

FWIW, rooting my phone with Note 2 went ahead without running anything as administrator. YMMV of course
[Verizon Samsung Galaxy Note II] 1nv1n:
Has anyone lost their "USB Mass Storage" options after applying the GhettoRoot? I cannot connect my phone to my computer (yes, the drivers are installed); but it does not show up & on my phone I cannot find the USB Mass Storage options. There's no USB Debugging icon once the phone's connected either.. I've tried with a couple of cables & USB ports.
[Verizon Samsung Galaxy Note II] RBEmerson:
If you're just trying to connect the phone, turn off USB debugging. Clear the authorizations. Connect the phone and see what happens.

Try using the Motorola Device Manager program on your PC to install drivers.
[Verizon Samsung Galaxy Note II] neemo6:
Will this update my phone to 4.4.2 and root it or just root it if i update to 4.4.2 ? Im still on jellybean and need to update.
[Verizon Samsung Galaxy Note II] RBEmerson:
You need to have 4.4.2 in place first. It will not update you to 4.4.2.
[Verizon Samsung Galaxy Note II] pobox1067:
I don't know what "ensure...device is authorized" means. I have Googled this and can't find any meaningful info.

---------- Post added at 11:57 PM ---------- Previous post was at 11:52 PM ----------

I don't know what "ensure...device is authorized" means. I have Googled this and can't find any meaningful info.
[Verizon Samsung Galaxy Note II] mattnmag:
Basically... you have to grant permission for the phone and computer to communicate with each other through adb.

See this article for specific details: http://android-developers.blogspot.com/2013/02/security-enhancements-in-jelly-bean.html?m=1 (Scroll down to the bottom and see Secure USB debugging).
[Verizon Samsung Galaxy Note II] RBEmerson:
Um, it looks as though SuperSu isn't installed during the process. How about installing it and Busy Box before running the script? You don't have to run it - it won't work, anyway. You'll get a complaint about it, but so what.
[Verizon Samsung Galaxy Note II] silentbob343:
Tried that as well.

If I install SuperSU before the process it gets removed during the process, still not root access either. Busy box stays, but without root can't do much.
[Verizon Samsung Galaxy Note II] RBEmerson:
Hmmm... that's odd, because I know SuperSU and BB were installed before I ran the script. There were only two "already exists" gripes - meh. I was going to suggest tweaking the SuperSU's file name but you need root for that.

Without SuperSU, you're flat out of luck for root access. BTW when you say "install super user", I assume you're referring installing the app SuperSU - right?
[Verizon Samsung Galaxy Note II] silentbob343:
Correct, I meant SuperSU. I'll correct my previous post.
[Verizon Samsung Galaxy Note II] RBEmerson:
It's probably a fool question but I assume you've done a full reset and still can't get rooted?
[Verizon Samsung Galaxy Note II] silentbob343:
I actually hadn't. Trying to gain access to edit the APN

to move off Verizon. Was hoping to avoid a factory reset to do it.
[Verizon Samsung Galaxy Note II] RBEmerson:
I've resisted FDR's in the past, too. But there's no getting around that they do clean up a lot of stuff that just might be getting in the way. BTW, even after the FDR, I put in SuperSU and Busybox. As I said, you'll see error messages because the apps are already there, but it doesn't hurt anything. I did have problems with SuperSU and BB not loading, when the script tried it, when they should, which is I put them in before trying to root the phone.
[Verizon Samsung Galaxy Note II] silentbob343:
I'll back up and try it after a reset. Thanks for the suggestions, I'll post back my results.
[Verizon Samsung Galaxy Note II] RBEmerson:
You're welcome, of course, but do remember the advice is worth what you paid for it. [/wink]
[Verizon Samsung Galaxy Note II] markvarvel:
Tether

have you tried xposed installer, then x tether?

it works on my ND7 4.4.2 note 2
[Verizon Samsung Galaxy Note II] ravenchaser:
Hi. after following this process for my SCH-i605 Galaxy Note 2, I ran a root-checker and it says that my phone is not rooted. Any ideas?

---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------

and like pmally says, same issues...
[Verizon Samsung Galaxy Note II] ravenchaser:
So, specifically "still coming up with knox and sysscope crashing"