Database Develop

[Q] Best way to get off of 5.1 LMY47D?

Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!

you can always use fastboot to go back to 5.0.1

stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?

i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.

simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.

gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.

EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.

EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.

Sweet, successful downgrade!

I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!

Disregard! Got it handled. Thanks guys!

Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1

EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??

Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?

Help, I want to Relock my Bootloader

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.

v21: Root/Unlocked Bootloader + TWRP?

Hi! When I got my R1 HD, I wanted to get Lineage OS and TWRP. I tried everything including:
adb "fastboot oem unlock",
SP Flash Tool, and
DirtyCow R1-HD Tool,
yet I found no luck. Does anybody know how to get an unlocked bootloader and TWRP on an R1 HD v21? Thanks!:good:
P.S:
My "Custom build version" is:
BLU_R0011UU_V21_GENERIC. Also, this is not the Amazon Prime variant, however I got this from Amazon (for example: I get no ads).

Sorry to tell you, but version 21 of the ROM cannot be bootloader unlocked or rooted. The more recent updates have secured the phone so that none of the previous methods you mention work anymore. The phone is no longer being manufactured and Blu does not provide a process for unlocking the bootloader as some other companies, like Motorola, do. So even though you paid more to get the no ad version, you can't root it. 8-( This was only possible in the earlier versions of both the amaon and non-amazon models.

yaconsult said:
Sorry to tell you, but version 21 of the ROM cannot be bootloader unlocked or rooted. The more recent updates have secured the phone so that none of the previous methods you mention work anymore. The phone is no longer being manufactured and Blu does not provide a process for unlocking the bootloader as some other companies, like Motorola, do. So even though you paid more to get the no ad version, you can't root it. 8-( This was only possible in the earlier versions of both the amazon and non-amazon models.
Click to expand...
Click to collapse
So, can I revert back to an earlier version of the ROM where it is possible to unlock the bootloader?

PastThePixels said:
So, can I revert back to an earlier version of the ROM where it is possible to unlock the bootloader?
Click to expand...
Click to collapse
no, the signed updates are incremental so, the checksum verification will pervent flashing old version

OK.... What's the best thing to do now?
I found this option in my updater that says "Local updates". Maybe this can help?

PastThePixels said:
OK.... What's the best thing to do now?
I found this option in my updater that says "Local updates". Maybe this can help?
Click to expand...
Click to collapse
No, sorry - there is no known way to root or flash modified software after the phone has been upgraded with factory software. You can't go back. And, even if you could, it wouldn't help - it still couldn't be rooted or flash a modified ROM. Blu does not offer to unlock bootloaders the way some companies, like Motorola, do. Your phone is stuck with what you have now.
The best thing to do now? Enjoy your cheap android phone with great performance for the price!

yaconsult said:
No, sorry - there is no known way to root or flash modified software after the phone has been upgraded with factory software. You can't go back. And, even if you could, it wouldn't help - it still couldn't be rooted or flash a modified ROM. Blu does not offer to unlock bootloaders the way some companies, like Motorola, do. Your phone is stuck with what you have now.
The best thing to do now? Enjoy your cheap android phone with great performance for the price!
Click to expand...
Click to collapse
Well, is there at least a way to skin the phone (ex: change bootanimation, remove bloatware (Yes, there is still bloatware apps, and I'm talking REMOVE the apps, no uninstall for user only), remove the Adups spyware) so that it is just like stock Android?

PastThePixels said:
Well, is there at least a way to skin the phone (ex: change bootanimation, remove bloatware (Yes, there is still bloatware apps, and I'm talking REMOVE the apps, no uninstall for user only), remove the Adups spyware) so that it is just like stock Android?
Click to expand...
Click to collapse
No - all those things require root, which you can't get. Only the phones that were shipped with earlier versions of the ROM and hadn't been updated over-the-air could be unlocked and rooted.

Related. I have an 8GB phone; Custom build:
BLU_R0010UU_V8.7_GENERIC 05-08-2017
I've been trying to install TWRP (and then Lineage) but I'm having zero luck with SPFlash. I've tried on a couple of computers and followed the directions step by step. Am I missing something here?
Thanks,
Edit: yep, saw in another thread anything above 8.1.
Imma email Blu and see if they'll loosen the restrictions if they're stopping development. Can't hurt at this point.

Upgrade to Android 7.0 with EMUI 5.0

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)

Question how to relock the bootloader?

hi guys ,
i want to make my oneplus 10 pro 2213 model back to store condition
how can i lock the bootloader?
i cant find any answer anywhere and im not sure if fastboot enhancer is the solution
my device is fully work btw
thanks

it's highly recommended that you don't do that. Most of the devices I've seen get brincked in that operation.
But if you wanna proceed with that, you have to flash the stock image back again, there must be no changed image (boot, recovery, system...).
And then you can run the command "fastboot flashing lock"

what about msm tool
anyway to do that with the tool ?

There is no tool current available to O10PRO, all there is require username and password.
A lot of people, myself included, are waiting for a msm tool so we can fix our devices.

OK
so if my bootloader is unlocked any problem for gpay ota ect?

It may not work .. Netflix doesn't work for example. Gpay as I don't use can't say for sure

sagiag said:
OK
so if my bootloader is unlocked any problem for gpay ota ect?
Click to expand...
Click to collapse
No unlocking the bootloader will not effect gpay or any other banking app. Now if you are rooted then yes gpay and banking apps will not work. You will have to use Magisk to fix that.

Well I'm not sure
foamerman said:
No unlocking the bootloader will not effect gpay or any other banking app. Now if you are rooted then yes gpay and banking apps will not work. You will have to use Magisk to fix that.
Click to expand...
Click to collapse
Well
I'm not rooted at all
But gpay is not working
Also Netflix is not findable in the store anymore

sagiag said:
Well I'm not sure
Well
I'm not rooted at all
But gpay is not working
Also Netflix is not findable in the store anymore
Click to expand...
Click to collapse
That could be the difference between the 2213 and 2215. I got my 15 from OnePlus carrier unlocked. That's the first thing I did was unlock the bootloader. Now my gpay, paypal and my banking apps all work. I'm not rooted yet I'm just waiting on a full rom update to get the boot.img. But I see that OnePlus is going to post oxygenOS 13 today. I might check it out. OnePlus has really done a number to the 10 this time. As for as Netflix I think there is a thread in here some place.

Hi guys
Anything new in the MSM tools?
Or maybe any other way to lock the bootloader?

look on GitHub for fastboot enhanced works really great as long your in de bootloader you can do every command with just a click i was thinking on doing that my self to but then i saw something's what i want to try out and there is also a fastboot ROM in the forums maybe that you help you too

Thanks !
I will read about that!

i have the same question.
I have a NE2213, unlocked and rooted and now want to sell it.
So my plan was to uninstall Magisk with all Modules, do a factory reset, update to NE2213_11_A.16 and then relock the bootloader.
since i am only rooted with stock rom - the only changed image should be the boot.img which will be stock after i update zo A.16.
Should be right, isnt it?
since my only other option ist to contact the support for a online MSM-Tool, which i need to do anyways when it does not work - i would give it a try...

n0gg said:
i have the same question.
I have a NE2213, unlocked and rooted and now want to sell it.
So my plan was to uninstall Magisk with all Modules, do a factory reset, update to NE2213_11_A.16 and then relock the bootloader.
since i am only rooted with stock rom - the only changed image should be the boot.img which will be stock after i update zo A.16.
Should be right, isnt it?
since my only other option ist to contact the support for a online MSM-Tool, which i need to do anyways when it does not work - i would give it a try...
Click to expand...
Click to collapse
Fastboot commands for restoring to stock worked for me.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
FYI - Was able to lock the bootloader on my OP 10T, A.06 Oxygen OS.