Develop Bugs

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have

Congrats! Would it work on the BV9000 HD version?

Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash

hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F

Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?

>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.

>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><

hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected

Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!

Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers

zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone

I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q

Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?

Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889

TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:

help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?

mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)

Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers

Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...

Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.

Moto G7 Power/Supra [All Versions] [Pie] Magisk Root Guide [OTA/SafetyNet Working]

Disclaimer: This WILL void your warranty. I am not liable for breaking/bricking your phone, you losing your data, or any nuclear war/other catastrophe. This process WILL totally wipe all data on your phone. Make sure you have a backup! You will also forever see "bad key" displayed in the top left of your screen for a few seconds after a reboot after unlocking the bootloader. There is currently no way around this that I'm aware of (let me know if you have a way)
This guide was assembled from mingkee's G7 guide here: https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
You will need:
1. Your Moto G7 Power (Any hardware version, any carrier, but running Android 9 Pie)
2. A stock boot.img for your hardware version, here are the two that I have. You can just extract the boot.img from a stock ROM for a hardware version not listed, although I'm not sure it actually matters which one you use. Experiment at your own risk.
XT1955-5 US: https://mega.nz/#!L0sHzSKY!323GrDQ8BTsPmKvrSoU7DV-2kJuVris0cWN8Xt3u_6o
XT1955-2 LATAM: https://mega.nz/#!uk912I4B!12_EgPML2l5sIXDeDGVqiVDB2RwA6iF6-H-mivNecOo
(Full stock ROM's for both versions will be linked in the next post. )
3. A USB cable to connect your G7 to a computer
4. Motorola USB drivers: https://support.motorola.com/uk/en/...moto-g-family/moto-g7-power/documents/MS98028
4. Your bootloader unlock code from Motorola, more on that below
5. Android SDK
Step 1: Unlocking the bootloader
First we'll need to unlock the bootloader, to do this, you'll need your unlock code from Motorola:
https://support.motorola.com/us/en/bootloader
Note that this will require you to register your device with Motorola, and this WILL void your warranty.
Then, download and install the Motorola USB drivers (link above), you may need to reboot your computer after installation.
Next you'll need to download and extract/install the Android SDK
https://developer.android.com/studio/index.html#downloads
Note that you'll only need the "command line tools" for this guide, unless you really want the whole SDK (huge).
Extract the command line tools to anywhere really, C:\Android is fine for Windows. If you downloaded/installed the whole sdk, the tools you need will be in C:\Users\[your username]\AppData\Local\Android\Sdk\platform-tools
Once you have that, open up a powershell window in your tools folder by holding Shift and right-clicking in the folder.
Now, reboot your G7 to fastboot mode by powering off, then holding power+volume down until you're in the bootloader. Now, connect your G7 to your computer with your USB cable.
In powershell, verify your device is recognized by typing "./fastboot devices". Your G7 should show up by its serial number.
Now, type "./fastboot oem unlock [your motorola unlock code]". THIS WILL WIPE ALL DATA ON YOUR PHONE. After that, use the volume up and down buttons and then the power key to restart the bootloader. You should now see "flashing_unlocked" at the bottom of the bootloader screen. Now use the volume/power buttons to select "start" to boot the phone. You will see "bad key" displayed in the top left corner of the screen. This is normal. The phone should boot and bring you to the Android set up wizard. Go ahead and set up the phone as you normally would.
Note that at this time, if you go to "Update" in system settings, it may warn you that "system integrity is compromised" and that you will no longer receive OTA updates. This is also normal, we'll fix that in a bit.
Step 2: Rooting
Now that we have an unlocked bootloader, we can flash things to the phone through fastboot (at the time of this writing, TWRP or other custom recoveries are not available for the G7 Power. Once it is, you can use that to flash the Magisk .zip file instead of using powershell).
Copy the correct *_boot.img for your hardware version to a folder on your phone. I used the downloads folder. (not too sure if the version makes a difference; I was able to flash the entire US XT1955-5 firmware/rom to my Latin America XT1955-2 without a problem, but experiment at your own risk)
Download and install the Magisk Manager APK through Chrome or browser of your choice on your G7
https://github.com/topjohnwu/Magisk/releases
It will ask you if you want to allow [your browser] to install things from unknown sources. Say yes.
Then, open Magisk Manager and tap "Install". Then tap "patch boot image file". Select the *_boot.img you copied earlier and let it run. It will tell you when its done.
Once it completes, copy the patched *_boot.img back to your computer and place it in the same folder as your Android SDK tools (where fastboot.exe and adb.exe live)
Now power off the phone then boot to fastboot, again by holding power + volume down until the bootloader appears.
Now in powershell, type "./fastboot flash boot [the name of your patched boot.img].img" and hit enter. Alternatively, type "./fastboot flash boot" then hit space, then drag your patched *_boot.img into powershell and hit enter.
(Note, if you get an error saying "Invalid partition name boot__a" like I did, add a "_a" to "boot" ie "./fastboot flash boot_a [the name of your patched boot.img]" instead. )
Powershell should tell you "Image signed with key bad key". This is normal.
Now use the volume up/down buttons and power button to start the phone.
Once booted, load up Magisk Manager again. You should see all green checkmarks. Congrats, your G7 is now rooted! One last thing:
Tap where Magisk says "tap to start SafetyNet check". This tests to see if its able to fool Google's checks and let you install OTA updates or use Android Pay. If you did everything properly, this should all check out fine. Confirm by going into Updates in System Settings and verifying that you are up-to-date and it doesnt say anything about "device integrity compromised".
Thanks to everyone who's work I shamelessly paraphrased. I wanted to make a concise guide specifically for the G7 power as I didn't find much online regarding it. (And the stock US rom was ridiculously hard to find and acquire). I'll link stock US and Latin America G7 Power firmwares/roms in the post below in case anyone wants to go back to stock, once the upload finishes. Note: there is no known way at the time of this writing that you can ever get rid of "bad key" being displayed at boot once you unlock the bootloader (again, if anyone knows how, let me know! Thanks!)

gedster314 linked me to a site in another thread where stock ROMS for a lot of devices can be found, including the XT1955 (codename: Ocean).
https://mirrors.lolinet.com/firmware/moto/ocean/official/
"RETUS" on that page would signify "Retail, US"

until some good custom roms will pop out i don't have needs to unlick/root...

mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse
Baby steps my friend.

Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
mrmcphisto77 said:
until some good custom roms will pop out i don't have needs to unlick/root...
Click to expand...
Click to collapse

Got everything to work! Flashed Tethering Enabler too. Thank you!

nucher said:
Their are still reasons to Root a phone besides ROMs. Titanium backup, Root explorer, and having super user
access. I used to Root my Pixel 2 to enable tethering when the carrier blocked it. The fact that we don't have
the option of super user access on a device we own is crazy. Jailbreaking the iPhone opens up so many
customization's with tweaks and apps that I went to the dark side. I also have the G7 Power so I'm not a
total traitor.
Click to expand...
Click to collapse
There's one more reason to root: CF Lumen
I want all devices have same exactly same white tone.

Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked

turboyo said:
Anyone with a regional phone that has NFC and 5ghz disabled try flashing to a region that has it enabled to see if it works?? I read the NFC and 5ghz options are just software locked
Click to expand...
Click to collapse
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.

diversenerd said:
I've tried that. Flashing the XT1955-2 with the XT1955-5 firmware. It flashes and boots up without a problem but no dice for the 5Ghz. I have gotten ALL LTE bands unlocked however, about to write up a how-to. If I can get 5ghz wifi working then the XT1955-2 will be the cats meow with its 4gb ram and dirt cheap price.
Click to expand...
Click to collapse
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?

turboyo said:
Perfect. How about NFC? Does the XT1955-2 come with NFC already enabled? Or does the -5 enable it?
Click to expand...
Click to collapse
I was wrong in my first thread, my -2 does NOT have NFC. Heres the newly minted LTE Band unlocking guide: https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-enable-lte-t3925246

After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?

Darkstarsx said:
After rooting i got some issues with appflix and a system app called motorolas notification
(I am peruvian i just tralated the name)
Anyone having the same issue?
Click to expand...
Click to collapse
What kind of issues? I haven't noticed any ill effects of rooting with this method.

my touchscreen is not working at all after the rooting step. how do i fix this?

jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Try rolling back to stock with my other guide. Then try again.

Thanks for the guide, phone is now rooted. Is it safe to do a factory reset to be able to start the phone set up again to automatically download apps, settings, etc from Google? If not, is there another, better way to do that?

diversenerd said:
Try rolling back to stock with my other guide. Then try again.
Click to expand...
Click to collapse
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday

jay8898 said:
my touchscreen is not working at all after the rooting step. how do i fix this?
Click to expand...
Click to collapse
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
Chickenaa said:
PLZ HELP!!!
before if found this thread, I unlocked the bootloader then i saw a magisk boot.img in another website that works with xt1955-5 & 1955-6 and hwen i flash it it said "Imaged signed with bad key bad" and when i reboot it bootloops between the "your device is now unlocked" and the motorola logo
This is my first time working with fastboot
i worked with EDL but not Fastboot
But after some research I FOUND out that i could have used "fastboot boot boot.img" before actually flashing it but I WAS TOO LATE.
ANY HELP
APPRECIATE IT SO MUCH
And i just bought this phone yesterday
Click to expand...
Click to collapse
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that

Poto222 said:
Could you fix it? It also happened to me, xt1955-2 claro Colombia
---------- Post added at 09:47 AM ---------- Previous post was at 09:42 AM ----------
You could try to flash a stock firmware with diversenerd's guide
https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138
And try to root again,
Also, I tried to "fastboot boot boot.img" and it does not work, dont blame yourself for that
Click to expand...
Click to collapse
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop

Chickenaa said:
It Worked and I root too
I was wondering if there's a twrp for this device and I want to install Dolby Digital Plus but Everytime I install it through a magisk zip module and then open it, it stop
Click to expand...
Click to collapse
Someone on the Telegram group has a working TWRP build, he said he'll be posting it soon.

[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware

First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.
Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.
This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions
Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img​8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.​
Code:
flash-all.bat
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).
You're done! Continue on if you want to root your device...
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
If you're interested in root:
11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.
Code:
adb reboot bootloader
fastboot boot modded-boot.img
12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)
=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.

nolimit78 said:
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. This will be a living first post as I'm currently not able to successfully get rooted. The idea of this thread is going from 100% T-Mobile Stock to Rooted Global Firmware. Once I can replicate and get root stable on my phone I will finalize this post. I will also add in shout outs to where I pulled this information from, both thread post and user, as it was through our group that I was able to piece this together. All this will be updated and make to look nice later.
The reason we flash to Indian and then Global is because if you don't, wifi/data and camera will be broken. I can't explain why it works, it just does.
Ok. Now to the good stuff. Please take the time to read every step carefully. It'll explain a little bit as to some of the why behind the steps. PM me if I've missed anything.
Requirements:
ADB setup and working
Global OTA ZIP (download from here)
Indian Fastboot ROM(download from here)
1. Unlock your bootloader. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!).
2. Move the Global Rom.zip file to the root of your OnePlus7T. It'll save you time later. Do this now or there's a later step where I give you the chance.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
4. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
5. Reboot your phone into fastboot adb reboot bootloader
6. Extract the Indian Fastboot Rom folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img
7. Open CMD (with admin rights) and navigate to your ADB folder.
Mine would be-- cd c:\adb\
8. flash-all.bat
9. It will also ask you to wipe data. This is your call. If you followed Step 2, this will wipe out this file and you'll need to replace it once your phone has converted.
9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says []. This is normal, just ignore it. Once everything settles, the device will reboot by itself. If it doesn't, start over and go back to Step 5 and try again.
10. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
11. You should have already moved the Global OTA to the root of the OnePlus 7t. If you haven't, do so now.
12. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
13. Select the Global OTA file and it'll start to flash from within the update app.
14. Once that finishes it'll have you reboot the phone.
15. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--==
This is where we should be able to root. Once I can verify getting this setup and replicate it I will continue with the tutorial. Hopefully, everyone who reads this will find it helpful.
Click to expand...
Click to collapse
I'm having a issue when inflash globel my phone stays on Indian firmware

Are we 100% sure that WiFi/Data/Camera will be broken if you just go straight to Global? Because just this morning I flashed from TMO 10.0.4 to Global 10.0.6 using the fastboot flashable ROM with perfect VoLTE/WiFi/Camera...
Also fully rooted!
Edit: Updated to 10.0.7, kept root via Magisk Manager install to inactive slot.

Reserved for old instructions. Going from 10.0.7 and up the instructions were changed and certain steps weren't needed, like flashing Indian before Global.
Keeping these here just in case someone purchases a phone with older firmware and doesn't want to wait updating to the latest version.
Requirements:
ADB setup and working
Global OTA ZIP (grab the 10.0.6 from here)
Updated 10.0.7 OTA Build from hereas well
Indian Fastboot ROM(grab the latest from here)
Pre-Rooted 10.0.6 boot.img file here
Magisk Canery apk
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.
1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.
6. Reboot your phone into fastboot--
Code:
adb reboot bootloader
Code:
fastboot oem unlock
This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
Now that you've unlocked your bootloader, lets get to flashing the Global Rom--
7. Extract the contents of the Indian Fastboot Rom zip folder directly into your ADB folder.
a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img​8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--
Code:
cd c:\adb\
This will also wipe your data, be sure to save anything that you need prior to running the following command.​
Code:
flash-all.bat
10. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 5 and try again.
11. Once the device boots up, you should now be on the Indian build for the OnePlus 7T.
12. Be sure to copy the Global OTA to the root storage of your OnePlus 7T. If you haven't, do so now.
13. Reboot the phone and boot the Modded-boot.img file from the bootloader
Code:
adb reboot bootloader
fastboot boot modded-boot.img
14. Once the phone boots up, you should now have temp root. Go to settings > system updates and look for the gear on the top right-hand corner. If it's not there, something didn't flash right. Go Back to Step 2 and try again. Click on it and select Local Upgrade
15. Select the Global OTA file and it'll start to flash from within the update app. Let this finish before proceeding.
16. Install Magisk Manager Canary from here
17. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
18. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
19. Once that finishes it'll have you reboot the phone.
20. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.6(as of the time of this post, I'll try to update this as I can)
If you'd like to update to 10.0.7:
1. Download and move the OTA file for 10.0.7 to the root of your OP7T
2. Go to Settings > System > System Updates and look for the gear in the top right.
3. Select Local upgrade and select the update file for 10.0.7.
4. Let it run through and finish, don't reboot.
5. Open Magisk Manager
6. Update and select direct install to inactive boot partition to update.
7. Once this finishes, reboot and you're now on 10.0.7 rooted.
=-=-=-=-=-=-=-=-=-=-=-=

nolimit78 said:
Yup, tried to be slick by going straight to Global and ran into this problem. Data worked for me but Camera was super unstable and Wifi was the only solid no that I got. Required more research to discover that this issue is avoided by flashing the indian rom first.
Tell me more about this. What steps did you take to do this? I'm thinking that once you flash the global ROM to reboot, and then use the a image-new.img that boots a temp-magisk to then use magisk canary to install magisk on the inactive slot (should be a right?)
Click to expand...
Click to collapse
Hmm I'll watch and see if my Camera is unstable but it seems fine so far.
To root I flashed (not booted) a 10.0.6 Magisk patched boot img (fastboot flash boot patched_boot.img) that someone posted in the "how to patch boot with Magisk" thread and installed Magisk Manager Canary.
I used Oxygen Updater to local update to 10.0.7 (it says 10.3.0 because of a typo from OnePlus, see another thread. It says 10.0.7 in settings) but make sure to download the full 2gb update not the 200 something mb incremental one because it will fail.
Then when the update is done, don't hit reboot, go to Magisk Manager, make sure you're set to the Canary channel (unless you patched the boot img yourself with something else) and install and choose inactive slot. Then you can hit reboot in Magisk.

Perfect, means I was thinking correctly with an extra unneeded reboot. Updated info in OP.

Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-free-op7t-sim-unlocking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything

Once converted to Global oos, will it support Dual SIM?

ysfk7 said:
Once converted to Global oos, will it support Dual SIM?
Click to expand...
Click to collapse
Yes it will support dual SIM as long as you have the dual SIM tray.

rgreen83 said:
Just now noticed this thread so I'll crosspost my applicable results from the MSM thread https://forum.xda-developers.com/showpost.php?p=81227253&postcount=113
I want to share my experience in case it might help someone else as I was quite confused for a while over the past few weeks trying to get off tmobile slow updates.
I can also confirm jumping straight from tmobile 10.0.4 to global 10.0.6 works. I didn't have the 10.0.7/10.3.0 downloaded and I have slow internet so I can't say if that would work but I have upgraded to it since via oxygen updater.
Basic steps how I got there is, assuming you know how to do stuff like enable dev mode and usb debugging
-sim unlock https://forum.xda-developers.com/one...cking-t4014053
-request bootloader unlock token and wait 7 days https://www.oneplus.com/unlock_token
-unlock bootloader
-get fastboot rom https://forum.xda-developers.com/one...us-7t-t3979213
-use all in one tool to flash flashboot rom https://forum.xda-developers.com/and...ctory-t3358711
I told the AIO tool I had a oneplus 7 (7T not an option) and did "flash factory images", and chose wipe and reboot to be safe and just waited until the phone came back to factory setup screen
that's it. oxygen updater incremental update failed for 10.0.7/10.3.0 but full worked fine, I've never used oxygen updater until now so idk if that is fairly normal or not. VoLTE works, WiFi calling, etc all seem to be working as far as I can tell (although it seems the global doesn't have the quick select option to disable wifi calling like the tmobile rom did).
I've also now installed Magisk Canary, patched boot img and have certified play store now and google pay is fully functional and I have used camera for mobile banking deposit. Still no issues with wifi, camera, anything
Click to expand...
Click to collapse
FYI link to fastboot rom is broken.

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
Sorry bout that, crosspost fail

Crappyvate said:
FYI link to fastboot rom is broken.
Click to expand...
Click to collapse
I clicked on it and it worked, but I didn't check through mobile. Can you show me what happens when you try?

There is no link to request unlock file from OnePlus. Also will regular global OTA updates work? Or will I have to manually update every time?

Will this work for McLaren 5g?

I just followed the instructions in post#7 and was able to do this successfully as well (direct Tmobile->Global, without the Indian version flash in between). Note that the phone will reboot sometime in the middle of the flash, do NOT manually go into the phone and reboot yet again, just wait for it to complete.

Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?

tkoreaper said:
Is waiting around for OnePlus to send you an unlock token really necessary to unlock the bootloader? I ask this because it's not necessary on the OP7 with the use of the MSM Tool (https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947) Would this tool work on the OP7T or does it need its own?
Click to expand...
Click to collapse
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+

cm0002 said:
Yes, unfortunately the loophole that let this work on the 6T and 7 was corrected for the 7T+
Click to expand...
Click to collapse
i guess thats why i can unlock the bootloader and convert the Tmo 6T without asking the unlock_code.bin from oneplus. thank you kindly for the info

I got the unlock bin today I just flashed via fastboot received message the bootloader is unlocked, but the device status still states locked?

nolimit78 said:
...
4. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
...
Click to expand...
Click to collapse
So OEM Unlock button suppose to be OFF or ON?

[SOLVED] Help Flashing Lineage OS

EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS

Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.

abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!

I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.

I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.

~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?

abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18

Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.

~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?

vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.

~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.

vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...

~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.

MOTO G STYLUS 2020 UNLOCK BOOT/ROOT all steps easy

Hi guys I know their are threads how to do this but they are all over the place, If you'd like a complete tutorial, that will get your 2020 MOTO G Stylus phone rooted without any errors let me know.
Edit: It looks like people are interested so here goes. The tutorial below is for the 2020 version I tested on Android 10 on two variants. This method once followed correctly will take no more than 30 min tops. Not sure if this will work on updated versions but you could try at your own risk. If this helped you leave a like, if you have any questions let me know.
prerequisites:
PC (duh lol)
Fully Charged Device
Motorola Account (for bootloader unlock purposes)
adb fastboot installed (take note of your folder location especially the platform-tools folder
motorola drivers (link in step 5 if drivers don't install correctly after connecting phone)
Tutorial:
Unlocking bootloader
1. first step is to unlock bootloader(all data will be erased) for this you will need your unlock key
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
Rooting
1. with bootloader unlocked time to get root. download the latest magisk manager (23 I believe) let it install and power off your phone we will use it later. We will be getting the specific boot image for your device through temporary twrp.
2. go to https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/ and download TWRP credits to @vache. Place the file in your platform-tools folder.
3. enter fastboot mode (by now it should be second nature) and plug into pc, verify fastboot device connected, by opening command window again in platform-tools folder
4. once verified type the following command without the quotes "fastboot boot twrp-3.5.0-0-rav-sofia.img" be patient, when it boots into twrp, cancel any password creation.
5. go to backup and select storage, choose a sd card, do not decrypt or do anything besides what I'm saying here. it will take you back to the beginning after sd card selected as storage, click backup and select only boot at the very top and creat backup. once done go out to twrp main menu and hit reboot, select "reboot system"
6. now to patch boot, open magisk manager and go to install, it will then give you the option to locate and patch boot.img, however we will be going into twrp backup on your sd card and locate boot.emmc.win (not the other two) once selected hit lets go on Magisk and allow it to patch. your patched boot.img will be in a download folder on your internal memory. Copy that file to your computer and then again move it to platform-tools folder
7. power off device and enter fastboot mode for the final time connect to pc, open command window in platform-tools folder and type the following command without the quotes "fastboot flash boot nameofbootfile.img" hit enter and allow to flash, once completed type "fastboot reboot" your device should now reboot, don't worry if it takes slightly longer than usual.
8. finally go into the magisk manager and let it complete its setup, it should reboot one more time and boom, you have root, remember to use magisk hide, That's it all set. If followed correctly this should only take about 30 min to a hour.

Shucks! I thought this was a tutorial.

zapjb said:
Shucks! I thought this was a tutorial.
Click to expand...
Click to collapse
I got you, updated tutorial up. Let me know if it helps.

If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?

Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm pretty sure a factory reset would restore to 11 not 10. As the 11 update replaced the 10 OS altogether.

Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.

kgalv419 said:
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
Click to expand...
Click to collapse
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.

EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11

kgalv419 said:
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
Click to expand...
Click to collapse
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.

For downgrading to android 10:
1. Grab the moto flash tool from here
2. Grab the a10 firmware from your device here
3. Unzip the moto flash tool and put the firmware zip in the folder called firmware
4. Plug your device in to your pc in bootloader mode
5. Start the moto flash tool and follow the instructions
(Unlocked bootloader required)

EpicSaga said:
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
Click to expand...
Click to collapse
Pretty sure theres a setting in developer options to turn off automatic updates.

ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).

EpicSaga said:
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
Click to expand...
Click to collapse
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.

ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
I already turned it off, but I still got the notification for the update.

ph4n70m-404 said:
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
Click to expand...
Click to collapse
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.

EpicSaga said:
I already turned it off, but I still got the notification for the update.
Click to expand...
Click to collapse
I got a notification again today saying that it will update today if It don't do it manually.

EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
Assuming you have a non Verizon or any other oem that blocks unlocking the bootloader follow the steps from the original post:
(step one makes no sense they wrote it kinda weird)
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.

EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
you can install magisk manager with bootloader locked but there is no sense in installing it on locked bootloader, because when you unlock your bootloader your devices will be factory reset, if you checked my instructions you will see that magisk manager is needed to patch boot.img that you will get from TWRP backup. You seem a bit green about the whole fastboot process, if that's the case I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.

kgalv419 said:
...I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
Click to expand...
Click to collapse
Sometimes it's been a couple years between me rooting phones. When I come back to root another phone I read & read & read & read some more here. And I have in case the shtf a back up phone to be safe.

EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Re: bootlock unlock code email
I went on the Lenovo/Motorola website just yesterday and input the long 5-line code from my phone (required) from SDK platform. Once I did this, the website replied that I will receive email with a unique 20-character bootloader unlock code (this is the part you should check again). Instead of getting a code, the email asked that I first "verify my email", so I followed the directions, clicked the link, the link brought me to their website and I was able to verify my account. Once that happened, the page just kinda froze. So I repeated the process and when I clicked the "verify email" button, it brought me again to the website but thus time to my profile page. There was no Bootloader Unlock Code, nor was I emailed the code as assured as I was, as per their website suggests. I repeated the process a 3rd time but the same thing happened. And when I tried to went back #2 + #3 times, I input all the information again, clicked on the "send email" link (where they email you the 20-character code) I never received any additional emails. I only received 1 email (the first time I input this into their website). So, the site will only work 1 time per unique phone (serial). I called customer support and got nowhere! I have Metro by T-Mobile Motorola Moto G Stylus XT2043-4. I hope you see this and please let me know if you are able to unlock or get a email code as promised (or not). And if you have any information on how else to solve this issue, please let me know. I hope this helps & my apologies for being a bearer of bad news. If I solve this issue, I will respond back.