LG Bootloader Unlocking - G4 Q&A, Help & Troubleshooting

Hi Guys
Interesting one here, I have an CPW UK G4 but unable to unlock the bootloader, I checked out the device and it appears we have a fastboot setup very similar to the HTC needing a .BIN code.
Am i right in thinking that HTCs method will not work with this?

fkofilee said:
Am i right in thinking that HTCs method will not work with this?
Click to expand...
Click to collapse
tried on htcdev site and not working

fkofilee said:
Hi Guys
Interesting one here, I have an CPW UK G4 but unable to unlock the bootloader, I checked out the device and it appears we have a fastboot setup very similar to the HTC needing a .BIN code.
Am i right in thinking that HTCs method will not work with this?
Click to expand...
Click to collapse
Android 5.0 introduced a feature called 'Allow OEM Unlock'
Without it, i find it hard to unlock the bootloader.
If that doesn't work try to connect to adb and excute the command fastboot oem unlock

SimpleTool said:
Android 5.0 introduced a feature called 'Allow OEM Unlock'
Without it, i find it hard to unlock the bootloader.
If that doesn't work try to connect to adb and excute the command fastboot oem unlock
Click to expand...
Click to collapse
Already done all that welllllllllllllllll before posting this. It fails.

SimpleTool said:
Android 5.0 introduced a feature called 'Allow OEM Unlock'
Without it, i find it hard to unlock the bootloader.
If that doesn't work try to connect to adb and excute the command fastboot oem unlock
Click to expand...
Click to collapse
fastboot oem unlock it doesn't work.
Need unlock.bin file by LG : fastboot flash unlock unlock.bin

wolfgart said:
fastboot oem unlock it doesn't work.
Need unlock.bin file by LG : fastboot flash unlock unlock.bin
Click to expand...
Click to collapse
Have you enabled USB Debugging?
---------- Post added at 09:55 AM ---------- Previous post was at 09:51 AM ----------
fkofilee said:
Hi Guys
Interesting one here, I have an CPW UK G4 but unable to unlock the bootloader, I checked out the device and it appears we have a fastboot setup very similar to the HTC needing a .BIN code.
Am i right in thinking that HTCs method will not work with this?
Click to expand...
Click to collapse
Enter these commands correctly.
adb reboot bootloader[/FONT
fastboot oem unlock

SimpleTool said:
Have you enabled USB Debugging?
---------- Post added at 09:55 AM ---------- Previous post was at 09:51 AM ----------
Enter these commands correctly.
adb reboot bootloader[/FONT
fastboot oem unlock
Click to expand...
Click to collapse
this work for anyone ??

SimpleTool said:
Have you enabled USB Debugging?
---------- Post added at 09:55 AM ---------- Previous post was at 09:51 AM ----------
Enter these commands correctly.
adb reboot bootloader[/FONT
fastboot oem unlock
Click to expand...
Click to collapse
Bro, i'm not a noob....

We have to wait for LG to release the BIN code for us. Which, given that they included the "Allow OEM unlock" option, sounds like they will provide eventually.

WACOMalt said:
We have to wait for LG to release the BIN code for us. Which, given that they included the "Allow OEM unlock" option, sounds like they will provide eventually.
Click to expand...
Click to collapse
Need a root solution too...

wolfgart said:
Need a root solution too...
Click to expand...
Click to collapse
That's the point...

Follow what this says http://forum.xda-developers.com/g4/general/how-to-oem-unlock-lg-g4-t3107101

Related

Fastboot refusing to take commands after oem unlock

I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
RenaldiDroidXDA said:
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
Click to expand...
Click to collapse
I think your problem is you used 'fastboot oem unlock' instead of 'fastboot flashing unlock.'
Well, now I see the problem.
Now I need to know how to fix it .-.
RenaldiDroidXDA said:
Well, now I see the problem.
Now I need to know how to fix it .-.
Click to expand...
Click to collapse
did you enable usb debugging in developer options?
lucky_strike33 said:
did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I did. adb works quite well enough, but fastboot detects nothing.

Please remove this thread

Hey there Xda members !
I've been trying to unlock my Whyred since past few weeks, i don't know what I've done wrong but here's what I've done :
1. Opened Mi unlock page to request for bootloader Unlock permission (but there isn't any such thing)
2.it automatically showed Mi unlock tool and I've downloaded it on my computer
3. Installed Mi usb drivers
4. Ran Mi unlock tool and connected my device in fastboot mode ( I've already binded my mi account)
5. Mi unlock tool detected my device and i pressed on unlock anyway
6.and it loaded up to 99% and asked me to try after 360 hrs
7. After about 16 days i reopened mi unlock tool and pressed unlock
8. It loaded up to 99% and said "Unkown error"
Can somebody suggest me a solution.
Please devs.
Ashokk8 said:
Hey there Xda members !
I've been trying to unlock my Whyred since past few weeks, i don't know what I've done wrong but here's what I've done :
1. Opened Mi unlock page to request for bootloader Unlock permission (but there isn't any such thing)
2.it automatically showed Mi unlock tool and I've downloaded it on my computer
3. Installed Mi usb drivers
4. Ran Mi unlock tool and connected my device in fastboot mode ( I've already binded my mi account)
5. Mi unlock tool detected my device and i pressed on unlock anyway
6.and it loaded up to 99% and asked me to try after 360 hrs
7. After about 16 days i reopened mi unlock tool and pressed unlock
8. It loaded up to 99% and said "Unkown error"
Can somebody suggest me a solution.
Please devs.
Click to expand...
Click to collapse
did you have developer options
debugged usb
bootloader status ... need to bind account here
and unlock oem ticked?
I have same problem too. I've been installed driver and adb
I also click oem unlock and debugging before go to fastboot
will it be work on dev firmware?
raptorddd said:
did you have developer options
debugged usb
bootloader status ... need to bind account here
and unlock oem ticked?
Click to expand...
Click to collapse
Yes! I've done everything they needs to be done to unlock bootloader.
aoiyuuichi said:
I have same problem too. I've been installed driver and adb
I also click oem unlock and debugging before go to fastboot
will it be work on dev firmware?
Click to expand...
Click to collapse
dont need to anymore.. i did in global stable.
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
Ashokk8 said:
Yes! I've done everything they needs to be done to unlock bootloader.
Click to expand...
Click to collapse
no idea then. sorry good luck
Keep trying. Meybe it is server side problem.
---------- Post added at 19:07 ---------- Previous post was at 19:06 ----------
If it doesn't work you can try with a diffrent account, but you will need to wait another 360 hour.
fnldstntn said:
Keep trying. Meybe it is server side problem.
---------- Post added at 19:07 ---------- Previous post was at 19:06 ----------
If it doesn't work you can try with a diffrent account, but you will need to wait another 360 hour.
Click to expand...
Click to collapse
Ok
Please remove this thread, the problem got solved.
And the solution was?
I've done a factory reset and then again logged in when Mi account and again requested for unlock bootloader and a miracle it unlocked the bootloader. It took me about 40 days to unlock it.

(Re)lock bootloader on Huawei Mate 20x

Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!
Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /
thiagoserrao said:
Try this method
"How to Relock Bootloader via Fastboot
Setup ADB and Fastboot on your PC.
Connect your device to the PC, and open a command window on the PC.
Issue the following command to boot device into bootloader mode:
adb reboot bootloader
Now issue the following commands (any one) to relock bootloader. You don’t need to use all the commands given below. If any one works, stop there and follow the next step.
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Once bootloader is locked. Reboot your device with the following command:
fastboot reboot"
Font: theandroidsoul com / relock-bootloader-fastboot-android /
Click to expand...
Click to collapse
On fastboot oem lock... I get "Command not allowed".
On the other 2... "root type is risk".
Not working.
same here
So... No method to lock the bootloader once it is unlocked?!
Update through OTG. It will relock bootloader.
alexcraciun said:
Update through OTG. It will relock bootloader.
Click to expand...
Click to collapse
any one can verify this method ?
greets, Peter
why would you want to relock when everyone is trying to unlock it?
the re-lock and un-lock bootloader function,
is it the same as the OEM lock and unlock option in developer mode ?
pardon me if this is a noob question but i really
TIA
How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter
I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked
CCJ22 said:
I am looking to buy unlocked bootloader evrL29.
So if you wish to lock before you sell it there are many people willing to buy unlocked
Click to expand...
Click to collapse
sorry, sell my unlocked evr-l29 yesterday
greets, Peter
Anyone willing to sell unlocked bootloader EVR-L29 please DM me your price
alexcraciun said:
Hello,
How can I relock bootloader on Mate 20x? I have EVR-L29.
Thanks!
Click to expand...
Click to collapse
Relock your Bootloader with your Unlock Code.
Command:
fastboot oem relock your Code (16 character)
---------- Post added at 04:29 PM ---------- Previous post was at 04:23 PM ----------
greddy said:
How can i make an Full-OTA ? I have unlocked Bootloader, flash the stock erecovery back (with App Partitions Backup 2.2.1) and later i
flash the stock recovery over the twrp. And then ?
The erecovery download only the latest version (9.1.xxxx) but i like go back to my 9.0.xxxxx
in my dload directory i have three files: (its the 9.0.208 for EVR-L29)
update_sd_base.zip <- 3.7GB size
update_sd_cust_EVR-L29_hw_eu.zip
update_sd_preload_EVR-L29_hw_eu_R1.zip
What is now the next step ?
Update: dload-Method not function, long time at 5% and show "installing Update", then after 5 minutes : Reset!
greets, Peter
Click to expand...
Click to collapse
Use this File and Dload Method works
https://www.androidfilehost.com/?fid=6006931924117916589
letschky said:
Use this File and Dload Method works
Click to expand...
Click to collapse
Do I lose my data if I go back to 9.0?
KalleGermany said:
Do I lose my data if I go back to 9.0?
Click to expand...
Click to collapse
Yes,please Backup your Data!
i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition
BlvckSensei816 said:
i have a huawei mate 20 x emerald bootloader unlocked with resurrection remix rom running 9.0 android for sale
$250.00 good condition
Click to expand...
Click to collapse
No thank you.

Root method for Oppo A52

Hey everyone,
I have just purchased an oppo a52 and looking to find out if there is any root methods currently available. I have searched but unable to find any information about it.
Any help would be greatly appreciated.
Cheers
The first thing to look for is unlocking the bootloader which is not currently doable
Regarding unlocking the bootloader in the developer options menu it has an option for OEM unlock. Forgive me as I am very very basic at this type of stuff but would that have anything to do with unlocking the bootloader?
Nope that is not enough.
There should be access to bootloader first (usually through "adb reboot bootloader"), then the command for unlocking bootloader (usually "fastboot oem unlock" or "fastboot flashing unlock") should work. But none of this is available yet
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
cdroge said:
Regarding unlocking the bootloader in the developer options menu it has an option for OEM unlock. Forgive me as I am very very basic at this type of stuff but would that have anything to do with unlocking the bootloader?
Click to expand...
Click to collapse
whoknowshimself said:
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
Click to expand...
Click to collapse
I just spotted it on India's site: https://oppo-in.custhelp.com/app/software_update_detail/p_name/A52
I know nothing about rom development myself, but hopefully it gets some sort of custom rom support in the future
whoknowshimself said:
Nope that is not enough.
There should be access to bootloader first (usually through "adb reboot bootloader"), then the command for unlocking bootloader (usually "fastboot oem unlock" or "fastboot flashing unlock") should work. But none of this is available yet
Even the full ROM is not available on Oppo website yet. So nothing to develop here!
Click to expand...
Click to collapse
hey,
as said by Mango is it possible to root this phone now that we have the ROM?
https://support.oppo.com/in/softwar.../?productname=A52&series=A&modelMultilingual=
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
kuahnas said:
hey,
as said by Mango is it possible to root this phone now that we have the ROM?
Click to expand...
Click to collapse
We could try to unlock Bootloader via Fastboot..Then Patch the Boot.img from the Stock Rom With magisk and flash again via adb/Fastboot.
My concern...i have this Phone the First das xD
Skolotaie said:
https://support.oppo.com/in/softwar.../?productname=A52&series=A&modelMultilingual=
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
We could try to unlock Bootloader via Fastboot..Then Patch the Boot.img from the Stock Rom With magisk and flash again via adb/Fastboot.
My concern...i have this Phone the First das xD
Click to expand...
Click to collapse
I thought everyone said it's not able to be unlocked.
Although the setting is able to be changed in developer options. Has that only just been enabled due to an update?
So can we just enable the setting and run fastboot flashing unlock from fastboot. Backup before trying if someone does it.
it is not possible to unlock the bootloader.
The device is already over 6 months old, nothing else will happen.
With ColorOS11 many adjustments by Oppo disappear, it will be more like AOSP.
A first alpha of ColorOS11 went to the first 100 users last week.
Aren't these methods true?
Oppo A52 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Oppo with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
How to Root Oppo A52 Without PC & Via Magisk
Are you waiting to Root Oppo A52 CPH2061, CPH2069, PADM00, PDAM10? Follow our detailed tutorial with to guide process to gain Superuser privileges without TWRP Recovery.
www.thenextdroid.com
How to Unlock Bootloader on OPPO A52 Phone
Detailed instructions how to unlock bootloader on OPPO A52 phone with a full description
firmwarespro.com
Oppo CAN'T be UNLOCKED!

Unable to relock bootloader without receiving message that says "Your device is corru

Unable to relock bootloader without receiving message that says "Your device is corru
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
I was able to relock my 7T using fastboot. If you can boot to fastboot? In linux the command was 'fastboot flashing lock'. Not sure in windows if it's the same. Worked for me. Now 'OEM unlocking' option is visible again under system / developer tools. Prior to re-locking it was grayed out, unavailable.
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
v.konvict said:
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
Click to expand...
Click to collapse
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
TBHSilentAce07 said:
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
Click to expand...
Click to collapse
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
Click to expand...
Click to collapse
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
Click to expand...
Click to collapse
Being that this is Debian 9, maybe my fastboot is an old version as well. ADB and fastboot both seem to work pretty good though. No stinkin' USB driver issues like with Windows 10.
SenyorMauricio said:
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
Click to expand...
Click to collapse
xe0r said:
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
Click to expand...
Click to collapse
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
Thanks. Confirmed this works. Needed to install an older version (went with 10.0.8 global), then skipped through most of the setup minus wifi, did a system update to 10.0.12, reboot to bootloader, fastboot oem lock, and no more corruption errors.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
So to be clear, can a T-Mobile converted to Global be bootloader re-locked the same way without getting the corrupt phone boot refusal screen? The wife's phone refuses to lock, but haven't tried the update from OnePlus method above?
YES.

Categories

Resources