Develop Bugs

[ROOT] N5206 v150108 - v150312 root method with working wireless

Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.

Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.

Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?

Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.

Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.

Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?

It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.

Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.

Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?

Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.

Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.

Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/

cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip

You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk

can this root work with Chines n5207

Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...

I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...

[Solved] Problems Switching Partitions (X9076)

Hello everyone,
I recently did upgrade my phones OS from 1.2.x to 2.1.5i (ColorOS) via flash, not OTA.
Afterwards I rooted it using TWRP & SuperSu.
I did return to Stock Recovery (community. oppo. com/en/forum.php?mod=viewthread&tid=17397&extra= (Sorry, I can't post links yet, you have to remove the spaces between community oppo and com)).
My problem now is, that I want to use the "Switch Partition" option, to unify my phone storage, but everytime I try the phone does only boot into recovery, as I had a custom recovery.
Do I need a newer Stock Recovery Version? And where/how can I update it?
Or is it possible to unify the storage manually and continue using ColorOS?
Thanks in advance for any help,
Carroll

Probably you need a newer version. Try this.

Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash open gapps pico, but I'm not sure this works

javier.pc said:
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash pico, but I'm not sure this works
Click to expand...
Click to collapse
I did just download and install the PlayStore APK, which worked fine.

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?

Hello, can you please share the stockrecovery.img for fastboot?

nizohio said:
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?
Click to expand...
Click to collapse
I think it is not necessary to download playstore.apk.
create a folder on your PC (Linux and Mac is your top choice), copy all your downloads in this folder (downloads = custom- rom zip, open_gapps zip, SuperSu zip etc)
next you need ADB (android debugging bridge) on your PC.
connect your smartphone with usb to your PC (usb debugging enabled on your phone- you find it under developer)
boot in recovery ( I assume you got lastest TWRP for your phone installed.)
in TWRP go to WIPE / ADVANCED WIPE --> tick Cache, Internal Storage, Data, System, Dalvik/Art Cache.
With this action you are going to lose all data, except data on your external SD and your OS as well. Common sense dictates to back up your data first :good:
after you swiped go to ADVANCED /ADB Sideload --> Swipe to Start Sideload
open your terminal on your pc and cd in your newly created folder with all your zip goodies.
type
Code:
adb sideload custom-zip
Use tab completion - very handy and you know there are no typos.
repeat this command with open-gapps.zip (beware you have to activate sideload in TWRP again) Caution: Do not reboot between installation of your custom - rom and open_gapps.
same procedure with Supersu.zip and so on.
After successful sideload installation, boot your phone to system. Now you should see welcome screen from Android and you have to do a few more setup steps to enjoy your new OS.

Blu Advance 4.0 L2 (A030U) - Custom Recovery TWRP and root

Hi all,
First of all be carefull, Nobody will be responsible for bricking your device but yourself.
I compiled twrp 3.0 for blu advance 4.0 l2 (A030U) https://drive.google.com/open?id=0Bw48RaTkRMm_eTRXVk84aWJTUjA here the sources https://github.com/contrerasojuanc/device_blu_advance_l2_A030U, thanks to @Dees_Troy and its guide on https://forum.xda-developers.com/showthread.php?t=1943625. So, in order to install it on this device, we will need to unlock bootloader (Factory reset needed), and flash TWRP recovery on recovery partition.
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal:
Code:
fastboot reboot
(Immediately press and hold Volumen + on device until custome recovery shows up.)
In order to achieve root on this device, we need to install from TWRP a Supersu system-mode, available thanks to @mauam, it can be get at https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 (I used SR3-SuperSU-v2.79-SYSTEMMODE.zip).
Note that maybe /system need to be mounted as writeable, so first mount System and then, on TRWP's terminal:
Code:
/system/bin/mount -o remount,rw /system
Hope, it can be useful somehow. Any questions, please let me know.

I did everything right but I can not get root

Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?

talesgs said:
I did everything right but I can not get root
Click to expand...
Click to collapse
Please give me more details of what was done, in order to try to help

4mand said:
Could you give more detail on how you installed supersu in system mode? I used the command mount -o remount,rw /system (replacing /system with the actual system folder path I found using the mount command in twrp temrinal) BUT discovered system remained read-only and everywhere I searched says you need to have root access to mount it as re-writeable.
I installed the zip you used anyways but am now stuck at the BLU logo screen. What should I do now?
Click to expand...
Click to collapse
The command I used for get writable /system was
Code:
/system/bin/mount -o remount,rw /system
exactly that one, remember that if you are in TWRP you have root access in recovery partition, so /system can be set as writeable from there. Probably you need to flash recovery and system partition again. I have those partitions from my stock device, let me know if want to give it a try.

Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.

4mand said:
Did you type any commands before that? I get the error "sh: /system/bin/mount: not found".
It would be great if you could link the stock partitions.
Click to expand...
Click to collapse
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.

contrerasojuanc said:
No command before, this is what I did:
1. In TWRP tap Mount menu, then check "Mount system partition read-only" then check "System", then middle bottom button (Home). (So now we have /system partition mount but as RO)
2. Tap Advance menu, Terminal and type
Code:
/system/bin/mount -o remount,rw /system
3. Now if all goes alright, we should have /system writeable.
4. With /system writeable, tap on Install menu, select the Supersu file (Only this worked for me SR3-SuperSU-v2.79-SYSTEMMODE.zip).
5. Deviced rooted.
Ok, I'll try to upload the partitions tonight, while you could search the rom in web.
Click to expand...
Click to collapse
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...

4mand said:
Yes, what you describe is exactly what I did on a previously stock device, but with the same issue on terminal I posted before. After ignoring that, and sideloading the supersu .zip you used, the device gets stuck on the second BLU logo screen on boot, no hope getting back to system. Hopefully it works the second time around with stock partitions...
Click to expand...
Click to collapse
Also here
;-;

Blu Advance 4.0 L2 (A030U) rom partitions
Blu Advance 4.0 L2 (A030U) stock rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools

contrerasojuanc said:
Blu Advance 4.0 L2 (A030U) rom partitions
HTML:
https://ufile.io/j6925
Inside there is a scatter file to use with flashtools
Click to expand...
Click to collapse
rooted? or stock?

talesgs said:
rooted? or stock?
Click to expand...
Click to collapse
Stock

I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??

I already gave up doing root does not work

doni.zeti said:
I have a Blu Advance 4.0 L2 (A030L) device, I know it is different, but I dared, now I have a bricking device with this twrp 3.0. Anybody knows somethings about reverse it or if it is possible??
Click to expand...
Click to collapse
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.

contrerasojuanc said:
Hi, the only way I know would be to flash stock partitions of that device. If you manage to find them in the web, I could tell you how to flash it.
Click to expand...
Click to collapse
thank you for your attention, I'm already trying your recommend, but no success yet. I have the stock, sp-flash and drivers (for win). I think it is any problem with drivers or sp-flash (v5.1712)...

Not working
Hi, I have a BLU Advance 4.0 L2 (A030U) and the TWRP doesn't work in my phone, it boots but the touchscreen isn't working, any suggestion?
UPDATE: I was booting twrp from fastboot because I wasn't able to flash it like is explained here, I think that is why my touchscreen wasn't working, anyways I managed to flash it through SP Flash Tools and It worked but now the root doesn't work, it softbrick the phone everytime I try, I'm able to mount system and all that stuff, everything is successfull but the phone does not boot.

Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.

i have a030u v12 rom. v5generic not work, after install result crash bootlogo loop same make option format... recovery not work! same press up button! after all process not enter in twrp. i test magisk not work customize boot.img flash to sp flash result crash boot! mtk droid not detect my phone too please help me.... very hard root this device!
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse
---------- Post added at 07:13 AM ---------- Previous post was at 07:13 AM ----------
[/COLOR]
TianNian said:
Thank you
.It successfully helped root my Advance 4.0 L 2 A030L in yesterday.
I bad English.
I tried flash superuser.zip(superuser.phh.me_2016-09-23), Magisk-v14.0.zip, SR3-SuperSU-v2.79-SYSTEMMODE.zip, they could root my A030L(stock-V05_GENERIC）
if not fastboot reboot"(Immediately press and hold Volumen + on device until custome recovery shows up.)" , devices will replace your custom recovery automatically during first boot.
Other unimportant: Recovery in A030L also need remount / system, there is not read SDcard (update.zip can be imported in TWRP or OS to internal storage),can't backup userdate.can't input password to read userdate after Encrypted.
update:2017-1007 22:16
SR3-SuperSU-v2.79-SYSTEMMODE.zip looks not work...try next time
2017-1012
SuperSU. ---- Both of these are need: SuperSU-v2.76(or2..79).zip and SuperSU-v2.76(or2.79)-SYSTEMMODE.zip
BLU_A030L_V05_GENERIC i find it in
HTML:
https://plus.google.com/collection/cnwFTB
Ver-V05 can root both ok. Ver-V12 look like something wrong in boot.img,it can only root by Magisk. Maybe you should flash boot.img from ver-V05 if you want use V12.
Click to expand...
Click to collapse

Hi, in order to know what can be happening, first let's try to flash recovery partition, for that, please follow these steps:
Settings -> About device -> Compilation number click multiple times to get new developer options menu.
Enable Unlock OEM.
On terminal:
Code:
adb reboot bootloader
On terminal:
Code:
fastboot oem unlock
On terminal:
Code:
fastboot flash recovery twrp_a030u.img
On terminal: After write the next command, press enter on your computer and immediately press and hold Volumen + on device until custom recovery shows up.
Code:
fastboot reboot

[GUIDE][TWRP] for TWRP and ROM installation

Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
-> Boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously, including everything in storage, photos, documents, everything).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push xiaomi.eu_multi_MIMix3_V10.0.12.0.PEECNFH_v10-9.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Note for AMD Ryzen machines: There appears to be a USB2.0 bug associated with Ryzen CPUs which prevent the fastboot flash from working. If the flashing process starts then fails, try a different machine.

ROM File and TWRP not listed
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link

fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
Yes they are, you need to look again

Mackay53 said:
Yes they are, you need to look again
Click to expand...
Click to collapse
Thanks, found them.

fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
They're right below the ROM table.

invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?

Lumpka21 said:
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Click to expand...
Click to collapse
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).

invisiblewave said:
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
Click to expand...
Click to collapse
You can use stock ROM and twrp. Twrp is replaced if you boot the OS

Mackay53 said:
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Click to expand...
Click to collapse
Ok, so once you've flashed TWRP, there are two recoveries on the device and booting into the stock OS changes the bootloader to boot to the MIUI recovery?

Hello, i found this very useful. thank you

Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)

Alexdruso said:
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Click to expand...
Click to collapse
You don't need ADB for flashing twrp so having usb debugging on is irrelevant.
Flash twrp In fastboot and once it's done and without giving any more commands just hold power and volume up. Eventually it will boot into twrp.

Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG

PWn3R said:
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
Click to expand...
Click to collapse
You never ever need to wipe the System so it won't be that, wipe would be recommended if you can do it

Which version of twrp should I use?

Herrick1209 said:
Which version of twrp should I use?
Click to expand...
Click to collapse
The only one there is for the MM3.

invisiblewave said:
The only one there is for the MM3.
Click to expand...
Click to collapse
I couldn't find it on the twrp website??

Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
You can't find one for the Mix 2s there either.
You can find one for the Mix1 there, but it is non- functional.
. . .
DYODD

Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
That's why I posted the link in the OP.

Thanks, does this apply to the Xiaomi MI Mix 3 Forbidden City Edition?

Question How to reflash OrangeFox due to missing Magisk addon?

I've been trying to reflash OrangeFox without success (ofoxginna2). I assume it's not reflashed because i had deleted the magisk addon folder while trying to solve the "missing magisk. quitting! " error when trying to install it (see orangefox thread post ) and after i "fastboot flash recovery2.img i get the same magisk manager error described here:
the install addon manager says "File Doesn't exist! Please reflash recovery using the installation zip"). If i then go to /sdcard and pick ofoxginna2.zip, i run into the same "magisk is missing error".
At this point, i'm trying to get back to the original issue (after first time flash) of the magisk manager install giving an error due to corrupt zip (somethng deeper about missing keys).
Should i try to:
1) fastboot flash the ofoxginna.zip (without touchscreen support) and then flash ofoxginna2,zip again?
2) blank flash the recovery ( haven't found the steps to do this)
3) flash the recovery from the stock rom (here again not sure how to do this).
thanks.

Wow, that's hard to follow.
If the recovery zip is giving you trouble, don't use it. Take ofoxginna2.img and boot it with fastboot. You can try flashing it as well, but it's really a waste of time bothering.
If your having trouble flashing the magisk recovery installer, don't use it either. Dump your boot image, patch it in Magisk Manager, and flash it in fastboot.
You seem to be getting caught up on little steps. Can you give me a better idea of where your at and what works and what doesn't? Your still trying to boot the nogapps build, and you just have no idea how to place that file, or what?

For your question on how to get back, boot recovery
Code:
fastboot boot ofoxginna2.img
Then format data, reflash lineage, and reboot.
If you wanted to get touch working through Magisk, you'd need an OTG cable and mouse to do it easily. You'd install Magisk Manager, patch that image I shared, and then flash it.
Code:
fastboot flash boot magisk_patched.img
Then you'd install the module I shared and reboot.
But if you don't have have an OTG cable, flash the boot image, Magisk is optional. Boot ofoxginna2, press the button on the bottom right, choose mount, and check the box for vendor. Then you pull up a root shell on your computer with "adb shell".
Code:
mount -o rw,remount /vendor
Then you can extract the module and push the firmware to the phone.
Code:
adb push chiptone-tianma-ICNL9911C-0288-0000-ginna.bin /vendor/firmware/
And reboot.
Please don't make any more threads. Ask questions or for help instead.