Database Info

Can I still do non-OTA updates after unlocking the bootloader?

Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
...can no longer receive ASUS software updates...
Click to expand...
Click to collapse
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?

nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
You'll be flashing ROMs, not getting ASUS's updates. A rom for the latest firmware usually takes less than a week to get on the dev section of the forum.

nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Click to expand...
Click to collapse
Only refers to OTA, as far as we currently know -- the bootloader unlock hasn't been available long enough to prove otherwise.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
Nope, it only reboots. It will leave your user data intact when performed correctly. Obviously, when the crap goes into the ventilator, global nuclear war might ensue or your cat may just die (if you don't have one, you will receive one from a local asylum a few days before, that's enough emotional attachment to make it hurt).
<Oh, sometimes I'm vile. Sorry! >

Avoid losing root if ATT forces 2.20 OTA update

I have an AT&T HOX. Came stock with 1.85.
I rooted it using the "redbend" method described here (http://forum.xda-developers.com/showthread.php?t=1709296)
(More or less, the pulling SIM card business wasn't part of the steps when I used it, but the root was successful).
I am using SuperSU to manage root access by apps.
I have not done anything beyond that.
Now, I understand, at some point, AT&T is going to force a 2.20 update on me.
My primary concern is to avoid losing root.
(I have enabled the "preserve root across OTA" in SuperSU, but not sure if its effective or not)
I've looked at the howto's for SuperCID, unlocking the bootloader, etc, and I'm not sure which I NEED, and which are optional, and/or what the pros/cons are of each...
I'd like to stay as close to "stock" as possible, but I want to ensure that I can keep root.
I'm still within my AT&T contract, and would really prefer to avoid bricking the phone.
I'm wondering what the recommendations are as to the minimum steps I should take to keep root in the event the OTA is forced on me?
Can I pre-empty the OTA by installing this? ( http://forum.xda-developers.com/showthread.php?t=1812459 )
If so, what is the safest method for installing it?
FWIW, I am a linux user, and I am comfortable with adb as well as the command line on the phone itself.
I have no windows systems, so any special tools I'd need other than adb I'd have to find a linux version.
I don't need "one click" methods, in fact I'd prefer to see/perform the individual steps and understand what they are doing.

unlock your bootloader using this method http://forum.xda-developers.com/showthread.php?t=1672284 if you don't you wont get root again afterwards.

Dont have to unlock to flash roms?
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
My ATT HOX is currently rooted, and I now have SuperCID. I assumed I would need to unlock my bootloader, but I havent done that yet.
Can I install this:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?

Megadave123 said:
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
Click to expand...
Click to collapse
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Megadave123 said:
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
Click to expand...
Click to collapse
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Megadave123 said:
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Click to expand...
Click to collapse
SuperCID survives OTA. But the 2.20 OTA has a new hboot, which fixes the hole by which kernels and radios can be flashed from recovery, so my recommendation would be not to install the OTA.

redpoint73 said:
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Click to expand...
Click to collapse
FWIW, I didnt google that site. It was linked to from an XDA post. I't didnt seem right to me, which is why I asked here
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Click to expand...
Click to collapse
Ok, that is VERY good to hear.
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.

Megadave123 said:
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Click to expand...
Click to collapse
I think bypassing the user acceptance dialogues for the OTA install would be a violation of how Android fundamentally works. It would be a serious security issue, as it might allow rogue software to be installed on your device without your interaction. I seriously doubt AT&T would institute such a thing.
The user confirmation of the OTA might be a liability thing, too. If the performance of the device is adversely affected by the OTA (happens to some people) and the OTA was forced by AT&T without the owner having a choice, it would seem to me that AT&T has to accept the responsibility. People can claim its AT&T's fault, and demand a replacement device (since AT&T technically installed the software remotely). By making you confirm the OTA installation (and giving you the chance to opt out), you pretty much are volunteering to install the software and accept the consequences.
In theory, unlocking the bootloader voids you warranty. But more than a few folks on here have gotten warranty replacements from AT&T (after unlocking the bootloader), without issue. Sometimes in-store (within the first 30 days) without them even checking for the bootloader unlock. No guarantee that this will always be the case. But just throwing it out there. Its still up to you whether unlocking the BL is worth the risk in your own case.

I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery

18th.abn said:
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
Click to expand...
Click to collapse
The hoxl is officially supported by twrp and can be downloaded from goomanager. I do not know if you can install a custom recovery without an unlocked bootloader. I would be interested to know if this can be done as well.
Sent from my Nocturnalized One XL using Forum Runner

when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.

Is there any harm in trying it?
If I install "goo manager", and let it do its thing, and the locked bootloader prevents it from doing so, there wont be any other side effects, will there?
If I come off as a complete noob at this - its because I am..
This is my first Android phone, and I *really* want to avoid bricking it, so I want to make sure I understand as much as possible before I go
trying to do anything to it.
Also I'm still wary of unlocking, mainly because of the whole "will erase your phone" bit.
I'm not yet fully comfortable that I know how/what to fully backup all of "my" data on the phone so as to facilitate easily putting it all back.

I'll answer some q's here.
1.) you cannot flash a custom recovery from hboot with a locked bootloader
2.) you CAN dd a custom recovery with a locked bootloader. However your device will be soft-bricked.
3.) you CAN install custom ROM's via dd right from android. This is how we did it back "in the day".
4.) you "might" be able to get away with dd'ing a custom kernel with locked BL, not not sure. In fact, I'd bet it will softbrick now that I think about it.
Anyways, the SAFEST way to do it is via unlocking the bootloader and installing your roms from custom recovery.

gunnyman said:
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Click to expand...
Click to collapse
Beaups pretty much already answered it. But this guy tried installing TWRP thru goomanager with a locked bootloader, and confirmed it doesn't work: http://forum.xda-developers.com/showthread.php?p=31220704#post31220704

Root and still getting OTA updates theory

Hi XDA-Devvers,
In a topic (http://forum.xda-developers.com/showthread.php?t=1510719) I read about the following:
Nonverbose said:
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
Click to expand...
Click to collapse
Doesn't that mean that we can root our tablet, lock the bootloader again (fastboot oem lock), install Voodoo OTA RootKeeper and once there's an OTA available, just backup the root with the Voodoo app and install it?
How awesome would that be :laugh:
Since I am not a pro in that kind of stuff: Can anyone confirm this theory might actually work for real?

fastboot oem lock is unavailable once you unlocked the bootloader.

Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?

TomONeill said:
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
Click to expand...
Click to collapse
No, as many informations -including bootloader version- are sent to check if a new OTA is available

alx5962 said:
No, as many informations -including bootloader version- are sent to check if a new OTA is available
Click to expand...
Click to collapse
Okay, thank you for replying. This makes the decision to root a little harder since I want to keep getting updates and for that you'll need ClockWork (and the people who are pushing the update to XDA)(Clockwork does have the nandroid backup though, which I want to have when rooting), which doesn't run very stable last time I read (I rooted before, but then I sent my tab back (heat problems) and got a new one. I flashed a beta ROM xd).
I thanked your post

Isn't it enough to have the original Kernel and ROM? Do you really need a locked bootloader to get OTA updates?
Has anyone tested the universal root method? See http://forum.xda-developers.com/showthread.php?t=1886460
As this doesn't effect the Kernel, OTA updates might work if rooting works with this method.

I've not tried it. I've read some people are bricking their tablets with the universal, and since the A700 is basically a brick waiting to happen, I think I'll pass on it for a while.

[Q]10.4.2.18 firmware and unlock

I recently got a tf300t which came already with 10.4.2.17 JB firmware.
At the moment I'm not plannig to install custom ROMs basically because I understand that I should unlock the bootloader and lose the warranty doing so.
The device is notifying that an update (the .18 firmware, I guess) is available, but before upgrading I want to be sure that in the future I will able to unlock the bootloader and then install custom ROMs.
Can someone please reassure me about it?
I'm sorry if this sounds as a dumb question, but I'm pretty new to this tablet and in the past I lost the ability to gain root access for another device beacuse of an OTA update.

Malobestino said:
I recently got a tf300t which came already with 10.4.2.17 JB firmware.
At the moment I'm not plannig to install custom ROMs basically because I understand that I should unlock the bootloader and lose the warranty doing so.
The device is notifying that an update (the .18 firmware, I guess) is available, but before upgrading I want to be sure that in the future I will able to unlock the bootloader and then install custom ROMs.
Can someone please reassure me about it?
I'm sorry if this sounds as a dumb question, but I'm pretty new to this tablet and in the past I lost the ability to gain root access for another device beacuse of an OTA update.
Click to expand...
Click to collapse
If you're already on 10.4.2.17, upgrading to 10.4.2.18 won't affect your ability to unlock. Some people (like myself) are unable to unlock for unknown reasons, but upgrading from .17 to .18 shouldn't make a difference(10.4.2.18 doesn't really change much). If you're able to unlock, you should be able to do it on either .17 or .18. If you're unable to unlock, you then wouldn't have been able to do it on either version.

reffu said:
If you're already on 10.4.2.17, upgrading to 10.4.2.18 won't affect your ability to unlock. Some people (like myself) are unable to unlock for unknown reasons, but upgrading from .17 to .18 shouldn't make a difference(10.4.2.18 doesn't really change much). If you're able to unlock, you should be able to do it on either .17 or .18. If you're unable to unlock, you then wouldn't have been able to do it on either version.
Click to expand...
Click to collapse
Thank you for your answer.
This inability to unlock somewhat scares me.
Is this connected in someway to the production date of the device (which maybe could retrieved from the serial number)?

Malobestino said:
Thank you for your answer.
This inability to unlock somewhat scares me.
Is this connected in someway to the production date of the device (which maybe could retrieved from the serial number)?
Click to expand...
Click to collapse
I'm not sure, I know I and several others have been unable to unlock. There are various theories as to why (ASUS unlock server problems, serial number not in their database, certain serial numbers don't work, etc...). Worst case scenario is that when you try to unlock, it gives you the error "Unknown error occurs, which may be a network connection issue. please wait and try again later" and nothing happens. Personally, I'm pretty sure my problem has to do with the fact that the serial number in settings is different from the one on the bottom of the tablet (the one on the sticker). Unfortunately for me, there is no way to change the internal serial number without being rooted, and no way to root on JB (for now) without being unlocked.

reffu said:
If you're already on 10.4.2.17, upgrading to 10.4.2.18 won't affect your ability to unlock. Some people (like myself) are unable to unlock for unknown reasons, but upgrading from .17 to .18 shouldn't make a difference(10.4.2.18 doesn't really change much). If you're able to unlock, you should be able to do it on either .17 or .18. If you're unable to unlock, you then wouldn't have been able to do it on either version.
Click to expand...
Click to collapse
you say you are unable to unlock can you tell me why? I was on ics and upgraded and now on .17 and wanted to unlock everywhere I look I find a file .13 but nothing for .17 or 18

danyal241 said:
you say you are unable to unlock can you tell me why? I was on ics and upgraded and now on .17 and wanted to unlock everywhere I look I find a file .13 but nothing for .17 or 18
Click to expand...
Click to collapse
Go to:
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Under choose OS , select android, go to utilities, the second file should say "Unlock Device App: Unlock boot loader." download the file, copy it to the tablet and open it in file manager. If you have install from other sources enabled it should bring up an install dialog and install an app called unlock tool. Open this app, scroll and click through all of the terms of agreement, and click unlock, If its going to work, this is where the unlock will happen.

reffu said:
Go to:
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Under choose OS , select android, go to utilities, the second file should say "Unlock Device App: Unlock boot loader." download the file, copy it to the tablet and open it in file manager. If you have install from other sources enabled it should bring up an install dialog and install an app called unlock tool. Open this app, scroll and click through all of the terms of agreement, and click unlock, If its going to work, this is where the unlock will happen.
Click to expand...
Click to collapse
Thanks could you also point me to which file I need to flash and how to obtain root?
Sent from my LT18i using xda app-developers app

[Video Guide] How To Root Galaxy S4 I337 / I337m Easy & User Friendly

Hey folks. It's me again :victory: So I've got another super easy video guide on how to root your shiny new Samsung Galaxy S4 I337 or I337m.
This guide is using djrbliss's Motochopper tool. This tool has made it easier than ever to root a device! So BIG thanks goes out to him!
Links to everything can be found in the video description.
Enjoy

Here is a couple of more. I figure its better to keep them all in one place so people can decide which guide they want to use.
http://forum.xda-developers.com/showthread.php?t=2257039
http://forum.xda-developers.com/showthread.php?t=2257058
I think there might be a couple more out there but this should help people to answer any possible question about rooting that they could ever have.
If you have the AT&T OTA (MF3) for the SGH-I337 S4, the method in the OP does not work. Here is a method for rooting MF3:
http://forum.xda-developers.com/showthread.php?t=2387577
For Canadian MG1 Firmware, try CF Auto-Root download for the SGH-I337M:
http://forum.xda-developers.com/showthread.php?t=2293800

Just sold my Rogers S2 LTE because I upgraded to the S4. My quick question, if I ROOT and retain the original Samsung Recovery will I be able to still get and do official firmware upgrades? This is the only thing stopping me from going forward with rooting.

You can still get updates, but you will loose your root access with each update.

thanks: im now rooted and sim unlocked for free!

Slade8525 said:
thanks: im now rooted and sim unlocked for free!
Click to expand...
Click to collapse
Hey, how did you sim unlock it for free, do you mind sharing?

yeah sure!
similar method worked for my GS III; havent tested the GS IV with different sim just yet but GF's old GS III is working just fine for her sister in Canada (Bell i think). GF found it actually, and did it to hers 1st. ill know if it works when we leave for work in Montreal next week or if i bum a t-mobile cell from a friend.
http://forum.xda-developers.com/showthread.php?t=2282683

Stoneyguy said:
You can still get updates, but you will loose your root access with each update.
Click to expand...
Click to collapse
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.

Whenever I try this method, when it goes to push the exploit, it says error multiple devices or something. when I only have the S4 plugged in. Followed step by step.

Dragosmp said:
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.
Click to expand...
Click to collapse
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.

Stoneyguy said:
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.
Click to expand...
Click to collapse
Could you post a link to where it shows how to regain the status will maintaining the root?

rsarwar said:
Could you post a link to where it shows how to regain the status will maintaining the root?
Click to expand...
Click to collapse
The link has already been posted on the first page.

thanks worked great just rooted min in 5 min

Safe to root?
Excuse my ignorance, but on another thread it was suggested that in the absence of recovery and a backup image rooting might be premature. Is the general consensus now that it is safe to root? There seems to be some backup images around thought I don't know if they have been tested, and I haven't heard about recovery.
sblevine

Newbie here... couple of questions
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:

speed2001 said:
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:
Click to expand...
Click to collapse
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.

Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Cool, thanks for the reply. I was under the impression that the bootloader was already exploited. Pure BS those protections that always end up broken like the IOS ones. What I would like is to have the S4 as factory released and load a good ROM without any problems and no bloatware. If not for the warranty I would buy an unlocked phone elsewhere.
Well, let's wait for the exploit next week. I don't want to brick my phone and not able to restore it. I will keep checking back.
Cheers and thanks again
Speed

Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference

rsarwar said:
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference
Click to expand...
Click to collapse
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.

zekeblue said:
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.
Click to expand...
Click to collapse
Your assumptions are correct:
1. Yep.
2. Yes, you can delete busybox and su in your system directory to get your phone switch your phone from "Custom" to "Official" status. If you install SuperSu and remove Superuser you can have root while keeping "Official" status.
3. Correct.
4. If you **** up while messing around with root you can recover to stock ROM via Odin or Kies. There is no reason to wait for root.
To answer your questions.
1. No, nothing changes. You just enable superuser privileges.
2. Typically yes. Don't accept OTA's until your know they're safe.
3. It depends if they patch the exploit or not.