Database Info

How do I prepare my phone for roms?

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.

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

[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.

Is it worth rooting / flashing the Mate 9?

I love this phone and have had it for more than 2 years now, and have no plans of upgrading and will use it until it breaks down. Since I don't expect any updates any more, I was wondering if its worth rooting and flashing an Android 10 ROM (any recommendations?) this phone, especially since I want to use the Google camera that only works with Android 10. But as I read the guides and threads here, it seems rooting is more complicated than other phones.
So, is it worth it?

tukmulin said:
I love this phone and have had it for more than 2 years now, and have no plans of upgrading and will use it until it breaks down. Since I don't expect any updates any more, I was wondering if its worth rooting and flashing an Android 10 ROM (any recommendations?) this phone, especially since I want to use the Google camera that only works with Android 10. But as I read the guides and threads here, it seems rooting is more complicated than other phones.
So, is it worth it?
Click to expand...
Click to collapse
To flash a custom ROM you don't need root but unlocked Bootloader.
If you didn't obtain BL code when it was easy and free or cheap, that is now complicated and expensive (although still possible)- look at some other threads where people asked about flashing and it always comes down to the question about unlocking Bootloader

zgfg said:
To flash a custom ROM you don't need root but unlocked Bootloader.
If you didn't obtain BL code when it was easy and free or cheap, that is now complicated and expensive (although still possible)- look at some other threads where people asked about flashing and it always comes down to the question about unlocking Bootloader
Click to expand...
Click to collapse
I see. Thank you. Looks like I'm stuck with stock then. Thank you! It doesn't make sense to me to root if I can't flash anyway since I won't be able to get Android 10. The phone has excellent battery life and I have no complaints about speed. Unless there are benefits to just rooting that I don't know about?

tukmulin said:
I see. Thank you. Looks like I'm stuck with stock then. Thank you! It doesn't make sense to me to root if I can't flash anyway since I won't be able to get Android 10. The phone has excellent battery life and I have no complaints about speed. Unless there are benefits to just rooting that I don't know about?
Click to expand...
Click to collapse
Did I miss, but you didn't mention the most important fact - what is your EMUI version.
Supposing you are on 9.1 or 9.0 since you are asing about Android Q....
For rooting you must also flash (e.g. Recovery-Ramdisk patched by Magisk to get root, on EMUI 9), so it again comes down to the same problem about obtaining the Bootloader code (locked Bootloader prevents Fastboot from flashing) - to get a picture why is it complicated to obtain the BL code, please read like:
https://forum.xda-developers.com/mate-9/help/mate-9-reached-dead-t3978105/post80497731
https://forum.xda-developers.com/mate-9/help/hi-to-downgrade-firmware-versions-gpu-t3917826
However, you can still do useful modding without TWRP, root, custom ROMs - that is, without the need to unlock Bootloader, see:
https://forum.xda-developers.com/mate-9/help/modding-removing-bloatware-blocking-ads-t3971297

zgfg said:
Did I miss, but you didn't mention the most important fact - what is your EMUI version.
Supposing you are on 9.1 or 9.0 since you are asing about Android Q....
For rooting you must also flash (e.g. Recovery-Ramdisk patched by Magisk to get root, on EMUI 9), so it again comes down to the same problem about obtaining the Bootloader code (locked Bootloader prevents Fastboot from flashing) - to get a picture why is it complicated to obtain the BL code, please read like:
https://forum.xda-developers.com/mate-9/help/mate-9-reached-dead-t3978105/post80497731
https://forum.xda-developers.com/mate-9/help/hi-to-downgrade-firmware-versions-gpu-t3917826
However, you can still do useful modding without TWRP, root, custom ROMs - that is, without the need to unlock Bootloader, see:
https://forum.xda-developers.com/mate-9/help/modding-removing-bloatware-blocking-ads-t3971297
Click to expand...
Click to collapse
Awesome! Will look them up. Thank you so much! These are invaluable resources.

Question Re-lock bootloader after root?

Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Click to expand...
Click to collapse
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Connorsdad said:
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
Click to expand...
Click to collapse
Pixel Flasher will work fine for updating.

Lughnasadh said:
Not unless you want to brick your device.
Click to expand...
Click to collapse
Huh, learn something new every day I guess...

Lughnasadh said:
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Pixel Flasher will work fine for updating.
Click to expand...
Click to collapse
Awesome, thanks a lot for your reply, much appreciated.

never ever* lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
* exception

alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
And you can't flash a factory image to fix a phone on your own when it's soft bricked. It might have to go to a shop for repairs.

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/
Click to expand...
Click to collapse
AFAIK, relocking the bootloader requires wiping the device -- much like unlocking does -- and if you're unwilling to set everything (including anything on your /sdcard internal storage, not to mention all apps and their settings & system settings) back up from scratch (as any good complete backups require root access), this might not be what you wish to do.
And, if you had managed to successfully relock the bootloader, you could simply run the in-system update (OTA) that would update without wiping -- or even manually applying OTA from the recovery.
But there are hardly any benefits in re-locking the bootloader (after unlocking it) -- even if one was to a paranoid degree of security; which is the only major reason to (I can point you to the discussions that had taken place on it here, if you wish). If you don't want to run into any issues, you could simply run the stock ROM without root and be hardly impacted by it; with the added benefit of having the option to advanced recovery options and/or rooting options open to you in the future if need be...
alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
*it just occurs to me you meant to never lock bootloader because it limits options; not the risk of hard-bricking the device -- in which I wrote the following with that assumption. I'll leave the following comment as it is still sound advice, but I apologize in advanced that it doesn't quite relate to what you meant...
I mean, I feel doing Google's official Android Flash Tool is a safe enough method; it wouldn't do well if Google's own tool bricked their devices using their tool...at the very least the tool ensures that the stock factory firmware flashed matches the bootloader version and automates the fastboot commands so when re-locking the bootloader, it has the least potential to brick the device...

Exactly. there is no official flash tool from google, that's why I personally won't recommend to keep bootloader locked. If it's bricked with no working recovery mode, not even repair shop can fix it. all you can do is RMA to google get new device. no edl mode or anything else will help, fastboot is the official flashing method.
If you're referring to the "Android Flash Tool" that's no flash tool at all. I haven't tested it, but to me it looks like a WebUSB browser plugin. Reading the requirements it works with adb commands, usb-debugging and fully booted android is required. Therefore cannot unbrick devices.

Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?

iRhyiku said:
Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?
Click to expand...
Click to collapse
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.

Trippyy Doee said:
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.
Click to expand...
Click to collapse
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!

iRhyiku said:
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!
Click to expand...
Click to collapse
That's of course another aspect. Good point. If you rely on SafetyNet or it's successor Play integrity, do not unlock bootloader. AFAIR the latter one can't be cheated.

simplepinoi177 said:
But there are hardly any benefits in re-locking the bootloader (after unlocking it)
Click to expand...
Click to collapse
There are some benefits like some banking apps, streaming apps and games beginning to work. So it really depends on what is important for the user. I don't like flashing random mods to make apps work on rooted/ bootloader unlocked devices, primarily banking apps.