yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] efrant:
Not sure. It worked for me on the first try.

I really have no idea if it makes a difference, but other users who are not on a stock Google build (like you) seem to have issues as well.
[Samsung Galaxy Nexus] nolook:
good idea although my nexus7 is unlocked/rooted and i lost for after the latest ota until i recovered it with root keeper...

Sent from my Nexus 7
[Samsung Galaxy Nexus] efrant:
If your bootloader is unlocked, getting root is extremely trivial. No need to even bother with OTA rootkeeper or whatever else.
[Samsung Galaxy Nexus] Mach3.2:
Exactly.

Beamed from my Grouper.
[Samsung Galaxy Nexus] maniaryan:
this is crazy that we've made it to this level, BIG UP TO THE AWESOME TEAM WHO CREATED THIS
[Samsung Galaxy Nexus] Ruffstaarr:
Android 4.1.2

I had previosly rooted my GNex with this method under android 4.1.1. I didn't unlock the bootlaoder, and everything was fine.

The OTA update to 4.1.2 removed my root. I didn't read the note, so I first tried to root it again with the same method, with - of course - no success.

I'm just wondering about the "while ! ln-s " loop. How is this supposed to work? If I make ln -s /home/user/foo/file_does_not_exist /home/user/foo/link_to_unexisting_file there is NO error! One is allowed to link non-existent files. For that reason I get no error on the first time executing the while-loop and continously "link failed, file exists" the second time. After that, there is a link in /data/data/com.android.settings/a/file99 pointing to /data/local.prop which is NOT existing!

Another thing I can't understand is:

I have still the su binary inside my /system/bin/su, as well as the SuperUser.apk.

adb shell

su just returns 1

How does android know that this su isn't allowed to execute anymore? The whole Busybox laying in /system/xbin is still executable, although some commands do not work because the lack of root.

Can someone explain, why one can have a su binary inside /system/bin and not having root? From my point of view, everything looks like a successful rooted phone. All files I should place in "EmulatorMode" are there and have the right access permissions.

Please enlight me
[Samsung Galaxy Nexus] efrant:
1) I don't understand why people do not unlock their bootloaders.

2) Having su in /system/bin does not mean you have root. In order to have root, the permissions on su MUST be set to 06755 or 04755. Otherwise you do not have root.

3) Every OTA update changes the permissions in /system (to 0644 I believe), effectively removing root access.
[Samsung Galaxy Nexus] chris_g:
Many thanks, efrant, for the instructions, it worked great on my Nexus 7 (Android 4.1.1) on the first try!

Now that it's rooted, is there a way to unlock the bootloader without losing all data? The BootUnlocker seems to be for the Galaxy Nexus only, not for the Nexus 7. Is there a similar tool for the Nexus 7 too? I already have the app Voodoo OTA RootKeeper. But it seems that I need to unlock the boot loader if I want to use a custom kernel (to use a USB DAC).

I don't want to risk to lose any data. I read that adb backup doesn't really backup everyting.
[Samsung Galaxy Nexus] efrant:
Now that you have root, boot or flash CWM, do a nandroid backup, copy it off your device, unlock the bootloader, and restore the nandroid. You will be back to the exact same state, except with an unlocked bootloader.

Not sure about the Nexus 7, but on the GNex, you do not need an unlocked bootloader to flash a custom kernel.

Yes, but he had used this method to root, and then did not unlock the bootloader, when he easily could have with no data loss.
[Samsung Galaxy Nexus] jmattp:
Is your Nexus 7 running 4.1.2? I can't root with this method. It worked on my Galaxy Nexus a while ago but the while loop command floods the terminal but doesn't stop after hitting restore. I've done it five times.
[Samsung Galaxy Nexus] efrant:
chris_g stated that he was running 4.1.1.

The first post also states that this no longer works on 4.1.2.
[Samsung Galaxy Nexus] jmattp:
OK. Sorry. In a motel room scanning the entire 20 page thread. When I reached the 20th page I was paying less attention to details People make mistakes.
[Samsung Galaxy Nexus] android.4.0:
i keep getting the $ instead of # what do i do

i tryed 3 times i keep getting $ help pls
[Samsung Galaxy Nexus] J_Caselles:
What exactly does adb backup not backup? In the first post it's mentioned that in Nexus devices this exploit is quite meaningless, cause we can easily backup everything and unlock bootloader; this refers to doing an adb backup, or to use another backup tool?

Thanks!
[Samsung Galaxy Nexus] chris_g:
There are many posts of users where it didn't work, just make a Google search (sorry, I'm not allowed to post any links yet).

That's why it would be nice to backup the entire ROM with nandroid backup from the recovery system (while the main system isn't running, so there are no open files).

However, nandroid backup is part of clockworkmod, and to flash clockworkmod, the boot loaded needs to be unlocked. But when unlocking the boot loader, the data will be erased - so nandroid backup comes too late. Am I missing something?
[Samsung Galaxy Nexus] efrant:
It is supposed to back up everything. It is kinda finicky (needs passwords set up, etc.), but it should work.

Most are from people who did not read and messed it up...

Yup, you are missing something. You do not need an unlocked bootloader to flash CWM if you have root. You can flash it using ROM Manager, or manually using dd.
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=32793031&postcount=187
[Samsung Galaxy Nexus] android.4.0:
i tryed 3 times keep getting $

what do i do now im on stock rom
[Samsung Galaxy Nexus] efrant:
If it doesn't work, then you have no choice but to do an ADB backup (as linked to in the first post) and then unlock your bootloader, and then restore the backup.
[Samsung Galaxy Nexus] chris_g:
Just when I wanted to unlock the boot loader, I got the notification that the update to Android 4.1.2 was ready! I installed it, and of course, root was gone. But thanks to "Voodoo OTA RootKeeper" (which MUST be installed and used while still rooted!), I could restore it easily.

Thanks, that worked indeed! I made a backup with nandroid, but it created only a tiny 21.5 MB "backup" folder containing boot.img, recovery.img and a few .dup files. It also created a 1 GB "blobs" folder with 3191 subfolders(!). I zipped these and transferred the archive to my PC.

I didn't really trust that because of the small "backup" folder, so I made also a backup via adb:

adb backup -apk -shared -all -f backup20121016.ab

This worked, so I unlocked the boot loader:

adb reboot bootloader

fastboot oem unlock

then chose "Start" in the boot loader.

As expected, the system was reset to factory defaults, including the sdcard folder. Restore via adb worked quite well:

adb restore backup20121016.ab

At first it looked like everything was restored. However, the following things were not:

- all paid apps were NOT restored. The icons were there, but gave an error "not installed".

- after reinstalling the paid apps from Google Play (fortunately without additional cost), their settings were lost.

- The "energy settings" widget on my home screen was not restored, so I had to re-add it manually

Otherwise adb seems to have restored everything, so I will not try the nandroid restore method.
[Samsung Galaxy Nexus] efrant:
This is normal if you are using the 6-series CWM - it is set up for incremental backups.

The nandroid would have taken you back to the exact state you were in before.

Not sure why you had issues with adb backup/restore though.

Another option would have been to restore apps and app data via Titanium Backup or something similar.

And yes, you can always re-download your paid apps for free at anytime after you have purchased them.
[Samsung Galaxy Nexus] Mach3.2:
You can actually change the backup format from dub to tar in cwm 6. You just need to look around the backup and restore menu of cwm.

Will the next nexus have a longer screen?
[Samsung Galaxy Nexus] efrant:
That's good to know, thanks. I honestly haven't really used CWM 6, other than testing it for a few minutes. 5.5.0.2 does everything I need.
[Samsung Galaxy Nexus] Mach3.2:
I found that out after poking around, it's a PITA to copy off all these dub and blob files...

Will the next nexus have a longer screen?
[Samsung Galaxy Nexus] chronopc:
I made a backup using the TWRP recovery. Is there a way to restore the TWRP recovery files using adb?
[Samsung Galaxy Nexus] ns2israel:
Lost my root access after updating to 4.1.2

and just saw that you said that google block this method.... what can I do? really needs it!!! :(
[Samsung Galaxy Nexus] efrant:
Why did you not unlock your bootloader when you had root before?? :confused:

The only thing you can do now is do an ADB backup, unlock the bootloader, and then restore your backup. Then you can easily root.
[Samsung Galaxy Nexus] efrant:
Why not use TWRP??
[Samsung Galaxy Nexus] Aquarius_Daddy:
Sorry but i'm stuck at step 4, cmd said: adb: unable to connect for backup.

I checked the files again and i'm pretty sure that the command and file name are used correctly.

Please anyone could help? I'm really appreciated.
[Samsung Galaxy Nexus] J_Caselles:
Actually it worked, but as other said, paid apps didn't backup, neither did their data. Also ringtones didn't backup, haven't really checked the other settings.

It restored shared storage too, but not sure if all data completely (I think a lot of application data under android folder was missing, but not all, as some games' data is still there)

Anyway, unlocked it is!
[Samsung Galaxy Nexus] phonedroid:
I am on stock 4.1.1 build JRO03C - according to the red warning in the first post, it should work upto JRO3O.

I have a question about step 6. Should one click 'restore' on the phone after the exploit command has finished or should it be done during that very small time window where you can see it running?

I had several tries where I tapped 'restore' WHILE the exploit was running and like many others, I am not getting the '#' prompt on adb reboot.
[Samsung Galaxy Nexus] efrant:
Should click restore as you see the errors flood your command window, i.e., as it is running.
[Samsung Galaxy Nexus] phonedroid:
Thank you. Somehow it doesn't seem to work for me.

Stupid question - "from ITL41D to JRO03O" -> this means inclusive of JRO03C build right?
[Samsung Galaxy Nexus] efrant:
Are you using a non-yakju or non-takju ROM, like yakjuxw for example?

Yes, including JRO03C
[Samsung Galaxy Nexus] sko2386:
I too have a problem in this step, I am at "FUll restore" on my phone and it says "If the restore data is encrypted, please enter the password below:" and the options: "Do not restore" and "Restore my data" are gray and I can not select it. my command prompt is still going with: "link failed no such file or directory" and that is constantly posted on cmd prompt. What do?
[Samsung Galaxy Nexus] efrant:
Have you encrypted your device?
[Samsung Galaxy Nexus] sko2386:
I have installed the attached file from OP and no I have not encrypted it. Should I restart the process? If so, should I just close my command prompt on my computer and exit out of "Full restore" on my phone?

---------- Post added at 11:53 PM ---------- Previous post was at 11:38 PM ----------

I purchased this phone from a third party about two weeks ago and he updated it to JRO03O. Maybe he encrypted it somehow, no matter what or how many characters I enter in the encryption password, the grayed out key doesn't go away and I can't select "Restore my data". I guess it won't be possible for me to root it this way without flashing a previous version :crying:
[Samsung Galaxy Nexus] efrant:
It's not a big deal. We have Nexus devices. Do an adb backup, copy it and the contents of /sdcard to your PC, unlock the bootloader, and then restore the backup. Most of your info should still be there.
[Samsung Galaxy Nexus] phonedroid:
I am having JB4.1.1 that came via OTA. I need to read further and understand what is a non-yakju or non-takju ROM. :confused:

Here's what I see
[Samsung Galaxy Nexus] efrant:
Yes, you are running yakjuxw, which is not a Google build, it is a Samsung build. Other users running Samsung builds have also reported it not working. It looks like Samsung changed something to make those ROMs not susceptible to this exploit.
[Samsung Galaxy Nexus] phonedroid:
Thanks for explaining.

I have unlocked the bootloader using fastboot oem unlock command, and then booted into cwm.img using 'fastboot boot' and managed to flash superuser. Luckily, all my data and sdcard contents were intact.

So now I am rooted without having to lose my data and then restore everything back!
[Samsung Galaxy Nexus] Mach3.2:
You must have some of these play store gnex where the boot loader will not wipe the sdcard.

Beamed from my Grouper.
[Samsung Galaxy Nexus] wasiful:
err....i guess i am the mother of all noobs, How does one "Open a command prompt in that same directory" ?? :eek:
[Samsung Galaxy Nexus] efrant:
Did you search? You know it has to be done: http://bit.ly/Suf43b :)
[Samsung Galaxy Nexus] ajpb:
I've seen how to root but the maximum I can do is root as rw access with this command

mount-o remount, rw-t ext4 mmcblk0p8 /

Giving me access to files

default.prop

init.goldfish.rc

init.omap4blazeboard.rc

init.omap4blazeboard.usb.rc

init.rc

The command cat /proc/partitions

major minor #blocks name

179 0 31162368 mmcblk0

179 1 128 mmcblk0p1

179 2 2048 mmcblk0p2

179 3 8192 mmcblk0p3

179 4 8192 mmcblk0p4

179 5 16384 mmcblk0p5

179 6 5120 mmcblk0p6

179 7 1048576 mmcblk0p7

259 0 1048576 mmcblk0p8

259 1 128 mmcblk0p9

259 2 29024895 mmcblk0p10

179 16 2048 mmcblk0boot1

179 8 2048 mmcblk0boot0

The partition / system to use the command

mount -o remount, rw-t ext4 / dev/block/platform/omap/omap_hsmmc.1/by-name/system / system gives error mount: Operation not permitted

I think the system partition is encrypted by this command in init.rc which encrypts the partition system

I'm trying to root toshiba tablet and the AT200 with ics 4.0.3. I have not seen much of android and ingles
[Samsung Galaxy Nexus] efrant:
As I had replied to you in your earlier post: I don't have those devices, and I have no idea which partition is the system partition on them. As well, I had written this guide of the Galaxy Nexus (but it should work on the Nexus S and Nexus 7 as well) -- I stripped out EVERYTHING else for the other devices. Ask in Bin4ry's thread please (linked in post #1).
[Samsung Galaxy Nexus] android.4.0:
click the folder once so its highlighted then pres ctrl and right click the folder the option should show:laugh:
[Samsung Galaxy Nexus] sethier:
Any chance on rooting 4.2 without unlocking?

I would like to root but dont want to have to wipe my device. Anyone working on a way to root Android 4.2? :o
[Samsung Galaxy Nexus] efrant:
How come your bootloader is not already unlocked? ;)

Not sure if anyone is working on rooting 4.2 yet, but you could always use this to back up your data, then unlock your bootloader, and then restore the backup. It should cover almost everything.
[Samsung Galaxy Nexus] tny2012:
There is a problem with the commands and the explanation of what they do!

Do You really understand what the command "ln -s /data/local.prop /data/data/com.android.settings/a/file99" does? Actually this command creates file file99 which is symbolic link to the file local.prop. So at end of procedure we need to "rm /data/data/com.android.settings/a/file99" , not the local.prop as you suggest!
[Samsung Galaxy Nexus] efrant:
The fill99 in /data does not affect anything. It only does something because of the symlink. Remove it if you wish. Removing local.prop gets rid of the link, and thus allows the device to boot normally, and not in emulator mode.
[Samsung Galaxy Nexus] samersh72:
very cool idea
[Samsung Galaxy Nexus] ufaak:
It is possible to apply the procedure for JOP40C build?

Thanks
[Samsung Galaxy Nexus] Shamestick:
I may pick up a gnex pretty soon that wont have anything on the sdcard so I dont need to work around keeping any data, will your guide on how to root it still work if it is on 4.1.2? and would I need to unlock the bootloader first?

EDIT: I know this guide wont work, but im talking about the one that is just to straight up root
[Samsung Galaxy Nexus] ynrozturk:
Hi efrant,

Don't know if this has been asked before so I apologize if it has been. I recently bought a Gnex and for some reason, it came unlocked. Here are the details of it :

"samsung yakjuxw"

My baseband version : I9250XXLF1

Build number : JRO03C.i9250XWLH2

It's on JB 4.1.1

I've been told that I can flash the latest version without having to root? I am clueless about this stuff - which files to download and how to go about doing this. I was pointed in your direction. Any help would be greatly appreciated.

Cheers.
[Samsung Galaxy Nexus] efrant:
http://goo.gl/rwt4b
[Samsung Galaxy Nexus] dankind.com:
Is it possible to downgrade from 4.1.2 to 4.1.1 to make this work? My Nexus S power button stopped working and now I'm stuck unable to remap the power button to another key without a rooted device...
[Samsung Galaxy Nexus] efrant:
Nope, not possible.

Why wasn't your bootloader already unlocked? :)
[Samsung Galaxy Nexus] efrant:
Actually, now that I think about it some more, it may be possible for you to unlock your bootloader by using OMAPFlash. You'll have to read up on it though.
[Samsung Galaxy Nexus] Mach3.2:
That guy is using a Nexus S, don't think it have a OMAP SoC.

Beamed from my Grouper.
[Samsung Galaxy Nexus] efrant:
Oops, good catch! I totally didn't read properly. :eek:
[Samsung Galaxy Nexus] akhenax:
<-- Referring to the error

I had the problem as well, but I tried to restore before running the command, and that worked for me.

What I did was click restore, and while it was restoring, I ran the command, It finished quickly, and I did not get the errors "link failed No such file or directory"

Verizon Gnex.
[Samsung Galaxy Nexus] kent_kinhwa:
thx for sharing...bookmarked...
[Samsung Galaxy Nexus] xero925:
How do I change directory in the command prompt to the directory where I put the toolkit?

Thanks
[Samsung Galaxy Nexus] efrant:
If you are in c:> to change to c:\junk> for example, it would be:

cd junk
[Samsung Galaxy Nexus] xero925:
Wow! Quick response! Thanks I'll give that I go!
[Samsung Galaxy Nexus] xero925:
I too can confirm that this method works on the Samsung Galaxy Nexus on 4.1.1 and build number JRO03O! Now I'm going to flash a custom ROM on my Gnexus. Probably Cyanogenmodd 10!
[Samsung Galaxy Nexus] AndroidAficionado:
Rooting on the Asus Transformer Infinity/Pad TF700T

I was able to successfully gain root access to my Galaxy Nexus, but recently got an Infinity and am looking to draw upon efrant/Bin4rys' magic again. However, I've tried several times, and after step 8 I'm still not getting the requisite # root access. Has anyone successfully rooted on the Infinity?

I'm getting a repetitive "link failed File exists" and then a few lines of "link failed No such file or directory" when I run the exploit and press restore (I can see /data/data/com.android.settings/a/file99 but not /data/local.prop, presumably for permission reasons).
[Samsung Galaxy Nexus] efrant:
You should ask in Bin4ry's thread linked in the first post. As I mentioned before, I've stripped out anything not related to Nexus devices in the commands for the purposes of this thread.
[Samsung Galaxy Nexus] zhuh04:
Myself stuck

Hi efrant thank you for your nice job. However, I have done all the same thing on my new GNex but always stuck at step 8. The pond sign has never come for tens of times. Is it because I manually pressed restore at the very first try in step 4? It is gonna be figured out anyway? Thank you very much.
[Samsung Galaxy Nexus] efrant:
If you have a new GNex, why not just unlock the bootloader? You won't have any data to lose.
[Samsung Galaxy Nexus] nickotym:
Does not seem to work with Build JR003U

My build is JRO03U.L700FH05. The exploit must have been fixed by this build as well. I was hoping since I was not in the upper range you mentioned in your October update it would work.

DEVICE: Samsung Galaxy Nexus (Sprint)

ROM: JRO03U.L700FH05
[Samsung Galaxy Nexus] efrant:
I hadn't seen that build before. I'll adjust the first post. Thanks.
[Samsung Galaxy Nexus] marc.ientilucci:
how long does step 5 generally take? been over 5 mins here and my phone is still on the "Full Restore" screen and my CMD is still showing "linkfailed no such file or directory"

looks like i let the "exploit" run a little to long before entering in the new command - rebooted and started over and it worked.
[Samsung Galaxy Nexus] SPKxNoOneStupid:
Tried your root trick, not working...

Also tried getting my phone into download mode & i've tried practically everything but the jig method. The model I have is a Chinese(?) clone, and I've tried every method i've found on the internet to root it. but no dice... i get all sorts of errors, and I think it is due to an unknown bootloader. if not, i'm not sure... My serial is also blank, and I only have the IMEI set because of the MTK droid program. Please help me, I'm at wits end... here are some system specs:

Model #: GT-I9300

Version: 4.1.5

Baseband Version: MAUI.11AMD.W11.50.SP.V27, 2012/08/04 20:43

Kernel Version: 2.6.35.7 Root@ubuntu #1 Sat Sep 29 10:54:30 CST 2012

Build Number: ALPS.GB2.MP.V2.17

Custom Build version: w988_XYKJ_T14_20120929_ML

Hardware: MT6575

Revision: 65fb8a00

OS:

Brand: ALPS

Radio: Unknown

Bootloader: Unknown

Product: x988_xykj_ml

Codename: REL

Release: 4.1.5

SDK: 10

Host: Ubuntu

CPU: ARMv7 Processor

CPUABI: armeabi-v7a

CPUABI2: ameabi

Fingerprint: alps/w988_xykj_ml/w988_xykj_ml:2.3.6/GRK39F/1348887300:user/test-keys

Build Prop:

ro.build.version.incremental= eng.root.1348887300

ro.build.type=user

ro.build.user=root

ro.build.host=ubuntu

ro.build.tags=test-keys

ro.product.manufacturer=Alps

ro.product.locale.language=zh

ro.product.locale.region=CN

persist.sys.timezone=asia/shanghai

rild.libpath=/system/lib/mtk-ril.so

rild.libargs=-d /dev/ttyco

ro.opengles.version=131072

dalvik.vm.stack-trace-file=/data/amr/traces.txt
[Samsung Galaxy Nexus] efrant:
Your device is running Gingerbread, not ICS or Jelly Bean. It will not work for you.
[Samsung Galaxy Nexus] SPKxNoOneStupid:
It's running gingerbread???? I guess the version was flashed to look like it is a newer model huh.... Any ideas on how to get this puppy rooted? It's driving me insane! :crying:
[Samsung Galaxy Nexus] efrant:
No idea. You could try one of the Gingerbread root methods like GingerBreak, but I don't know if that would work either. I don't know much about knock-off devices.
[Samsung Galaxy Nexus] SPKxNoOneStupid:
:crying: Already tried that... no dice....
[Samsung Galaxy Nexus] brb8two:
I have a i9305 grey import to Australia (Build JRO03C.i9305ZHBLL3) which is within the range specified in the title.

I was hoping this would work for me, as I just want root but not CWM or Flashing a custom ROM.

I've found a Stock ROM's to Flash, but I'm unsure if I'll loose any customizations / data on my phone if I were to use that method.

Also I'm unsure what that will do to my Flash counter or OTA updates. (just got an OTA update yesterday and I'm interested in keeping this)

I've tried this exploit a few times and have an un-ending "link failed No such file or directory" command prompt window.

I've tried ctrl+c then adb reboot & 2nd command prompt while it was running. waiting longer, waiting shorter, etc.

so far all have resulted with adb shell of $ not #

should this work for me, or do I need to try another root method?
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=35988142&postcount=259