How to Install Roms, and resolve Issues on the Xiaomi Mi8 - Xiaomi Mi 8 Guides, News, & Discussion

I am making this post to serve as a All in One Guide for Rom installation or switching to Miui Beta Roms. Happy Flashing!
This post is for people looking for first time Rom flashing instructions, or people wanting to go back to a Miui Rom
__________________________________________________________________________________________________________
I have been told that this post is too long and I agree, so it will be improved upon ASAP ( within a couple of days)
TO BE CLEAR,
If you have unlocked your bootloader, install TWRP and then YOU Must Format Storage
Next flash the Global Rom and flash root.
Boot to system, and go past Google Assistant setup.
Now you can reboot to recovery and dirty flash the EU Beta Rom or my preference the Mi-Globe EU Beta ( more options)
Dirty Flash Beta Rom , then reflash root, reboot to recovery, clear cache and reboot to system
Done
__________________________________________________________________________________________________________
If you are experiencing issues: you are likely dealing with encryption problems that are caused by certain roms.
In addition you need to ensure that you are not only using the correct files needed for your device ( Chinese or Global) You will want to use the most current Vendor and Firmware files.
Go to the first post below this OP for Custom Rom installation steps and to download the Vendor and Firmware files.
THese instructions assume that you have already unlocked your bootloader
⇧⇧⇧⇧⇧⇧⇧⇧⇧⇧⇧ Click Link for unlocking Bootloader ⇧⇧⇧⇧⇧⇧⇧⇧⇧⇧
Two methods for your rom installation
See instruction below for preparing your phone for your very first installation
Flashing TWRP: You can use ADB, Mi-Flash or >>The All in One Tool ( I Recommend the All in One Tool) )
You need to be in Fastboot Mode ( Enter Fastboot by Pressing and holding the volume down and power simultaneously)
Using ADB
1. Install ADB/Fastboot tools on your computer
[*]Enter fastboot mode on phone (hold power and VOL -)
[*]Make sure adb can see and control your device
[*]Run { adb reboot bootloader } - No spaces (before/after)
[*]Run { fastboot devices } to make sure you see your device
[*]Run { fastboot oem device-info } just to reverify your unlock status
[*]Run { fastboot boot recovery_twrp-3.2.3-1-dipper.img}
[*]Reboot back to TWRP ( Press and Hold Volume up and Power button simultaneously) and then begins the installation of your Firmware, Vendor, Root, Your Rom of Choice, and Gapps ( only If needed) and then Magisk 18.1 again. ( Note DM Verity is built into Magisk 18.1)
[*]If you wiped data, your device will now proceed to re-initialize itself as if from the factory
[/LIST]
If you do not own an OTG adapter and a good sized USB drive , buy them and save yourself many hassles
You will save your self a lot of time, especially if you want to fully save a complete Nandroid backup for later re-installation or transfer to your desktop. Thanks to @The War Profiteer for correcting my assumption that the Mi8 has superspeed transfer capability via its usb port ( It does not!)
Regardless using an OTG adapter is still convenient when you are away from your network and need to quickly restore a backup, I have one shaped like a key that I keep with me at all times.
To remove encryption you will always need to format the storage
Not wipe >> choose Wipe > then choose > Format data > > type "yes" to format
Now You Must reboot to Recovery, or the installation may not recognised the formatted data partition
If you see a message that says there is no OS installed are you sure > Don't worry about it, yes, you need to reboot to Recovery
After Formatting and booting to recovery
Install Firmware and Vendor, then install Rom, and whatever else is needed for that installation such as Gapps and Root.
Let's repeat this steps again for Clarity.
Installation of Firmware, Rom, Gapps, Magisk
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install" and install base firmware and vendor if needed. ( See first comment below for files)
5. Select the ROM's zip file and then press "Add more Zips" and select the Gapps zip file ( If needed) , and then the Magisk root file.
6. "Swipe to confirm Flash" and wait
7. After the flashing is finished, just reboot to Recovery, Check Boxes > Reboot to system
Finished!
More about the All in One Tool
The tool is an easy way to resolve a myriad of issues.
It keeps your desktop drivers and adb up to date and provides ADB system wide privileges
See More about all in One tool by clicking unhide
USE @mauronofrio "TOOL ALL IN ONE""
It can be used for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
TOOL ALL IN ONE : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
If your device not recognized, there is little doubt that it is a desktop USB driver issue, so ensure that device drivers are installed
You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
FYI: The All in One tool can do all of this for you, it's done within the advanced menu section.
You will need to temporarily disable Windows defender for installation.
Typical Custom Rom flashing Pre-Instructions - this is relevant to all non Miui , custom roms.
Update firmware & vendor by flashing : Firmware and Vendor from here : https://mega.nz/#F!tZQDSSzZ!3z0iX5nlwwr6RNjJDid39A
Alternate: https://mega.nz/#F!tZQDSSzZ Passkey: 3z0iX5nlwwr6RNjJDid39A
You can also find the latest Vendor and Firmware drivers here : ( Smaller No bloat) https://xiaomifirmwareupdater.com/#stable
1. Flash Firmware and vendor, when flashing vendor choose Mount and then check vendor only, then flash.)
2. Flash Force Decrypt, then Flash ROM of choice & OpenGapps ( if not included in Rom)
3. Flash Root, Reboot to Recovery, Reboot to system.
If coming from Oreo ( You must first have Miui Stable installed Version: MIUI 10.0.2.0)
[*] Flash MIUI V10.0.2.0.OEAMIFH global stable Rom DON'T REBOOT
[*]Flash Disable_Dm-Verity_ForceEncrypt Here DON'T REBOOT
[*]Wipe Data,System,Cache Your Data will be lost
[*]Flash Rom of Choice + Gapps
[*]Reboot and Enjoy[/LIST]
If want to go back to Miui
Flash firmware based on last Official Miui install , Flash root ,
Reboot to Twrp Recovery and perform factory reset
Then flash Miui Rom of choice. and Root if wanted
Enjoy
Please Read - Jan 2020 update
Edit: This post was assembled in March of 2019 : It needs some updating which I will do, when I have time and feel like spending it on updating this thread. Disregard versions of Firmware listed on this OP, those suggestions are now irrelevant. Instead follow the advice from the Rom developer. Very often the rom will include the vender and driver firmware ( AKA DFE)
I definitely recommend using the version of TWRP that I linked here: https://forum.xda-developers.com/showpost.php?p=81329605&postcount=366
For additional suggestions, check my next posts, immediately after the OP ( first comments ) and for update information check here:
https://forum.xda-developers.com/showpost.php?p=81372749&postcount=74

Update vendor + firmware for custom Rom use
Thanks to user Lurii G from 4PDA, when I first bought the phone I updated my knowledge by following his posts, the following is partly paraphrased from his original posts.
Install updated version of TWRP Recovery for the M8 ( AKA Dipper) : https://dl.twrp.me/dipper/
Update*vendor*using TWRP* :
Global and Chinese Stable Vendor files : https://xiaomifirmwareupdater.com/#stable
Global and Chinese Beta Vendor files : https://xiaomifirmwareupdater.com/#weekly
Certain Roms cause encryption issues and there is no way to resolve installation issues without first decrypting storage and then flashing the Vendor + Firmware files
Download the vendor and firmware either from the links above or my mega link on the OP ( doesn't matter)
If you want to know more about the most up to date vendor versions directly from yshalsager
Go here: Firmware update Sources : https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_dipper
Note that firmware is not a complete copy of the Miui stock ROM firmware, it is only a package of the most essential drivers, partition images all of which serves as a base for a custom rom.
Be sure to read the OP of any Rom that you plan to install, You may need to change the base firmware depending on what drivers that developer built the rom over. Use at your own risk.
I strongly suggest that you make a nandroid backup prior to making any changes.
I suggest using an OTG drive and flash the following files prior to flashing any AOSP Rom:
AOSP Installation Steps
1. Flash Vendor in this case : FSTAB-EXT4_F2FS-Dipper.zip it is the most current >
2. When installing the vendor file: Be sure that you select Mount and then Vendor , so that you are only flashing to the vendor partition
3. Next Flash Drivers: At the time of writing this post, I am using : 9.3.14 Firmware :
Note you may need a more up to date or older version depending on what Rom you flash. At the time of writing this 9.3.14 is the most recent firmware
4. Flash your Rom of choice ROM
5. Flash Disable_Dm-Verity_ForceEncrypt_v1.4.zip ( FYI: Magisk 18.1 includes DM verity disable)
6. Flash Gapps ( Only if needed )
7. Flash Magisk optional*
8. Reboot* to Recovery ( Check boxes to install TWRP Manager)
9. Reboot to system and setup
Lets Recap :
1. After installing the the vendor, be sure to flash the radio driver ( Firmware) Next you flash the Rom, the disable DM Verity file, Gapps if needed, Root if wanted > Reboot to Recovery, Reboot to system > setup.
2. Some Roms may already include the vendor, if you have a bootloop, try reflashing the vendor file only, and be sure to mount the vendor partition

Thanks a lot mate for the big description, its really helpful. What I do not really understand is , I got a chinese mi8 and doesnr it mean I would enable ARB by installing a vendor of 9.3.14 ?
Gesendet von meinem MI 8 mit Tapatalk

Eclipse1991 said:
Thanks a lot mate for the big description, its really helpful. What I do not really understand is , I got a chinese mi8 and doesnr it mean I would enable ARB by installing a vendor of 9.3.14 ?
Gesendet von meinem MI 8 mit Tapatalk
Click to expand...
Click to collapse
I quickly pieced together an answer for you, keep in mind that this is not a definitive guide. Give me a couple of days and I will try to expand on it by editing this post with more detailed ARB information. Plus, I will link to here from the OP.
Use any of these steps at your own risk,
I own a global version of the Mi8 and will not personally experience the bricking potential that people with the Chinese version of the Mi8 have to worry about.
Regarding 9.3.14 :
Should be fine if you are using the chinese firmware version, I.E: fw_dipper_miui_MI8_*.zip is Xiaomi Mi 8 (dipper) China firmware >>>> Keep in mind that base firmware is really nothing more than just drivers, and radio bands >>>> Get your correct firmware from here: https://xiaomifirmwareupdater.com/#stable
EDIT : See this post too: https://forum.xda-developers.com/showpost.php?p=78911687&postcount=8
Basic ARB Instructions if you have a Chinese device
First ensure that your phone is correctly unlocked with the Xiaomi Unlocking tool, setup your Miui account and use the Miui Forum app and you will get access to better features and themes while using a Miui OS.
The main issue and thing to beware and afraid of is installing a global rom on a Chinese version of the Mi8 … It seems that it is really only an issue If The Bootloader Is Locked or if you try to relock it.
Do not install Global firmware on a locked device or you will have a definite brick.
Make sure that your phone is linked to your account, this way you have complete control. Personally, If I had a device with a vendors account, I would demand a refund either from the vendor or the website dealer.
To Check ARB
Go to fast boot and type in the code "*fast boot*fastboot getvar anti*" on your CMD.
ARB level is max to 1.
AFAIK: Most roms are Arb=1 or Arb=0 so its apparently safe to install those roms.
To be safe, do not mess with ARB always flash rom using Fastboot method.
Paraphrased Excerpt below from user “YoungChaos” (member of MIUI Device Team) rephrased for clarity in English.
Arb is anti-rollback and it's used for security reasons:
It will deny any attempted installation of older firmware, it used for security purposes to prohibit old exploits. ( So he is saying that once you install base firmware, don’t try to install old bad firmware over top of it.)
Re-locking the bootloader, is another thing to to avoid
To avoid brick you CAN-NOT re-lock bootloader with a global rom on a Chinese Phone.
To avoid ARB issues just flash "official" firmware using fastboot ( Firmware is used in this context as the base drivers.)
If using ADB, you will be alerted you if you are risking ARB or not. The Bootloader has a check to protect you from flashing a lower-arb rom , so it will protect you from bricking your device and It will show you an error and you will understand that you cannot flash it.
This may have been updated to include warnings within TWRP. I install almost everything strictly within TWRP…But I have a global device.
I hope this helps you.
Edit:
I have a theory, I believe that the only thing that make the chinese phone and the Global one different is the Radio drivers ( well specifically the modem, or Non.Hlos.Bin image. and vendor files.
On other phones, you can make a Global phone think its a Chinese phone and vice versa. I am wondering if there is maybe a way to a create a flashable file to get around the risk of bricking a Chinese phone. The only differences that I can see between firmwares is with the modem, outside of that it looks identical. If this can be solved, customer roms could be setup to flash certian firmware based on the device ID. Maybe.

According to this post , i could flash the newest Global weekly over Fastboot, am I right ?
Gesendet von meinem MI 8 mit Tapatalk

Eclipse1991 said:
According to this post , i could flash the newest Global weekly over Fastboot, am I right ?
Gesendet von meinem MI 8 mit Tapatalk
Click to expand...
Click to collapse
The link that you posted is not working for me, it only goes to Google, with the link in the searchbox.
I found a video for you that should help clarify.
https://www.youtube.com/watch?v=Bf44z8xbKH4
So to answer your question you should be able to flash the Global Weekly, granted that you have followed all of the preliminary steps, also be sure to back up your data with the built in Backup tool. Trust me is makes these updates so much faster and much more convenient.
Watch the 5 minute video to ensure that you have covered all steps.

I recommend USB 3.0 because it's much faster and using at least 32 GB's for easy access to your files and nandroid backups
Click to expand...
Click to collapse
Mi8 supports USB 2, not 3. It'll have no effect on the performance rather than a placebo.

tsongming said:
I am making this all in one guide after seeing the countless posts of people looking for instructions for first time Rom flashing, or dealing with encryption issues caused by some roms. I enjoy helping people. But, I don't want to type this stuff over and over. So this post will help me help them. If this post helps you, you can thank me by helping someone else and clicking thanks. Happy Flashing!
If you have followed everything on this OP and you are simply experiencing a bootloop go to the first comment under the OP for the solution. ( Skip these steps and go there instead)
NOTE: If you have already unlocked the bootloader and flashed TWRP to the recovery partition. But have not yet flashed root or your Custom Rom, the OS your recovery can very likely reset back to the factory recovery >>> UNLESS YOU ROOT THE SYSTEM.. <<<<< Don't worry : Your device is still unlocked. But the recovery can be overwritten by the stock recovery, so be aware.
See the bottom section for preparing your phone for your very first installation > see the first comment for the vendor and driver files
I am providing two methods for your rom installation
You can of course use ADB and flash TWRP .......You just need to be in Fastboot Mode
Alternatively you can use the All in One Tool :
If you are new to flashing I highly recommend using this tool because its easy to use even if you are an ADB guru, it's Quick and Easy period.
Developer Options
Make sure you have enabled the developer tools,
Turned on USB debugging, and authorized your computer on your device “MTP”
Have your files and notes ready, if flashing AOSP don't forget the firmware and vendor files.
If using ADB
Be sure to be in in the correct ADB directory and place needed files within that directory ( If you don't know what this means, it may be better for you to use the All in One tool method instead)
Install ADB/Fastboot tools on your computer
You should already have the unlocked Bootloader and have setup Developer Options
Using ADB Method
Enter fastboot mode on phone (hold power and VOL -)
Make sure adb can see and control your device
Run { adb reboot bootloader } - No spaces (before/after)
Run { fastboot devices } to make sure you see your device
Run { fastboot oem device-info } just to reverify your unlock status
Run { fastboot boot recovery_twrp-3.2.3-1-dipper.img}
Reboot back to TWRP ( Press and Hold Volume up and Power button simultaneously) and then begins the installation of your Firmware, Vendor, Root, Your Rom of Choice, and Gapps ( only If needed) and then Magisk 18.1 again. ( Note DM Verity is built into Magisk 18.1)
If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Side Note - Not really needed just FYI
DM Verity can be enabled or disabled from with fastboot commands
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
If you do not own an OTG adapter and a good sized USB 3.0 drive , buy them and save yourself many hassles
I recommend USB 3.0 because it's much faster and using at least 32 GB's for easy access to your files and nandroid backups
Concerning your device's storage
When you boot into Twrp you may see a message that asks if you’d like to use TWRP in “Read Only” mode. Read Only mode means TWRP will only exist on your phone until you reboot it.
You Do not want Read only, if you want permanent access to TWRP ( You do)
*****************Important************************ ******************
Ensure that you have TWRP installed permanent by rebooting to Recovery
Ensure that you have TWRP installed as the primary recovery
Always reboot to Recovery and check the boxes to install TWRP when rebooting to recovery
To remove encryption you will always need to format the storage
Not wipe >> choose Wipe > > Format data > > type "yes" to format > > Now You Must reboot to Recovery, or the installation may not recognised the formatted data partition (If you see a message that says there is no OS installed are you sure> Yes, reboot to Recovery))
After Formatting go ahead and install your needed Firmware ( Read Below and the OP of whatever ROM you are using) then install Rom, and whatever else is needed for that installation >>> Enjoy Root: Yes you should absolutely should root for the full custom Rom experience. However, its not always necessary. Plenty of people choose to remove Root after installing their software of choice.
To Reiterate >> Installation of Firmware, Rom, Gapps, Magisk
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install" and install base firmware and vendor if needed. ( See first comment below for files)
5. Select the ROM's zip file and then press "Add more Zips" and select the Gapps zip file ( If needed) , and then the Magisk root file.
6. "Swipe to confirm Flash" and wait
7. After the flashing is finished, just reboot to Recovery, Check Boxes > Reboot to system
Finished!
USE @mauronofrio "TOOL ALL IN ONE""
It can be used for removing encryption, installing TWRP, Root, your ROM, Gapps, and even to restore to stock Recovery, or to flash a stock Rom
TOOL ALL IN ONE : https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807
If your device not recognized, there is little doubt that it is a desktop USB driver issue, so ensure that device drivers are installed
You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
FYI: The All in One tool can do all of this for you, its done within the advanced menu section.
You will need to temporarily disable Windows defender for installation.
Easy Way to so many issues with do this with one tool >>>>Donate to @ Mauronofrio he totally deserves it!
@mauronofrio built this excellent tool for us. It keeps your desktop drivers and adb up to date. Plus it will give ADB system wide privileges. In addition to all of that it is easy to use.
You have encrypted data this tool can solve that issue easily.
The software tool is called: "TOOL ALL IN ONE"" and it's great and will unencrypt your drive.
After you install it, make sure to check for AIT updates.
To Reiterate
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Pre Installation Steps
You have unlocked the bootloader and have TWRP installed, plus you can you boot into Recovery Note Firmware will get upgraded over time so use the OP firmware and vendor files that are suggested by the maintainer on the first page of every Rom.
Havoc Pre-Instructions - relevant to all custom roms.
If coming from Miui Pie
Flash Force Decrypt Zip Here
Update firmware & vendor by flashing : Firmware - 9.2.15 - Download HERE + Force Decrypt Zip from step 1. again (just to be sure)
Flash ROM of choice & OpenGapps ( if not included in Rom)
If coming from Oreo ( You must first have Miui Stable installed Version: MIUI 10.0.2.0)
[*] Flash MIUI V10.0.2.0.OEAMIFH global stable Rom DON'T REBOOT
[*]Flash Disable_Dm-Verity_ForceEncrypt Here DON'T REBOOT
[*]Wipe Data,System,Cache Your Data will be lost
[*]Flash Rom of Choice + Gapps
[*]Reboot and Enjoy[/LIST]
If want to go back to Miui
Flash firmware based on last Official Miui install , Flash root ,
Reboot to Twrp Recovery and perform factory reset
Then flash Miui Rom of choice. and Root if wanted
Enjoy
Sorry these post are so long, I didn't want to leave anything out.
Click to expand...
Click to collapse
Really good guide, but my tool can't directly unlock the mi 8 bootloader

mauronofrio said:
Really good guide, but my tool can't directly unlock the mi 8 bootloader
Click to expand...
Click to collapse
Wow, thanks for pointing that out, it was left there by mistake.
I knew that it could not unlock the bootloader for the Mi8, since the Xiaomi Unlocking tool is needed.
But your All in One Tool can no doubt unlock the bootloader of other devices. A section the guide was copied from my original write up written for the Le Pro 3 almost 2 years ago. .and I thought that I removed all of the Le Pro 3 references and even proofread the post. I facepalm?
I completely missed and apparently left that part in. So thanks for letting me know, I will remove that part ASAP.
Otherwise your tool is amazing, and I hope that we can get more people to use it and then contribute something to you for your hard work, and building such an highly useful and amazing tool.

The War Profiteer said:
Mi8 supports USB 2, not 3. It'll have no effect on the performance rather than a placebo.
Click to expand...
Click to collapse
No, You misread/misunderstood the post, or I didn't explain it well enough to be clear.
I actually only recommended using USB 30 flash drives, because they are much faster than usb 20 flash drives and can take advantage of the high speed offered by the USB C Port.
The reason why USB 3.x drives are better is because you can keep a massive library of files, and more importantly large nandroid backups on the USB drive and as long as backups are stored with the correct folder hierarchy in tact, you can quick restore those backups quickly and from the USB flash drive itself instead of the storage partition.
Next, the USB 2.0 transfer speed is 480 megabits per second (Mbps) while USB 3.0 transfer speed is 4,800 Mbps. This means that USB 3.x is approximately 10 times faster than USB 2.0.
You can take advantage of this speed by using USB 3.0 drives. Plus they are cheap.
I bought 2, 64 GB USB 3.0 and flash drives for $21 a year and a half ago, after getting tired of waiting on transferring 12GB files to and from USB 2.0 drives.
The drives are in fact compatible, I use them in real life, so there is no placebo effect, usb 3.0 is dramatically faster, and the time difference transferring files is large. I am sure that there are plenty of whitepapers out there and videos to prove it., if you have doubts. In fact probably can find info here : USB C : 3.1 Interoperability Testing v0.95 w USB Type-C.pdf , to be able to use "USB C" there are standards in place about power delivery and transfer speed.
EDIT: I embarrassed myself, after spending a hour and a half researching this for myself, I found that the The War Profiteer was indeed correct, the Mi8 does not have Super Speed transfer which for me is I think very unusual to me since I have several other phones in my house with USB 3.0 compatible Usb 3.0 Ports.
This is one of the corners that Xiaomi cut to keep their prices low. So my argument above is moot, and I have no issue admitting my mistake..learned something new! At the end of the day, I would rather have amoled over USB 3.0 speed so no worries.

tsongming said:
No, You misread/misunderstood the post, or I didn't explain it well enough to be clear.
I actually only recommended using USB 30 flash drives, because they are much faster than usb 20 flash drives and can take advantage of the high speed offered by the USB C Port.
The reason why USB 3.x drives are better is because you can keep a massive library of files, and more importantly large nandroid backups on the USB drive and as long as backups are stored with the correct folder hierarchy in tact, you can quick restore those backups quickly and from the USB flash drive itself instead of the storage partition.
Next, the USB 2.0 transfer speed is 480 megabits per second (Mbps) while USB 3.0 transfer speed is 4,800 Mbps. This means that USB 3.x is approximately 10 times faster than USB 2.0.
You can take advantage of this speed by using USB 3.0 drives. Plus they are cheap.
I bought 2, 64 GB USB 3.0 and flash drives for $21 a year and a half ago, after getting tired of waiting on transferring 12GB files to and from USB 2.0 drives.
The drives are in fact compatible, I use them in real life, so there is no placebo effect, usb 3.0 is dramatically faster, and the time difference transferring files is large. I am sure that there are plenty of whitepapers out there and videos to prove it., if you have doubts. In fact probably can find info here : USB C : 3.1 Interoperability Testing v0.95 w USB Type-C.pdf , to be able to use "USB C" there are standards in place about power delivery and transfer speed.
EDIT: If these phones had a micro usb connection your point would be valid.
Click to expand...
Click to collapse
There were probably an error on your side, at this point I'll consider that you are OK to export your backups/data from your phone over USB 2 connection, I guess. But USB C port does not offer any kind of high speed, Type C is only a different form of an USB port, like door handles. Just a different shape but nothing else.
Nice thread tho, there are a lot of things that I think newbies would learn about.

hello, I have a problem, I can not mount the partition system, I'm with the rom of xiaomi.eu developer version 9.3.14.
When installing the TWRP for the first time if you make the format data, the partition is mounted and works well, but not the partition system, I hope you can help me, greetings from Chile

17007501 said:
hello, I have a problem, I can not mount the partition system, I'm with the rom of xiaomi.eu developer version 9.3.14.
When installing the TWRP for the first time if you make the format data, the partition is mounted and works well, but not the partition system, I hope you can help me, greetings from Chile
Click to expand...
Click to collapse
You can not modify system and vendor partitions on Android with this device, you have to do your stuff on TWRP.

The War Profiteer said:
You can not modify system and vendor partitions on Android with this device, you have to do your stuff on TWRP.
Click to expand...
Click to collapse
query, if I can not mount system, how can I install an app to the system?
Thanks in advance

So after reading all your stuff in this Thread and on other pages I guess that you can still flash n official.global rom on a chinese mi8 AS LONG as you do not lock the bl and you dont downgrade it. That should mean that in theory it should always be possible to update to the newest available version.
Gesendet von meinem MI 8 mit Tapatalk

Eclipse1991 said:
So after reading all your stuff in this Thread and on other pages I guess that you can still flash n official.global rom on a chinese mi8 AS LONG as you do not lock the bl and you dont downgrade it. That should mean that in theory it should always be possible to update to the newest available version.
Gesendet von meinem MI 8 mit Tapatalk
Click to expand...
Click to collapse
Yes, that is correct so just be careful and you should be fine.

17007501 said:
query, if I can not mount system, how can I install an app to the system?
Thanks in advance
Click to expand...
Click to collapse
Don't worry about choosing mount unless you are installing the vendor file., in that case you only want to install it to the vendor partition and it only matters If you are installing a CAF or AOSP custom rom. You can aleve yourself of confusion by rebooting to recovery after installing vendor and the mount points will automatically reset. Chose factory reset and then install your rom from within TWRP
Most Custom Roms have a script that will choose the correct partition for installation, if there is a problem you will get an installation error 1 or error 7 if the issue is storage encryption.

The War Profiteer said:
There were probably an error on your side, at this point I'll consider that you are OK to export your backups/data from your phone over USB 2 connection, I guess. But USB C port does not offer any kind of high speed, Type C is only a different form of an USB port, like door handles. Just a different shape but nothing else.
Nice thread tho, there are a lot of things that I think newbies would learn about.
Click to expand...
Click to collapse
Thanks for comments and yes this thread is for new people.
Regarding USB C and door handles, I really thought you were joking? You say that are from Uranus, so I thought that you were surely just being hilarious and simply pulling my leg.
Absolutely manufacturers can indeed use the USB C shape, and even implement quick charge technologies and yet cut corners and choose to not implement USB 3 + speed.
According to everything that I read the Mi8 is rated for Quick Charge and one would assume high speed transfers as well.
Sadly No that is not the case, you are absolutely correct and I was completely wrong, I tested the speed and my old LeEco phones are much much faster with USB file transfer speed.
While I still love this phone, Xiaomi did not implement USB 3.X Super Speed Technology. For some reason! It's really disappointing because this USB C port also does not support USB C to HD video, while my Le Pro 3's USB C port does.
Thank you for being persistent. I ended up spending over an hour looking for information to prove my case only to find that I was flat wrong.
Thanks again.

The War Profiteer said:
There were probably an error on your side, at this point I'll consider that you are OK to export your backups/data from your phone over USB 2 connection, I guess. But USB C port does not offer any kind of high speed, Type C is only a different form of an USB port, like door handles. Just a different shape but nothing else.
Nice thread tho, there are a lot of things that I think newbies would learn about.
Click to expand...
Click to collapse
You are right, so slow!
By the way, I off topic... 9.3.14 is a perfect build.

tsongming said:
Thanks for comments and yes this thread is for new people.
Regarding USB C and door handles, I really thought you were joking? You say that are from Uranus, so I thought that you were surely just being hilarious and simply pulling my leg.
Absolutely manufacturers can indeed use the USB C shape, and even implement quick charge technologies and yet cut corners and choose to not implement USB 3 + speed.
According to everything that I read the Mi8 is rated for Quick Charge and one would assume high speed transfers as well.
Sadly No that is not the case, you are absolutely correct and I was completely wrong, I tested the speed and my old LeEco phones are much much faster with USB file transfer speed.
While I still love this phone, Xiaomi did not implement USB 3.X Super Speed Technology. For some reason! It's really disappointing because this USB C port also does not support USB C to HD video, while my Le Pro 3's USB C port does.
Thank you for being persistent. I ended up spending over an hour looking for information to prove my case only to find that I was flat wrong.
Thanks again.
Click to expand...
Click to collapse
You are welcome.
There are no obvious reason for this, but I'd say its about the cost, perhaps. There are some alternative options to transfer any data over ADB, always. It's way faster than MTP interface or any other software that can be used for this purpose. First of all, transfer over wifi will be the fastest and most convenient way when there's only a USB2 port, which will be done with a companion app that will let you use ADB over wifi. Here's the app I've been using for years for this purpose: https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb
On other conditions that you will not be able to use any app or network interface, like getting stuck on TWRP, it will still allow you to send adb commands.
After getting the recent adb libraries on your computer, all you need will be two commands and the path of the desired file or folder.
adb pull input output
adb push input output
These two commands will provide you way faster file transfer, without root. still, I'd recommend using them over WiFi.
The problem here is that if you will be transferring to a USB device, you won't be able to use them since there will be no adb interface. I guess using terminal emulators with native Linux commands should be fine, just in theory, but haven't tested it yet.

Related

[TWRP][RECOVERY] Asus ZenPad 10 Z300M, Z301M & Z301MF (locked bootloader ok)

This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????

[HOW TO] ROOT Mi 9T Pro/K20 Pro WHEN ON MIUI 12

The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone, or to a type C usb stick if the device is encrypted.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
Code:
fastboot flash recovery [twrp version name]
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
It was always the trick to survive twrp is to boot into recovery and flash magisk. Anyway, good to have a clean thread.
Mi 9T Pro ll Tapatalk
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
hoopsnake said:
Hasn't this been the preferred method since forever? And dfe just isn't needed at all encrypted unencrypted doesn't matter you can still flash magisk, and since when would twrp not work on stock miui roms?
It's just a update of a skinned Android, not a major android os update like android 11, really very little has changed to warrant making this thread, sorry.
Click to expand...
Click to collapse
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Nothing changed regarding unlocking, flashing TWRP/Orangefox and rooting regarding the 9T Pro since it's release.
There is NO special method for Miui 12 and the method is overall as good as the same for all Xiaomi/Poco devices.
And the "many people" you mentioned is just 1 person who asked for it in the Questions/FAQ section so no need for unnecessary cluttering of threads.
It sometimes takes a while after flashing magisk for the phone to boot up. Make sure you double check that it was successful by using the Magisk Manager app!
trelokeeper said:
Preferred? I think it's the only one. But many people are asking about miui 12 and what's changed. Many things have changed with Android 10 and/or miui 12 in many other xiaomi devices and extra things are needed (especially on mediatek devices). Also there are some lies being spread about the need of DFE and alternative recoveries as "better".
Not everyone is familiar with the method of rooting and no one cared to create a straightforward how-to without spreading BS with idiotic recoveries and unnecessary things. Have a nice day.
Click to expand...
Click to collapse
Yes but is it really relevant to discuss changes on other devices on this forum? No
If those people can't do some simple basic research they shouldn't be rooting in the first place it's designed to be simple and easy and if people can't get that they should have never unlocked their bootloader in the first place. Nothing but clutter here. Give one example of someone speading as you say "lies" about dfe.
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
jugul said:
Is there a way to fix the "ctsProfile: false" ?
Tried a couple modules but they didn't work.
Click to expand...
Click to collapse
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
zgfg said:
First of all, make sure that Magisk Hide option is enabled in Magisk Manager settings (reboot afterwards) - but if it's not enabled then Basic Integrity would also fail
Problem with CTS Profile failing started about month ago (it has been thoroughly discussed in the general Magisk thread) when Google enforced Hardware backed attestation for CTS Profile (for certain phones / stock firmwares). In that case Magisk Hide cannot hide that Bootloader is unlocked and therefore CTS Profile fails
If so, try how it works for Mi 9T, MIUI 11:
https://forum.xda-developers.com/showpost.php?p=83035713&postcount=40681
In short, install Magisk Hide Props Config module and use its option to delete ro.product.model and reboot afterwards.
The post above describes also how to get back Device is certified in Google Play settings, as well as about a sidefect with Settings/About that will no more properly display your phone model
There is a more 'generic' fix you will also find a link in the post above, to use a particular hardwareoff module for Magisk but that module redefines several ro.product.* props (not only ro.product.model), to cover for other phones like Samsung, etc - IMO, better not to redefine props whose redefinition is not needed for MIUI to pass CTS Profile
Click to expand...
Click to collapse
That worked. Thanks!
trelokeeper said:
The procedure is very simple. DFE or OFOX are NOT required. I myself flashed TWRP on an encrypted device and it boots and works as expected. Also twrp does not go away if you follow the steps correctly. No format needed either. Just remember your password.
0. First of all an unlocked bootloader is required. If this is your first time, go to miui.com/unlock. Backup your personal data before unlocking.
1. On windows install ADB DRIVERS and download PLATFORM-TOOLS and TWRP. Also download Magisk and move it to the phone.
2. In Developer Options Enable USB Debugging, then reboot to fastboot (Vol Down + PWR Button).
3. Connect the device to PC. Extract the platform tools folder and in it press Shift+Left Click and open a powershell window. Type
4. Type fastboot reboot and hold Vol+ to go staight into TWRP.
5. From there flash magisk, wipe caches and reboot to system.
6. Come back here and hit that thanks button. :good:
Click to expand...
Click to collapse
Hey there I am a completely newbie in this thing, can you please guide me through dm's or anybody else there to help me . I am from India I bought k20 pro in alpha sale and it's warranty is now over so I wanted to root my phone.
I patched the b0ot file of my ROM with magisk and then I flashed it with fastboot. My devices is rooted but I have a issue with WiFi, suggestions?
I'm install twrp on powershell. I got information, is it succesful and when i want to go to recovery i see only miui recovery,. Not twrp. Where is a problem? Bootloader unlocked
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
nigol said:
Hi, through OrangeFox I tried to install the version miui_RAPHAEL_20.8.7_e721f66562_10.0.zip on my MI 9T Pro, starting from miui_RAPHAELEEAGlobal_V12.0.1.0.QFKEUXM_68e06ebeaa_10.0.zip.
Apparently everything went smoothly, but when the reboot starts again with OrangeFox.
Can someone help me?
Thank you
nigol
Click to expand...
Click to collapse
Did you Format (not Wipe) Data?
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
mustali said:
if i just use rooted miui , do i still need to flash dfe? what are the benefits of decryption?
what are problems with leaving encrypted partition... pls help
Click to expand...
Click to collapse
Just for rooting you don't need DFE, nor to format (neither to wipe) Data.
You need it if you go to flash custom ROM
Btw, rooting can be done without TWRP, just by patching boot.img and flashing the patched image from Fastboot
zgfg said:
Did you Format (not Wipe) Data?
Click to expand...
Click to collapse
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
nigol said:
No, I just installed the zip with OrangeFox.
How can I fix it?
Orange restarts every time you restart ...
nigol
Click to expand...
Click to collapse
Try to Format Data from TWRP: Wipe, Advance, Format Data
ok thanks, I'll try
nigol
---------- Post added at 10:24 AM ---------- Previous post was at 10:11 AM ----------
On OrangeFox in the Wipe directory there are only these entries:
Dalvik / ART Cache, Cache, System, Vendor, Data, Internal Sorage, USB-Storage.
Which entries should I format?
Thank you
nigol

Noob advice please.

Hi all from Noob member.
I am wanting to update my Redmi Note 4 Snapdragon from stock MIUI Global 11.0.2 as no OTA updates for a long time.
Having searched the forums I see a lot of guides are from 2017 so need up to date help.
I understand first step is to install unlock bootloader and install TWRP.
Q1 I need a recommended guide for 2021. I have found this but the advice is slightly different from that on the TWRP Redmi page e.g. regarding how to deal with DM Verity. These terms are all new to me and somewhat confusing.
Q2 Will I be able to backup the factory ROM in case it all goes wrong and I need to get it back to the current state?
Any other advice gratefully received.
Hi. I have recently installed LineageOS 18.1 on my Redmi Note 4 Global (Snapdragon) and have written a detailed guide for myself, in case I would need to do it again. At first, I had problems with fingerprint not working even though I have installed everything correctly. I have fixed that issue with the help of LOS 18.1 main tester, and I have also written myself a guide for that fix.
If you would like to install LineageOS on your mido, I could share the guide with you.
Regarding your question 2, you can always make a backup of your current ROM before installing customs ROMs, and usually backups work fine, although I do not have any experience with that yet, so your mileage may vary.
Also, if your device is not bricked after tinkering with custom ROMS, you can always use latest fastboot MIUI ROM for your device, and flash it with official Mi Flash tool to get back to MIUI.
First step, as always, is to unlock your bootloader with Mi Unlock tool, which you can find here:
Apply for permissions to unlock Mi devices
en.miui.com
Read this FAQ as well:
https://c.mi.com/thread-2262302-1-0.html
By the way, bootloader on my mido was unlocked instantly with that tool, I did not have to wait at all.
Hi Rigadelt
Many thanks for the reply. I would indeed be interested in seeing your guide if it is not too much trouble.
Everything working correctly including the fingerprint reader would be a must for me. Glad to hear you fixed it.
Good to know you can make backups - I'm assuming this is via TWRP?
Appreciate the tip about fastboot MIUI ROMs - I think I have found them before on the official site when I searched a year or so ago about flashing a new ROM. It seems things are a bit more developed now.
Thanks for getting me pointed in the right direction!
Grump
No worries, just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time you will need to use OrangeFox recovery instead, because LOS 18.1 works better with it.
I have written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
First install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
After that, unlock your bootloader with Mi Unlock tool.
Confirm that bootloader is unlocked on your Redmi Note 4 via ADB + Fastboot, following this article (go to PC section, ignore Android phone):
How to check if bootloader is unlocked or locked on Android
How to check if bootloader is unlocked or locked on Android
www.addictivetips.com
At this point, if everything is working fine and your phone is indeed unlocked, I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
Next, download these files and put them in your SD Card or internal phone storage (for example, Download folder). I recommend formatting SD Card and putting the files on it, but you can use internal storage as well.
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware (you will probably not need it, but have it just in case): https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 4.9 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/28.0/lineage-17.1-20201215-UNOFFICIAL-4.9-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/31.0/lineage-18.1-20210107-UNOFFICIAL-mido.zip
GApps (FlameGApps "basic" is recommended for LOS 18.1):
https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/2020-12-29
I will continue the guide in the next message.
Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
Then, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file.
If you installed LOS 18.1 successfully but your fingerprint does not work anymore (although it worked fine on MIUI and LOS 17.1), then you will need to go back to latest mido MIUI ROM with Mi Flash tool and then follow the instructions in "Fingerprint fix and MIUI errors" text file.
Good luck. If you have any questions, I recommend creating a Telegram account and joining discussions on Redmi Note 4/4x groups.
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
the_real_grumpazoid said:
Thanks for this !!!
I was going to ask about the orangefox option, as some guides I have found suggest this.
I had looked on the LineageOS page and see their listed version for Redmi note 4 is 16.0, so looks like you are leading the way with your method.
I'm going to take my time and digest all this excellent info you have provided.
Great tip on the telegram group !
Click to expand...
Click to collapse
You're welcome.
Just wanted to let you know that the main tester of LineageOS 18.1 as of recently recommends using FlameGApps "basic" instead of NikGapps. Apparently some users experienced failed OTA updates (bootloops) due to problems associated with NikGapps.
Download it here:
FlameGApps - Browse /arm64/android-11/BETA/2020-12-29 at SourceForge.net
A Google Apps installer package for devices running on arm64 platform
sourceforge.net
Also, I have updated the installation instructions a bit, so I recommend re-downloading both attached text files above.
Some new info regarding LOS 18.1 updating:
Dirty flash method
1) Download the latest ROM udpate zip file and save it in phone's internal storage or SD Card.
2) Turn off your phone and reboot to recovery.
3) Go to Wipe and wipe:
Dalvik / ART Cache, Cache, System, Vendor
-- DO NOT WIPE "DATA" or "INTERNAL STORAGE" --
4) Ignore "Reboot System" option.
5) Go back to OrangeFox recovery, select latest ROM Update zip and flash it.
6) Ignore "Wipe Caches" and "Reboot System" options.
7) Go back to OrangeFox recovery, select GApps zip and flash it.
8) After flashing, tap "Wipe Caches". Wait for it to wipe and then ignore "Reboot System" option.
9) Go back to OrangeFox recovery, go to Menu, tap on Reboot, then Reboot to Recovery.
10) When the phone successfully reboots to OrangeFox recovery, go to recovery Menu, then Reboot, and Reboot to System.
OTA Update
1) Do not change anything in OrangeFox recovery OTA update options, leave all settings default (OTA disabled). To check if OTA is disabled in the recovery, do this:
1a) Turn off your phone and boot to OrangeFox recovery.
1b) Go to OrangeFox recovery Menu, tap on the Gear symbol in the upper right corner and select OTA & ROM.
1c) Make sure that OTA is disabled (enable OTA is greyed out)
1d) Go back to OrangeFox recovery Menu, then Reboot, and select Reboot to System.
2) Go to Settings, System, Advanced, Updater.
3) Tap on three dots in the upper right corner and select Preferences.
Preferences must be set like this:
* Auto updates check: Once a week
* Delete updates when installed: OFF
* Mobile data warning: ON
* Update recovery: OFF
If you can't disable "Update recovery" option in Updater preferences, then do not worry and leave it enabled. The stock recovery won't be updated (replaced) with LineageOS recovery even if this setting is enabled.
***--- OTA PROBLEMS ---***
In some (rare) cases OTA update might fail (usually due to GApps issues) causing your phone to bootloop, i.e. the phone gets stuck at LineageOS logo loading screen for a couple of minutes, and then reboots to recovery.
To solve this problem you need to install the update manually using Dirty flash method.
The downloaded OTA update file is in this location (in recovery):
root/data/LineageOS Update folder
You will have updated ROM without loosing any data.
Also, you can change GApps from NikGApps to FlameGApps or other GApps every time when you are using Dirty flash method to update your ROM.

Can't boot into TWERP

So, this is the first time I'm installing a custom rom and I was following along with this guy:
(I found the xda steps to be too confusing to follow) and everything was going just fine until around the 5.20 min mark where after flashing TWERP on the device through Odin I was supposed to press the volume - & the power key to restart the device and as soon as the device went black I was supposed to then press volume + & the power key which I did but then I got this: (attachment)
(btw, even when I don't press the volume + & power key afterwards I get the same result)
Can this still be fixed or have I bricked my device?
Hi @Winter413
I found a wonderful description on the installation of TWRP here .... maybe it's easier to follow though it's for the 8.
Just read the whole story .... your troubles while installing TWRP are not at all new.
It's a kind of trick which you learn as soon as you want to root your phone, or want a good user friendly recovery backup app.
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Hope it might be of help ....
Nice Sunday for you !
Here on the forum you will be able to meet all the specialists you need.
[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hi @xabu
First I'd like to greatly apologise you for answering so late. I did not mean to be rude I just didn't want to reply with "ok, I'll be working on it than" & I actually wanted to get something done first. I decided to do things that way becouse I thought that I'll find some time to do this rather soon however unexpected things happened that kept me from doing it but now I have some time & have done something in this regard so enough of my excuses let's get to what I did & what I want to ask you about:
So first I went onto the s8 thread you suggested & I flashed vbmeta_disabled & to my suprise when I restarted again & pressed volume up + power it actually booted into TWRP "and relief washed over me in an awesome wave" but then I went on to get lineage os on it and it doesn't show up in TWRP. I have also gotten some other stuff (magisk & a few files from NanoDroid) & those show up just fine. I got the file from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/
& the link I got from this thread: https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/
& as far as I'm concerned that is the only thread about lineage os on this phone on xda so that doesn't work I guess.
I have also tried this: http://www.mediafire.com/file/4w6vaq4lu2tbjfj/lineage-17.0-20200110-UNOFFICIAL.zip/file
& this: https://mega.nz/file/gw4QTYSS#IqqswGusWIW5l10LyvSfmtVUoE4gqn6_g6jywH96Z5Q
& got this:
(I've done these sequentially but I hope that doesn't make any functional difference however one important thing is the first one goes 'till the first "done" and the second one is the rest. You surely could figure that out by yourself but I wrote this just for clarity's sake.)
P.S. I know that both of the error messages I got seem to refer in one way or another to the fact that I'm not using an sd card for this operation, however as far as I'm concerned it should also be possible to install lineage os to the internal storage of the phone & that is what I want to achieve with this.
P.S. 2
I forgot to mention that I obviously wiped everything properly before trying to install lineage os so that's not the problem.
Hi Winter ,
it's important to check if you found the right version of TWRP:
Samsung Galaxy A10
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
every other version might get you in trouble.
And then: there is still no official LineageOS for the A10 (this gives problems too)
[ROM] [GSI] [GUIDE] Lineage os A10 A105F
A guide for how to install Lineage OS [ GSI ] on Samsung A10 A105F Notes / Warning! Use at your own risk, I’m not responsible for bricking your device. Make sure to backup your important data before everything. here is a summary of the steps I...
forum.xda-developers.com
should be the place to be, though there is not too much activity there ...
but look at this thread too:
Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot
Improve your Samsung Galaxy A10's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
with many good ideas.
Whatever:
I learned that LineageOS should be installed before other additions like Magisk and G-apps. Do this from internal storage and not from an external sd-card.
In TWRP we always make a Zip queue before installing but always starting with the OS or ROM.
You should be successful now you experienced how to install TWRP.
Always check for the right version or ask in the threads.
Thanks for coming back to me though I just wanted to help you
with installing TWRP and I don't have a A10 at my disposal.
Sincerely @xabu
Ps: I saw that you had courage enough to experiment. Be careful but go for it.
Hi @xabu
So as I mention I made it work by flashing this file through odin while in dowload mode & then restarting & pressing the volume up + power buttons which was supposed to take me to twrp & it did & twrp for me seems to be working just fine so I'm a little hesitant to try & install some different version of it but if you think that's the issue than I will try installing those other versions.
As soon as you are in TWRP and it functions fine, then just look to it's version and go to the link which I gave you for the newest version of TWRP for the A10.
"
If you intend to root your (a10) device, be advised that Magisk will be installed to the recovery partition, not the usual boot partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually."
In this website the instructions about flashing TWRP to your device goes further .... so try to understand it step by step.
If you want to install Magisk, then you should know that from some weeks ago, Magisk started a complete new life with new important instructions: look here:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
As you can see .... there is a lot to do and to learn.
Hope you'll enjoy it like your
"and relief washed over me in an awesome wave"
no one could have said it better .
PS:
Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
is especially for your kind of device and certainly not in general.
Alright, so I checked my twrp version with your link & I have the latest one so everything is fine. I also got lineage os 18.1 & it seems to have installed just fine. So now it's time for Magisk. So first I'm also kinda following this guide:
& Wolfgang recommends to not only install the .zip file but also Magisk manager & I couldn't find any link to download it.
"The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP" so does that mean that I have to go back to the download mode & from there flash the root file in odin & then install magisk.apk like here?:
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Also, If you're curious, the "and relief washed over me in an awesome wave" is an almost direct quote (I only changed "washes" to "washed") from my favourite movie - American Psycho.
@xabu
If you liked my previous post, does that mean that I should do the steps I mentioned?
Dearest @Winter413 ....
No, this does not mean that you should do the steps mentioned.
Again read the instructions on the official TWRP where they help you with Magisk. You can always upgrade the moment all works.
I'm not familiar enough with your device. All is working here on the S7.
A complete different device as I noticed while studying your situation.
My like also shows my admiration for your courage to root your phone and try out how to go further and further.
Ps: https://github.com/topjohnwu/Magisk/releases/tag/v24.1
What about Magisk Manager? Do I need that?
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Winter413 said:
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Click to expand...
Click to collapse
Yes you need the new Magisk manager. If you want a rooted phone.
But as I told you....Magisk is changed maybe a month ago .... this means totally new instructions ... so keep this in mind while working with older instructions.
And also regarding the root - If I've gone this far than I might as well go further & attain some more control over my device & also learn a bit about how computers work along the way. This is definitely not the last project of this kind that I'll be doing. I'm already running Pop os on my main computer instead of windows (however I did use windows for this whole process as Odin is unfortunately unavailable for linux). For now I'm also very very slowly learning javascript (I'll try to pick up the pace cuz it's really bad) & once I buy myself a new computer I'll try installing arch on it & using that as my daily driver & yeah, further carrer routes in IT & such are definitely also something that I'll be looking into so while pretty inconmpetent I'm not afraid to play around with computers.
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
So I must admit I haven't looked to much into rooting yet & it seems that It is not required to install a custom rom, however this sounds pretty cool:
Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. mmediately expectable advantages of rooted devices include the following:
1. Support for theming, allowing everything to be visually changed from the color of the battery icon to the boot animation that appears while the device is booting, and more.
2. Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
3. Full application control, including the ability to fully backup, restore, or batch-edit applications, or to remove bloatware that comes pre-installed on some phones.
4. Custom automated system-level processes through the use of third-party applications.
5. Ability to install software (such as Xposed, Magisk, SuperSU, BusyBox, etc.) that allows additional levels of control on a rooted device or management of root access.
Winter413 said:
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
Click to expand...
Click to collapse
Yes learn about the denylist and Zygisk !
So from my understanding currently the steps left are:
1. installing Magisk.zip & Magisk Manager
2. Installing NanoDroid
3. & perhaps locking my bootloader afterwards to make my device more secure? (I think that's something that should be done but correct me If I'm wrong)
& then I can finally start using my phone on Lineage os, right?

Question [SOLVED] Phone's bricked, either need an answer or 11.0.4.0's image

NOTE: Will just clarify, probably am an idiot and messed up a simple thing, so please do take everything I say here with a grain of salt.
The phone was rooted with Magisk v25.1, and I had also installed the unofficial TWRP from this very forum. I also believe I was on 11.0.4.0 of OxygenOS. It is the factory unlocked version.
I was following a guide to update the phone through fastboot, since stock recovery was just showing a screen with a keyboard, which appeared to be impossible to get past. Said guide is here.
Linked in the guide above is the 8th step of that guide, where you then flash the files from the OTA file after extracting them with payload_dumper. I believe the version I was extracting was 11.0.7.0, but to be honest, it was whatever I downloaded off of the Oxygen Updater app, so I'm not entirely certain. I had installed "boot.img", "dtbo.img", and "modem.img", then getting to "abl.img", before receiving an error: Flashing is not allowed for Critical Partitions. "Well," I thought, "I suppose I just can't do it then. *shrug*. Back to this version of OxygenOS I go." That was before remembering to attempt doing "fastboot flashing unlock_critical", which, gave me: Device already unlocked! Well, clearly not, as I should've been able to write abl.img. Attempting to flash again gave me nothing, so, I said screw it.
Well, upon trying to hit start in fastboot, I noticed the phone were now bootlooping back to fastboot over and over. So, I'm lead to a few conclusions:
a) I'm gonna need "dtbo.img" and "modem.img" (I already have boot.img) from the 11.0.4.0 stock image. I cannot find the actual image, so I'm lead to now needing some help here.
b) There has to be some way to continue flashing the files in fastboot (that is, if that is the correct course of action; I am assuming, please feel free to correct me).
c) There is a different way to fixing this than I am thinking.
d) Worst case scenario, this thing has to go back to OnePlus.
Would really hate to have to get to Step D, as this phone was a birthday present to me, and I'd find it wholly embarrassing to throw my hands up in the air a single day after getting the damn thing for my birthday just to need to send it back already, but if nobody can help me out here, then that's where I'm at.
Would appreciate any and all help/suggestions! Thanks.
EDIT: Phone is stuck in Qualcomm Crashdump mode now, bootable into fastboot with vol up+down+power. Looks like it's irreparable. Already working with OnePlus to get it replaced.
EDIT 2: Fixed it!! Big thanks to this thread for the help.
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Raghaov said:
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Click to expand...
Click to collapse
No offense, but this is a pretty dumb response. I don't think you're very familiar with how TWRP is on this device, nor the state of my own. I cannot mount storage, and even if I could, I don't even believe this rom exists for the N200 5G. Along with that, why would a USB OTG be necessary when there's.. I don't know, an SD card slot that works fine and is readable?
Also step 3 is a little laughable. That's why I'm even here in the first place; I couldn't flash every damn thing!
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
justauserthatusesaphone said:
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
Click to expand...
Click to collapse
Do you have one for metro T-MO variant?
Tyreethetruth said:
Do you have one for metro T-MO variant?
Click to expand...
Click to collapse
Nope, I also don't know how to get it, unfortunately.
sounds to me like you dont want a real answer i mean at least respect the one person that replied to your post, not our fault you got yourself in this situation.

Categories

Resources