Database Develop

[How to]: going from China ROM to a working, rooted international ROM (2016/06/20)

Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.

Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx

m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?

Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..

Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!

Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.

Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?

[Guide][No Root]Enable Camera2API in stock rom with Locked bootloader, OTA compatible

This Guide Can Also Be Used For Unlocking & Relocking Bootloader, Installing TWRP & Rooting
If Any Ota Messes With The Implementation Then Whole Procedure Needs To Be Redone
To mitigate the problem requesting developers for making a hack for Relocking Bootloader Without Wiping Data PM me if Interested
Data Will Be Wiped So Make Backup First
What Will We Be Doing: Unlocking Bootloader, Installing TWRP,Flashing Camera2api Enabler, Installing Back Stock Recovery, Relocking Bootloader
Procedure:
1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows
2. Install the drivers according to your OS (happens Automatically In Most Cases) and open the unlock folder
3. Reboot your phone to fastboot mode by pressing volume up + power on at the same time.
4. Connect it to pc and open unlock.bat in unlock folder
5. Long Press Power Button & Reboot. A wiping Data screen will appear followed by an encrypting sceen then the phone will reboot (A warning of unlocked bootloader will show up initially)& then the initial setup screen will show up don't add any thing & skip the setup(there will be another wipe).
6. Download Cam2Api & copy it to sd card or internal storage of phone. Then switch off the phone once again & reboot in fastboot mode once more.
7. Download TWRP from here & Install Minimal ADB to root of C drive.
8. Copy the twrp to the adb folder in your C drive.
9. Open the 'cmd-here.exe' the adb window will open
10. With the phone connected in fastboot mode type in adb "fastboot flash recovery twrpasus.img" & press enter then type "fastboot boot twrpasus.img" & hit enter.
11. Switch Off the phone & boot in twrp by pressing vol down+power, opening TWRP will take time
12. A decryption popup will open in twrp skip it.
13. Select Install Zip & slect the storage where you have kept the cam2api.zip & flash it, then select reboot system.
14. Download Gcam from here (Arnova v8 is best) & copy it to phone and install it, check if it works, dont configure it. Reboot your phone to fastboot mode
15. Download stock asus recovery from here & copy it to the adb folder.
16. Again open the adb & type "fastboot flash recovery recovery.img"
17. Download Zenfone_Max_M1_Pro_Relock.zip and extract it.
18. Open the directory where you extracted the file
19. In that directory, open a file named relock_bl.cmd
20. A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
21. It will then erase all the data on your phone once again (excluding Micro SD card).
23. Reboot
22. Now the phone won’t show the “bootloader unlocked” warning that was displayed after you unlocked the bootloader. Now setup the phone and install the Gcam downloaded earlier also all manual camera apps will work fine too.
Done! You Have Successfully Relocked Bootloader & Enabled Camera 2 api in stock rom. As the bootloader is locked & we have'nt rotted our phone you have your warranty and ota updates work well. If any kind of future ota breaks the camera2api then you have to redo the procedure once again.
Installing Magisk Or SuperSU while twrp is installed will root your phone (breaks ota updates though)
Credits to:
@Sudeep Duhoon : For Original Unofficial unlock & Camera2api Enabler script
@Shivam Kumar Jha For Unofficial TWRP
@style2345 For Providing ASUS Stock Recovery
@myapky For Relocking Script
Hit Thanks If This Helped You!

Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?

mehtasu said:
Ok, I have got stuck. Have a windows 10 machine so was unable to apply the drivers since they were automatically installed. When I tried to install manually, I got an error message that driver is not compatible. Rest of the steps when fine till Step 10. But thereafter TWRP was not installed and the phone went into default recovery with options and th botton of the screen showing an error showing E: couldn't load bitmap fill_ball (error -7). What could have happened?
Click to expand...
Click to collapse
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)

AstroBiswas said:
You need to uninstall the drivers & redo the process most times we dont need to manually install the drivers. We install drivers only if flashing doesnt occur(you did the opposite) after installing twrp make sure to clear data(factory reset through it)
Click to expand...
Click to collapse
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?

mehtasu said:
Oh I found my way into TWRP. Am i supposed to keep it read only or accept swipe to allow modifications?
Click to expand...
Click to collapse
Swipe to allow modifications ofcourse how would we change anything without that permission

Thankyou, the guide works perfectly. Just to add when installing twrp, boot directly into recovery, otherwise twrp won't install. Just wanted to put it here so that people don't have to go through other threads.

1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test May Security Patch arrived via ota & it installed fine, didnt break the api.

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
The June Security Patch is arrived via OTA now?
Sent from my [device_name] using XDA-Developers Legacy app

The Wolf Dark said:
The June Security Patch is arrived via OTA now?
Click to expand...
Click to collapse
No actually my phone has just arrived I Did this procedure on the day itself

AstroBiswas said:
Thanks for reminding, credits given to each hardworking dev who made this guide possible
Yup I Did Test June Security Patch arrived via ota & it installed fine, didnt break the api.
Click to expand...
Click to collapse
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota

Aftab_khatri said:
Last update was on june 14 with may security patch. I highly doubt this method works without losing ota
Click to expand...
Click to collapse
Oh my bad they provided may patch in june update.
We havent done any kind of detectable large system modification so ota's work

Sudeep Duhoon said:
1. Ask before using someone else's stuff in your guide without providing op links or at least give credits
2. Did you test it before posting if the ota will flash fine? As i highly doubt that
Click to expand...
Click to collapse
Thankyou. I had to search for your thread to take care of some troubleshooting. Also, will surely have to follow the guide to go stock/relock to get furture OTA updates. Never the less a big thank you to you and the other developers for their contributions for this phone. Makes this divice so very worthwhile.

Well its working as mentioned by OP.......
Well done !!!

What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img

pranavsree00 said:
What if we use the command fastboot boot revovery.img and flash the cam 2 api zip when it boots to twrp or is it necessary to use the command flastboot flash recovery recovery.img
Click to expand...
Click to collapse
I had tried it. It didnt work

AstroBiswas said:
I had tried it. It didnt work
Click to expand...
Click to collapse

pranavsree00 said:
Click to expand...
Click to collapse
if you already have twrp installed then you just have to flash the cam2.zip thats all ...........
& if you don't have twrp then you have to first install twrp using the command by OP & then flash cam2.zip as mentioned it original thread .

Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...

Amal Prabhakaran said:
Anyone who has done this, please reply to this post if they get the next OTA when released, and installed it without any issues. So that I can perform it without any trouble on updates and warranty...
Click to expand...
Click to collapse
Well just follow the give procedure or steps one by one & relock the bootloader at last and you would be good to go .....
Well I didn't relocked the bootloader & I frequently change my ROMS & regarding updates well there is none after 309 so whenever there would be an update I will give it a try then but for now everything is working fine so you can give it a go .........

[Guide] Switch From Beta to Stable OOS/Fix Random Reboots in Custom Rom

So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.

i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Gesendet von meinem xXx_NoLimits_6.0 on ONEPLUS 6T mit Tapatalk

MarcoG: said:
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Click to expand...
Click to collapse
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.

ultyrunner said:
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
Click to expand...
Click to collapse
I'd like to see a resolution to this ^

This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want

Causical said:
I'd like to see a resolution to this ^
Click to expand...
Click to collapse
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.

se7ensde said:
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Click to expand...
Click to collapse
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
ultyrunner said:
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
Click to expand...
Click to collapse
Awesome, you sir are THEE man. Please get a job with XDA or something

Causical said:
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Um ... OK ... ?

Causical said:
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Yeah sure you can mix up the steps or skip whatever you want..

se7ensde said:
Yeah sure you can mix up the steps or skip whatever you want..
Click to expand...
Click to collapse
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.

ultyrunner said:
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
Click to expand...
Click to collapse
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.

Causical said:
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Click to expand...
Click to collapse
Nope. I was surprised because ...
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.

ultyrunner said:
Nope. I was surprised because ...
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
Click to expand...
Click to collapse
Cool I'm glad you can explain the "tone" and characteristics of my own words to me. I'll remember to try and not be so nice towards you next time, at least if I really be a **** it won't be mistaken.
I WAS originally thrilled by your simple and to the point response, but since you decided to twist my words and make yourself look like a jack ass... well nicely done, is all I have to say ?
Words of a Wise Guy: "hmmm seems odd after receiving a like..."
Huh, just think about that one for a second.

Causical said:
Cool I'm glad you can explain the "tone" and characteristics of my own words to me.
Click to expand...
Click to collapse
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.

ultyrunner said:
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
Click to expand...
Click to collapse
Oooo scary...I guess I'll take my "like" or thanks back whatever you call it.

the.emilio said:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
Click to expand...
Click to collapse
Thank you it works[emoji16]
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

se7ensde said:
Fastboot format userdata
Click to expand...
Click to collapse
What is formatted? The complete internal sdcard?

TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible

Ryano89 said:
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Click to expand...
Click to collapse
Yes.

Mannan Qamar said:
Yes.
Click to expand...
Click to collapse
Thanks, I only ask because I see a lot of disagreement about it on different threads. Some say you can do it, other's say you can't do it if you are flashing back to an older security patch. It's not urgent for me so I might just wait until I have access to my laptop again, but I was hoping to do it now. Won't format completely erase the device?

[GUIDE] How to flash Lineage OS 16 Official + Gapps from OOS10 and pass SafetyNet

- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.

Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?

Great guide. I just have one question for you. I have a GM1910 Model of the phone with international rom. I'm currently on Oxygen OS 10.0.2, can I still follow your steps to downgrade to the 9.5.1.1 and then flash Lineage as per your instructions? I'm new to the OnePlus devices and I want to be sure before doing something that I'll end up regretting. I know that with my S10+ I was able to downgrade between builds easily, but don't know what to do with my OP7P.
Thanks for your time and help in advance.
Edit: How stupid of me, I didn't even read properly before commenting. My apologies. Your title clearly states how to install Lineage OS from OOS10. Disregard my question about downgrading. I just would like to know if my GM1910 model is supported with Lineage or other OOS ROMs. I would think yes, but better to make sure of course.

wp007 said:
Thanks for this guide. I can' use MSM toolkit because I'm not on windows. Is there a linux version? Why can't I just dirtyflash 9.5.1.1 zip over installed OOS 10?
Click to expand...
Click to collapse
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.

If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?

Iolaum said:
If one unlocks bootloader, flashes twrp and then installs LineageOS16 + openGapps only on guacamole, will they pass safetynet or do they need magisk?
Click to expand...
Click to collapse
Magisk is most definitely required. Without it you cannot pass safetynet.

[*] Just go through the menu system and pick your phone. Just type in a number, and enter. And so on.
[/LIST]
Click to expand...
Click to collapse
I have followed all of your instructions and have successfully installed Lineage, TWRP, and Magisk. I've even downloaded the Magisk hide prop from downloads. The only thing I DO NOT understand is STEP 7. PLEASE explain what you have to exactly do here. I don't understand what you mean by: "Just go through the menu system and pick your phone. Just type in a number, and enter. And so on." After I type su, and then props, I get the following options:
1. Edit Device Fingerprint
2. Device Simulation(Disabled)
3. Edit MagiskHide props
4. Add/edit custom props
5. Delete prop values
6. Script settings
7. Collect logs
r. Reset all options/settings
b. Reboot Device
e. Exit
Where do I go to select my phone and number as you're mentioning? And when you say just type in a number and enter? What does that mean? What exactly do I type in? Any random number and enter? I don't understand this at all.
I'd appreciate some feedback here.
- Thanks
Edit: Turns out it only needs the fingerprint to be updated. (ro.build.version.security_patch) Do you have such a code. The developer says he has OP7P added to the list, but I for one, cannot seem to find it. What have you put for yours?
Edit #2: Issue has been resolved. Just did some digging of my own and figured it out. So all that needs to be done is you need to pick your device from the options of 1. Edit device fingerprint, follow the menu options until you see select from certified devices, and then you will see a list of certified devices.
Edit#3: Unfortunately, my devices model is not listed for the certified fingerprints. My model is GM1910, and I tried using the 1911 model, but it doesn't seem as though it worked. Because Google Play is still saying device not certified. Any other model numbers I can try for my model (GM1910)?
Edit #4: What a rough day it has been LOL. Finally found a working version. GM1913 works fine and I can confirm that my device has been indeed certified by Google Play Store. So for my model (GM1910) the GM1913 is the one that works. Ignore all of the above as I've explained it all here in case someone else is confused.

malimt said:
I....
Click to expand...
Click to collapse
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...

h8Aramex said:
Oh man, I am terribly sorry I wasn't really around. Sorry.
One major thing that I cannot figure out - I wasn't able to update.
For some reason after I updated LOS (via TWRP), my whole installation of LOS + Gapps broke.
Now, I needed my phone ASAP so I had to revert to OOS quickly because I needed my phone the next morning.
But, maybe it would work if you update from LineageOS itself.
I would VERY, VERY heavily recommend doing a TWRP full backup before attempting a LOS upgrade.
Shouldn't take long, for me it was like 10 minutes tops, I copied over the files to my PC and that was it. If something breaks, just copy the backups back and restore the backup.
If someone figures out a safe way to upgrade from LOS to LOS... let us know and I'll update the thread.
Ps.: In case your LOS breaks during an upgrade and your backup doesn't restore, you can install OpenGapps now via TWRP (you need the bigger package). This way you'll still have permission issues (like for some reason all Google apps will have bad permissions, so you have to give all perms to each one-by-one) BUT you will have a kinda working phone...
Click to expand...
Click to collapse
Thank you for your response. Never apologize, you have a great guide here. I understand you were busy and had to step away. Also, I'm not sure why you experienced that because I followed your guide every step of the way and everything went perfectly, aside for the safetycheck but I managed to figure that out so you're good! Furthermore, I used Dec. 3 build and right after I installed it, there was an update. I updated the phone in the settings of LOS itself and it worked flawlessly, I downloaded the OTA and updated, rebooted and it was great! No issues there. Did yours use the OTA update? If not, give that a try.
Thanks again for a such an easy guide! Its great! Really works!

I hate A/B partitioning. It only works in increments with your guide, outdated tools everywhere and a ****ty system, on top of not having an sd card. I loved my Samsung. Not for the Touchwiz, bloat etc, but they had sd cards an the old system, which just....worked. Either the gapps fails, the twrp gets overwritten or it boots, without actually loading magisk or gapps. It seems random if the lineage recovery wants to boot to a or b. This is horrible, but now I have to finish it....

You have not specified what you include in a "wipe". This is never the same for anyone, often not necessary and mostly something people do superstitiously - Therefore clarification would be nice. Still fighting with getting this ****ty system to work. Hope it will be restored with a OOS10 flash, if this keeps failing

malimt said:
Usually, you cannot dirty flash an older Build to downgrade. This will most likely cause an issue. You need to perform a clean install. I'm not entirely sure in OP7s case, but I do know this applies to Samsung devices and many others as well.
Click to expand...
Click to collapse
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/

h8Aramex said:
- In case some step fails, just make sure your bootloader is unlocked.
- I assume you have a working adb and fastboot. I used the official Google package: https://developer.android.com/studio/releases/platform-tools . It's possible you will still have an older version installed because some "pack" installed it and put it in your path. How to edit PATH? What is PATH?! https://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
- Advanced Reboot is an option so you can easily enter recovery/fastboot mode. Enable it in Developer Options. How to enable Developer Options? Tap Build Number several times.
I realize the guide is long but it's overly detailed. If you get stuck, have questions, just ask and I will also edit the OP to answer more questions / clarify on points I guess.
Let's go back to latest OOS9.
Make sure to back everything up. If you have Google One, you can do a backup there. If you have root, even better, you can do a full backup with TWRP. I would also copy every important files over to my PC as well - just in case.
Make sure you are unlocked. This can reset if you flashed a full system update or anything so just make sure. If not, unlock.
Grab the MSM toolkit - we will use this to flash back OOS9. See: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In my case I didn't have to mess with drivers or anything, just had to run the tool as admin. However, do read the steps, follow them in case you run into any trouble. Also, I just plug in the phone from a power off state with VOL buttons held down, start it, and I can start the flash process.
At this point you are locked, but does not matter for now. Thing is, now you are on a bit borked image. The stock image has broken fastboot, and might be AA or BA. Point is, you have to flash the correct update at this point. Grab the correct 9.5.11 for your device (AA = global; BA = EU): https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
Just copy it up to your device and use System Update -> Local Update once again to flash it.
Now it's time to flash LineageOS 16.
Now it's time to bootloader unlock again. (Via Developer Options, enable oem unlock and advanced reboot, go into Bootloader, use fastboot oem unlock.)
Now download the latest LineageOS rom from the official site: https://download.lineageos.org/guacamole
Copy up the files to your phone. You can also use adb push at later step. I leave it to you. Copying up might be easier.
Use fastboot boot ...img to boot up the latest unofficial TWRP: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 . You need the .img, but also grab the installer. Make sure you grab the Pie version, LOS16 == Android 9 (Pie).
Once you are in TWRP, go Install, and pick the Lineage zip. Then make sure to do a Wipe from the TWRP menu.
Reboot, let phone boot LineageOS. Shut down once it's booted. No need to set anything.
Press VOL_DOWN + Power to go into Lineage Recovery. Press Sideload here.
You need to grab "Mindthegapps" package from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps and you need to use adb sideload ...zip to load it onto the phone. It will cry about the zip being unverified, just tap proceed.
Now, once it's installed, wipe again from LineageOS Recovery again. At this point, you can also sideload TWRP. You need to use the .zip, and again - make sure you have the Pie version.
Phew, we are almost there! Reboot, log in to Google, do whatever. Set up your device.
Now, finally, let's finish up with SafetyNet.
Once everything is done, install the Magisk Manager APK and grab the ZIP from here. Since you have TWRP, you can just grab the zip to the phone itself.: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Enter TWRP by using Advanced Reboot, Install magisk ZIP.
Almost done!
Go into Magisk Manager, make sure all is green. Go into the left hamburger menu -> Downloads. Grab "MagiskHide Props Config", Install. Reboot.
Now you have to install "Busybox" from Play Store, and you need to install a Terminal Emulator from Play Store as well. Just grab any.
Go into BusyBox, grant root, Install.
Open Terminal, type "su", then type "props".
Just go through the menu system and pick your phone. Just type in a number, and enter. And so on. If you get stuck / afraid to do harm, just reboot the phone and install busybox again, open terminal again, try again. Or ask.
Upon rebooting as you go through the tool, SafetyNet should 100% pass upon reboot.
Click to expand...
Click to collapse
GeeAyeZee said:
https://www.getdroidtips.com/how-to...d-10-q-to-android-9-0-pie-on-oneplus-7-7-pro/
Click to expand...
Click to collapse
Awesome! Thanks. I guess I'm liking the OnePlus more than my S10+ now. Samsung makes much more difficult to rollback using Odin and such. But this is just great!

How To Guide [TWRP] MI 11 (Pro/Ultra) (mars/star)

[TWRP] MI 11 (Pro/Ultra) (mars/star)​
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang

Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D

skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.

The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile

speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?

skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes

Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/

deleted post

I keep getting a " no such partician " fail msg , what am I doing wrong here?

speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?

heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!

SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers

innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?

speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes

Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future

sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet

You click on everything ?

Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo

I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery

Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?