Database Users

Unlock Bootload , Install TWRP , Root : Redmi Note 3[Snapdragon] 7.2.3

Its been inspired by Sudeep Duhoon Thread , Thank him if possible . Except the rooting part everything is preety much same as Sudeep Duhoon did.
I just found out you could 7.2.3 much easily Root the device rather than editing scripts and all of the stuff which i didn't get from his thread.[No offense sir]
Downloads :
1. Minimal Adb Tool
2. MiFlash_2016.03.30.exe
3. Fastboot 7.2.3 Rom
4. Unlocked EMMC or check the attachment.
5. 7.2.3 PATCHED BOOT IMAGE
Unlocking Bootloader :
​1 . Connect your Phone to Computer in USB DEBUG and OEM UNLOCK mode to the computer. [Both of these settings are turned on from developer option.]
2. In ADB check if your device is successfully connected using "adb devices" command .
3. NOW , Reboot the phone into EDL mode using this command "adb reboot edl" .
4. Now make sure you're device is connected in "Qualccomm HS-USB QLoader 9008" , if yes continue .
If the device is connected in "Qualcomm HS-USB Diagnostics 900E" Start it from step 1 again.
5. DOWNLOAD 7.2.3 fastboot Rom . Extract the rom.
Download, Extract unlocked_emmc_appsboot.mbn. Rename it to "emmc_appsboot.mbn" And move it inside the extracted ROM FOLDER.
6. Now Start the MI Flash Tool and Browse to the Location Where you have Extracted the Fastboot ROM
7. Go to Advanced and Select:
Flash Programmer, Raw XML File and Patch XML File
from the Fastboot ROM\Images folder.
8. Close the window and click on refresh , Your device with certain COM# will appear. Just click on Flash.
Wait until its successful .
9. Once it is successful , Hard Boot your phone to fastboot using POWER DOWN + POWER ON buttons on your phone.
10. Now in command prompt type "fastboot oem device-info" , you'll see the DEVICE UNLOCKED : FALSE
11. Now Enter the following command "fastboot oem unlock-go" . Your device must be unlocked , to confirm enter the previous[step 9] command again.
YOUR BOOTLOADER IS UNLOCKED NOW
FLASHING TWRP :
​1. Move the twrp image in minimal adb folder. Rename the twrp image to twrp.img
2. Enter the command "fastboot flash recovery twrp.img"
TWRP HAS BEEN SUCCESSFULLY Installed.
P.S : To boot into twrp : volume up + power on . But it might take 2-3 tries to boot into TWRP . [ I don't yet know why this happens .]
ROOTING :
​1. Move SUPER SU and PATCHED BOOT IMAGE into your mobile.
2. Install Super Su.
3. Install Boot Image, Dont forget to select install image and boot partition while installing.
4. You've SUCCESFULLY ROOTED your device .
P.S : PLEASE TRY IT AT YOUR OWN RISK.

Emmc rar does not get extracted... I think the archive is corrupt... Please check onto that
Sent from my Redmi Note 3 using Tapatalk

kirkirehani93 said:
Emmc rar does not get extracted... I think the archive is corrupt... Please check onto that
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
rar file is just fine , anyway i have uploaded a zip file in the attachment . please check.

reply fast
if i m right... i have to put supersu and boot.img to phone fefore flashing twrp. bcoz after flashing twrp if i reboot to system, phone will not boot and may be bricked...plzzz reply

vivekjha said:
if i m right... i have to put supersu and boot.img to phone fefore flashing twrp. bcoz after flashing twrp if i reboot to system, phone will not boot and may be bricked...plzzz reply
Click to expand...
Click to collapse
No no. It doesn't matter when you put it in. And your after flashing twrp you can directly boot into TWRP and then move the files into mobile.
P.S : While in recovery , you can always copy files in to your mobile.

What if bootloader unlocked officially? Start from "Flashing TWRP" section?

any 1 tried this
any one tried this succesfully plzzz reply

Error during flashing with MiFlash
Got this error during Flashing process:
Status: Not enough storage space is available to process this command.(0x80070008; Max buffer sector is 256)
What should I do? My device does not boot...

anirudh281998 said:
Got this error during Flashing process:
Status: Not enough storage space is available to process this command.(0x80070008; Max buffer sector is 256)
What should I do? My device does not boot...
Click to expand...
Click to collapse
Use Windows 64bit edition.
The flashing process will fail in Windows 32bit edition

will this work in RN3 MTK ???

Will this work on 7.2.5 ?

RedBux said:
will this work in RN3 MTK ???
Click to expand...
Click to collapse
No

Thri11 said:
Use Windows 64bit edition.
The flashing process will fail in Windows 32bit edition
Click to expand...
Click to collapse
Thank you.....i tried it on windows 64 bit and it worked.

I tried unlocking bootload. I got this error "The system cannot find the path specified. (0x80070003: Open Programmer c:...)"
What have I done wrong?
Edit: I deleted the file. Extract it again. Then I unlocked bootloader successfully.

will this void warrenty ?
and to flash miui china roms we need to edit the fastboot everytime ?

When I flash supersu my device won;t boot. Boots fine before though

Hi, I'm on MIUI 7.5.3, can I use 7.2.3 ROM as provided to unlock bootloader or I have to find a 7.5.3 one?

GitGudWolf said:
Hi, I'm on MIUI 7.5.3, can I use 7.2.3 ROM as provided to unlock bootloader or I have to find a 7.5.3 one?
Click to expand...
Click to collapse
I too would like to know the same.
Would this work on 7.5.3 or will I need to do something else

not working sir....
when perform fastboot oem unlock-go, result:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s

UPDATE
SOLVED : "Enable OEM unlock" must be turn on in dev option.

[Discontinued] Unofficial Bootloader Unlock Method for Hydrogen[32GB]

hello,
first of all i recommend the advanced users to try this method first to see if they succeeds or not if they then, cheers for the new unofficial bootloader unlocking method. here i will provide steps to do:-
Things you need:
- fastboot rom MiUi 8 8.2 will work
-the modified bootloader file
-helpful quick answers
ok so here we begin
PREREQUISITE
-adb and fastboot setup already on your pc
-usb debugging and oem unlocking must be enabled(from developer options)
-mi flash tool ~>Get older version from here (use 20160401)
-driver signature off
step 1
Enable USB debugging and connect device to pc,
now open fastboot and adb folder and there open cmd and type
Code:
adb devices
step 2
you can recognize the device connected to pc
now reboot device to edl mode
Code:
boot to edl by button combination or fastboot command
you can see your phone is in edl(emergancy download mode)
step 3
extract the fastboot file, and goto extracted_folder/images
there you can find a file named emmc_appsboot.mbn
replace with the downloaded emmc file(from begining of post)
step 4
open mi flash tool and connect phone via usb and click on refresh you can seee a COM port with a number on display,
now browse and load the fastboot rom.
step 5
(in this step i'll be specific as same as redmi note 3 bootloader unlocking method is)
click on advanced and there
and choose these
Browse to flash_all.bat in Fastboot rom folder at First option ,
Third option to prog_emmc_firehose_8976_ddr.mbn ,
then last two options browse to rawprogram0.xml and patch0.xml
step 6
after selecting files in advanced ,go back and click on refresh
step 7
now flash the fastboot file as soon flashing completes remove cable and keep holding fastoot combination keys
now you are booted into fastboot
step 8
the fun part(i guess)
goto adb and fastboot folder and open cmd there'
and type
Code:
fastboot devices
to check if device detected or not
now type
Code:
fastboot oem unlock-go
now it should show
Code:
...
OKAY FINISHED
like this
step 9
now if you succeeded step 8 completely
i'd suggest you to check if bootloader is unlocked or not
type
Code:
fastboot oem device-info
if that shows as
Code:
<bootloader> Device Unlocked:true
then Congratulations.. you successfully unlocked bootloader without permission from xiaomi
now for the people who are trying do please inform if this method worked or not
(will be helpful to me for re edit post with ease steps)
credits to my whatsapp friend who given me required files lol :highfive:
AGAIN please do reply, if this method works or not if worked then cheers :victory:

This is the second time I see this Note 3 unlocking stuff posted here...
Since when adb reboot edl works for MI Max? I'll tell you... since never...
Have you tried this procedure yourself? I bet you haven't...
So don't post something so risky without confirming it working personally, please...
I will strongly advice everyone even considering this!!!

nijel8 said:
This is the second time I see this Note 3 unlocking stuff posted here...
Since when adb reboot edl works for MI Max? I'll tell you... since never...
Have you tried this procedure yourself? I bet you haven't...
So don't post something so risky without confirming it working personally, please...
I will strongly advice everyone even considering this!!!
Click to expand...
Click to collapse
Actually.. i curruntly dont have my mi max now.. i saw on a post they told about edl mode.. and i asked other members from xda whatsapp group many of them told me max has edl mode.. and they said they tried it...

Swapnil Soni said:
Actually.. i curruntly dont have my mi max now.. i saw on a post they told about edl mode.. and i asked other members from xda whatsapp group many of them told me max has edl mode.. and they said they tried it...
Click to expand...
Click to collapse
Mi Max has Edl Mode but it cannot be booted by adb reboot edl, edl in mi max can only be booted by combination of buttons.

paarkhi said:
Mi Max has Edl Mode but it cannot be booted by adb reboot edl, edl in mi max can only be booted by combination of buttons.
Click to expand...
Click to collapse
Oh okey, i edit the post

EDL can be booted from fastboot by typing fastboot oem edl on the Mi Max

TheLolageMann said:
EDL can be booted from fastboot by typing fastboot oem edl on the Mi Max
Click to expand...
Click to collapse
Yes i edited in the post

Btw, i wanted to ask has anyone tested this method yet, ?

The method is much too dangerous to test, the modified bootloader file depends on android version and may brick your phone - read more in RN3 thread.
You should not have even posted such a method without personally testing it - we, as in users, are not guinea pigs.
step 5
(in this step i'll be specific as same as redmi note 3 bootloader unlocking method is)
click on advanced and there
and choose these
Browse to flash_all.bat in Fastboot rom folder at First option ,
Third option to prog_emmc_firehose_8976_ddr.mbn ,
then last two options browse to rawprogram0.xml and patch0.xml
Click to expand...
Click to collapse
Xiaomi MiFlash has no "Advanced" button, you are not even linking to the program you are advising to use.
Please remove this post and either do the procedure yourself first or do not post such pos here as nobody could even complete the procedure.

mat9v said:
The method is much too dangerous to test, the modified bootloader file depends on android version and may brick your phone - read more in RN3 thread.
You should not have even posted such a method without personally testing it - we, as in users, are not guinea pigs.
Xiaomi MiFlash has no "Advanced" button, you are not even linking to the program you are advising to use.
Please remove this post and either do the procedure yourself first or do not post such pos here as nobody could even complete the procedure.
Click to expand...
Click to collapse
Actually Mi flash tool has the option for advanced .. if you had the older version .. till now i havent updated to latest version yet, also if you may read above post i told that i currently dont have my max now, and i aint gonna get it in next 1 or 2 years, my brother took it and now he is at his hostel...
I ll link the old miflash tool, and the dangereous thing is only one soft brick(stuck at logo) and bootloop, I have experienced some that bootloaders doesnt vary device by device...
So probability is to get a stuck on logo or get a bootloop its simple that you just load the original fastboot firmware and flash, that reverts back to normal state, for now,
I'm just trying to help, if people dont like it then I will defineatly leave.

Swapnil Soni said:
Actually Mi flash tool has the option for advanced .. if you had the older version .. till now i havent updated to latest version yet, also if you may read above post i told that i currently dont have my max now, and i aint gonna get it in next 1 or 2 years, my brother took it and now he is at his hostel...
I ll link the old miflash tool, and the dangereous thing is only one soft brick(stuck at logo) and bootloop, I have experienced some that bootloaders doesnt vary device by device...
So probability is to get a stuck on logo or get a bootloop its simple that you just load the original fastboot firmware and flash, that reverts back to normal state, for now,
I'm just trying to help, if people dont like it then I will defineatly leave.
Click to expand...
Click to collapse
Yes! We appreciate you trying to help but your missing the point... You have uploaded a guide from another handset expecting it to work for our devices having not tested it previously, the guide isn't even for out device so have fun being guinea pigs

kyler084 said:
Yes! We appreciate you trying to help but your missing the point... You have uploaded a guide from another handset expecting it to work for our devices having not tested it previously, the guide isn't even for out device so have fun being guinea pigs
Click to expand...
Click to collapse
I didnt took all things from rn3 bl unlocking page, i just took method of flashing. And the bootloader file thats taken from officially unlocked bootloade, and i just told if previous post i dont hav max right now, so i wish if someone tried this and if he succeeds.. then its very good news for all locked bl users..
But i think none is not even trying

Definititely some procedures must be changed and adapted to mi max. Experimented developers has portion of truth but some users can`t get answer to unlock devices and me personally if my bootloader was locked don`t want have a device wich can`t be real owner.
Opennig file emmc... remember that an old trick from kitkat to unlock with sucess my old xperia z. some looks be based on the principle to replace original values in the clusters just for zeros. I uploaded two orginal and unlocker emmc files to consider this but of course I can`t confirm cause my bootloader is unlocked.

Some ideas aloud.
There are differences between locked and the official unlocked bootloader (please, see in the hex-editor the end of both files). It's a right idea for replace the locked bootloader (emmc_aboot) to official unlocked emmc_appsboot. The official unlocked emmc_appsboot we can get by dump of the partition in official unlocked device and this binary file will be have the .img extension (uncompressed binary file).
For checking we should check two binary files in the hex-editor: emmc_appsboot.mbn from ROM for fastboot flash and modified bootloader file from author. But files with .mbn extension should be uncompressed.
Sorry, but I don't know as uncompress the .mbn file.

SubwayChamp said:
Definititely some procedures must be changed and adapted to mi max. Experimented developers has portion of truth but some users can`t get answer to unlock devices and me personally if my bootloader was locked don`t want have a device wich can`t be real owner.
Opennig file emmc... remember that an old trick from kitkat to unlock with sucess my old xperia z. some looks be based on the principle to replace original values in the clusters just for zeros. I uploaded two orginal and unlocker emmc files to consider this but of course I can`t confirm cause my bootloader is unlocked.
Click to expand...
Click to collapse
Yeah i checked in hex, i guess its the some kinda lock codes with it so they got removed(i m noob in hex ' )
As far as .. result will be known by practically

Maybe developers can make something similar to safestrap, it was a great project based on bootstrap (now abandoned) that works with a modified recovery that allows install almost any rom on bootloader unlocked (and unlockable cause company never want to unlock it at least till the time I used) on my old galaxy note 3 at&t. This app created a second slot and more directly to install roms.

[U][B]Please, Somone who can revive their device from bootloop[/B][/U]
I thought someone will try it

This is far too risky to try
Sent from my Xiaomi MI MAX using XDA Labs

fail
already try this tutorial and ended my device brick no fastboot mode,cant turn on..solution im using testpoint to get my device unbrick...

Swapnil Soni said:
hello,
first of all i recommend the advanced users to try this method first to see if they succeeds or not if they then, cheers for the new unofficial bootloader unlocking method. here i will provide steps to do:-
Things you need:
- fastboot rom MiUi 8 8.2 will work
-the modified bootloader file
-helpful quick answers
ok so here we begin
PREREQUISITE
-adb and fastboot setup already on your pc
-usb debugging and oem unlocking must be enabled(from developer options)
-mi flash tool ~>Get older version from here (use 20160401)
-driver signature off
step 1
Enable USB debugging and connect device to pc,
now open fastboot and adb folder and there open cmd and type
Code:
adb devices
step 2
you can recognize the device connected to pc
now reboot device to edl mode
Code:
boot to edl by button combination or fastboot command
you can see your phone is in edl(emergancy download mode)
step 3
extract the fastboot file, and goto extracted_folder/images
there you can find a file named emmc_appsboot.mbn
replace with the downloaded emmc file(from begining of post)
step 4
open mi flash tool and connect phone via usb and click on refresh you can seee a COM port with a number on display,
now browse and load the fastboot rom.
step 5
(in this step i'll be specific as same as redmi note 3 bootloader unlocking method is)
click on advanced and there
and choose these
Browse to flash_all.bat in Fastboot rom folder at First option ,
Third option to prog_emmc_firehose_8976_ddr.mbn ,
then last two options browse to rawprogram0.xml and patch0.xml
step 6
after selecting files in advanced ,go back and click on refresh
step 7
now flash the fastboot file as soon flashing completes remove cable and keep holding fastoot combination keys
now you are booted into fastboot
step 8
the fun part(i guess)
goto adb and fastboot folder and open cmd there'
and type
Code:
fastboot devices
to check if device detected or not
now type
Code:
fastboot oem unlock-go
now it should show
Code:
...
OKAY FINISHED
like this
step 9
now if you succeeded step 8 completely
i'd suggest you to check if bootloader is unlocked or not
type
Code:
fastboot oem device-info
if that shows as
Code:
<bootloader> Device Unlocked:true
then Congratulations.. you successfully unlocked bootloader without permission from xiaomi
now for the people who are trying do please inform if this method worked or not
(will be helpful to me for re edit post with ease steps)
credits to my whatsapp friend who given me required files lol :highfive:
AGAIN please do reply, if this method works or not if worked then cheers :victory:
Click to expand...
Click to collapse
please post steps with pictures or link a youtube video, I'll sub you, and I'm sure others will too.

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

Axon 7 not bricked but almost.....pls help

Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck

Following this post, you device should be rescued.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
If your phone can not automatically boot into edl mode, then try follow method.
1) Power off your phone,
2) connect your phone to PC with a USB cable while holding hold vol up and vol down at same time.
here2for said:
Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck
Click to expand...
Click to collapse

Thanks for reply but link is 404...pls resend tks
:::::::::::::::::::::

https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

further....
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??

Run command： fastboot devices
If you device show up, then you can flash twrp by command
fastboot flash recovery "path"/"twrp file name".img
here2for said:
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??
Click to expand...
Click to collapse

mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!

....tried to install a couple different roms (placed them on the SD card) twrp....begins to install but then generates the error - "zip signature verification failed" ?? have tried resurrection remix and aokp nougat for axon 7.... get same error. Thoughts please

you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
here2for said:
mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!
Click to expand...
Click to collapse

llaalways said:
you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
Click to expand...
Click to collapse
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck

which model is your phone? A2017U, A2017G, or A2017?
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck
Click to expand...
Click to collapse

I suggest stock rom, you can follow this post to flash it.
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
llaalways said:
which model is your phone? A2017U, A2017G, or A2017?
Click to expand...
Click to collapse

axon 7 almost bricked....
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse

Do not forget install Magisk16.4 after install ROM.
And try factory reset and then reboot disemmcwp.
If there is still problem, try format data again.
here2for said:
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse
Click to expand...
Click to collapse

[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. Screenshots and MSM logs will be best.
!!! I have officially retired my 8T, and can no longer provide additional support on this device !!!​
It's finally here! A MSM tool that will convert your T-Mobile OnePlus8T+5G to EU KB05BA. From here you can local upgrade to any OOS flavor you want. This gives you Local Upgrade option, faster upgrades, open betas, dual SIM, and more! In fact, after conversion, you can unlock the bootloader without the unlock token (still need to be SIM unlocked, but in case you don't want to wait for the unlock token or if OnePlus's website is broken)!
If you are still SIM locked, you lose the Unlock app for when your device becomes unlocked, it's only available in the stock TMO ROM. If you want to go back to TMO ROM at any point, flash back with the TMO MSM: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/
Steps:
Download the MSM Conversion package:
AFH
MD5: 5ddb543c8a5e7587e0b2ad24d2025e77
Run MsmDownloadTool V4.0.exe (Windows 7 users may need to run the win7 version included)
Select User type: "Other" and press Next.
Press "Start". Don't mess with the default settings.
Put your phone in EDL mode.
Code:
adb reboot edl
or completely turn off your device, hold vol up + vol down and plug in the cable.
Wait about 5 minutes while it works.
Done! If you keep the bootloader locked and run it stock, the About Phone page will be missing some fields.
If you run into any MSM tool issues, most likely you have a driver problem. See the FAQ in @Some_Random_Username's post
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Old fastboot method
*** Know how to use the MSMTool, Don't start before figuring it out.
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH THE STEPS DESCRIBED IN THIS GUIDE
* The steps in this guide will convert your TMO KB2007/KB05CB to Global 11.0.5.6.KB05AA, or EU 11.0.3.4.KB05BA
* NR and LTE bands are flashed in nvRAM, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
* Instructions are the same as running any other MSM unbrick tool.
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. See manual instructions towards the end.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools, https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445. DO NOT USE MINIMAL ADB, it has not been updated for years and will cause a crash where you'll need to MSM back to stock.
* Make sure your drivers are up to date. This guide will not walk you through setting up platform tools or updating drivers. When encountering fastboot issues, make sure to include the output of fastboot --version in your post.
* Do not ask for OTAs, MSMs, or anything else not related to the steps described herein. There are plenty of threads around for those.
* This guide does not pertain to Cyberpunk conversion. See other threads.
* This guide converts you to an older firmware so you can take a FULL OTA via Oxygen Updater. Do not skip this step if you want a stable build.
Steps to convert your device to Global or EU
As simple as possible:
You need your device bootloader and SIM unlocked. Follow the instructions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition)
Download and unzip the conversion package:
Global 11.0.5.6
EU 11.0.3.4
Boot to fastbootd.
From adb:
Code:
adb reboot fastboot
From fastboot/bootloader:
Code:
fastboot reboot fastboot
If you are having trouble booting into fastbootd, and have a FC number at the bottom of the bootloader screen, you'll need to MSM to factory first.
[*]You should be at a screen that says "fastbootd" on top. DO NOT CONTINUE IF YOU ARE NOT HERE. SEE HIDDEN FOR AN EXAMPLE.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Execute "flash_all.bat" for Windows, or "flash_all.sh" for Linux, from the unzipped directory from step 2 as cwd.
Optional: Flash magisk'd boot
Code:
fastboot flash boot boot_magisk_patched.img
Reboot into recovery, and wipe everything.
Once fully booted, download Oxygen Updater, set your device to OnePlus 8T of your regional choice and local upgrade to the latest OTA of your regional choice.
Optional: You can re-lock your bootloader at thois point. DO NOT TRY before the full OTA upgrade above, or you'll have to MSM.
Manually:
Unlock bootloader
Download the full OTA of your choosing
Extract the OTA payload with https://github.com/vm03/payload_dumper or https://androidfilehost.com/?fid=818070582850510260
With the output of the payload as your cwd, execute:
Code:
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Replace boot.img with your magisk'd boot if desired
Reboot to recovery and wipe everything
Troubleshooting
Error: "remote: no such file or directory"
You are not in the correct cwd. Fastboot needs to be accessible from the same directory as the .img files, so fix your PATH or make a copy fastboot.exe in the same directory as the .img files
Error: "remote: Flashing is not allowed for Critical Partitions"
You are not in fastbootd. Check step 4.
Error: "Invalid sparse file format at header magic"
Ignore this message, not an error
Special thanks to:
@jwarrior319 for the initial linux script
@cammykool and @awr128 for helping debug some of the steps and clarifying pain points
@radiohead7778580 for a better Global conversion
Fixing the About Phone page
These steps are optional, and will fix the "About Phone" page. There are no performance differences.
You need to rooted with Magisk
Download the fix: here
In the Modules page in MagiskManager, Install the downloaded zip file via "Install from storage"
Reboot, the About Phone page is filled out.
Issues so far (please post if you run into more):
In OOS11, "About phone" page does not work properly.
Use the magisk module above to fix it.
In OOS12, Dual SIM is not supported.
A11 based A12 ROMs support Dual SIM after conversion, use my enable_dsds module.
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.3.4
Extract the payload.bin, and dump the payload using Payload Dumper
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
5G
AOD
Fingerprint sensor
Click to expand...
Click to collapse
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Edit: I am SIM unlocked & I do have my bootloader unlock token so I should be good (just haven't actually unlocked my bootloader YET). I think you may want to mention those requirements in the OP, hopefully to help avoid unnecessary questions. It seems obvious, but you know... it's the internet.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Sent from my OnePlus 8T using XDA Labs
Click to expand...
Click to collapse
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.

craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Perhaps an update to the very latest Magisk Canary & Magisk manager might help? Canary gets updated often, and I ran into that a few times on my 7 Pro. It's also entirely possible it may take extra work...I don't know, but I hope not!
Sent from my OnePlus 8T using XDA Labs
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Click to expand...
Click to collapse
LOL that was it... feels like a dummy man

craznazn said:
LOL that was it... feels like a dummy man
Click to expand...
Click to collapse
Dude, I've doing this s**t since 2010 with the HTC Evo and still do that type of s**t all the damn time. I just get comfortable (cocky is more accurate), like, "oh I know what to do, I can do this in my sleep"...and then yeah, scratching my head, wiping my phone or some dumb s**t because I didn't do the easy trouble shooting stuff.
Sent from my OnePlus 8T using XDA Labs

SafetyNet is fine if you do the global Magisk Hide

So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
You need your device bootloader unlocked. Follow instrustions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-edition)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.2.3
11.0.3.4
Also check this thread
Extract the payload.bin, and dump the payload using Payload Dumper
Execute the following starting from ADB and in the payload output directory. You can start at Fastboot if you are already there:
I haven't used it much yet, but here's what I know so far:
Issues (please post if you run into more):
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
What appears to work:
5G
Dual SIM, though I can't test without a proper 2-SIM tray
AOD
Fingerprint sensor
Click to expand...
Click to collapse
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.

awr128 said:
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.
Click to expand...
Click to collapse
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Click to expand...
Click to collapse
Nice, I looked for one a few days ago and couldn't find any.

LLStarks said:
SafetyNet is fine if you do the global Magisk Hide
Click to expand...
Click to collapse
Whats going on buddy, nice to see you! Broke down and bought the 8t as well I see

I am successfully on the European. I extracted the payload before but I wasn't flashing correctly in fastboot, had everything working except the phone.
Now all good..
Thing to test is to see if I lose data like I did randomly with the 8.

cammykool said:
So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.
Click to expand...
Click to collapse
Not sure yet, it might not but the local upgrade option is now available, at least in the EU version. I tested that to install the EU version on the second slot and it worked fine.

After we follow the guide can we just do the local upgrade option as normal

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
I couldn't find one, but it looks like the 8 tray may fit so I got one of those. Even if it doesn't work, it's not that expensive until I can find a dual-tray 8T

cammykool said:
After we follow the guide can we just do the local upgrade option as normal
Click to expand...
Click to collapse
The option is there.

This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices

SmileBigNow said:
This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices
Click to expand...
Click to collapse
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert

Shooter7889 said:
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert
Click to expand...
Click to collapse
if this works ill do this, BUt currently bsdiff4 is kicking my ass and refuses to install