I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Nope, can't root w/o unlocking bootloader anymore.
Sent from my Nexus S using XDA App
If it means anything, u can re-lock the bootloader just as easily as u can unlock it.
Also, u can unlock and root without messing with baseband or kernel.
Sent from my Nexus S
anishs said:
I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Click to expand...
Click to collapse
You don't have to change any of those things with an unlocked boot loader. Unlocking the boot loader does only one thing, unlock the boot loader. It doesn't need a custom rom. You don't even have to install a custom recovery if you don't want to.
All stock OTAs will continue to work as well - it will just allow you to load a custom recovery and the su binary if you please, with the ability to relock at any point in the future if desired.
One of the features of the nexus line of phones (and upcoming unlockable boot loaders) is that you aren't reliant on finding an exploit to elevate privileges in order to gain root access - you simply unlock the boot loader and you are free to do as you please (or not do if you choose).
Have a look here
This method
http://forum.xda-developers.com/show....php?t=1479831
worked perfectly on my i9023 running stock ICS.
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
I just unlocked the bootloader to install twrp and maybe magisk i wanted to also try the Android P dev preview. but i know having a unlocked bootloader is a security risk also your get that warnign message at boot which makes booting up longer,is there a way to lock and unlock without losing data if im root.
Unlocking and locking wipes all data by design.
Telperion said:
Unlocking and locking wipes all data by design.
Click to expand...
Click to collapse
Is there a way to make the device secure with it having a unlocked bootloader?
With an unlocked bootloader, anyone can install a factory image, which wipes all your locks and your google account (and, therefore, defeats FRP), which is what makes it insecure. The only way to avoid that is to have a locked bootloader (and USB debugging off). (And I've seen reports here that unlocking the bootloader, installing TWRP and Magisk, then locking the bootloader, results in a hard brick (meaning buying another phone, because Google won't replace it)
Run with the unlocked booloader, don't ever leave the phone off your person and have "insurance" that replaces stolen (and possibly lost) phones.
I am aware that there is already a thread for unlocking Bootloader on Android 8.1.0, but I tried the steps in that article and it unfortunately was unable to unlock my device. I bought my Pixel 2 secondhand, but because the OEM Unlocking toggle in Settings is grayed out and in the off position, I am led to believe that I have a Verizon model. I have an AT&T SIM card however. I also tried looking up how to downgrade my phone to the Google version of Android 8.1.0 but they all require that OEM Unlocking be turned on. Is there any updated guide on how to unlock the Bootloader for my phone so that I can possibly root it?
Not right now but there is an interesting vulnerability out right now.... I'd turn off updates for a little while incase something arises
Unlocking the bootloader is a totally different prospect than gaining root. Root can be obtained with an exploit, the recent one being a good example, but it will only be temporary. To make it permanent you need to unlock the bootloader. To unlock the bootloader you need yet another exploit for the bootloader since all the refurbished models appear to be unable to use the factory unlock process. Combine that with low demand for a two year old device and odds are it will never happen unless Google itself provides a solution. In short, I wouldn't hold my breath or leave a giant security hole on your device in hopes that it can be bootloader unlocked in the future. If you need a device that can be bootloader unlocked, go to Google and buy one.
***Unlocking the bootloader is a totally different prospect than gaining root.
Agreed
***Root can be obtained with an exploit, the recent one being a good example, but it will only be temporary.
Not always true, there have been many roots that didn't require bootloader unlock. Towel root comes to mind also many sunshine roots and countless others.
***To make it permanent you need to unlock the bootloader.
It helps a lot but see above....
*** To unlock the bootloader you need yet another exploit for the bootloader since all the refurbished models appear to be unable to use the factory unlock process. Combine that with low demand for a two year old device and odds are it will never happen unless Google itself provides a solution. In short, I wouldn't hold my breath or leave a giant security hole on your device in hopes that it can be bootloader unlocked in the future. If you need a device that can be bootloader unlocked, go to Google and buy one.
I don't want to buy a other phone..... The first one I bought was supposed to be unlockable. I'll deal or hope. The security hole really doesn't worry me at the moment. I won't leave it open permanent.
After thinking about it, the a/b partition may throw a serious monkey wrench in the full root issue.
Is there a way then to root my Android without turning on OEM Unlocking? My limited research on this makes me conclude that there's no such method for the Google Pixel 2.
Right now there is a temp root.
mrkhigh said:
Right now there is a temp root.
Click to expand...
Click to collapse
Would you be able to provide a link on how to do a temporary root on the Pixel 2?
I believe if you read the whole thread one person said it worked on the p2.
Careful though, change system they say it bricks the phone.
https://forum.xda-developers.com/pi...-magisk-root-vzw-pixel-2-xl-xl-t3981423/page5
Hello. What's the easiest way to backup everything (and I mean everything, including detailed app data) before unlocking my bootloader? I want to flash a custom kernel with minimum modifications to anything else, and obviously I want to take a backup of everything before I lose them with the unlock process, but I haven't been able to find a way to do so on a stock ROM that's not even rooted.
Or is there a way to root my phone before I unlock it?
I've never had a OnePlus device before, so here I am, asking dumb questions. :silly:
Also, one more question (in three parts, sorry!): since some of the newer apps, especially banking apps, have started using stricter safety procedures, they can detect an unlocked (or even merely rooted) device, and so they don't work. 1) Is there any way I can use a custom kernel on a locked (or relocked) bootloader? 2) Is it possible to use a custom kernel on an unlocked phone that's not rooted? 3) If neither of the two is possible, how can I prevent said apps from detecting my unlocked bootloader and rooted phone?
Thank you very much in advance for taking the time to answer all of my questions.