yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ÜBER™:
The ability to control your phone like you should. However being a really new person to android I wouldn't recommend you do it right away. Maybe browse the forum and learn somethings. Knowledge is power.

Sent From My Sprint Galaxy Nexus
[Samsung Galaxy Nexus] RogerPodacter:
Root gives you admin access to your phone. Definitely you should root, even if you want to stay on stock factory rom.
[Samsung Galaxy Nexus] martonikaj:
Only if he sees the benefits for himself. There's absolutely no reason for him to root if he doesn't understand what it does or how it will help/hurt him.
[Samsung Galaxy Nexus] fiki29:
As mentioned previously, root access is admin access to the phone. Some benefits of it include being able to use the Adfree app to block advertisements in apps or Titanium Backup to backup apps the data associated with them. I'd take the time to get to know the phone and operating system first and then decide if you have a need for apps that require root access.
[Samsung Galaxy Nexus] fredryk:
Off the top of my head:

-Fastest updates

-Ad removal

-Firewall

-True call blocking

-Lightflow

-Theming

-Backups (titanium, nandroid)

-Custom ROMs and all the millions of features they have (you could write pages and pages about this alone)

-Custom kernels (better battery+performance, touch wake, etc)

Since you have the Galaxy Nexus(a dev phone) as opposed to another locked-down phone, rooting is very, very easy. Unless you do something totally retarded you'll be safe. Just don't use toolkits -- do it manually.
[Samsung Galaxy Nexus] martonikaj:
-You don't need to root to get fast updates. You can flash update files the day they come out via fastboot w/ an unlocked bootloader.

-Lightflow also works w/o root.

-You can do backups with ADB also.
[Samsung Galaxy Nexus] fredryk:
I guess I was thinking of "root" being synonymous with unlocked bootloader. My old phone required root...still need root for TB.
[Samsung Galaxy Nexus] martonikaj:
Yes this is usually the case with other phones. With the Nexus, its extremely easy to unlock the bootloader and

not

root. I'd recommend unlocking the bootloader on this phone, but I'm not so quick to recommend rooting. People on XDA or too quick to recommend rooting to people who have absolutely no idea what it is and end up bricking their device.
[Samsung Galaxy Nexus] efrant:
+1. Exactly.

You do not need root to flash custom ROMs, get updates, etc. if you have an unlocked bootloader. I totally agree with martonikaj: you SHOULD unlock your bootloader, but you shouldn't mess around with root until you know what root is and need it.
[Samsung Galaxy Nexus] ufmace:
I would unlock the bootloader immediately if you think you'll ever want to root the phone. Reason why is that you can unlock the bootloader easily with a single command, but it will wipe your phone, and there's no good way to do a real backup without rooting it. Better to do it now, before you have everything set up the way you want it and all of your apps installed.

For rooting, I agree that you shouldn't do it until you have a better idea what it is and why you want to do it.
[Samsung Galaxy Nexus] asawoszc:
I've been back and forth between root and non-root (always unlocked bootloader) and other than a few things already mentioned (Ad-free, Titanium Backup) I'm the type that can live with Stock ICS. I do flash custom ROM's once in a while to see if I enjoy them but I've always come back to Stock (for now) because of random reboot issues.
[Samsung Galaxy Nexus] kennwoodkenn:
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
[Samsung Galaxy Nexus] asawoszc:
From someone who knows just enough to get by....

Unlocking your bootloader allows you to flash custom recovery/ROM/Stock version/etc. You don't need root for this.

Root allows you full access to the phone with superuser permissions and install some apps that require full access to system files.
[Samsung Galaxy Nexus] efrant:
You couldn't have been doing a lot of good reading if you've been reading for a year and don't know the difference. ;) But don't feel bad -- there are lots of senior members that use the terms interchangeably which is completely and utterly wrong.

Root means having root user access to the file system. Kinda like being the administrator user on Windows machines. You can access all the files and modify and delete anything. The process consists of placing two files on the /system partition of your device. The problems with this process, is finding a way to make /system write-able to place those two files there (as it is read-only by default when you are booted in Android). Chicken or the egg -- You need root to get root. :D

Think of the bootloader as the BIOS of a computer. It loads up before the operating system, and allows you to perform certain basic tasks. In our case, the bootloader allows you to flash images to your device, and to boot images on your devices (without actually writing them to the NAND). Unlocking the bootloader removes the security on the bootloader, which means that the bootloader no longer verifies the signature of images you are trying to flash or boot and, thus, allows you to flash or boot non-Google signed images.

Now, are rooting and unlocking your bootloader related? Well, to a certain extent yes. If you unlock your bootloader, you can easily obtain root access. This is true because you can flash or boot a custom recovery, which will allow you to write files to /system without being booted into Android. So, with an unlocked bootloader, "rooting" becomes trivial. However, there are other ways to root -- by using exploits. GNex Android builds up to ICL53F can be rooted by mempodroid (see link 4 in my signature), but to-date, an exploit has not been found for IMM76D and higher.
[Samsung Galaxy Nexus] kennwoodkenn:
For the epic touch it looks pretty easy to root in Odin mode it seems to be a way to go I know I want root for all the reasons above

My process

Root with ODIN

Install CWM

And like what I see in the AOKP ROM

I HAVE NOT FORGOTTEN TO BACKUP

Am I on the right track
[Samsung Galaxy Nexus] efrant:
Why don't you ask in the Epic Touch forum?? :confused:
[Samsung Galaxy Nexus] fredryk:
Rooting your gnex doesn't need to be seen as taking a dive off a cliff while blindfolded. This is a myth perpetuated by people who have either never rooted their devices or did something retarded and bricked it. It's easy, painless, and uncomplicated if you follow the instructions. If you can take advantage of the ad removal, backups, call blocking, etc with ease....why not do it?

Use this: http://xdaforums.com/showthread.php?t=1529058
[Samsung Galaxy Nexus] Kr8w20:
Thanks for all your help!

I'll proceed to unlock the bootloader, but will remain on stock for a while until I get the hang of it and want to expand my options.
[Sprint HTC EVO 4G LTE] scottborasjr:
So I disabled the Phone/people app from stock because I couldn't find a way to stop the phone from vibrating profusely when people called me. (Hate vibrate unless ringer is off, waste of battery to me) So anyway cannot find a way to enable the stock app again. Running Fresh's ROM
[Sprint HTC EVO 4G LTE] Saneless One:
Just reflash the Rom, it should copy the system files back to where they belong.
[Sprint HTC EVO 4G LTE] scottborasjr:
Yeah I figured I could reflash or restore a nandroid but am trying to avoid that until this whole Google Wallet BS gets figured out. I really don't care about using Wallet (would like to use the 10 bucks I was promised) but don't want to brick NFC in anyway whether it is Wallet or another program.
[Sprint HTC EVO 4G LTE] Evo_Shift:
Did you scroll all the way down to the bottom of the app list(not the app drawer but the list under settings>apps>all)? That's where stuff hangs out when you disable it instead of staying in alphabetical order. This is assuming you disabled it in settings>apps>all apps
[Sprint HTC EVO 4G LTE] scottborasjr:
Thanks, for some reason the search option is not popping up in my window right now. It was at the bottom of said list. Mods lock if you feel necessary.
[Galaxy S III Q&A, Help & Troubleshooting] lgkahn:
I am trying to change some icons in my att version of systemui.apk (with 7zip)

i have gotten the flight mode, sound, and battery icons to change as well as the wifi icons, but for some reason the signal icons are not changing..

is there another copy somewhere else.. i have searched in the framework-res but the signal icons in here are not the ones currently in use.

I also tried clearing cache and dalvek cache.. still the same..

any help would be appreciated.. thanks
[Galaxy S III Q&A, Help & Troubleshooting] lgkahn:
No one
[Captivate Q&A, Help & Troubleshooting] adobrakic:
I'm stuck in a pretty crappy situation. The phone is on some weird bootloop. When it boots, the AT&T screen comes up, then some weird multi-colored screen comes on, the phone turns off, and this process repeats.

I know how to put it into download mode, but the phone turns on as soon as I put the battery in. I'm not sure how to have it powered off with the battery in long enough so I can hold the volume buttons down and plug the USB in. If I could at least get into download mode and flash something via Odin, I could possibly fix it.

Any suggestions?
[Captivate Q&A, Help & Troubleshooting] fractaline:
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
[Captivate Q&A, Help & Troubleshooting] pizz0wn3d:
(psst, he said his power button is broken)

You dont need to use the power buttons to enter download mode. Just hold both volume buttons and plug in usb. Though tbh I haven't had to do it in so long my memory is a bit foggy on whether it was both volume buttons + usb or just volume up + usb. Either way one of those should work. Im pretty sure you should be able to do it without the battery inserted.

When all else fails, jig it. Jig it hard.

Herp derp Captivate Tapatalk 2
[Captivate Q&A, Help & Troubleshooting] adobrakic:
Well, the power button doesn't work, so I haven't tried the latter. It's not rooted, so trying to get into CWM wouldn't really do much. When I try to plug in the USB, hold the volume buttons, and plug in the battery last, the phone just goes to the battery charging screen. If I take the USB out.. it stays there.

I'm not sure why the phone turns on by itself as soon as I put the battery in. My sister has the same model, and she has to hold the power button to turn it on. :/

I just turned it on, and it's stuck on the AT&t screen instead of bootlooping. This is the first time it has done this after the bootloop began. Odin recognizes it. Is this ninja download mode? If so, could you please point me in the right direction of getting out of this mess? :x This is my sister's fiance's phone, I own a SGS4G. Really don't wanna risk this phone any more than I already have, lol.

Thanks, guys.

--Edit--

To be more specific, I attempted using this to root the phone, which resulted in this situation. Not sure if that's even helpful, but it can't hurt.
[Captivate Q&A, Help & Troubleshooting] baconatorXVI:
I feel for ya, I hate having hardware issues when a software issues happens..

follow fractaline's instructions: Odin ON, battery out, Good USB cable with good USB port Insert, (this is where it gets tricky), hold down volume up and volume down, whilst 2 seconds later putting the battery back in.

if you see the screen with something that looks like this, http://movilzone.org/files/2011/09/Captivate-Download-Mode1.jpeg

or this,

http://1.bp.blogspot.com/-BwmbWV5u6h8/TvNq1jXT7oI/AAAAAAAAMpU/_Mh4V9LMYd8/s1600/Semi-bricked.jpg, Then you can flash a kernel.

Were you on gingerbread 2.3.5? if so I would recommend this http://xdaforums.com/showthread.php?t=1294477&highlight=corn

if you flash corn there is an option in CWM to install root I believe.

I used to flash the corn kernel all day to fix my 2.3.5 problems.

it really depends which version you previously were running. which is hard to tell since it wasn't your phone... more info needed, i'll be back in the morning. hope this helps.

Oh and on the hardware side of things, you could take the back plate off, the plate under the battery, and clean all the crap out. i find with mine i often get dust particles that interfere with my power button. there is a guide to properly tear down a captivate on xda somewhere... I've posted on it before as well.

or, take your fingernails and try and peel back the plastic on the edge of the glass up by the power button, if you can pull it back enough to blow air in there sometimes you can dislodge/clean out whatever is obstructing the power button.

Edit: if you do get it rooted, bring it up to ICS, it's fantastic up here
[Captivate Q&A, Help & Troubleshooting] Red_81:
I think you were not on Gingerbread and you attempted to flash a gingerbread kernel. That is why it is bootlooping. You can flash back to stock (Gingerbread or froyo) and that should solve your issue. I'm trying to download and get the stock froyo kernel for you so you can flash that again. Just an FYI, applying root through CWM would require the use of the power button.

Try flashing this in the PDA in Odin. It is the stock froyo kernel.

https://www.dropbox.com/s/vx5r7hr3iokj764/zImage.tar
[Captivate Q&A, Help & Troubleshooting] adobrakic:
@Bacon, it was version 2.2. I can't get to download mode because the phone turns on as soon as I put the battery in. I'm not sure why it does this. Also, I don't get the bricked screen because it just bootloops. The AT&T screen comes on, then this comes on, the phone turns off, and this repeats. I'm assuming that the multi-colored screen would be the SGS screen, or something similar.

If it comes to that, I'll definitely keep this in mind. :P

@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.

--Edit--

Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
[Captivate Q&A, Help & Troubleshooting] Red_81:
You're not stupid. I added that after reading your post to prevent others from getting into the same situation.

As for download mode, if you don't have a jig, try this:

Take battery out

Plug phone into computer

Hold down Volume Buttons

Put battery in
[Captivate Q&A, Help & Troubleshooting] baconatorXVI:
I can't tell you how many times i flashed the wrong kernel because i didn't read that it was for my version! lol!

that screen is unsettling...

well it's tough to say what to do next... just keep trying for a download mode. I've never used a Jig, perhaps that would be a good investment. Maybe use a one click.. I don't know..

I don't suppose this could be a bootloader issue could it?

EDIT: You're sure you have a reliable USB port/Plug? it's very important that both are good.
[Captivate Q&A, Help & Troubleshooting] adobrakic:
When I do that, I get to this screen. I'm assuming that's the battery charging screen, but the picture of the battery never comes up, just that refreshing icon.

If I keep holding the volume buttons, the phone seems to turn off in this state. I tried immediately unplugging the USB cable and letting go of the volume buttons once it does this. It stays off (if it's actually off). However, when I hold the volume buttons down and plug the USB back in, it just goes back to that screen. No download mode.

@Bacon

To be honest, I have no idea if it could be a bootloader issue. I'm knowledgeable of Android as far as a user goes, I know nothing about the OS past rooting it, and tweaking it to OC/UC, etc. Also, I believe that the USB port/plug is reliable. It's the same combo I used prior to bricking it (lol). However, I have about 8 different ports and a few different cables as well, I'll give those a go.

Thanks for the help guys, I really do appreciate it.
[Captivate Q&A, Help & Troubleshooting] baconatorXVI:
Man I wish I could help more, i tend to be a hardware guy so i'm not much help other than telling you how to fix you power button... just keep flashing the crap out of it i guess. see if anything sticks...
[Captivate Q&A, Help & Troubleshooting] Red_81:
Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)

Type:

adb wait-for-device reboot download

and hit enter.

Now try booting the phone with it plugged in again. If the computer recognizes it during the bootloop, it will issue it the command to boot into download mode.

Otherwise, I would suggest getting a download Jig. It will put you into download mode every time.
[Captivate Q&A, Help & Troubleshooting] adobrakic:
@Bacon

All good buddy, thanks so much for your help. :)

@Red

Holy ****, that worked perfectly. I'm in download mode right now, and am in the process of using a one click to get back to stock.

I'll post back with results.

--Edit--

This is the one click I was using. It won't flash bootloaders at first to prevent bricking, so I'm now in Android system recovery. I'm wanting to get into download mode again, but I guess since it's not in bootloop, the command Red gave me doesn't get me there. I need to get back into download so the bootloaders can be flashed. Any suggestions as to how I could get there again?
[Captivate Q&A, Help & Troubleshooting] baconatorXVI:
the most success I've had is using kies mini up to 2.3.5 and then using corn from there on.
[Captivate Q&A, Help & Troubleshooting] Red_81:
Does it always boot to recovery? You could just pull the battery and then try to let it boot normally.
[Captivate Q&A, Help & Troubleshooting] adobrakic:
@Bacon

Don't I need the phone to boot up for kies, though?

@Red

Yes. As soon as I put the battery in, the AT&T screen comes on, and then the Android System Recovery <3e> screen comes on.

When I try to plug in the USB, hold the volume buttons down, and plug in the battery last, it simply goes to the battery charging screen. I don't know why it doesn't go to download mode. I've tested the volume buttons in the Android System Recovery screen, both work just fine.
[Captivate Q&A, Help & Troubleshooting] Red_81:
If you could get that power button to work you could try wiping data. That might get it out of that funk.

Try this:

Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)

adb reboot recovery --wipe_data
[Captivate Q&A, Help & Troubleshooting] adobrakic:
Crap, my computer doesn't seem to recognize the device when it's in the Android System Recovery screen. Should I try prying open the power button and seeing if I can get it to work? Don't see any other way out of this. I wish the soft-key buttons could be used for 'enter' instead of just the power button. :|
[Captivate Q&A, Help & Troubleshooting] baconatorXVI:
Shoot, sorry i misread i thought you said you had gotten it partially fixed... my b.

I was just commenting how I'd had the most success using a one click to stock and moving up with kies. I'm afraid you may have to wipe data, which would suck.

Try the power button first. It's really easy taking the hardware apart. Just don't strip the tiny screws.... i only have three of the 6 holding my back plate in. You really don't need them all
[Captivate Q&A, Help & Troubleshooting] adobrakic:
Honestly man, at this point, I wouldn't care if I had to repurchase all of the apps that I had if it was necessary to get the phone working. :P I'll YouTube some instructions for disassembly. Hopefully it'll get me out of this jam.
[Thunderbolt Q&A, Help & Troubleshooting] Mortland:
Lte just started in my area and I'm ansy to get it going.. I am running Baseband version 1.49.00.0406w_1, 0.01.79.0331w_1 Kernel version 2.6.35.14 on cyanogen 7.1.1

Witch radios are the newest I should have and should I flash to get the best quality and lte cause I'm not picking up signal and I don't think this is up to date.. Also when you do this are you flashing two separate radios at once or individually naming then the PG05 IMG in fast boot.. And where would I download these? I tried reading a thread on it but it was too confusing. Thanks for you're advice.
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
You're on the latest radio already. Some people have better results with older radios as every phone is different. I am currently running the 605.9 radios because I was having data drops with the most recent radios.
[Thunderbolt Q&A, Help & Troubleshooting] Mortland:
Do you have a link by chance maybe it will work good for me. Your on cm7 right?
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
Im running sense 3.5. Go over to rootzwiki and download thundershed. Its cm7.2 maybe it will help.
[Thunderbolt Q&A, Help & Troubleshooting] santod040:
Have you tried removing your battery and sim card, placing them back,

and then rebooting? This is what's generally required to reestablish the connection and update your prl, etc...might just help.
[Thunderbolt Q&A, Help & Troubleshooting] disconnecktie:
I have used that method several time and it works occasionally. I think his problem is more related to using aosp than anything. The most recent radios work pretty well with 7.2 I think that 7.1.1 just has that issue no matter what though.
[Thunderbolt Q&A, Help & Troubleshooting] Brakiss:
Have you tried getting a new SIM card? that was my problem
[EVO 4G Q&A, Help & Troubleshooting] HipKat:
That's what I call a well written post. Excellent description. I'm sure one of these guru's can help you out, but the guy to look up is Captain Throwback. He is the master at recovering these phones. Just PM him this same thing
[EVO 4G Q&A, Help & Troubleshooting] NxNW:
I imagine a lot of Evo veterans will read this and have a knee jerk reaction "why not try Amon Ra instead of CWM?"

Not that this is definitely your problem, but it was the first thing that jumped out at me.

If you have red triangle, you probably need to reinstall your recovery anyway, so see if you get better results with Amon Ra this time?

Not a big fan of all the later variants: just go with 2.3 . Tried and true.
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
Nice thoroughly documented post :)

I would say, at this point, to unlock your bootloader using HTCDev, and then reinstall a custom recovery (Amon_RA-based recoveries are the best choice). If that goes successfully, I would flash the latest stock rooted ROM (mine) and see if it works. If so, you're good to go. If not, then we'll have to do some additional troubleshooting.

It seems like the bootloader flashes didn't complete successfully for some reason (even without an error message). Could be bad blocks, but it's difficult to tell at this point.

You won't be able to downgrade your bootloader with the version you're on (and it's not really necessary), but without first checking the eraseblock size, that's not a good idea anyway.
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
Ok. I unlocked and flashed the recommended recovery (Aman_RA 2.3) via PC36IMG.zip. No problems.

I downloaded this file:

5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip

I then booted into Recovery. Seems to work fine. Upon trying to choose the zip from sdcard, I received the following error:

Build : RA-supersonic-v2.3 - HAUS MOD rev.A

E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)

(No such file or directory)

E:Can't mount /sdcard

Here is my updated HBOOT Status:

*** UNLOCKED ***

SUPERSONIC EVT3 SHIP S-ON

HBOOT-2.18.0001

MICROP-041f

TOUCH PANEL-ATMEL224-16ab

RADIO-2.15.00.12.19

DEC 21 2011,12:50:32
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
Try booting into fastboot, and applying the SD card fix from here. Then, boot back into recovery and see if the SD card will mount.
[EVO 4G Q&A, Help & Troubleshooting] NxNW:
EDIT - The captain beat me to it. Never mind.

You've tried booting with your existing micro SD card and without it, but have you tried a *different* card? Have you (backed up all your data and) reformatted the existing SD card?

Instead of bad blocks in internal ram, maybe you just have issues with your external storage?