Related
I used to flash new ROM's on my old Galaxy S2 and there was never a issue of bootloader thing and same goes for old Xiaomi phones like redmi 1s.
But recently When xiaomi started locking bootloader , even after unlocking bootloader ,In most of ROM threads there is warning to delete the bootloader file from MIUI recovery ROM and then flash the ROM through recovery as it'll relock the bootloader.
Why does this happen so ?
1) What is the difference between official and unofficial unlocked bootloader ?
2) How much difference does one make if we want to flash all type of ROM's including MIUI , CM ,RR etc ?
3) Is there any way in which bootloader once unlocked , we don't have to worry about getting it relocked by flashing other ROM's like exactly what happens in most other android smartphones after unlocking their bootloader ?
Please clear the above doubts as it's becoming very confusing and irritating on flashing the ROM and what points needed to be kept in mind to avoid bricking the RN3.
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
lack of good/complete tutorials
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
timberwolf60 said:
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That is a lot of If else there
Why we can't just flash any rom after unlocking bootloader officially and always have to fear about bootloader relock again?
If i am not mistaken this situation is in Xiaomi phones right ?
Dust2Dust said:
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
Click to expand...
Click to collapse
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and What's the difference between officially and unofficially unlocked bootloader ? i have unofficially now , should i officially unlock it ? if it makes flashing procedure easy ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Dust2Dust said:
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Click to expand...
Click to collapse
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
I did the same steps above after flashing resurrection remix with cm13 radio,after restoration of miui from twrp Alka backup my fingerprint sensor stopped working bcos the firmware didn't restore and I unchecked that partition so what i did was again.
1) go back to twrp Alka
2) flash the full MIUI 8 rom .zip and rebooted
3) then the fingerprint started working .
So Alka twrp has a bug in Restoration of firmware partition .so be careful and have a full twrp Alka backup and then flash cm13 and firmware
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
They look more or less correct, I choose not to go the CM way (yet) since there are still some flaws that I can't live with.
I would try to go to official unlock, whatever it takes. It just looks more solid & safe from what I have been reading so far.
Also I would choose to use an other Recovery:
Official TWRP with F2FS Support
• Based on official TWRP 3.0.2-2 & updated CyanogenMod source
• Adds Support For F2FS based file systems.
• Used for flashing official CyanogenMod 13 based ROMs.
• Users with official unlocked bootloader will have to flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip.
• Users with unofficial unlocked bootloader should strictly not use this TWRP for flashing MIUI Recovery ROM Zip.
That seems optimized for CM the most.
II should tell you that I received the phone two days ago and I am also still catching up on reading.
Add on, taken from the above link:
In case of unofficial unlock:
4. Flashing Official CM13 ROM
• Flash F2FS TWRP & Backup Current ROM.
• Select /data & /cache Partitions & Select Change File System
• Select F2FS & Swipe To Change
• Reboot to Recovery & Factory Reset
• Reboot to Recovery & Flash CM13 Firmware
• Reboot to Recovery & Flash CM13 Zip
• Flash Appropriate GApps Version Zip & Reboot to System
• To Return Back To Any ROM After Flashing CM13, Flash Safe TWRP v2 & Proceed.
I am a beginner about miui and redmi note 3 stuff.
1.)I hate MIUI since ot doesn't get updated.
So please gove me step by step on how to install unlock bootloader and get twrp so that i can flash lastest android n build.
Please please please please help me as i am tired of miui and android lollipop.
Please note:i am an extreme begineer so step by step guide.
Also tell me the best twrp beacuse there are many twrps. I just want to flash aosp stuff and also tell me the best kernel with the most stable latest android n with volte
Thanks i advance☺
Hey there.
1) I think you should try to check and see if you do have an official version of MIUI, not a vendor version.You can check this by seeing if you have ads or things like that popping up in your phone. The reason I say this is because MIUI actually gets updated pretty regularly. If you just don't like MIUI because of update issues, I think you might want to try flashing a known global stable version of MIUI(which is the official MIUI that is supposed to ship on MI devices) before doing anything else.
As for how to flash your device, the steps are below.
1) Unlock your bootloader using the official method from Xiaomi.
you can apply for unlock permissions here http://en.miui.com/unlock/
after applying, you will have to download the MiUnlock program and install it on your computer.
Plug in your phone to your computer to allow the drivers to install.(It's an automatic process)
Check the email account associated with the Mi account you used to apply for unlock permissions every few days.You should receive permission to unlock within the week.
After you have received permission,
Boot your phone into fastboot mode(vol down and power buttons held down at the same time from power off state)
plug your phone into your computer(please note to use the original cable and a stable usb port)
open the MiUnlock program
Click unlock.
You will have successfully unlocked your bootloader at this point.
2)Check your device version by going to settings> about phone.
If it says hexa core processor, refer to the snapdragon forums
If it says octa core processors, refer to the mediatek(mtk) forums
3)Flash an official Xiaomi ROM for the appropriate version of your device.
you can follow this extremely detailed tutorial here(please note that everything from this point forth will be a tutorial for the snapdragon version and should not be used on the mediatek version)
http://en.miui.com/thread-235865-1-1.html
4) If you are still unsatisfied with the Official MIUI, you can then proceed to flash a custom ROM of your choice.
Flash TWRP.
After that, flash Alka recovery.
You can compare the different versions of TWRP available here http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
For this part, you can follow the tutorial made by rootjunky.com on youtube.
After that, backup all partitions of your device onto your sd card.
Flash the appropriate firmware for your Custom ROM
Flash your chosen ROM
Flash Gapps.
Done.
A good ROM to start out with would be CM13 by TheStrix.
A good kernel would be Radon Kernel.
Personally, I wouldn't use CM14 yet as it is not completely stable.
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in our opinion the better ones out of the Pie-list.
It’s not to be intented to be ‘the’list but only to give you a guidance to what there is at the moment. And most of, it’s very easy to install
The ones that I will list are the ones WITHOUT call bugs on our Axon 7. As you wish you can vote for your favorite of the listed ones above.
Note : the LOS16 PPR2 is not the same as the one under ROM section (Ordenkrieger)
LIST AVAILABLE : (not in a specific order and more to come)
1. HavocOS : based on https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Latest stable : https://sourceforge.net/projects/havoc-os/files/arm64aonly/
2. BenzoROM : based on https://forum.xda-developers.com/pr...device-development/gsi-benzo-rom-9-0-t3837127
Latest stable : https://forum.xda-developers.com/showpost.php?p=78312149&postcount=284
3. PixelExperience : based on https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Latest stable : https://github.com/EnesSastim/Downloads/releases/tag/PE-A-2018-09-05
4. LOS16.0 PPR2 : based on https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
Latest stable : https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ!DD4z0AhA . More info.
5. ArrowOS : based on https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
Latest stable : https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/7_sep_2018/
6. DescendantOS : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
7. PixelDust : https://forum.xda-developers.com/showpost.php?p=78184921&postcount=212
8. AEX 6.0 OFFICIAL : https://forum.xda-developers.com/showpost.php?p=78245997&postcount=254
Pre Requisitions :
Unlocked BL, Bootstack B12 NFound or your preferred one
Vendor partition by @djkuz or your preferred one
TWRP3218-treble under the hood @NFound or your preferred one
Installation : or your own preferred method as this is just an example
Wipe System. Data, Vendor, cache dalvik (although data does the job)
Flash the v1.1 NFound
Flash the .img that you have extracted and if needed renamed to system.img
And just….reboot
After installation there can be applied some fixes :
a* Use the aroma COMBIFIX v3.1 to fix the NFC/HS general lag, choose button reverse, flash new kran framework overlay, magisk and gapps
update : for magisk 18.1 use the latest Combifix v5.1 or with Magisk 19.0 you can use Combifix v6.0 or the latest one with magisk 19.1 and latest MHPC : COMBIFIX 6.1
a. NFC when laggy or not working combined with Hotspot : Pie_NFC /Hotspot fix by @kountry83
On ArrowOS and Benzo they both work after applying the fix although the Hotspot works on ArrowOS and Benzo die to v105 phh
b. GCAM when default one isn’t working
c. Camera fix if you have a settings bug
d. Reverse BACK/RECENT (mount system / vendor) or A2017X_softkey_reverse_module
e. System settings color accents
f. DarkMode & SettingsColorAccents thnx @kountry83
g. safetynet issues
Misc :
* A2017X-MoKee_vendor_boot_combo
* AEX bootanimation
* Havoc bootanimation
* There is no need to an incall fix as all of the listed are free of the bug.
* Also no problems with SD card or booting the roms.
* In some cases the package provided by the dev is GAPPS included. If no gapps provided you can simply flash the OFFICIAL GAPPS.
* All roms have NFC working. Hotspot isn’t reliable and mostly not working.
* Some Pie Roms do have more customization as to the other. Up to you to vote which one you do prefer. When voting it would be good when you make your vote based on ‘most stable/most customs/best battery life’
* Substratum works (tested on Benzo and NOS...)
I’m not going get into detail about each rom. I’ll leave that up to you to discuss further on. Perhaps if voting leads us to a one of a kind, we can focus on that in the future.
It would be much appreciated as you add your input even with your fixes or additions you want to point out.
This is something that is growing on XDA and all the input is welcome to improve what we have.
ENJOY !
@Oki, thnx for your guidance on flashing back and forth between (treble) roms
Credits to all mentioned in the thread and to all members for testing and improving it on TG !
Feel free to join us too on Axon7-trebleshoot
-----
Havoc P seems to be a good option. Im voting for havoc.
nays_pl said:
Havoc P seems to be a good option. Im voting for havoc.
Click to expand...
Click to collapse
A good one. As for me the Benzo, Los16PPR2 and Havoc are the best to this point.
Especially smoothness, battery life and customization are more then ok atm.
Updates will follow and improve things where needed.
Thanks @raystef66 ! Took some time away from flashing and was a bit lost of where to go on my axon after moving to aex5.8 and how to do. Good that you also have the instructions
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Axebladewarrior said:
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Click to expand...
Click to collapse
Thnx for the input !
True, as for me too, the AEX Oreo has a bunch of customs that Benzo still hasnt. But out of all GSI's Benzo and a couple others have the most.
Even on some Pie GSI's the displayed features aren't even working.
Batterylife as on NOS gave me 4-5 SOT on average use.
Anyway, like you said, still building up....
raystef66 said:
@Oki, if you want to guide the users on your method to flash a (s)GSI from scratch with your PartyTool, be our guest
Click to expand...
Click to collapse
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Awesome :highfive:
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
That would be great and much appreciated as you have followed your own guideline next to NFounds ! That's why I asked
I follow what you're trying to achieve and in fact I'm waiting to test the LabMods. Thnx !
As said, I come along with many people asking how to go back and forth between N,O and Pie. I know what to do in such occasions but many don't.
Because of your tools I'll leave the full guide on that up to you
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Thx. How about adb and encryption for TWRP2. 3.2-0L?
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
Read his OP in the thread he linked.
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
I have not developed new kernels but I have taken care of both situations. Just go to the TWRP Labs Mod thread, the info is in the OP and you can ask there too. This thread is all about the Pie implementations, Let's try to keep on topic as much as possible.
really hope MIUI 10 will be stable enough, miss MIUI
HOW TO...
Round Trip from NOUGAT or OREO to PIE GSI
OK, the full instructions to go from Nougat or Oreo to Pie, and back, would be:
Prerequisite
Bootloader Unlocked Axon 7
Install tools and configuration
1. Install TWRP Labs Mod Custom Recovery. Use the B12 version in case you are currently using Oreo encryption. Reboot to recovery.
2. Open the PARTY tool under Advanced > Oki Labs. If you do not have vendor partition you need to create one. Use the default configuration (System, 512MiB, at the end). Accept to reboot recovery. If the vendor partition is there, then just leave PARTY tool and continue with the next step.
Backup your daily driver config:
3. Go to the EDL Backup tool under Advanced > Oki Labs and create the Backup zip choosing FULL. If something goes wrong you will be able to restore your device using TWRP or MiFlash
4. From the Main Menu, backup your Data partition to the External SD.
5. Backup your Internal Storage using the option under Advanced > Oki Labs (Check the available space, the tool is not yet checking for available space, I will add it this weekend)
Prepare Treble configuration:
6. From TWRP Install the special B12 Bootloader with enabled EDL key combo support (The Universal Bootstack leads to DFU mode) and the modem for your region.
7. From the Main Menu, Wipe Vendor
8. Flash Axon 7 Treble ROM v1.1
Flash GSI package:
9. From the Main Menu, Wipe Dalvik / Cache / System / Data
10. From here you have to follow the installation instruction for the Generic System Image (GSI). Usually it is a single img file. So go to Install, press Install_Image button and navigate to the GSI file to flash it. Then just reboot. Some images would require additional ZIPs such as GApps or recommended patches.
Here you test the Pie ROM. If you want to test another Pie ROM you can try just going back to step 9. However, to ensure everything is clean you should start in step 7.
Return to your Daily Driver Config
11. Boot Recovery and flash the backup EDL ZIP you created in step 4. If you bricked your device just extract the contents of the file in your HD, Boot your phone into EDL mode, and use MiFlash. This step restore your original bootstack, modem and OS.
12. From main menu restore your Data partition
13. Go to Advanced > Oki Labs and restore Storage.
14. If you had to create the vendor partition in step 2, just run the PARTY tool again to remove the vendor partition.
15. From the Main Menu, Wipe Dalvik / Cache and reboot to system.
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Misc
Magisk Camera Module (MI A2 stock camera for Pie) - tested and works very good. Even flash is synchronised as well.
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
raystef66 said:
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Click to expand...
Click to collapse
How about hotspot? Is it working now?
privatedoodle said:
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
Click to expand...
Click to collapse
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Oki said:
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Click to expand...
Click to collapse
This new version works. Thanks!
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.
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.