Related
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.
Trying to downgrade from Android N preview 2 back down to 6.0.1, but after it downloads the update won't verify. I have a locked bootloader and the option in developer options is grayed out. Any help?
blakemoore111 said:
Trying to downgrade from Android N preview 2 back down to 6.0.1, but after it downloads the update won't verify. I have a locked bootloader and the option in developer options is grayed out. Any help?
Click to expand...
Click to collapse
Did you try doing oem unlock in bootloader? Not sure exactly but I remember reading that the option was greyed out because it was set to permanently on to avoid issues like they had with the first preview OTA
StykerB said:
Did you try doing oem unlock in bootloader? Not sure exactly but I remember reading that the option was greyed out because it was set to permanently on to avoid issues like they had with the first preview OTA
Click to expand...
Click to collapse
Yeah I tried that and it failed after telling me that I needed to check the allow OEM unlock in dev options.
StykerB said:
Did you try doing oem unlock in bootloader? Not sure exactly but I remember reading that the option was greyed out because it was set to permanently on to avoid issues like they had with the first preview OTA
Click to expand...
Click to collapse
That`s why first and foremost you always unlock your bootloader when you get a phone, just to avoid these kind of issues. I guess you have to turn it in for RMA or repair to get it running or replaced, it should be covered by warranty though as its a Google software failure.
Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?
RacerXO said:
Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?
Click to expand...
Click to collapse
Hello... Why do you specifically ask about Nougat? Unlock/relock is not firmware dependant..
Something to read just in case you didn't find it when you searched: https://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Good luck...
RacerXO said:
Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?
Click to expand...
Click to collapse
And why do you want to relock? Paranoid about security? Keep your phone in your pocket.
All advice in XDA is not to relock your bootloader because it reduces the possibilities of recovering if you ever make a mess of an update.
dahawthorne said:
And why do you want to relock? Paranoid about security? Keep your phone in your pocket.
All advice in XDA is not to relock your bootloader because it reduces the possibilities of recovering if you ever make a mess of an update.
Click to expand...
Click to collapse
I want to relock my bootloader so I can use Android Pay.
5.1 said:
Hello... Why do you specifically ask about Nougat? Unlock/relock is not firmware dependant..
Something to read just in case you didn't find it when you searched: https://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Good luck...
Click to expand...
Click to collapse
Thanks for the reply, I read it and didn't know if it would work on Nougat.
RacerXO said:
I want to relock my bootloader so I can use Android Pay.
Click to expand...
Click to collapse
Just install a custom Kernel that "kind of" hide your unlocked bootloader. EX Kernel, Franco and some others will be just fine. Android Pay will work... I would never lock the bootloader of mine, except for RMA purpose. If something fails, you have way more chance fixing it..! :good:
RacerXO said:
Thanks for the reply, I read it and didn't know if it would work on Nougat.
Click to expand...
Click to collapse
Yeah don't worry, it's still a Nexus
RacerXO - did you get Android Pay to work on the N6F26U Build? I also cannot get the bootloader to relock. I tried using WugFresh Nexus Root Tookit v2.1.9.
Did you install a custom Kernal? Wondering if this the answer. Thanks for the help.
I was unlocked from the first day I got the phone. Today I am locked, running nougat. Having read some of the horror stories here, I've always booted the phone after flashing updates before rooting. Did the same thing when I went back to stock to use AP. I backed everything I wanted to keep and made sure it booted, before I locked the bootloader. No issues after almost a month.
What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates (thru April 2017) was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.
voyageurs60 said:
RacerXO - did you get Android Pay to work on the N6F26U Build? I also cannot get the bootloader to relock. I tried using WugFresh Nexus Root Tookit v2.1.9.
Did you install a custom Kernal? Wondering if this the answer. Thanks for the help.
Click to expand...
Click to collapse
Rooting with Magisk then using Magisk manager to "hide" root should give you android pay again. This may not be the directing you want to go in, but it is an option.
I locked Bootloader but you have to flash stock recovery 1st
I was on stock 7.1.1 unlocked bootloader, rooted Nexus 6.
I relocked my bootloader by simply going into adb/fastboot and flashed the latest stock factory firmware image (not the ota) with the June 5, 2017 security update, rebooted, activated developer options and enabled usb debugging, adb/fastboot again, and entered the command "fastboot oem lock", hit okay/yes when I got the relock warning, and voila! phone relocked.
Rebooted and set up phone/reinstalled my apps, music, and files.
No issues.
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
md sabuj said:
I have rolled back from Anddroid 7.0 Nougat with EMUI 5.0 to Android 6.0 with EMUI 4.1.1, Now i want to go back to latest Android 7.0 , I dont know how to do it. Update app/HiSuit/HiCare app Says no update available.
My current Build is EVA-L19C185B180
Click to expand...
Click to collapse
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
zgfg said:
Download from Firmware Finder and install by DLOAD FullOTA-MF-PV (PV is important) EVA-L19c185b385, as on the screenshot
Or, follow the guide to rebrand to c432 and upgrade to Noogat (unlocked Bootloader is required):
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Click to expand...
Click to collapse
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
md sabuj said:
I have successfully upgraded to Android 7.0 Nougat by the help of firmware finder app .
My current Build is EVA-L19C185B403.
Is there anyway to upgrade to Oreo without unlocking Bootloader? I don’t have a card to buy code from DCunlock.
Click to expand...
Click to collapse
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
zgfg said:
No, you cannot flash TWRP and from TWRP the oeminfo and no-check recovery, network patch... without the unlocked Bootloader
Click to expand...
Click to collapse
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
md sabuj said:
I have found some videos and Threads saying some Huawei's Tool can read Bootloader Code.
Is it true?
Click to expand...
Click to collapse
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work
Click to expand...
Click to collapse
Thank you?
zgfg said:
I don't know anything about 'some' such tools
DC Unlocker for 4 Euros will work for EMUI 5
Click to expand...
Click to collapse
How much credits I have to buy from DC Unlocker for bootloader code?
md sabuj said:
How much credits I have to buy from DC Unlocker for bootloader code?
Click to expand...
Click to collapse
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have contact page and ask them directly
zgfg said:
4 Euros was enough for me two years ago (also P9).
Don't know if prices changed, but they have a contact page and ask them directly
Click to expand...
Click to collapse
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
md sabuj said:
Brother, I have bought 4 credits from Dc Unlocker and successfully read Bootloader Code, Now will you please guide me on how to unlock the bootloader and rebrand for upgrading to Oreo?
Click to expand...
Click to collapse
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
zgfg said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Code:
fastboot oem unlock <your code>
If not familiar, and if not clear as below, search on Google how to:
- enable Developer menu by clicking 7 times to the build number in Settings/About
- enable OEM unlock in Developer menu
- install "Minimal ADB and Fastboot" to Windoze (smallest, self containing package with everything for ADB and Fastboot)
- reboot to Fastboot: keep pressing Vol-, then Pow button
Unlocking Bootloader triggers hard-reset, wiping also Internal memory. Backup as much as you can - use Google account, HiSuite, WA own chat backup, copy DCIM to PC, Contacts can be exported to vcard file, etc
Rebranding to AL10c00, upgrading to b540 Oreo, applying the neccesary Network patch to make SiM card(s) working - all is in deep details explained in the OP posts:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Read two times before you start, and keep the instructions opened on the PC while doing - wrong moves can cause (soft) bricks
Click to expand...
Click to collapse
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
md sabuj said:
First, keep your code (on several places, even printed on the paper), it is good for relocking/unlocking (you never know, some actions may lock the Bootloader back) for the lifetime of your phone.
You don't want to go buying the same thing again
Assuming you know how to enable OEM Unlock in Developer's menu and you are a little familiar with Fastboot, it is simple to unlock the Bootloader
Thank you, Brother, I have done all procedure and my device is now at Oreo, Build EVA-AL10 8.0.0.540(C00).
After doing all the required steps I have flashed Huawei's Official Recovery and enabled OTA, after that I have received an OTA update of 3 MB, Should I install the update or not?
SCREENSHOT
https://drive.google.com/file/d/1s9c7zZoN8fJ3Xq62DW1GAL2P_9maq1Bn/view?usp=sharing
Click to expand...
Click to collapse
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I have already applied Network Patch, See my both SIM is working.
Right now I don’t need Root so I'm skipping Magisk.
I just want to disappear the update available Notification, if the update is Safe I'll go for it.
zgfg said:
It is safe, just some Patch02 (never found exactly what for).
If you don't mind, you can skip (you can disable OTA - see in OP)
If you go for, you must first flash back the stock Recovery, hence not having TWRP. Not sure anymore, maybe also stock Ramdisk, hence not Magisk
Patch02 will not affect Network Patch or Face Unlock (cool add-on, see OP)
If you didn't apply Network patch yet, etc - then accept Patch02 and continue with OP instructions.
If you already rooted by Magisk, then don't bother with Patch02, too much trouble preparing clean sheet for OTA and rooting again
Click to expand...
Click to collapse
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
md sabuj said:
I'm from Bangladesh, some Operator in our country introduced VoLTE.
It seems there is an option called VoLTE after upgrade to Oreo. Is it really works?
Click to expand...
Click to collapse
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
???
zgfg said:
Nope, VoLTE does not work.
Everything else, like location sharing and Ok Google are fixed with Network patch, but not VoLTE.
The guy who did the whole majestic work went tired (although he believed he was close to fix VoLTE) and gave up. Later he upgraded to newer Huawei devices with Pie, etc, and eventually moved away from XDA
Click to expand...
Click to collapse
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
md sabuj said:
Brother, How to remove the warning when Phone boots "Your device has been unlocked and can't be trusted"??
Click to expand...
Click to collapse
It's not possible to remove the warning on booting "Your device has been unlocked and can't be trusted" (IMO, it must have been commented somewhere in the OP) - that's price for the unlocked Bootloader.
But you must not relock Bootloader - it would trigger Hard reset, removing Network patch (even worse, it could also cause soft brick if TWRP or Magisk are installed)
15 credits for unlock in fastboot mode (not pay over sms)
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.