I need to root, unlock, and install CWM right? How exactly do I do this? I tried to locate a how to without any luck.
The dev section is filled with all the info you need to know.
Also, not trying to be a **** but saying you searched when it is obvious that you didn't will get you nowhere.
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
johnl199 said:
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
Click to expand...
Click to collapse
Some of the roms, prior to the unlock discovery, were executable as an RUU. All the updated versions require recovery which you need the bootloader unlocked to get in to. It's a painless process and there's even a 1-Click script method for those who dont want to take chances.
Will I be able to get the phone back to COMPLETELY stock should I decide to sell it in the future?
From what I know it will say relocked or tampered but maybe I'm wrong
Sent from my HTC One X using xda premium
After unlocking your phone, there will be no way to get back to 100% stock unless we can get S-OFF (which hopefully may be in the near future due to a few devices already being S-OFF).
However, you can root your device and not unlock it (1.82 and prior as of now) and still be able to revert to 100% stock as if it came right out of the box.
Most of the ROMs currently do not require an unlocked bootloader.
However, this will definitely change as we begin to see custom kernels (hopefully soon with the release of the source by HTC Dev) and more complex ROMs (such as those based on AOSP, such as CM9 and AOKP).
So in short, you can still use most of the ROMs in the dev section. Just be aware however that if you do not unlock then you cannot install CWM (limiting the number of ROM options) and also if you update past 1.82.502.3 then you cannot root (at this time, other root exploits are being explored).
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
lamenramen said:
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
Click to expand...
Click to collapse
Nope. You are thinking of SIM unlock.
Bootloader unlock lets you load custom ROMs and change recovery, that's all.
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
There are many threads about how to unlock and root but things get old much fast, I feel like FAQ is too old to follow.
I prefer ask before make same thing wrong.
I have a Moto G 4g with lollipop locked and orginal, so I decide to put new thing now because same things are annoying me in the phone, I think xposed can help me well, so I only need unlock and put root, but need to know the last way to do this, I know unlock is easy but what recovery to flash and how? What I need to root? Is there same problem with xposed in lollipop?
I did come from Razer D3 mediatek, had not unlocked bootloader but was easy to root and te best way to custom was with xposed, so im more "acquainted" with this.
any help on this would be appreciated.
Please someone answers!!
If your phone is not retail and your carrier locked your bootloader, it's not currently possible to unlock the bootloader or permanently root it. You can only temproot it currently.
If you want to flash a recovery your bootloader must be unlocked. You cannot flash anything with a locked bootloader. But if you wish to know, you can use TWRP or CWM for peregrine phones.
I am thinking of getting an S6 and i wanted a rootable phone. i see a root method available but no bootloader unlock and yet i see ROMs available. how does this work. i thought bootloader needed to be unlocked in order to do custom ROMs. Or is htere a verizon bootloader unlock available i could not find?
johnbravado said:
I am thinking of getting an S6 and i wanted a rootable phone. i see a root method available but no bootloader unlock and yet i see ROMs available. how does this work. i thought bootloader needed to be unlocked in order to do custom ROMs. Or is htere a verizon bootloader unlock available i could not find?
Click to expand...
Click to collapse
There is not and 99% chance there will never be a bootloader unlock. Root method no longer works in later versions of android. The bootloader does not need to be unlocked with a custom recovery.
I apologize for not diligently searching as I should, I came across this asking the same more or less as I was.... I have one sitting on lrx22g.g920vvru1a0c3 which if I read the root method correctly I can root... At that point you say that the boot loader doesn't need to be unlocked so I can ( mfastboot flash recover xxxx.IMG ) on a locked boot loader? Or use rashr ? And after which we can ROM it?... Could I then theme it as well? I am coming for Motorola's all I've ever had/used/touched ever.... Running stock do I need to deodex it to be able to theme it? Do we have firmware out there n a tool (like Moto's rsd lite/ house of moto) to flash it with? With unlimited data is there a mobile hotspot mod/hack use utilize the baked I hotspot app? Can I still pull system apps theme um zip um and flash up.... Not having the Sim card yet I can really play with it as I wish to ... I just powered it on and its asking for an update... So I figured it'd try to root it now as there's no unlock for it..... Thank you kindly for your time and information
OE2 is the latest firmware that is rootable. Once rooted, you can flash a custom recovery and load roms through that.
There is a rooted S6 available for sale on swappa right now, just so you know
So I sold my s8+ g955fd seexynos to this guy for a really good price.
My s8+ was rooted with magisk and bootloader was unlocked.
But this guys wants it unrooted and wants the bootloader to be locked so that he can have the ota updates working. And if I fail to do so (which I am at the moment), I would have to return the money (which I dont want to).
I tried flashing stock rom (latest from Sammobile) from the scratch with Odin but still when I check with Intercept X app, it says bootloader unlocked. and I checked in developer options too, the oem unlock is greyed out and set to off and says "bootloader is already unlocked".
Could someone please guide me with working steps please? I am good with flashing and stuff.
I tried searching the s8+ forum but couldn't find anything helpful.
Need urgent help. :foldedhands:
Edit 1: now the OEM unlock is gone from developers options after flashing magisk again :scared:
Edit 2: After uninstalling magisk from magisk manager app
, phone went to bootloop. So I flashed stock rom "bl,ap,cp,csc" with odin again and the greyed out oem unlock is back with status "bootloader is already unlocked"
Any hint guys?
Just a hint would be enough!
Its a one way process from what I understand.
Anybody will want it locked because without it locked you cant use Knox or any of the payment apps that depend on Knox.
I could be wrong but this is what I feel.
RonChinoy said:
Its a one way process from what I understand.
Anybody will want it locked because without it locked you cant use Knox or any of the payment apps that depend on Knox.
I could be wrong but this is what I feel.
Click to expand...
Click to collapse
Already figured it out. I am sure that guy doesn't care about knox, but does care about ota updates