yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kudoboi:
tnks... im new to rooting on samsung phones :) the past few android phones i used were all htc and motorola which all required to boot into bootloader mode to root or unlock...

and i guess i didnt need the OMAP driver after all... i was able to sucessfully root without that driver
[Samsung Galaxy Nexus] efrant:
:)

Just FYI, rooting any Android device (HTC, Motorola, Samsung) via an exploit requires you to be booted into the OS for the exploit to, well... exploit, the security hole in the OS.

As well, for the drivers, you obviously had them installed already. There is no driver for when the phone is off.
[Samsung Galaxy Nexus] nexusfracker:
effect of locked bootloader

Thanks for this howto; it was very useful to me. I was curious what the lockedness of the bootloader accomplishes when one acquires root privileges via an exploit like this one. Is there some read-only hardware toggle that's turned on for some partitions by the locked bootloader at boot-time, thereby preventing even someone who acquires root from modifying those protected partitions?

If the answer is no, there's no hardware toggles or any such additional protection for a locked bootloader from apps vulnerable to remote exploits, i'll probably start feeling less secure about my device. Even so, if someone has the answer please let me know.
[Samsung Galaxy Nexus] efrant:
The answer to your question is no. If you have acquired root privileges via this exploit, you can essentially do the same things as you can with an unlocked bootloader. The only thing you can't do is flash/boot images using fastboot commands.
[Samsung Galaxy Nexus] nomad4ever:
Worked like a charm! Thanks for the great guide!
[Samsung Galaxy Nexus] Sh0k:
Is there a new method for rooting the new update 4.0.4 IMM76I / IMM76D ?
[Samsung Galaxy Nexus] efrant:
Not without unlocking your bootloader. At least not yet anyway.
[Samsung Galaxy Nexus] alex2583:
I cant go beyond step 3.... yes am a noob I have all the files on my pc but What I dont get is how to open adb shel and all the stuff.:confused:
[Samsung Galaxy Nexus] efrant:
Then I suggest you do a bit more reading before attempting this.
[Samsung Galaxy Nexus] salem_christ:
Just thought I'd share this. I rooted using this exploit on 4.0.1. Installed 'voodoo OTA rootkeeper' from the Play store. Then after I updated to 4.0.4 OTA (which lost my root), I used the voodoo app to re-root really easily without even needing a pc.
[Samsung Galaxy Nexus] aryonoco:
Just wanted to say many thanks. Worked perfectly for me running Linux.

Tip for Linux users, make sure you've got ADB setup properly according to your instructions and have the adb folder added to your PATH, then you don't need to download the adb or fastboot from here, just download the exploit and run it accordingly to the instructions and it all works fine. Of course you don't need the any drivers either on Linux.
[Samsung Galaxy Nexus] JonathonReinhart:
Wow, props to zx2c4 for finding this exploit, and saurik for getting it working on Android! I just walked through the code, and am quite impressed!

I just got a G-Nex, and am going to root it in the next couple days. I can't decide whether to "fastboot oem unlock" the bootloader, or to use this exploit.

Questions:

1) Can one still install Clockwork Mod (or other) recovery without an unlocked bootloader? It was my understanding that the locked bootloader checks the signature on that recovery before executing it, but I may be wrong.

2) What are everyone's primary reasons for unlocking vs. using this exploit? I just got the phone, so I have nothing to lose during the unlock wipe.

3) Is there anything else you don't/can't get by sticking with a locked bootloader (and using this exploit)? I'm assuming you can still install custom ROMs (I will eventually want to run CyanogenMod 9).

Thanks!
[Samsung Galaxy Nexus] efrant:
Yes, you can.

Unlocking allows you to use fastboot commands (such as "boot" and "flash"). They make your life extremely easy. And you never have to worry about "losing" root, as all you have to do is boot a recovery image and get it back.

With a GNex, you can do pretty much everything with root and a locked bootloader, but I would still recommend unlocking your bootloader and leaving it unlocked. Otherwise, you are giving up one of the key benefits of owning a Nexus device! :) What happens if you somehow lose root with the next update? What are you going to do? Wait for another exploit? Or just unlock the bootloader and be done with it?

And besides, you can always re-lock the bootloader if you so desire, although I can't see why anyone would other than to return the phone to the store.

Thanks![/QUOTE]
[Samsung Galaxy Nexus] JonathonReinhart:
Thanks efrant. I come from an HTC world where it wasn't quite so straightforward. The main reason for my post was the lingering thought that, "If you can simply unlock the bootloader, then why bother using the exploit? (other than the fact that it is sweet :-D)" I suppose if you have data to lose during the unlock wipe (which seems unnecessary to me, btw) then I guess this is the route for you.
[Samsung Galaxy Nexus] efrant:
Yeah, there are two reasons I think this would help people:

1) if you hadn't unlocked before, and you have a lot data to lose, this allows you to flash CWM and back up everything.

2) if you hadn't unlocked and your power button is busted, there is no way to unlock. At least with this, you can still get root if you are on ICL53F or earlier.
[Samsung Galaxy Nexus] gti3358:
Well I may be in trouble with the wife X-p

I decided to try and get the last leak (IMM76K) on her still stock nexus and I thought this would be a great way to brush up on my adb knowledge. Well everything completed just like the write-up stated however I kept getting a whole bunch of FC's and I may have done something stupid by pulling the battery and restarting because I thought I had root. Now the phone goes to "Google" and then the poor little green guy laying on his back with a red triangle over his pulled open belly. I can get into the bootloader but I have no idea what to do from here. Any thoughts or help would be fantastic! Obviously I don't want to lose her date but at this point I don't know if I have a choice.

o and PLEASE HELP!!!!
[Samsung Galaxy Nexus] JonathonReinhart:
That was your first mistake.
[Samsung Galaxy Nexus] efrant:
First thing's first: take a deep breath and try to relax. :)

Had you already unlocked the bootloader? If so it makes things much simpler. If not, and you are still on ICL53F then, again, things are not too bad. If you managed to get to IMM76K and your bootloader is locked, then it may be difficult to save your wife's data. In any case, there is nothing wrong with the device -- worse thing is that what data that is not backed up on Google's servers is lost. That's it.

Let me know if your bootloader is unlocked, and if you are still on ICL53F, and I'll try to guide you through it. I'm off and on the computer, so I may not respond instantly...
[Samsung Galaxy Nexus] gti3358:
Bootloader is still locked and still on ICL53F...it's all good with the wife, well other then she may kill me tonight while I sleep :)
[Samsung Galaxy Nexus] efrant:
Ok, so assuming the drivers are installed properly, boot it normally an plug into your computer. Open a command prompt in the same directory as your adb.exe file, and type: adb devices

If the drivers are set up properly (and you had enabled USB debugging), then it should show up. If it does, just type: adb pull /sdcard

This will get all the data that was in /sdcard. Then I would proceed to unlock your bootloader, and re-flash the stock ROM.
[Samsung Galaxy Nexus] AshleyPem28:
Do if this roots your phone without unlocking the bootloader, does this mean it doesn't void your warranty either?
[Samsung Galaxy Nexus] efrant:
The bootloader on a Galaxy Nexus is re-lockable anyway, so whether you unlock it and re-lock it, or leave it locked, it is the same thing...
[Samsung Galaxy Nexus] AshleyPem28:
So to answer my question, is the warranty voided or not? Also, it's suppose to say "So if you" not "do if this"
[Samsung Galaxy Nexus] efrant:
Messing around with the system partition technically voids a warranty as much as a bootloader unlock.

But in both cases, the changes are reversible... so no one will be able to tell the difference.
[Samsung Galaxy Nexus] goudsalami:
so how can you explain this post: http://xdaforums.com/showthread.php?t=1073724&page=2

I really need to know for sure if I get my warranty back if I re-lock my nexus s because I want to update to 4.04 and regain root again. By the way i can't update manually because I can't boot into recovery mode because it's apparently broken in ics 4.03
[Samsung Galaxy Nexus] efrant:
Not sure what you are asking. As I had said, unlocking the bootloader voids that warranty, but you can re-lock it, so that no one can tell you unlocked it. What's the problem?

EDIT: You guys should really carry on this discussion in a different thread. It is off-topic.
[Samsung Galaxy Nexus] goudsalami:
Ok let me ask it differently. How can this guy ( http://xdaforums.com/show...1073724&page=2 ) not get his warranty back after he re-locked his phone. So did this guy have done something wrong, or can they found out in someway that he unlocked his boot loader in the past?

EDIT: sorry about being offtopic but this was the only place where it really came to the point what I'm after, after a well search ofcourse. Please let me know if you know a better topic on this.
[Samsung Galaxy Nexus] efrant:
It seems like that guy left an app on the system partition of his device. If mess around with the system partition and leave non-stock files on it, of course the warranty will be void. Just because you have a locked bootloader does not mean that your warranty is still valid.
[Samsung Galaxy Nexus] goudsalami:
Ok so whatever I do with the software on your phone, it get broken (hardware) I re-lock and completely restore the phone back to the factory settings (so remove everything and unroot it) there is no way that they can find out that I messed with it? I don't think they will check the storage for removed things, like forensic people would do.
[Samsung Galaxy Nexus] efrant:
Correct. Except that if you break your USB port, then there is no way to re-lock. You need a working USB port.
[Samsung Galaxy Nexus] jamontoast1291:
Is this possible to do on a mac?
[Samsung Galaxy Nexus] efrant:
Yes it is. With two differences:

1) You just need the mac version of adb. You can get if from here.

2) You need to put ./ in front of the adb commands. For example, adb push becomes ./adb push
[Samsung Galaxy Nexus] jamontoast1291:
Perfect. So otherwise copy and past everything from the first post, just with the minor addition of ./ ? I'm going to try this now, hopefully with success. My first Nexus I unlocked and rooted when I got it, but then I had to have it replaced and never did it to the second one.
[Samsung Galaxy Nexus] efrant:
Yup, that should be it.

I would still recommend you unlock your bootloader after you have backed up your data. Makes life much easier.
[Samsung Galaxy Nexus] jamontoast1291:
Yeah I definitely intend to once I back everything up.

EDIT: Good to go. Thanks, great thread and instructions!
[Samsung Galaxy Nexus] fpbasilio:
is this process reversible?

reason is after i root using this process, i wana backup my app datas with titanium backup. then i wanted to reverse the root process before i make a system backup using CWM (as described here http://xdaforums.com/showpost.php?p=21266325&postcount=239) so it will backup a non rooted system. then proceed to flash to yakju.

so i can restore the backup of the original yakjuxw build unroot later on if i need to send back for warranty

or is there a better process?

thanks
[Samsung Galaxy Nexus] efrant:
Yes, this process is reversible.

I think I understand what you want to do, so follow these steps:

1) Root using the method in this thread.

2) Do this, install Titanium and backup up your apps/data.

3) Then install ROM Manager. Use it to flash CWM.

4) Download a file explorer that has root access or a terminal emulator and delete all the files that you had placed on your ROM (in doing this process).

5) Turn off your device and boot directly into CWM, and do a nandroid backup. This will be your original yakjuxw ROM backup (although I doubt you will ever need it, as you should be able to send it in for warranty with yakju anyway. As well there are full images of a yakjuxw build already available in the dev section here.)

6) Now move all your data off your device and proceed to convert to yakju.
[Samsung Galaxy Nexus] fpbasilio:
great! thanks again efrant. But if i do nandroid backup, wont it backup a Rooted yakjuxw? so when i restore it, it will still be rooted? right? so how do i unroot it then?

im not sure whether they will accept the phone for warranty if its in yakju build. I bought the phone here in Singapore and all phones sold here are yakjuxw. so if they find a yakju build , or find the phone is rooted,they myt nyt accept it. I think..

Thanks for your time
[Samsung Galaxy Nexus] efrant:
When you "root" a build, all you are doing is copying two files to the /system directory. When you remove them, the build is no longer rooted. So, as per what I said above, if you remove the files before doing a backup, the backup will not be a "rooted" backup.

Again, as I had mentioned, the full, original yakjuxw ROM is available here, so there is no real need for you to do a backup...
[Samsung Galaxy Nexus] fpbasilio:
Awesome! thanks for your patience! fully understood now. :-D
[Samsung Galaxy Nexus] NCguy:
Efrant, is ota rootkeeper compatible with this exploit? I need to hide root from my time Warner cable app :rolleyes:
[Samsung Galaxy Nexus] efrant:
Yes it is!
[Samsung Galaxy Nexus] TheLeeDynasty:
Had to open up the superuser app (which i had to redownload from play store) but this method works, was able to then flash CWM and installed the 4.0.4 OTA on my Verizon Gnex.

Thx!
[Samsung Galaxy Nexus] efrant:
Not sure if I had used old builds of the su binary and Superuser.apk in the first post. That may be why. I'll update the attachment in the first post with the latest versions over the weekend.
[Samsung Galaxy Nexus] efrant:
I've updated the attachments in the first post with the latest versions.
[Samsung Galaxy Nexus] NCguy:
Efrant,

At this point I'm I am rooted using this exploit. and on 4.0.2 yakjuzs. I've backed up using titanium and I'm almost ready to flash takju.

It would be nice to be able to get a full unwiped nandroid before I flash the new rom but of course not necessarily required with the titanium backup.

It sounds like AdamOutler's unlock without wipe is the only way so far? If there is problem flashing that param partition is it recoverable? Would you be comfortable, in theory, using this method? Too soon to comment?
[Samsung Galaxy Nexus] efrant:
If you want a full nandroid backup, just download ROM Manager from the Play Store. Use it to install CWM, and run a full nandroid backup. This will backup your system, data and boot partitions. (If you want to backup up your stock recovery, use dd to back it up prior to installing ROM Manager).

As for what AdamOutler did, I kinda like figuring out how things work before I use them. Over this week, I'll try and have a look.
[Samsung Galaxy Nexus] codkill:
Limitations of Locked Bootloader

Efrant, thank you for the instructions. I used this process a while ago but forgot to thank you. It worked perfectly. I rooted on 4.0.2, used OTA root keeper, updated to 4.0.4, and am now running 4.0.4 rooted.

As a general question to everyone, what are the limitations of leaving the bootloader locked? As I have it now, I am rooted on stock 4.0.4 and I don't intend on flashing roms or kernels. I would like to flash CWM, which I believe I can through Rom Manager, to be able to make nandroid backups and MAYBE some small .zip tweaks (though I know a lot can't be flashed on stock because its not deodexed). Is there a good general list of what can and can't be done based on the state of the bootloader? Thanks for the info.
[Samsung Galaxy Nexus] efrant:
If you leave your bootloader locked, you cannot use fastboot commands. That is all. You may say, "No prob. I don't plan on using fastboot commands anyway, as I don't want to flash anything." Well, let me put it to you a different way: let's say for whatever reason, your stock ROM crashes, and you are stuck in a bootloop, or it just won't boot up period. And let's say that you just took a photo of your son's first steps <or insert whatever is applicable to you here> a few minutes before. If your bootloader is locked: bye-bye anything that was not previously sync'ed to the cloud. If your bootloader was unlocked, you would be able to boot CWM from your PC, and pull any file you wanted to keep off your device.

Yes, if you had already flashed CWM through ROM Manager, you would be able to recover the files that way, but it is much easier to ensure the recoverability of data when your bootloader is unlocked.

The only, and I mean only, negative of having your bootloader unlocked, is that, in the event that you lose your device, and the person who found it is android-savvy, he would be able to pull your data off your device. However, there are remote wipe apps out there...
[Samsung Galaxy Nexus] codkill:
Thank you for the information. Since I have only had this phone for a short time, it really wouldn't be a big hassle for me to wipe everything at this point. But looking into the future, if I went against what I said and began to want custom roms, are you saything that flashing those is still possible with the bootloader locked? I was told (and was under the impression) that with the bootloader locked I would be unable to flash roms, kernels, and radios. Is that not the case? You said that the only negative is if I lost my device and that scenario, but was that because I already said I wasn't interested in flashing other things, or does that apply in general? Thank you for the clarification.
[Samsung Galaxy Nexus] efrant:
As long as you have root, you can flash anything you want on this device.
[Samsung Galaxy Nexus] Sh0k:
Hi Hefrat,

do you know any new metod/exploit for our GneX 4.0.4 IMM76I, I know that I already posted this question but i prefer root my device with manual method posted in the first post ;)

Thank you.
[Samsung Galaxy Nexus] efrant:
No, I haven't seen anything. As far as I know, 4.0.4 is still not "rootable" without an unlocked bootloader.
[Samsung Galaxy Nexus] yancyn:
Hi Hefrat,

I have rooted my galaxy nexus successfully with your method. However, I want to unroot back my galaxy nexus and wish to get official OTA. What i have done is i mount again the system folder with adb, then remove su and superuser.apk. So am I now turn back to unroot? But I still unable to get the OTA after few days :( Or I still missing some step? How about the bootloader portion?

I found there are a simple way to unroot with Wugfresh. So my question is, can I just simply unroot with the tool directly after your method?

Thank you very much,

--yeangshing
[Samsung Galaxy Nexus] efrant:
Rooting had no impact on you being able to install an OTA update. The update will install if you are rooted or not. If if doesn't install, you have a different issue.
[Samsung Galaxy Nexus] vicodian:
Cannot get device listed on adb

hello,

can anyone help..pleaseee

I've tried many drivers including naked-driver but still cannot make the device serial number listed.

on device manager, subbed to Android phone, it shown Samsung Galaxy Nexus Bootloader Interface (device on fastboot)...but it seems the device is not connected to PC.

the device is unlocked (from fastboot info), but somehow I cannot apply cwm recovery. Should I perform another unlock procedure?

I have also purchase root explorer (to manually rename recovery file), but it says "root explorer has not yet to obtain root access. because of issues with superuser,..." --> is it mean my previous root process failed?

I used few android device before, yet nexus is my first "DIY" device. Any help would be appreciated. Thanks
[Nexus One Q&A, Help & Troubleshooting] ShadowCodeGaming:
Wtf is this bull****. It claims to only have 405 mb ram. It should have 512!!!!!! Is mine broken?!
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
Would you read before asking, please? I thought you're enough time here for that...

The RAM taken by kernel RAM disk is something you don't see. Answered 2 years ago.
[Nexus One Q&A, Help & Troubleshooting] Jacotb:
RAM doesn't just simply disappear, it's always in use by something.
[Sony Ericsson Xperia Neo, Pro] royalchild:
I rooted my phone and unlocked my bootloader here= http://xdaforums.com/showthread.php?p=21838619

And i downloaded this = http://xdaforums.com/showthread.php?t=1525955

And I tried to install custom rom= http://xdaforums.com/showthread.php?t=1387832

When power on my phone its only SONY text it won't open.

what can i do
[Sony Ericsson Xperia Neo, Pro] Madfysh:
for start you should ask in that thread instead opening new thread.

second, have you wipe everything as stated in that thread, step2? to be more precise, wipe system before flashing that zip?
[Sony Ericsson Xperia Neo, Pro] royalchild:
I think i wipe it, if i try it again will it work and my phone work?
[Sony Ericsson Xperia Neo, Pro] kormatoes:
get stock kernel and try again u

Have to fast boot a kernel
[Sony Ericsson Xperia Neo, Pro] royalchild:
I used wotanserver and i can open my phone now.

But i still want to install this rom
[Sony Ericsson Xperia Neo, Pro] Madfysh:
You think or you know?

Go from start and read first post of that thread. Specially part where it tells you what you need to wipe. Wipe everything that is written!
[Sony Ericsson Xperia Neo, Pro] royalchild:
Thanks guys, i installed custom rom!
[Sony Ericsson Xperia Neo, Pro] poyensa:
Also the title thread is wrong. It will not help to others with similar problems. Please use search function and post in an existing thread. Do not open a new thread. It will help to keep the information uncluttered. if you wish you can also use this chat thread
[Samsung Galaxy Nexus] stktd:
Is there any way to extend the memory like the galaxy tab 10.1 using this

http://www.amazon.co.uk/gp/aw/d/B0051D3KMG
[Samsung Galaxy Nexus] doormouse:
in the same vein

it is possibile to use an OTA cable and mount a usb thumb drive on a rooted device.
[Samsung Galaxy Nexus] stktd:
Thanks man, just found this

https://m.google.com/app/plus/mp/824/#~loop:aid=z13cwp1ztvzxu1g5204civrhkxfqytgxx34&view=activity

Bit ugly but at least its possible
[Samsung Galaxy Nexus] MilkPudding:
I just use cloud storage.

Box.net gave out 50GB lifetime account for free a couple of days ago.
[Samsung Galaxy Nexus] stktd:
Thanks gonna set that up .. but don't think it will help with on the move coz iv only got 500mb fair usage
[Android Q&A, Help & Troubleshooting] JackyJack:
Hi there, I have to android phones and I found an app on the store that doesn't appear for my second phone (xperia ray and Desire S).

So I extracted the apk from my /data/app/ fodler but of course I still can't install it on my other phone.

I guess this is something to do with the AndroidManifest.xml, so here are the questions :

- What tool I can use to extract, compile apk's ?

- What tool can I use to mod my apk so it launches on my 2nd phone ?

Thanks :D
[Android Q&A, Help & Troubleshooting] Dataslycer:
you can use apk tool to decompile the apk. then you can edit the whole apk using eclipse. to be able to install an apk from system/app you have to put the apk into the same spot and restart the phone.
[Android Q&A, Help & Troubleshooting] JackyJack:
Thanks, so the device compatibility list is generated when compiling from Eclipse ?
[Android Q&A, Help & Troubleshooting] flshg:
You are unlikely to be able to get the apk working on an incompatible phone. The reason for the incompatibility is likely to be that the phone lacks certain necessary features (e.g. CPU type or version of android) so can't run. Unless you intend to reprogram the app to run on reduced features you are better off asking the app dev to add support for the 2nd phone.