yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Cmoore0965:
Off topic, but I'm convinced its pertinent to this thread, any time I try to get to page one of this particular thread, xda premium force close... I've never experienced this with the app, I've rebooted, and tried several threads, cleared app data, I've even tried going back single page by single page, selecting the specific page, and immediately tracking to the first page. I know this may sound moronic, and it's hardly ruining my night lol, but I'm now curious and annoyed. I'm completely stock, and unrooted thus far. Anyone have an idea, or want to tell me to shut up? Anything would help scratch this itch that's bugging me

I777 gets it done, gnex just for fun
[Samsung Galaxy Nexus] marayag001:
$ instead of #

Hi, I'm really a noob at using adb to root Androids. With regards to the #/$ thing, no matter how many times I do it, I still only get $. I've repeated it maybe 20 times or so, and still doesn't give me #. I follow the instructions to the letter, I copy/paste everything and hit restore at the EXACT same time every time. Please, help me!
[Samsung Galaxy Nexus] soloxp:
Thinks Efrant, It works. No problems at all.

I hope I hit the right button for the Think you.....
[Samsung Galaxy Nexus] J_Caselles:
Hi. First of all, many thank's for this, I was really looking for it and everyone said it was just not possible. I can confirm that worked in my Nexus7.

Though, I have to open the paranoid question... does anyone feel a little lag/unstability afer rooting? could it be related to Mountstick and mounting usb in general? I've faced 2 reboots and a freeze since I rooted last night... and one time, while surfing, it kept prompting a Toast saying "shell has been granted root permissions" :S (about 200 times acording to superuser app)

Thanks!

_----------------------

****, now I've lost root cause I wanted to try temporary unroot and I can't get it back....

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

Redone process, any issue at all. And this time I've tried to use the phone when in emulator mode. Just to know what "laggy" really means ;) also I've read some post before about the shell permissions bug. Why do you prefer superuser above SuperSu?, seems quite more reliable SuperSu...
[Samsung Galaxy Nexus] efrant:
Not related to getting root. It could be due to one of your root apps, but I have never noticed anything like that.

This happens to me occasionally, but only when I try to insert my phone into the car dock, and the volume/power keys get press in some combination. A reboot solves it. See below.

I'm not sure what the shell permission bug is, but it may be related to Superuser (I can't confirm though). If it happens to you often, try using SuperSU. I don't prefer one over the other -- it's just that I've been using Superuser for years, and gotten used to it.
[Samsung Galaxy Nexus] J_Caselles:
Thank's for your answer! Finally I'm using SuperSU, cause this second time I've rooted, superuser didn't ask me to grant or deny permission, just granted automatically... (of course it was configured to prompt).

And for the unstability, yes, it's only when plugging/unplugging usb drives. It doesn't bother me, and I'm happy to know it is quite normal.

Thank's for your great job, your awesome explanations and your commitment to our learning!
[Samsung Galaxy Nexus] pkchips:
Tested and working on the nexus 7.

I had the issue where the loop didn't stop when pressing restore on my device (no typos). I simply repeated exactly the same process and it worked.
[Samsung Galaxy Nexus] 57op:
I had the same issue on my nexus 7. I repeated from point 4 and worked too :)

Thanks OP.
[Samsung Galaxy Nexus] costinu:
I noticed that this happens when you wait to long between the while loop and the restore on the phone.

Unfortunately, even after the process is ok I still don't have root.
[Samsung Galaxy Nexus] Burn2Hell:
Awsume guide worked for me. :good:

Only was the rooted part not fully working.

Love the galaxy nexus because you can simply lock and unlock the bootloader.
[Samsung Galaxy Nexus] jackerhack:
No root shell for me too. The ln part works, and when I pull /data/local.prop or /data/data/com.android.settings/a/file99, both have one line with ro.kernel.qemu=1 followed by 512K worth of null characters. However, adb reboot does not get me into a root prompt.
[Samsung Galaxy Nexus] JustusIV:
Might seem like a silly question but anyway to relock with a custom rom????
[Samsung Galaxy Nexus] 3rdstring:
Relock the bootloader?

If your rooted there's an app for that

If your not rooted

fastboot oem lock
[Samsung Galaxy Nexus] efrant:
What do you mean by relock? Do you mean relock the bootloader? If you follow this guide your bootloader will still be locked. You can unlock and relock the bootloader with segv11's Bootunlocker app if you have root. Otherwise, you can use "fastboot oem lock" to lock and "fastboot oem unlock" to unlock (but this will wipe your data).

EDIT: 3rd string beat me to it.
[Samsung Galaxy Nexus] mnomaanw:
Is emulator mode available only in Galaxy Nexus or it is available in all phones?

Are this files nexus specific?

Can we use these files or method for other phones too?

As other phones can also restore /data partition with adb so it might work...
[Samsung Galaxy Nexus] efrant:
It may work on other devices as well. Best to read/ask in Bin4ry's thread here.
[Samsung Galaxy Nexus] runandhide05:
I would also like to know that, as soon as my chick gets home I'm going to see if her phone has it too. Also if it would work on gingerbread phones
[Samsung Galaxy Nexus] efrant:
This will NOT work on Gingerbread -- only ICS and later.
[Samsung Galaxy Nexus] jlv3:
sync!

Thank you OP for writing this up in a nice and tidy way! :good:

One thing that tickled my fancy...

As an "Old UNIX™ Guy" (sans white beard), I found this a cross between amusing and absurd! Three syncs were the norm for UNIX systems in the 80s... And running three had lots to do with the workings of the UNIX kernel (some of which Linux mimics, but only sort of) and the delays associated with very slow rotational disks. http://utcc.utoronto.ca/~cks/space/blog/unix/TheLegendOfSync

I would assume that "adb reboot" would be invoking reboot on the device in such a way to flush any unwritten blocks, eliminating any need to manually run sync even once. Maybe it's not. And, I don't know if anything special is happening in emulator mode. So, I could maybe imagine that one sync was needed.

(and even if one was needed, it could have been run from the shell just before exiting it in step 16 -- no need to run adb again)

So, in this case, thou shalt not count to three!
[Samsung Galaxy Nexus] efrant:
:) I didn't think it was needed, but Bin4ry had it in his script, so I left it in my guide here (with my note of course :) ). I didn't use it, and I was fine.
[Samsung Galaxy Nexus] userno69:
I'm having this exact issue with the Sprint CDMA Gnex running 4.1.1 OTA. The exploit floods the command prompt properly, pressing restore makes it stop, etc... Then when I do adb reboot, followed by adb shell, the prompt is always $, not #. I've done this like 10 times now, it is never any different. It's definitely not rebooting to emulator mode, the phone is never laggy or flickering.
[Samsung Galaxy Nexus] gregvfx:
Question and suggestion

Hello Efrant,

Thanks for the great guide. After a couple of times I was able to root my Verizon GNex GB 4.1.1

Question: I keep seeing multiple Superuser permissions being granted to the same app during the same session. For example, doing a backup with Titanium backup, for every file backed up I see the Superuser permissions granted pop up. I don't recall this being normal. If not, is there a solution?

Suggestion:

In your guide, several of the steps, 4, 7 & 8 have the adb commands ending in a "." (period) People who are copying and pasting may not know not to include the period. If you include it in the command you will not get an error or indication the command failed, so someone may think they've succeeded when they have not.

Observation:

Also, at first with my already installed Samsung drivers, "adb devices" command detected my device so I assumed I was good to go. However I could not successfully root or push the files to the device (and was given no indication of failure). Only once I uninstalled the Samsung drivers and installed the universal drivers in your post, was I able to root successfully.
[Samsung Galaxy Nexus] J_Caselles:
True, first time I waited to much (cause I was looking for what to do) and didn't work. When clicking restore quickly right after the loop fires works fine everytime, maybe there is the key to make it work.

Second that. This periode can be really tricky for blind copy-pasters... this might be the error in most of the non-succeeded.
[Samsung Galaxy Nexus] costinu:
I just noticed that the loop keeps saying "link failed File exists". I think this may be the problem. Is there any way to fix this?
[Samsung Galaxy Nexus] efrant:
Some people have reported this or something similar. I likely has to do with Superuser.apk. If it is bothering you, feel free to install SuperSU instead.

Thanks. Periods removed.

Interesting. Thanks for the info. (I have always been telling people to not use the driver pacakage from Samsung or PDA or where ever else, and pointing them to the 1wayjonny's repack.)

You didn't read note #1 did you ;)

Again, thanks. Periods removed.

The problem is: if you have that file on your device, the exploit worked and it should reboot into emulator mode. All that the "adb restore" does is put that file with that one line in /data. So if it is there, it worked -- but I haven't figured out why your device is not booting in emulator mode though...
[Samsung Galaxy Nexus] costinu:
Tell me it there is anything I can help you with.
[Samsung Galaxy Nexus] userno69:
Anybody with a Sprint GNex on 4.1.1 OTA able to do this successfully? I still can't. I did not copy the periods, and I am using the universal drivers. My phone will never reboot to emulator mode.
[Samsung Galaxy Nexus] rjcart4:
+1 Sprint 4.1.1 fail

I have the same provider/phone/ota update/problem. I'm curious if the latest update patched this exploit. I knew I should have stopped the sales guy when he did it. I am still within the period that I can exchange for another no questions asked. Has anyone had success in rooting the Sprint GNex from ICS? If so, I'm gonna head to the sprint store.
[Samsung Galaxy Nexus] billyx1:
Worked perfekt on my GNex 4.1.1 JB like the first hack with 4.0.2 ICS. Finally again root without unlocking the bootloader! :victory:

It seems if Step 5 keeps running in the loop the hack didn't work and has to be retried!
[Samsung Galaxy Nexus] efrant:
Why not just unlock the bootloader, root, and if you want, re-lock the bootloader (although I don't know why you would want to...)?
[Samsung Galaxy Nexus] bradleyyy:
I'm stuck at running the exploit...my terminal is blinking no such file or directory constantly
[Samsung Galaxy Nexus] efrant:
That is what is supposed to happen until you click restore on your device.
[Samsung Galaxy Nexus] JustusIV:
The reason for this is HULU is f'ing stupid and it blocks itself on phones with unlocked bootloaders. I have been unlocked since day 1 and never really though i could go back to locked status but still have my custom roms/kernals.
[Samsung Galaxy Nexus] efrant:
Although I don't use Hulu, I find it hard to believe that it blocks itself on phones with unlocked bootloaders; (on phones with root, maybe, but not phones with unlocked bootloaders).

And if you are already unlocked and have root, you don't need this method -- just used segv11's app to re-lock and unlock whenever you want.
[Samsung Galaxy Nexus] oldblue910:
--SNIP--
[Samsung Galaxy Nexus] dj0:
Hi,

I'm trying to root Toshiba Excite 10 LE (AT200) using your nice "How to".

After step 8, I have a root shell as expected :

josian@josian-VirtualBox:~/android-sdk-linux/platform-tools$ ./adb reboot
josian@josian-VirtualBox:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
60A3C2E5E0600C01B	device

josian@josian-VirtualBox:~/android-sdk-linux/platform-tools$ ./adb shell
255|root@android:/ #

But when I try to Mount the system partition as r/w (step 9), I'm facing :

255|root@android:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
mount: Operation not permitted
255|root@android:/ #
255|root@android:/ #
255|root@android:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt tmpfs rw,relatime,mode=775,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/info /info ext4 ro,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:25 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
255|root@android:/ #
255|root@android:/ #
255|root@android:/ # mount -o remount,rw -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system /system
mount: Operation not permitted

Does it mean toshiba protects fs from remount in emulator mode? Or am I doing wrong elsewhere?

Thanks for your great work
[Samsung Galaxy Nexus] efrant:
I would ask in Bin4ry's thread linked in the first post. As also mentioned in the first post, I have stripped out

everything

not needed for the Galaxy Nexus -- you are trying to use this on a Toshiba Excite which, among other things, has a different mounting point for /system. This guide will NOT work on most devices (other than the Galaxy Nexus, Nexus S, and Nexus 7). Bin4ry's script should work for most devices, so either ask in his thread, or try his script.
[Samsung Galaxy Nexus] dj0:
Thank you efrant, I will read Bin4ry's thread.
[Samsung Galaxy Nexus] userno69:
That is of course a possibility, but more hassle in my opinion if you've already got tons of apps and things set up on your phone. I thought the whole purpose of this thread was to be a guide for rooting without unlocking the bootloader or wiping data? ;)
[Samsung Galaxy Nexus] efrant:
Yes, but I responded with that while quoting a guy who said he just got his device from the store, i.e., he would not have had much if any data on his device... Why would you go through the hassle of doing it this way if you have no data on your device? It doesn't make sense.
[Samsung Galaxy Nexus] gussde:
Link to attached files broken? Can't download them.
[Samsung Galaxy Nexus] efrant:
I just checked and the link works fine.
[Samsung Galaxy Nexus] gussde:
Got it! Must have been Comcast hating on me again. Thanks!
[Samsung Galaxy Nexus] chispynexus:
Hello, I'm having some trouble with this, as was reported by someone earlier in the thread I get "link failed File exists" when I run the exploit the second time after rebooting and not getting # in shell. Is there any way to manually boot into emulator mode now that the file does indeed seem to be in place?

Thanks for your help
[Samsung Galaxy Nexus] efrant:
Are you using a Sprint device as well?
[Samsung Galaxy Nexus] Chris302:
Thank youuu :)

hahaha waited so long for this!

I knowed about the Timing problem and the script but i not have the Time (and also some missing acknowledge) how this works and if could port it over to the GNex.

But thank you so much that you was able to port it and bring it up running.

Will test it later at home.

The Main issue was that i know their was an Timing Problem but i didn't know right how to get it working for the GNex.

But thankt you for Porting it over.

Will Report later if it's work.

On an Stock JB European GNex.

Grettings

Chris

P.S. Sorry for the Bad English, hope you will not blame me that much.
[Samsung Galaxy Nexus] chispynexus:
I'm using a GSM (maguro) GNex. Here's my baseband and kernel info:

Baseband: i9250XXLF1

Kernel: 3.0.31-g6fb96c9

Android-build@vpbs1 )

#1 SMP PREEMPT Thu Jun 28 11:02:39 PDT 2012

Edit: Build number: JRO03C.i9250XWLH2
[Samsung Galaxy Nexus] efrant:
Not sure why it is not working for you. There is no way (that I'm aware of) to "force" the GNex into emulator mode aside from what is described in this thread.

For those that can't get it to work, all you need to do is an adb backup, unlock using fastboot, and then restore the adb backup. And then you can get root very easily.
[Samsung Galaxy Nexus] chispynexus:
Thanks mate I will just follow your suggestion above. If I relock the bootloader it shouldn't void my warranty I guess?
[Samsung Galaxy Nexus] efrant:
I guess. Although "root" would also technically void the warranty. However, all of those discussions on warranties are pretty meaningless on the GNex, because we have the ability to return it to out-of-box state, with no traces of tampering.
[Samsung Galaxy Nexus] adrianblack:
Wow, big thanks. I had Google Authenticator on my phone and N7 -- and ended up wiping my phone to fix lag issues (stupid Motorola crap) and didn't realize the Google Auth database doesn't backup and restore using adb backup/restore! DUH! I didn't write down the seed codes and I didn't feel like resetting auth on all of my Google accounts -- so this saved me. I was able to root, use Titanium Backup to get it off my N7 and then restore onto my phone.

In case anyone is wondering, unrooting is just a reverse. When done, do ADB SHELL, then 'su' and then remove all of the files and links that were created, sync sync sync and reboot and no more root.

Thanks again.

EDIT: I tried this on my HTC Amaze 4G (stock 4.0.4) and it didn't work. The device has encrypted storage so that may have something to do with it? When you run the "while" loop and then hit the restore button on the phone, it is never able to create the link. I tried several times with different timing with no luck.
[Samsung Galaxy Nexus] myvijay:
Works Great (Yakju GNex 4.1.1)

The exploit worked after a couple of retries for me, in the first few cases I had taken a lot of time before hitting the restore button on the phone, after running the exploit, in that scenario the restore looks stuck and the exploit just keeps looping till it is stopped. It worked when I hit the restore button as soon as the exploit started running, the restore happened as expected and the scrolling immediately stopped.

Thanks efrant for this guide, this has been the most useful thread on XDA for me.
[Samsung Galaxy Nexus] Chris302:
So Yesterday Evening i tested the Exploit.

It has worked very good :) . I'm now on rooted stock rom and can use MyMobiler.

Thank you for the tut and "porting" the Exploit to the GNex.

One little question is left.

I also need to Unlock Bootloader for Booting a Custom Recovery or?

For Exampling using Nandroid.

Or wroks Online Nandroid without Unlocking ?

Thank you and Greetings

Chris :)
[Samsung Galaxy Nexus] efrant:
If you want to "boot" a custom recovery from your PC using fastboot, you must have an unlocked bootloader. If you flash it using something like ROM Manager, a locked bootloader is fine. But now that you have root, why not just unlock using segv11's app linked in the first post?
[Samsung Galaxy Nexus] JoeDoom:
Coming from the iPhone jailbreaking world, I am a total noob to Android rooting but got this working perfectly the first try. I also used the guide linked to make a full ADB backup, just incase anything went wrong.

It was a very easy tutorial to follow, thanks a million.

I did it all on a Mac by the way, and it wasn't difficult at all. So if anyone needs help with that, let me know.
[Samsung Galaxy Nexus] anubthomas:
Not working on 4.1.2

Looks its not the exploit is not working on 4.1.2.

GSM Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
Thanks for reporting. I kinda figured that it would be patched very quickly.

I'll wait for another confirmation before I make a note of it in the first post.
[Samsung Galaxy Nexus] mossholderm:
Yeah, I can't get it to work on my Nexus 7 with 4.1.2 either.
[Samsung Galaxy Nexus] maxximuscool:
Same my Nexus 7 Root is now kind of dead. Can't root with the method above anymore.
[Samsung Galaxy Nexus] efrant:
Well, I guess Google patched it up. I will make not of it in the first post. Thanks for reporting.
[Samsung Galaxy Nexus] JoeDoom:
Bummer that it's patched, but essentially we can just root while on 4.1.1 and use something like OTA RootKeeper or even SuperSU Pro to keep root through 4.1.2. Although, I've never personally tried a method like that and don't know how effective they really are.
[Samsung Galaxy Nexus] egrueda:
Thanks efrant for your great work.

I've sucessfully applied in a maguro JRO03C and now I'm making a backup with titanium ;)

Thank you very much.
[Samsung Galaxy Nexus] efrant:
Or you can root while on 4.1.1 and unlock the bootloader and be done with it. ;)
[Samsung Galaxy Nexus] phazer250first:
Thanks!! I will try it:good:
[Samsung Galaxy Nexus] OssianGrr:
Had to Clear Data on SuperUser app

Hi, I apologize if this got mentioned somewhere else in the previous pages of responses.

I just successfully did this, and I had 2 things hang me up:

1) I had previously been using the "adb backup" command, and I had set a password for backups. In order for this to work, you have to reset your backups password to blank.

2) After performing all the steps, the SuperUser app did not prompt me for root access for anything (although, curiously, when I did "adb shell" and typed "su", I could get root). After I used "Clear Data" on the SuperUser app, everything started to work again.

Thanks for this method. I specifically wanted root for backup reasons (my screen is damaged, and my whole phone might need to be replaced), and obviously a root method that requires wiping data would be counterproductive.

Thanks again!
[Samsung Galaxy Nexus] closurez:
when i run this command with quotes included my command prompt just repeatedly says "link failed No such file or directory" am i suppose to reboot while it's repeating this line?
[Samsung Galaxy Nexus] efrant:
You are supposed to click restore on your device when you see the repeated errors.
[Samsung Galaxy Nexus] poutcho:
For mac OSX users

As a mac user, the step about using fakebackup didn't work for me at first. Instead of:

I had to run it with dot forward slash to indicate location:

Otherwise, the restore would never happen and the loop would just go on.
[Samsung Galaxy Nexus] arsenal_fan:
Ok,noob here. I goofed up and clicked restore on my device after the "adb restore fakebackup.ab" command and now I get "Link failed: file exists" when I try to run the exploit. Any way to get around this?

Someone should include that you should hit restore on your device after you see the "link failed No such file or directory" error in the OP. Not seeing that error in the instructions threw me off, I hit Ctrl-C, started from instruction number one again, forgot that you shouldn't have to hit "restore" during adb restore fakebackup.ab and so hit it and now I'm stuck with another Link failed loop.
[Samsung Galaxy Nexus] gussde:
Since doing this successfully on my gnex I cannot install anymore apps. Getting insufficient space error. Even after uninstalling apps. Can't install the bootloader app or rom manager BUT CAN install Astro....? Thanks for any help! Btw, cleared cache too to no avail.