CyanogenMod 12.1 for YU Yureka

YU Yureka recently received an official Cyanogen OS 12S update. If you prefer to use a newer revision of … more

Open War for Open Android: Antitrust for Cyanogen?

Android and openness is something we talk about all the time, but the recent … more

What Do You Do with All of Your Old Photos?

Smartphone cameras have advanced so tremendously over the past few years that they have … more

Diving into the April 2015 Material Design Update

Before the release of Android 5.0 Lollipop, the Holo Design guidelines served as the … more
Post Reply Subscribe to Thread Email Thread

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

8th April 2015, 03:33 PM |#471  
wolfballz's Avatar
Senior Member
Flag Prescott
Thanks Meter: 190
 
609 posts
Join Date:Joined: Jul 2012
Donate to Me
More
Quote:
Originally Posted by Chocolil

Following the directions my phone is now rooted. Even though I can't use the custom roms the fact that I can freeze apps was my main agenda. But some of the those Xposed Modules are also catching my eye so I'll check them out later. I did get SysScope and KNOX error on boot but I froze them and now they no longer appear.

My question now is how do I go about backing up the entire phone or whatever in case of a brick? I know how important it is to have a backup in case of that since I always experimented with stuff on my Wii which sometimes needed to be restored. I also would like to know how do I go back to an unrooted factory like state. I got this phone used so it was already on 4.4.2 so I don't mean to downgrade. I don't think that is possible from what I've read. Just in case if I want to sell the phone later though I'd rather it be clean.

To go back to stock use Odin to flash a factory image. To make a backup you need to grab safestrap from here http://forum.xda-developers.com/show....php?t=2704992 (don't worry that it says for mj9 as it does work on nd7)
once you get safestrap installed you can boot into TWRP (which gets installed when installing safestrap). From there you can flash things and make backups.
 
 
8th April 2015, 03:47 PM |#472  
Senior Member
nyc
Thanks Meter: 4
 
101 posts
Join Date:Joined: Sep 2011
More
Thumbs up
When I hold up, home and pwr , Iboot into a recover but its not twrp?

---------- Post added at 10:47 AM ---------- Previous post was at 10:39 AM ----------

Quote:
Originally Posted by wolfballz

To go back to stock use Odin to flash a factory image. To make a backup you need to grab safestrap from here http://forum.xda-developers.com/show....php?t=2704992 (don't worry that it says for mj9 as it does work on nd7)
once you get safestrap installed you can boot into TWRP (which gets installed when installing safestrap). From there you can flash things and make backups.

My bad I just got it working ty
8th April 2015, 09:50 PM |#473  
virginwidow's Avatar
Member
Knoxvegas TN
Thanks Meter: 3
 
95 posts
Join Date:Joined: Mar 2013
More
Unhappy My Ghett0 w0nt r00t :(
Quote:
Originally Posted by GingerSnapps

I see a lot of people are getting success with the Networking Pro link but I'm still not getting there.

Adb working:

{{Etc, all the same here}}
- 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.

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
Unable to chmod ghettoroot: No such file or directory
/system/bin/sh: ./ghettoroot: not found

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

Any ideas?

I'm having the exact same thing.
I have not yet done the factory reset wipe first, which may help?

Code:
SCH-i605
Baseband i605VRUFND7
Kernel Version 3.031 dpi@SWDD5710#1 TH May 8 KST 2014
Build number KOT49H.i605VRUFND7
SE for Android Status Enforcing
SEPF_SCH-i605_4.4.2._0016
I have heard there's a way to "Odin" the phone back to jelly bean, have found some rooted stock roms to download for that purpose... would I be better off trying that?
Does anyone have link to tutorial for this? (Yes I have google and it's like drinking from a fire hydrant)

VW
9th April 2015, 07:33 PM |#474  
Junior Member
Thanks Meter: 2
 
6 posts
Join Date:Joined: Apr 2015
More
Quote:
Originally Posted by virginwidow

I'm having the exact same thing.
I have not yet done the factory reset wipe first, which may help?

Code:
SCH-i605
Baseband i605VRUFND7
Kernel Version 3.031 dpi@SWDD5710#1 TH May 8 KST 2014
Build number KOT49H.i605VRUFND7
SE for Android Status Enforcing
SEPF_SCH-i605_4.4.2._0016
I have heard there's a way to "Odin" the phone back to jelly bean, have found some rooted stock roms to download for that purpose... would I be better off trying that?
Does anyone have link to tutorial for this? (Yes I have google and it's like drinking from a fire hydrant)

VW

I've rooted twice using the ghettoroot method, and needed to use both versions pretty much simultaneously both times I rooted. Are you using the double ghettoroot method? It took me a restart of my computer to have my phone to show the usb debugging prompt one time, and many other people have noted the necessity to disable your anti-virus while running the batch files, but after 8-10 tries it finally works for me.

Good luck, let me know if any of this helped

Sent from my SCH-i605 through space and time

Brought forth to your face by the XDA Developer app
14th April 2015, 08:02 PM |#475  
Junior Member
Flag El Cerrito
Thanks Meter: 0
 
5 posts
Join Date:Joined: Jun 2010
More
Finally got Note 2 rooted after some battles
I finally got my Note 2 rooted, thanks to various posts and pointers here, but it took a lot of work (about 4 hours!) and some of my experiences may help others ...

I did this with a Verizon Note 2:
Model SCH-I605
Android version 4.4.2
Baseband version I605VRUFND7
Kernel 3.0.31
Build KOT49H.I605VRUFND7

Prep:
Downloaded two versions of GhettoRoot:
- GhettoRoot v0.3.2
- the All-In-One "post 27" version by NetworkingPro at http://forum.xda-developers.com/show...3&postcount=27

I unzipped them both to root folders (not sure if this is important?) on C:

Factory reset phone.

Put phone into debug mode.
To do this you've gotta access Developer Options.
If you don't see Developer Options you've gotta go into Settings / About device and click on the build number a bunch of times.

Also under Security make sure you allow "Unknown sources" for apps.

Getting the device recognized:
When I'd plug my phone into my pc it would come up as a media device (MTP). This meant I could browse my phone and SD card on my computer.

I opened a Windows command (DOS) prompt as administrator and cd'd to the Ghetto Root v0.3.2 folder.

To open command prompt as administrator you need to right click on the Command Prompt in the Start menu and choose 'Run as administrator'.
I initially tried without being administrator but had no luck, but this may have nothing to do with whether or not I was at admin level or not.
So it may or may not be important to be administrator ... just telling you what finally worked for me.

Run INSTALL.cmd.

In my first several runs (when I was not administrator, if that's important) the adb server would start but it could not find the device, even though I could browse it in Windows Explorer!

Finally I took the advice of a poster here and watched the YouTube video "How To Download & Install Android Studio For Windows" at https://www.youtube.com/watch?v=Vy34ZcFRhZo

During the install of Android Studio I chose a different spot for installing the Android SDK ... hiding it beneath a hidden AppData directory seems pointless.
I installed it at C:\Java\Android\AndroidSDK.

USB Drivers:
Although Windows could see my phone fine there are numerous posts about needing the right drivers to do the rooting thing, so I ended up getting USB drivers from three places:

I got Koush's USB drivers from https://github.com/koush/UniversalAdbDriver

For good measure I also downloaded the latest USB drivers from Samsung at http://www.samsung.com/us/support/downloads
Note that the model # did not match exactly ... The closest match on the Samsung site was SCH-I605TSAVZW while on the inside of my phone it showed something like SCH-I605TSV.
I have no idea if this step was important.

I also installed PDANet on my computer, from http://pdanet.co/. This apparently also installs the USB drivers.

I doubt if I absolutely needed to install USB drivers from three sources ... just letting you know what worked for me.

Then, when connecting my phone in debug mode, it showed up in Windows Device Manager up near the top as an Android device, and it said something about "ADB" when you drilled into it. (Sorry, I don't have the exact wording).

Now I ran the newly installed adb (from Android SDK) to see if it could detect my phone. It did!

Code:
C:\ghettoroot-v0.3.2> C:\Java\Android\AndroidSDK\platform-tools\adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
430xxxxxxxxxxxxx        device
At some point above I was asked on my phone if I wanted to allow the PC to have access. (This is a debug mode thing). I said yes, of course. If this step doesn't happen apparently you'll never make it through the rest of the steps! You only have to do this once.

Also, along the way I made multiple attempts of unpluging/pluging-back-in the phone, as well as turning USB debugging mode off / on in order to get it recognized. Not sure if I needed to do this once I made it to this point where I had the latest adb installed.

What seemed to work (but I didn't validate by testing back and forth) is that once I had done the "adb devices" thing the GhettoRoot could connect to my phone. Call me superstitious, but after that I ran "adb devices" every time before running GhettoRoot and every single time GhettoRoot was able to connect.

Rooting
I then ran GhettoRoot v0.3.2 again:

Code:
C:\ghettoroot-v0.3.2>INSTALL.cmd
This time it took off roaring, with messages scrolling up the screen. However it stumbled at the SuperSU installer ZIP section:

Code:
...
/data/local/tmp/ghetto/META-INF/com/google/android/update-binary-2[64]: unzip: not found
...
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

etc ...

./root.sh[399]: dirname: not found
./root.sh[399]: 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.
The script doesn't have the greatest error checking ... clearly it had failed.

But I'd heard others had also failed with GhettoRoot v0.3.2, but had gotten it to finally work all the way with the GhettoRoot All-In-One "post 27" version by NetworkingPro from http://forum.xda-developers.com/show...3&postcount=27

But at first I had even worse luck with this one - it couldn't find the phone:

Code:
C:\GhettoRoot>GhettoRoot.bat
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.

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
Then I noticed in the GhettoRoot folder there was a version of adb.exe that was a different size than the one I had downloaded with the Android SDK.

So I renamed C:\GhettoRoot\adb.exe to adb-old.exe and copied adb (three files actually) over from the Android SDK at C:\Java\Android\AndroidSDK\platform-tools:

- adb.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll

(I have no idea if the dll files were also needed ...)

I re-ran GhettoRoot.bat and this time with the newer adb it worked!!!

I now had SuperSU on my phone (it was in the app drawer) and I verified I had root by opening ConnectBot to a local connection and typing "su" to see that I get the '#' prompt. [Details at http://trendblog.net/check-android-p...ed-two-steps/]

It was a long four hours but finally I'm rooted ... hope this helps someone ... Good luck!
16th April 2015, 06:55 AM |#476  
virginwidow's Avatar
Member
Knoxvegas TN
Thanks Meter: 3
 
95 posts
Join Date:Joined: Mar 2013
More
Unhappy GhettoRoot says "THis is a SCARY PHONE" (help? android jedi's?)
Quote:
Originally Posted by wolfballz

Use this from post 27 http://forum.xda-developers.com/show...3&postcount=27.
If unable to root after using this method let me know and I will call you to try and help walk through it.

I tried that version. No Joy. I removed Kaspersky, (with BSOD & reload windows boo hoo )

I did find some relief by copying all the adb.exe and drivers from the newest SDK into a "system path" so the batch & cmd files are finding the right stuff... USB and ADB are plying nice together etc... I've gotten into pretty much the same fix as THIS POST

Code below is output of "postcount 27" version of GR. It appears to be doing everything until it comes into getting SU & busybox in place & chmod. Fails with google maps popping up. Done this 3-4 times...

>>> marks lines where I can see it's not working. I know it's an adb shell script thing but I'm a CLI noobster

Code:
<<Snip>>

Removing old root files.
drwxrwxr-x shell    shell             2015-04-16 00:55 arm
drwxrwxr-x shell    shell             2015-04-16 00:55 common
-rwxr-xr-x shell    shell       34208 2014-08-31 20:58 ghettoroot
drwxrwxr-x shell    shell             2015-04-16 00:55 x86

Pushing necessary files to your phone.
4175 KB/s (34208 bytes in 0.008s)
push: data/local/tmp/arm/su -> /data/local/tmp/arm/su
push: data/local/tmp/arm/chattr.pie -> /data/local/tmp/arm/chattr.pie
push: data/local/tmp/arm/chattr -> /data/local/tmp/arm/chattr
push: data/local/tmp/common/Superuser.apk -> /data/local/tmp/common/Superuser.ap
k
push: data/local/tmp/common/install-recovery.sh -> /data/local/tmp/common/instal
l-recovery.sh
push: data/local/tmp/common/99SuperSUDaemon -> /data/local/tmp/common/99SuperSUD
aemon
push: data/local/tmp/META-INF/com/google/android/updater-script -> /data/local/t
mp/META-INF/com/google/android/updater-script
push: data/local/tmp/META-INF/com/google/android/update-binary -> /data/local/tm
p/META-INF/com/google/android/update-binary
push: data/local/tmp/META-INF/MANIFEST.MF -> /data/local/tmp/META-INF/MANIFEST.M
F
push: data/local/tmp/META-INF/CERT.SF -> /data/local/tmp/META-INF/CERT.SF
push: data/local/tmp/META-INF/CERT.RSA -> /data/local/tmp/META-INF/CERT.RSA
push: data/local/tmp/x86/su -> /data/local/tmp/x86/su
push: data/local/tmp/x86/chattr.pie -> /data/local/tmp/x86/chattr.pie
push: data/local/tmp/x86/chattr -> /data/local/tmp/x86/chattr
push: data/local/tmp/UPDATE-SuperSU.zip -> /data/local/tmp/UPDATE-SuperSU.zip
push: data/local/tmp/busybox -> /data/local/tmp/busybox
16 files pushed. 0 files skipped.
5082 KB/s (5922613 bytes in 1.138s)

Starting root exploit.
3711 KB/s (34208 bytes in 0.009s)
************************************************
native ghettoroot, aka cube-towel, aka towelroot
running with pid 7028
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)
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)
0xe51c4000 is a good number
Enter get_root (310; tid: 1b7b)
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)
0xe546fd5c 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: 1b7d)
GOING
get_root 315
cpid3 resumed
   In get_root(358): read(HACKS_fdm, readbuf, sizeof readbuf);
get_root 361
   In write_pipe(258) dest:e51c6008 src:00011000 count:4
get_root 364
get_root 367
WOOT
Enter read_pipe (233)
read_pipe(236) src:e51c6000 dest:40b7fa4c count:16
Exit  read_pipe(248): len:16
ti.task=e7cb61c0 .flags=00000200 .preempt_count=1 .addr_limit=ffffffff
Enter read_pipe (233)
read_pipe(236) src:e7cb61c0 dest:40b7f64c count:1024
Exit  read_pipe(248): len:1024
00000000 e51c6000 00000002 00400040 00000000 00000000 00000001 00000001 00000082
 00000082 00000082 00000000 c065fae0 00000000 0000006e 0253c825 eb78d540 0000000
0 00000000 eb78d54c c316b5a0 00000001 bf6fa6e6 0000002e 0003c143 00000000 568a6a
07 00000306 0003c143 00000000 00000000 00000000 00000000 00000000 0055c655 00000
000 0000000d 00000000 005a9c9d 00000000 00000000 00000000 00000000 00000000 0000
0000 00000000 001152e6 00000000 0013e0b5 00000000 00000000 00000000 00000000 000
00000 0000f4f4 00000000 0000bfbb 00000000 00000000 00000000 00000009 00000000 00
000000 00000000 00000000 00000000 00000000 00000000 0000000d 00000000 00000000 0
0000000 00000000 00000000 0000000d 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 c316b570 00000000
 00000000 e7cb6328 e7cb6328 00000000 000000c8 00000001 00000000 00000000 c316b61
0 00000000 00000000 00000000 00000000 00000001 00000000 00000000 e7cb6364 e7cb63
64 00000000 0000000c 00000000 005a7275 00000000 bf6fa6e6 0000002e 00000000 00000
000 c0acfb40 e53e6390 0000008c e7cb639c e7cb639c e7cb63a4 e7cb63a4 e6fea820 e6fe
a820 00000001 00000001 00000000 00000001 00000000 00000000 00000000 ffffffff 000
00000 00000000 00800000 00000000 00001b7d 00001b74 e53e61c0 e53e61c0 e7cb63f4 e7
cb63f4 e7cb63fc e7cb63fc e5ad0cc0 e7cb6408 e7cb6408 e7cb6410 e7cb6410 00000000 e
95820c8 e95820c0 e53e6424 e6f0a70c e6f0a700 e53e6430 e6f0a710 e6f0a700 e5ad0f3c
e7cb4abc 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 00000000 00000000 00000002 00000009 000000c8 2e0f5b75 000000c8 2e0f5b75 0000000
1 00000000 00000000 00000000 00000000 00000000 00000000 e7cb64a0
Supposedly found credential at taskbuf[184]: e5bedd00
Enter read_pipe (233)
read_pipe(236) src:e5bedd00 dest:40b7f5f0 count:92
Exit  read_pipe(248): len:92
Enter read_pipe (233)
read_pipe(236) src:dbf18820 dest:40b7f5d8 count:24
Exit  read_pipe(248): len:24
YOU ARE A SCARY PHONE                              <<<<<<< is it spose to say THAT?
   In write_pipe(258) dest:dbf18820 src:40b7f5d8 count:24
   In write_pipe(258) dest:e5bedd00 src:40b7f5f0 count:92
   In write_pipe(258) dest:e7cb63e4 src:00011004 count:4
-rw-rw-rw- root     root            0 2015-04-16 00:59 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
Disabling FWUpgrade: Success
Disabling Samsung Data Migration tool: Success
Remounting /system: Success
Remounting /: Success
Archive:  /data/local/tmp/UPDATE-SuperSU.zip
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
>>> /system/bin/cp: /system/app/Maps.apk: No such file or directory
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
Archive:  /data/local/tmp/UPDATE-SuperSU.zip
  inflating: META-INF/MANIFEST.MF
  inflating: META-INF/CERT.SF
  inflating: META-INF/CERT.RSA
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
  inflating: arm/chattr
  inflating: arm/chattr.pie
  inflating: arm/su
  inflating: common/99SuperSUDaemon
  inflating: common/Superuser.apk
  inflating: common/install-recovery.sh
  inflating: x86/chattr
  inflating: x86/chattr.pie
  inflating: x86/su
ui_print - Disabling OTA survival
ui_print
ui_print - Removing old files
ui_print
ui_print - Creating space
ui_print
>>> cp: /system/app/Maps.apk: No such file or directory
>>> rm failed for /system/app/Maps.apk, No such file or directory
ui_print - Placing files
ui_print
>>> mkdir failed for /system/bin/.ext, File exists
>>> cp: /system/etc/init.d/99SuperSUDaemon: No such file or directory
ui_print - Restoring files
ui_print
>>> cp: /Maps.apk: No such file or directory
>>> rm failed for /Maps.apk, No such file or directory
ui_print - Setting permissions
ui_print
>>> 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/Maps.apk: No such file or directory
>>> Unable to chown /system/app/Maps.apk: No such file or directory
>>> Unable to chmod /system/app/Maps.apk: No such file or directory
>>> chcon:  Could not label /system/etc/init.d/99SuperSUDaemon with u:object_r:syste
m_file:s0:  No such file or directory
>>> chcon:  Could not label /system/etc/init.d/99SuperSUDaemon with u:object_r:syste
m_file:s0:  No such file or directory
>>> chcon:  Could not label /system/app/Maps.apk with u:object_r:system_file:s0:  No
 such file or directory
>>> chcon:  Could not label /system/app/Maps.apk with u:object_r:system_file:s0:  No
 such file or directory
ui_print - Post-installation script
ui_print
ui_print - Unmounting /system and /data
ui_print
>>> failed: Device or resource busy
>>> failed: Device or resource busy
ui_print - Done !
ui_print
>>> failed on '/system/app/Maps.apk.prespaz' - No such file or directory
get_root 550
Thank you for choosing ghettoroot. Please enjoy your stay.

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

10 seconds...
5 seconds...
Rebooting...

Your phone should now be rooted. Press any key to exit.
Press any key to continue . . .
Where it says "failed on system maps yada yada" the map screen pops up right before it reboots... I've tried cancenlling that... no joy...
I'm too tired to type at this point... What DUMB thing am I missing?

Thanks in Advance
VW

---------- Post added at 01:55 AM ---------- Previous post was at 01:44 AM ----------

Quote:
Originally Posted by rmhand

I finally got my Note 2 rooted, thanks to various posts and pointers here, but it took a lot of work (about 4 hours!) and some of my experiences may help others ...
<<snip>>
So I renamed C:\GhettoRoot\adb.exe to adb-old.exe and copied adb (three files actually) over from the Android SDK at C:\Java\Android\AndroidSDK\platform-tools:

- adb.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll

(I have no idea if the dll files were also needed ...)

I re-ran GhettoRoot.bat and this time with the newer adb it worked!!!

I now had SuperSU on my phone (it was in the app drawer) and I verified I had root by opening ConnectBot to a local connection and typing "su" to see that I get the '#' prompt. [Details at http://trendblog.net/check-android-p...ed-two-steps/]

It was a long four hours but finally I'm rooted ... hope this helps someone ... Good luck!

I'm sure removing the antivirus didn't hurt. And things definitely got alot quicker when I moved the AdB etc from the SDK into a spot in my windows executable path.... but still didn't work. I'm missin something. See post below I must be an idiot.....
VW
Last edited by virginwidow; 16th April 2015 at 06:04 PM. Reason: reran GR to check output, it's the same
17th April 2015, 02:12 AM |#477  
Senior Member
Flag Lansing, MI
Thanks Meter: 52
 
330 posts
Join Date:Joined: Nov 2010
More
No Superuser? :(
I think the all in one was the trick for me. If ADB lists your device try that. Thank you so much to everyone working so diligently on this!!!

Edit: Howcan I get rid of the Knox and SysScope force close?
Last edited by Wishkah420; 17th April 2015 at 02:40 AM.
17th April 2015, 02:48 PM |#478  
wolfballz's Avatar
Senior Member
Flag Prescott
Thanks Meter: 190
 
609 posts
Join Date:Joined: Jul 2012
Donate to Me
More
Quote:
Originally Posted by Wishkah420

I think the all in one was the trick for me. If ADB lists your device try that. Thank you so much to everyone working so diligently on this!!!

Edit: Howcan I get rid of the Knox and SysScope force close?

Install Titanium Backup or any app that will allow you to uninstall system apps. Then find and remove Syscope. To remove the knox junk find and uninstall or freeze the following:
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store

Don't worry if you can't find all the ones listed above but you should find at least 3-4 of them.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes