Related
Install CFW Recovery on Redmi Note 8 Pro Included:
Flashing Antibrick Factory preloader
Flashing TWRP non CFW
Install CFW ROM
Flashing CFW Recovery.
STEP 1: Flash Anti Brick - Factory Preloader
The bootloader must be unlocked
Your Redmi Note 8 Pro must be in Android 9, If you are in Android 10, you must downgrade it to Android 9.* Read How to Downgrade Redmi note 8 pro MIUI 11 Android 10 to Android 9 MOD EDIT: Link Removed
Download Preloader FIX noBrick.zip and extract it
Enable USB Debugging
Connect the Phone to Computer
run "CMD" - Run as Administrator
In CMD command, go to "c:\platform-tools"
type "adb devices"
type "adb reboot bootloader"
Go to folder "Preloader FIX noBrick"
open flash_noauth.bat
Press any key to exit the command prompt windows
Press and hold Volume Up + Power key to enter Factory Preloader
Select [Normal Boot] Use Volume Up to select menu and Volume Down to confirm
STEP 2: Flash TWRP non CFW support
Enable USB Debugging
Connect the Phone to Computer
run "CMD" - Run as Administrator
In CMD command, go to "c:\platform-tools"
type "adb devices"
type "adb reboot bootloader"
Flashing twrpnoncfw.img* ( command: fastboot flash recovery twrpnoncfw.img )
Remove USB Cable
Press and hold Volume Up + Power key, when phone vibrate release power key, keep pressing volume up until preloader mode appears
Select [Recovery Mode] to enter TWRP Recovery
STEP 3: Install CFW Begonia
Select Wipe - select Dalvik, Cache, System, Swipe to confirm
Select Install ( If image file in SD Card: Select Storage - Micro SD card - OK ) - select begonia-A10-CFW_20200530.zip Swipe to confirm Flash
Install CFW Compatible ROM: Select Install ( If image file in SD Card: Select Storage - Micro SD card - OK ) - select cesiumOS.zip Swipe to confirm Flash ( you can use CFW compatible rom that you like )
Select Wipe - Format Data, type "yes" and Confirm
Select Reboot - Bootloader
STEP 4: Flash CFW Recovery
Connect Phone to Computer
Flashing TWRPCFW.img ( CFW Recovery ).* Go to CMD command type "fastboot flash recovery twrpcfw.img
Reboot phone: type "fastboot reboot"
Done! The phone now on CFW
Watch Video: https://youtu.be/Bgv8UTfd4Qw
Download:
Preloader FIX noBrick.zip
begonia-A10-CFW_20200530.zip Copy to SD Card
TWRP: cfw non recovery and cfw recovery copy to c:\platform-tools to make easier you can change the twrp image file to twrpnoncfw.img and twrpcfw.img
CFW ROM: CesiumOS ROM copy it to SD Card
Notes / Warning!
Use at your own risk, I'm not responsible for bricking your device.
Using the incorrect file may brick your device.
Make sure to backup your important data before flash it
thanx
another rn8p CFW'ed
with pixel experience rom
but in twrp internal storage is crypted
i followed all steps
it ask password for user [0]
perhaps one steps missing?
harmakhis said:
thanx
another rn8p CFW'ed
with pixel experience rom
but in twrp internal storage is crypted
i followed all steps
it ask password for user [0]
perhaps one steps missing?
Click to expand...
Click to collapse
Just type yours screenlock password/pin.
yeah i tried that but no success
harmakhis said:
yeah i tried that but no success
Click to expand...
Click to collapse
He forgot the first & second step... Which are the most important:
1. Turn OFF screen lock (pattern, pin or code)
2. Log out from Mi Account (if you are logged in)
Sent from my Redmi Note 8 Pro using Tapatalk
Good morning, I am terribly confused. Inside the Megapost, what is the noncwf and the cwf to flash? How do I know that my device has the cwf correctly? I hope you can guide me.
redymedan said:
to make easier you can change the twrp image file to twrpnoncfw.img and twrpcfw.img CFW ROM:
Click to expand...
Click to collapse
What do you mean change it??? Do you mean to say rename "twrp-CFW-3.3.1-0-begonia_UNOFFICIAL_0506.img" (the file that you linked) to "twrpnoncfw.img" and then make another copy and rename that one to "twrpcfw.img"?
eckre said:
What do you mean change it??? Do you mean to say rename "twrp-CFW-3.3.1-0-begonia_UNOFFICIAL_0506.img" (the file that you linked) to "twrpnoncfw.img" and then make another copy and rename that one to "twrpcfw.img"?
Click to expand...
Click to collapse
Yes, I mean rename it. twrp cfw support and TWRP non cfw
@redymedan I've removed the downgrade guide link from the first post, as it was linking to your blog/website. As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
...
...
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Request you to please list the downgrade steps directly in the first post, or create a separate post here and link that post in the your first post as the downgrade guide.
what are the procedures downgrading from miui 11 10 to miui 11 9
Preloader FIX noBrick.zip is 404, please provide an alternative.
@redymedan your download links are broken
Totara said:
@redymedan your download links are broken
Click to expand...
Click to collapse
Please ask to moderator LOL
I installed a Pixel Experience (Android 10) on my unlocked Redmi Note 5 India / Redmi 5 Plus (Vince) (Here on I'll refer to the device on Vince). Volte and data didn't work, and the call quality was pretty bad, so I decided to go back to the official MIUI and the Mi recovery.
This guide basically explains the easiest way to go back MIUI. Assuming your phone is unlocked. I'm adding direct download links to MIUI and other Mi tools because they are blocked in India.
Download Links:
Link 1: Normal Update ROM (Zip File)[bigota<dot>d<dot>miui<dot>com/V11.0.2.0.OEGMIXM/miui_HM5PlusGlobal_V11.0.2.0.OEGMIXM_f74369de0c_8.1.zip]
Link 2: Fastboot ROM (tgz File)[bigota<dot>d<dot>miui<dot>com/V11.0.2.0.OEGMIXM/vince_global_images_V11.0.2.0.OEGMIXM_20191108.0000.00_8.1_global_90dd70aa99.tgz]
Link 3: Last Updated Stable ROM(zip file)[update<dot>miui<dot>com/updates/v1/fullromdownload.php?d=vince_global&b=F&r=global&n=]
Link 4: Last Updated Beta ROM(zip file)[update<dot>miui<dot>com/updates/v1/fullromdownload.php?d=vince_global&b=X&r=global&n=]
Link 5: MiFlash(rar file)[cdn<dot>alsgp0<dot>fds<dot>api<dot>mi-img<dot>com/micomm/MiFlash2020-3-14-0.rar]
Link 6: Mi PC Suite(exe file)[bigota<dot>d<dot>miui<dot>com/MiFlash/MiSetup2.2.0.7032_2717.exe]
Link 7: This is not a direct link download twrp from one of the servers a direct link TWRP for Vince(img file) [twrp<dot>me/xiaomi/xiaomiredmi5plus<dot>html]
Link 8: This is not a direct link download Unlock tool from the page MIUI Unlock Tool(zip file) [en<dot>miui<dot>com/unlock/download_en<dot>html]
Link 9: This is not a direct link download Orangefox recovery tool from the page Orangefox Recovery(zip file)[orangefox<dot>download/en/device/vince]
Steps:
1. Download MIUI Unlock tool(Link 8) and extract it. Open cmd prompt inside the folder.
2. Switch your phone to fastboot mode (power + volume down). Connect it to your PC.
3. The device should show up when you enter "fastboot devices" in cmd.
4. Download TWRP (Link 7). extract it, rename it to "twrp.img" copy the image and copy it to the MIUI unlock tool. Now run "fastboot boot twrp.img". This should automatically take you to TWRP.
5. Now wipe everything. If you are not able to mount "data". Go to "Wipe", "Advanced", "Repair" then change the format of the data to exFat, then to FAT then to Ext4. This should mount data.
6. You should see your phone on your PC, if not mount USB in TWRP. Download orangefox recovery from Link 9. Copy it and flash it from twrp. Your phone will restart. Go to recovery mode and you should see orangefox.
7. Download fastboot ROM from Link 2. Unzip it copy "persist.img" from the folder to your phone, flash it using orangefox.
8. Download MiFlash tool from Link 5. Extract it and run it. Select the folder where you extracted fastboot ROM. MAKE SURE THAT THE PATH DOESN'T HAVE ANY SPACES OR FLASHING WILL FAIL. Now hit refresh on flash tool. It will show your device, at the bottom there is a selection where you can select the script to be executed. I generally select flash_all.bat, you can select flash_all_lock.bat for a locked OS.
It might show you "error:Not catch checkpoint (\$fastboot -s .*lock),flash is not done", but your phone will boot properly, it will show a success message only if you choose lock option bat. But this error shouldn't affect the installation.
9. Restart your phone, everything should work properly.
Good luck!
Thank you.
What to do with the link 1 file the ROM file ? Can I directly flash it in twrp ??
thanks bro
That answered all my questions, and i don't know why but all the other mi flash tool found on the web didnt work but this one is just perfect. Thank you so much bro !!! you really simplified my life
[28NOV20][Guide] How To ROOT ALL US VER. NOTE 10(+) & Flash TWRP (SnapDragon Only)
Step by Step: How to Root & Flash TWRP on Samsung Galaxy Note 10(+) and Every other Galaxy from S10 and up (SnapDragon Only)
Update: If You Want To Unlock Your Bootloader go here: U.S. Samsung Galaxy Bootloader Unlock Service
So You Figured Out How to Unlock The Bootloader on your Shiny New/Old (Snapdragon) Samsung Galaxy Thing-a-ma-jig
Good on you, but now you want to figure out how to Root properly and enjoy the spoils of said Unlock. Well You've come to right place.
DO NOT QUOTE THE OP PLEASE, (If you would like to place this guide in your respective Device Threads ie. Galaxy s10, s20, s20 Note 20 Ultra 5g etc. thats perfectly fine)
Welcome: Be nice, be courteous and *enjoy
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with unrooting, some functions may never.
- All your data on device will be lost (Factory Reset is in the Instructions below)
- Flashing custom binaries may brick (Usually it's a soft but can be hard brick too), so follow it on your own risk!
Now that you accept the risks, let's have some fun -
Important: Although this is a simple guide you must follow all directions clearly
Simple guide to root your device and install TWRP after unlock: (Thanks to @Krog18 )
1. Download vbmeta_disabled.tar, TWRP for your device, magisk and multidisabler-samsung-2.6-afaneh92
2. Reboot to download mode and flash vbmeta_disabled.tar in ap slot and reboot. Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
3. Uncheck auto reboot in Odin and flash TWRP in ap slot.
4. Hold volume down and power until the screen goes black then immediately switch to holding volume up, Bixby button (10 series only) and power to reboot into TWRP
5. Flash multidisabler and reboot recovery
6. Go to wipe, format and type yes to format data
7. Flash magisk
8. Make a backup of efs and store it somewhere safe
9. Reboot
*First boot may take 10-15 minutes. If it doesn't boot in 15 minutes, force reboot by holding power and volume down for at least 10 seconds
Additional Method For Rooting If Above method did not work for you:
Step 1 : (Root Base Firmware with Magisk By patching files yourself, Then Flash TWRP in Odin)
Prepare Firmware files for root
You need to Patch AP File to flash using Odin to root device.
1. Download stock firmware for your device ie (SM-N975U/U1, SM-G973U/U1, SM-G975U/U1)
You need to download file according your region and model.
2. Once you finish download, extract files and keep all files on in a folder on the desktop of PC. From extracted files find the file with name AP_[device_model_sw_ver].tar.md5 copy to your Phone.
3.Download Latest Magisk Manager and Install to your device (Make sure to check for updates) (Optionally go into settings and switch the update channel to BETA)
4.Open Magisk Manager - Find Magisk Install (Top One) - Click Install - select to "Select and Patch file" - Click the AP file you have copied to your device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the entire firmware file and output the newly Patched AP file to [Internal Storage]/Download/magisk_patched.tar
6.Now Copy patched AP file magisk_patched.tar back to Your PC
7.Download latest Odin and extract to Desktop on your PC
Step 2. Installing custom firmware files with Odin
1. Reboot to download mode and select volume up to continue:
2. Open Odin (as administrator) {Right-Mouse click--Open As Administrator}
Select AP in Odin and use the magisk_patched.tar file you have patched {The file you just patched with Magisk} for AP tab of Odin
Select BL,CP and CSC files (Use the files from the firmware you downloaded earlier) (This is VERY important, DON'T just flash only the magisk_patched.tar)
(Use All of the respective files BL, CP, CSC)
3.From Odin option - uncheck Auto Reboot option (I do this because I like rebooting when I'm ready)
4. Make sure all files are in the right place, Now Hit Start and wait till it's completely finish. When It shows PASS in Odin, disconnect device.
Okay Now the hard part is over, you can let the phone boot to system and Skip all Setup Steps because Next is TWRP.
Step 3. Odin: Flash Twrp and Boot with Magisk
Very Simple yet very Important:
1. Download the respective TWRP (Twrp<version_number>.TAR for you phone model (This is going to Odin flashed so you need .TAR file)
2. Reboot your phone into Download Mode, Hold Vol- and Power Button until it gets to DL Screen and press up for "Yes"
3. Put the Twrp<version_number>.TAR in the AP slot
4. Make sure the file is selected, (Unselect Auto-reboot in options tab in Odin) and in place and hit Start
5. Wait until it's finished, Now Hold Vol- and Power until you see black screen, release and then hold Vol+ and Power until you see TWRP recovery
Now Flash Multidisabler and Magisk
1. Flash multidisabler (Mega) (Google Drive) and reboot back to TWRP
2. Wipe data and storage
3. Flash Latest Magisk
*Enjoy
*** Remember: Make a backup of EFS through TWRP and save it to your desktop or Cloud service ie. MEGA, GDrive, Dropbox ****
Please I can't seem to unlock my bootloader because OEM Unlocking functionality is missing on my device. I have tried and still can't find it. Can I root the device without Unlocking the bootloader?
stylemonument said:
Please I can't seem to unlock my bootloader because OEM Unlocking functionality is missing on my device. I have tried and still can't find it. Can I root the device without Unlocking the bootloader?
Click to expand...
Click to collapse
If you could just download and install Telegram app and PM this guy on there (drivel2787)
Please see here: Bootloader Unlock Service For US Variants
BoiBundy said:
If you could just download and install Telegram app and PM this guy on there (drivel2787)
Click to expand...
Click to collapse
Okay.... let me do that. Thanks.
Maybe should include that US Snapdragon will have to get their bootloader unlocked first and how they do..include Telegram. Or your probably going to constantly get the "I can't find OEM unlock" question.
Sent from my SM-N975U using Tapatalk
Msgd re: oem unlock! Btw, if we got any awesome Sam sec experts out there who wouldn’t mind entertaining some qs from me regarding a lot of WEIRD stuff happening w my phone, be eternally grateful. Could even work out a monetary deal for your time, and (perhaps) help!
Thanks much in adv, msg on telegram as @nemotheDreamer.
butchieboy said:
Maybe should include that US Snapdragon will have to get their bootloader unlocked first and how they do..include Telegram. Or your probably going to constantly get the "I can't find OEM unlock" question.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
You might be right, I will edit it tonight
So we can legit root the Snapdragon version now?
Nickdroid86 said:
So we can legit root the Snapdragon version now?
Click to expand...
Click to collapse
Yes, it's been going on now for a few months. I've done it myself. It's completely legit
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
Nice Tut BoiBundy, well written.
cerj said:
Yes, it's been going on now for a few months. I've done it myself. It's completely legit
---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------
Nice Tut BoiBundy, well written.
Click to expand...
Click to collapse
Thanks man, wanted to have a central "fool-proof" way for people to enjoy the freedom of root
Just to be clear - I need to pay to get my bootloader unlocked? That's still the case, right?
MonkeyJug said:
Just to be clear - I need to pay to get my bootloader unlocked? That's still the case, right?
Click to expand...
Click to collapse
Check Here: https://forum.xda-developers.com/t/sampwnd-usa-model-bl-unlock-info-u-u1-w.4201689/
I've been on Nexus and Pixel devices so long now I cannot remember much about modification on Samsung devices. Last one I had rooted was the Note 2. Anyway, bootloader unlocked and successfully rooted my SM-N975U (Note 10+). Now there are updates available so I am sorry if this isn't the place or if a dumb question, but is there any special way I need to do updates on the snapdragon so I don't relock the bootloader or lose root? With Pixel, ADB sideload was easy, not sure with this one.
Is there a multi disabler package that is compatible with the SM-N976V ? I have tried multiple iterations of multidisabler-samsung-2.6c-afaneh92 but am have trouble.
nabnab25658 said:
Is there a multi disabler package that is compatible with the SM-N976V ? I have tried multiple iterations of multidisabler-samsung-2.6c-afaneh92 but am have trouble.
Click to expand...
Click to collapse
I was in the same boat, went to the telegram channel and the guy who made that file added support for 976V. Not sure where else it's available, but you should be able to get it there from Mohammad.
TWRP for S20/N20/TabS7/ZFold2 (Snapdragon)
t.me
Dick_Stickitinski said:
I was in the same boat, went to the telegram channel and the guy who made that file added support for 976V. Not sure where else it's available, but you should be able to get it there from Mohammad.
TWRP for S20/N20/TabS7/ZFold2 (Snapdragon)
t.me
Click to expand...
Click to collapse
Hey, just wanted to thank you for pointing me in the right direction. I've had my Sm-976V BL unlocked and rooted for a bit now, but have been busy hence the late reply.
I have an issue. I boot into TWRP just fine but all my files in sdcard are nothing but random numbers and letters
I think this happens when you don't wipe your data. You also need to flash a decryption file. It happened to me at first because I didn't wipe all data.[/QUOTE]
BoiBundy said:
[28NOV20][Guide] How To ROOT ALL US VER. NOTE 10(+) & Flash TWRP (SnapDragon Only)
Step by Step: How to Root & Flash TWRP on Samsung Galaxy Note 10(+) and Every other Galaxy from S10 and up (SnapDragon Only)
Update: If You Want To Unlock Your Bootloader go here: U.S. Samsung Galaxy Bootloader Unlock Service
So You Figured Out How to Unlock The Bootloader on your Shiny New/Old (Snapdragon) Samsung Galaxy Thing-a-ma-jig
Good on you, but now you want to figure out how to Root properly and enjoy the spoils of said Unlock. Well You've come to right place.
DO NOT QUOTE THE OP PLEASE, (If you would like to place this guide in your respective Device Threads ie. Galaxy s10, s20, s20 Note 20 Ultra 5g etc. thats perfectly fine)
Welcome: Be nice, be courteous and *enjoy
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with unrooting, some functions may never.
- All your data on device will be lost (Factory Reset is in the Instructions below)
- Flashing custom binaries may brick (Usually it's a soft but can be hard brick too), so follow it on your own risk!
Now that you accept the risks, let's have some fun -
Important: Although this is a simple guide you must follow all directions clearly
Simple guide to root your device and install TWRP after unlock: (Thanks to @Krog18 )
1. Download vbmeta_disabled.tar, TWRP for your device, magisk and multidisabler-samsung-2.6-afaneh92
2. Reboot to download mode and flash vbmeta_disabled.tar in ap slot and reboot. Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
3. Uncheck auto reboot in Odin and flash TWRP in ap slot.
4. Hold volume down and power until the screen goes black then immediately switch to holding volume up, Bixby button (10 series only) and power to reboot into TWRP
5. Flash multidisabler and reboot recovery
6. Go to wipe, format and type yes to format data
7. Flash magisk
8. Make a backup of efs and store it somewhere safe
9. Reboot
*First boot may take 10-15 minutes. If it doesn't boot in 15 minutes, force reboot by holding power and volume down for at least 10 seconds
Additional Method For Rooting If Above method did not work for you:
Step 1 : (Root Base Firmware with Magisk By patching files yourself, Then Flash TWRP in Odin)
Prepare Firmware files for root
You need to Patch AP File to flash using Odin to root device.
1. Download stock firmware for your device ie (SM-N975U/U1, SM-G973U/U1, SM-G975U/U1)
You need to download file according your region and model.
2. Once you finish download, extract files and keep all files on in a folder on the desktop of PC. From extracted files find the file with name AP_[device_model_sw_ver].tar.md5 copy to your Phone.
3.Download Latest Magisk Manager and Install to your device (Make sure to check for updates) (Optionally go into settings and switch the update channel to BETA)
4.Open Magisk Manager - Find Magisk Install (Top One) - Click Install - select to "Select and Patch file" - Click the AP file you have copied to your device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the entire firmware file and output the newly Patched AP file to [Internal Storage]/Download/magisk_patched.tar
6.Now Copy patched AP file magisk_patched.tar back to Your PC
7.Download latest Odin and extract to Desktop on your PC
Step 2. Installing custom firmware files with Odin
1. Reboot to download mode and select volume up to continue:
2. Open Odin (as administrator) {Right-Mouse click--Open As Administrator}
Select AP in Odin and use the magisk_patched.tar file you have patched {The file you just patched with Magisk} for AP tab of Odin
Select BL,CP and CSC files (Use the files from the firmware you downloaded earlier) (This is VERY important, DON'T just flash only the magisk_patched.tar)
(Use All of the respective files BL, CP, CSC)
3.From Odin option - uncheck Auto Reboot option (I do this because I like rebooting when I'm ready)
4. Make sure all files are in the right place, Now Hit Start and wait till it's completely finish. When It shows PASS in Odin, disconnect device.
Okay Now the hard part is over, you can let the phone boot to system and Skip all Setup Steps because Next is TWRP.
Step 3. Odin: Flash Twrp and Boot with Magisk
Very Simple yet very Important:
1. Download the respective TWRP (Twrp<version_number>.TAR for you phone model (This is going to Odin flashed so you need .TAR file)
2. Reboot your phone into Download Mode, Hold Vol- and Power Button until it gets to DL Screen and press up for "Yes"
3. Put the Twrp<version_number>.TAR in the AP slot
4. Make sure the file is selected, (Unselect Auto-reboot in options tab in Odin) and in place and hit Start
5. Wait until it's finished, Now Hold Vol- and Power until you see black screen, release and then hold Vol+ and Power until you see TWRP recovery
Now Flash Multidisabler and Magisk
1. Flash multidisabler (Mega) (Google Drive) and reboot back to TWRP
2. Wipe data and storage
3. Flash Latest Magisk
*Enjoy
*** Remember: Make a backup of EFS through TWRP and save it to your desktop or Cloud service ie. MEGA, GDrive, Dropbox ****
Click to expand...
Click to collapse
which TWRP version to flash and which odin? hope i can get answer i had N975U1 unlocked bootloader
Anyone else getting that pesky "Android 11 Update" since they have rooted? I keep postponing it. I'm guessing it will fail if I try to install. Not sure what I should do.
Sammobile don't seem to have the firmware available yet. I was thinking installing it with odin then patching AP with Magisk
BoiBundy said:
[28NOV20][Guide] How To ROOT ALL US VER. NOTE 10(+) & Flash TWRP (SnapDragon Only)
Step by Step: How to Root & Flash TWRP on Samsung Galaxy Note 10(+) and Every other Galaxy from S10 and up (SnapDragon Only)
Update: If You Want To Unlock Your Bootloader go here: U.S. Samsung Galaxy Bootloader Unlock Service
So You Figured Out How to Unlock The Bootloader on your Shiny New/Old (Snapdragon) Samsung Galaxy Thing-a-ma-jig
Good on you, but now you want to figure out how to Root properly and enjoy the spoils of said Unlock. Well You've come to right place.
DO NOT QUOTE THE OP PLEASE, (If you would like to place this guide in your respective Device Threads ie. Galaxy s10, s20, s20 Note 20 Ultra 5g etc. thats perfectly fine)
Welcome: Be nice, be courteous and *enjoy
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with unrooting, some functions may never.
- All your data on device will be lost (Factory Reset is in the Instructions below)
- Flashing custom binaries may brick (Usually it's a soft but can be hard brick too), so follow it on your own risk!
Now that you accept the risks, let's have some fun -
Important: Although this is a simple guide you must follow all directions clearly
Simple guide to root your device and install TWRP after unlock: (Thanks to @Krog18 )
1. Download vbmeta_disabled.tar, TWRP for your device, magisk and multidisabler-samsung-2.6-afaneh92
2. Reboot to download mode and flash vbmeta_disabled.tar in ap slot and reboot. Device will reboot to recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
3. Uncheck auto reboot in Odin and flash TWRP in ap slot.
4. Hold volume down and power until the screen goes black then immediately switch to holding volume up, Bixby button (10 series only) and power to reboot into TWRP
5. Flash multidisabler and reboot recovery
6. Go to wipe, format and type yes to format data
7. Flash magisk
8. Make a backup of efs and store it somewhere safe
9. Reboot
*First boot may take 10-15 minutes. If it doesn't boot in 15 minutes, force reboot by holding power and volume down for at least 10 seconds
Additional Method For Rooting If Above method did not work for you:
Step 1 : (Root Base Firmware with Magisk By patching files yourself, Then Flash TWRP in Odin)
Prepare Firmware files for root
You need to Patch AP File to flash using Odin to root device.
1. Download stock firmware for your device ie (SM-N975U/U1, SM-G973U/U1, SM-G975U/U1)
You need to download file according your region and model.
2. Once you finish download, extract files and keep all files on in a folder on the desktop of PC. From extracted files find the file with name AP_[device_model_sw_ver].tar.md5 copy to your Phone.
3.Download Latest Magisk Manager and Install to your device (Make sure to check for updates) (Optionally go into settings and switch the update channel to BETA)
4.Open Magisk Manager - Find Magisk Install (Top One) - Click Install - select to "Select and Patch file" - Click the AP file you have copied to your device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the entire firmware file and output the newly Patched AP file to [Internal Storage]/Download/magisk_patched.tar
6.Now Copy patched AP file magisk_patched.tar back to Your PC
7.Download latest Odin and extract to Desktop on your PC
Step 2. Installing custom firmware files with Odin
1. Reboot to download mode and select volume up to continue:
2. Open Odin (as administrator) {Right-Mouse click--Open As Administrator}
Select AP in Odin and use the magisk_patched.tar file you have patched {The file you just patched with Magisk} for AP tab of Odin
Select BL,CP and CSC files (Use the files from the firmware you downloaded earlier) (This is VERY important, DON'T just flash only the magisk_patched.tar)
(Use All of the respective files BL, CP, CSC)
3.From Odin option - uncheck Auto Reboot option (I do this because I like rebooting when I'm ready)
4. Make sure all files are in the right place, Now Hit Start and wait till it's completely finish. When It shows PASS in Odin, disconnect device.
Okay Now the hard part is over, you can let the phone boot to system and Skip all Setup Steps because Next is TWRP.
Step 3. Odin: Flash Twrp and Boot with Magisk
Very Simple yet very Important:
1. Download the respective TWRP (Twrp<version_number>.TAR for you phone model (This is going to Odin flashed so you need .TAR file)
2. Reboot your phone into Download Mode, Hold Vol- and Power Button until it gets to DL Screen and press up for "Yes"
3. Put the Twrp<version_number>.TAR in the AP slot
4. Make sure the file is selected, (Unselect Auto-reboot in options tab in Odin) and in place and hit Start
5. Wait until it's finished, Now Hold Vol- and Power until you see black screen, release and then hold Vol+ and Power until you see TWRP recovery
Now Flash Multidisabler and Magisk
1. Flash multidisabler (Mega) (Google Drive) and reboot back to TWRP
2. Wipe data and storage
3. Flash Latest Magisk
*Enjoy
*** Remember: Make a backup of EFS through TWRP and save it to your desktop or Cloud service ie. MEGA, GDrive, Dropbox ****
Click to expand...
Click to collapse
it works on my N975U1 android 10 Q version 1st method so no need 2nd method
Spoiler: Quick Links
Official LineageOS 16.0 (15.02.2021)
.401 Stock Images (C432)
Stock Recovery
Stock E-recovery
Official TWRP (3.7.0)
Official TWRP (3.4.0-1)
Modified TWRP (3.4.0)
Heavily Modified TWRP (3.4.0)
Magisk Patched Recovery (25.2)
Magisk-Delta Patched Recovery (25.2-delta)
Stock Kernel (4.9.148)
Phenix Kernel (4.9.319 by Turex)
Phenix Permissive Kernel (4.9.319 by Iceows)
Phenix Permissive Kernel (4.9.235 by Abdelhay.ali)
Phenix Enforcing and Permissive Kernel for Android 13 (4.9.319 by Abdelhay.ali)
Selinux Rules for Android 13 (by Abdelhay.ali)
Everything Else (47GB)
Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing Any GSINote:Phh is "retiring". Community of builders created trebledroid initiative to keep his work alive. Don't expect same level of quality for a while.
Use vndklite variants.
At no point you need to wipe /data or any other partition. Just do factory reset.
If you want to backup via twrp you need to have encryption disabled.
Almost all chromium based browsers including chrome freeze after few minute of use. That is caused by DRM not working as intended in gsis. To fix it flash DRM fix.
Permissive kernel shouldn't be used daily. Please only use it for debugging purposes.
Prerequisites:
ADB and Fastboot Installed (1)
Any Arm64 AB GSI image (1) (2) (3) (4) (5)
Google apps package (Optional) (1) (2) (3) (4)
TWRP
Unlocked Bootloader
Spoiler: Android 12 and Below
Spoiler: GSI with GAPPS
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Stock Recovery: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Factory Reset > Type yes > Press power
Boot into system
Spoiler: Vanilla GSI + Gapps + Zips
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash Phenix Kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Resize system: Wipe > Advanced Wipe > Tick System > Repair or Change File System > Swipe Resize File System
if it fails issue these commands from your computer:
adb shell "/sbin/e2fsck -fp /dev/block/platform/hi_mci.0/by-name/system"
adb shell "/sbin/resize2fs /dev/block/platform/hi_mci.0/by-name/system"
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash DRM fix (Optional): ''
Flash NFC fix (Optional / Might not Work): ''
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Android 13 and Beyond(?)
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash gsi image: fastboot flash system drag & drop img file to console
Flash one of these kernel (Optional): fastboot flash kernel and drag & drop img file to console
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset: Wipe > Swipe Factory Reset
Flash this AIO fix : Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Flash Gapps Zip (Optional): ''
Boot into system: Reboot > System
Spoiler: Tweaks
Spoiler: TWRP on Erecovery, Magisk on Recovery Setup
Flash over to erecovery:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash one of these (1) (2) twrp images: fastboot flash recovery_ramdisk and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Push twrp to /cache: adb push drag & drop img file to console /cache
Flash twrp to erecovery: Install > Install Image > Select twrp image from /cache folder > Pick erecovery_ramdisk partition > Swipe
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash magisk patched image: fastboot flash recovery_ramdisk and drag & drop img file to console
From now on this is how you boot:
No keypress: System (Long yellow warning)
Power & Vol+ before Yellow Warning : System with magisk (Short yellow warning)
Vol+ on Yellow Warning : TWRP
If you want to return to stock erecovery, do these:
Boot into twrp
Push erecovery image to /cache: adb push drag & drop img file to console /cache
Flash erecovery to erecovery: Install > Install Image > Select erecovery image from /cache folder > Pick erecovery_ramdisk partition > Swipe
Spoiler: Passing Safetynet (For Android 12 and Below
Keep in mind that Safetynet is deprecated and Google is encouraging developers to switch to Play Integrity API. To pass safetynet you need to have 3 checkmarks, as such you'll need to follow all 3 instructions I'm about to give you.
Spoiler: Evaluation Type Basic
Disable "Spoof Pixel 5" & Enable Safetynet in phh options then reboot.
Download YASNAC from play store and check for "Evaluation Type" from result.
If it says Basic and others fail you can skip this part.
If test fails or doesn't finish do these:
Install Magisk
Enable Zygisk & Enforce denylist
Install Universal SafetyNet Fix module by kdrag0n
Now check YASNAC again. It should finish test and say Basic in evaluation type.
Spoiler: Basic Integrity Fail
This happens because root is detected most of the time.
If your GSI has Dynamic Root, uncheck root from phh settings.
If your GSI has SU, securize from phh settings.
If you had to flash magisk because of evaluation type, tick google play and google play services in denylist.
If those didn't fix, contact GSI maintainer.
Spoiler: CTS Profile Match Fail
This happens because build fingerprint is not play certified.
Make sure you have safetynet option ticked in phh settings and do these:
Edit /data/adb/phh/secure
Add these 2 lines to bottom:
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
Reboot and test again.
Everytime you untick safetynet you have to edit this file again. You can also pick any other fingerprint from here should you choose to. You need both fingerprint and patch date. If you want to simulate other devices add following lines:
resetprop_phh ro.product.brand HUAWEI
resetprop_phh ro.product.device HWANE
resetprop_phh ro.product.manufacturer HUAWEI
resetprop_phh ro.product.model ANE-LX1
resetprop_phh ro.product.name ANE-LX1
Spoiler: Passing Play Integrity (For Android 13 and Beyond)
If you want to pass it you're going to have to read this wall of text. I can't shorten it.
What is Play Integrity:
Google enforces Play Inregrity once your api level is set to 33 (android 13). I currently don't have enough information about it other than apps can decide which checks to perform on your device. One of those checks is called strong integrity. We can't pass strong integrity because it requires hardware backed checks which our device lack. However you can still fool some apps that don't enforce strong integrity.
How you can fool it:
Ever since magisk retired magiskhide, some forks have been made to keep it maintained and improved. One of those forks is Magisk Delta. Before you head over to it's github and install it, you still need to install a valid CTS fingerprint. Then you can install Magisk Delta.
Steps:
Disable Spoof Pixel 5 & Enable Safetynet from phh settings if they exist.
Add these 2 lines to bottom of /data/adb/phh/secure (create if it doesnt exist) & Reboot
resetprop_phh ro.build.fingerprint HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L01/9.1.0.368C432:user/release-keys
resetprop_phh ro.build.version.security_patch 2020-08-01
If you have magisk :
- Download Magisk Delta apk
- Change .apk to .zip
- Install it as magisk module
If you don't have magisk :
- Download & install Magisk Delta apk
- Patch recovery_ramdisk & flash it via fastboot
Enable Zygisk and MagiskHide from Magisk Delta App
Install this module : https://github.com/HuskyDG/safetynet-integrity-fix/releases
MAKE SURE GMS IS NOT IN HIDELIST
Reboot and test safetynet. (Feel free to link any app that tests for Play Integrity)
Spoiler: I went back to EMUI, why it looks like aosp?
That happens because EMUI stores it's themes and few stock apps in /data/hw_init folder. When you factory reset with stock recovery, they are preserved. But when you use twrp to factory reset they are removed. Doing factory reset once from twrp is enough to make EMUI think it's corrupted, in acuality it isn't. To fix it you can either let EMUI update from system settings or you can download this, extract hw_init folder and push folder to /data from twrp with this command :
adb push drag & drop hw_init folder to console /data
Flashing LineageOS 16.0Note:Stock kernel from EMUI .300> have trouble with wifi. Use Phenix 4.9.319 or above to fix it.
Prerequisites:
ADB and Fastboot Installed (1)
Google apps package (Pick Pie or 9.0 editions) (1) (2) (3) (4)
LineageOS Zip (From Archive or From Mega)
Phenix Kernel (Else you won't have wi-fi)
TWRP (3.4.0 is needed for factory reset functionality)
Unlocked Bootloader
Spoiler: Steps
Tick "Enable OEM Unlock" from developer options
Boot into fastboot: Hold vol- while usb connected and phone rebooting
Flash this TWRP: fastboot flash recovery_ramdisk and drag & drop img file to console
Flash Phenix Kernel (Required for Wi-Fi): fastboot flash kernel and drag & drop img file to console
Boot into twrp: power + vol+ while NOT connected to pc
Flash lineage zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Factory reset: Wipe > Swipe Factory Reset
Boot into Vanilla LineageOS or Keep following to flash gapps
Encrypt or Decrypt /Data (Optional): Mount > Tick Vendor > adb push drag & drop fstab file to console /vendor/etc
Flash gapps zip: Advanced > ADB Sideload > Swipe to Start Sideload > Write adb sideload and drag & drop zip file to console
Boot into system: Reboot > System
Getting Stock Firmware Files And DowngradingSources:
A certain russian site (linking is prohibited)
EMUI's System Updater (via root)
Firmware Finder (Revived)
HiSuite
Huawei Update Extractor
HuRUpdater Guide / HuRUpdater Download (For older builds)
HwOTA8 (For Emui 8)
Spoiler: Getting Individual Images
Firmware finder has been revived and you can use that to get your prefered cust or build.
If you need only one image not the whole build, I uploaded each one you'd typically need below.
CUST.img
DTS.img
ERECOVERY_KERNE.img
ERECOVERY_RAMDI.img
ERECOVERY_VBMET.img
ERECOVERY_VENDO.img
FASTBOOT.img
KERNEL.img
ODM.img
PRODUCT.img
RECOVERY_RAMDIS.img
RECOVERY_VBMETA.img
RECOVERY_VENDOR.img
SYSTEM.img
VBMETA.img
VENDOR.img
XLOADER.img
They are from .401 c432.
If you wiped /data once you probably won't have emui themes etc if you go back to emui. To fix that you can push hw_init folder (in data.7z) to /data. Not the contents of it, just put the folder in root of /data. It should be like this: /data/hw_init
Spoiler: Hisuite
Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip to your documents folder. update_full_base.zip file contains main UPDATE.APP. You can extract images from it with Huawei Update Extractor
Spoiler: EMUI's System Updater
Flash magisk patched image from quick links. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot because recovery is not stock. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done go to /data/update with a root file explorer. Copy HwOUC folder to internal storage and from there to your pc. There should be 3 folders with numbers. You can find our main update_full_base.zip in one of them.
Spoiler: Downgrading
Spoiler: From EMUI 9 to EMUI 9
Spoiler: Using just the SYSTEM.IMG
Get files of your prefered build. I recommend build .278. Extract SYSTEM.IMG from UPDATE.APP via huawei update extractor and flash it with fastboot flash system . Factory reset with stock recovery then flash any TWRP except for the official ones. Official TWRPs freezes when wiping /data which is what we need to do. After wiping /data boot into system. You should have aosp background with square app icons if you did correctly. Check for system updates and it should find your current build. Download and install.
Spoiler: Using dload from Certain Russian Site
BOOTLOADER WILL RELOCK, DON'T DO THIS IF YOU DON't HAVE YOUR BL CODE
For this you need to have a sd card that is formated as exfat. Fat32 doesn't allow >4gb files so exfat is required. Download your prefered build from Androidhost.ru or mega link above. Inside the zip file you'll find a folder named dload. Extract this folder to somewhere and transfer it to your sd card. Folder structure should look like below. Hw_eu and L01/L21 will depend on your region and single/dual sim status. After this unplug your phone and shut it down. Start pressing vol- vol+ and power all at the same time. Different kind of yellow warning will appear and a screen with blue progress bar over black background will appear. If you downloaded correct variant for your phone it'll start progressing. After process is done you'll boot into stock emui with NO yellow warning. This is because your bootloader is locked. Do whatever you want at this point but remember, unlocking bootloader again will low level factory reset your phone.
-/storage/AAAA-BBBB/dload
---/update_sd
---/ANE-L01_hw_eu
---/ANE-L21_hw_eu
Spoiler: From EMUI 9 to EMUI 8
If I recall correctly there is only one way to do this. You can't dload between emui versions. You also need to be on stock emui for hisuite to function. Some people say a specific hisuite version is required but it wasn't the case for me. Plug your phone to pc, hisuite should show up beside your phone in drives section. Install it and open it. Do whatever it instructs you to function correctly. After you see your phone in app click Update button. Then click on "Earlier Versions". It'll show version 8.0.0.167 along with some warnings. Rest it pretty straightforward. Follow along and it'll return you back to emui 8. But if you're doing this to unlock your bootloader, build .167 is not enough. Exploit that dc-unlocker uses is patched in this version. So you have to roll back further. I had success with .125 build but up until .150 could work. Link to .125 build.
edit ? : Revised guide
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
If you want to disable encryption do it now
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have TWRP installed, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zip (EMUI8 and EMUI9)
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download
HwOTA
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the EMUI9 from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours if you don't know what you're doing. C432 for Europe for example. After you download the zip file open it up and find the dload folder. You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. It might not get all 3 files most of the time so you have to copy each of them and update a few versions consecutively to get them. Keep in mind, it deletes each update file after it is successful so make sure to make a copy of them some place else. I recommend reverting back to EMUI8 through hisuite and then updating it to latest one to get all files. It is tidious but you need to do this once. It doesnt update you to .370 from .132. It'll send you .132 then .200 then .368 then latest whatever. You can actually use these files with HuRu updater or HwOTA to manually update. Or you can get the UPDATE.APP inside them and extract images with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA requires.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Click to expand...
Click to collapse
I wish good luck to those who will use your guide .
Among other things, the HwOTA and HuRupdater methods have not worked since February (unless someone has the necessary files stored on the disk). Huawei changed servers and Firmware Finder is dead.
EMUI 8 firmware download doesn't work for the same reasons .
avenger.forsyth said:
I wish good luck to those who will use your guide .
Click to expand...
Click to collapse
Everyone has the right to write a guide, but the author must know what he is writing about. Guide made by the "copy/paste" method will not help anyone very much...
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select shut down
Press and hold power + vol+ buttons until short yellow warning shows up
Select factory reset and type yes, while it is doing that plug the phone to pc
After factory reset is complete select reboot option and hold down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so go to install and select gapps zip
Reboot to system
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
You're good to boot up the system
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send adb reboot bootloader command from console
After restart write fastboot flash system to console and drag gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
You should be at stock recovery_ramdisk, do a factory reset
Plug your phone back and press reboot from screen
While booting press and hold vol- button until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize
Press Install, select and flash gapps zip
Reboot to system
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Boot to TWRP (power + vol+ after shutting down)
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe resides
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts part from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img, if you have it installed go to step 21 if not do 19 or 20 first
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select and flash stock recovery_ramdis.img to recovery_ramdisk partition
If not shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Click to expand...
Click to collapse
Oh, man! Are you serious?
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Frax3r said:
I don't know what anyone expects from a guide... Is it better to just repeat the same thing over and over again? "Flash system with fastboot, factory reset with stock recovery, flash and boot twrp, resize system, flash gapps" is literally the summary of this. That summary is what you'll get as an answer if you ask for help on any telegram group. Instead of saying flash twrp, I wrote how you can flash twrp. Thats why it's so long. This guide is for "how" not "what".
Click to expand...
Click to collapse
I would say that even so far, people have managed to install GSI, Magisk, etc. .
Btw, Recovery and eRecovery are the same for all models and build numbers . They are even compatible with LLD and BND models.
Frax3r said:
Thats why it's so long
Click to expand...
Click to collapse
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Sorry but Chapter "Magisk" is useless. Nowadays nobody needs to install the old Magisk. Rather focus on some of the nuances of installing Magisk on EMUI 9.1 that would be helpful.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
No comment...
Frax3r said:
Get the official TWRP .img and patch it with magisk manager
Click to expand...
Click to collapse
No comment...
Have a good day!
Frax3r said:
Hello there! Alive parts of this forum is still filled with simple help requests so I decided to put together a simple all-in-one thread that basically covers most stuff. I don't wanna get into bootloader unlocking because right now only free way to do so is with potatoNV which I do not know how to use. Dc-unlocker is an option too but it is 4€ so pick your poison.
I have uploaded all my resources for this device to here. Inside EMUI folder you'll find some of the versions that I archived with the methods I explained on getting firmwares section. You can find recovery_ramdis.img from each of these version inside RECOVERY_RAMDISK folder as well.Special key combos:
Power + Vol+ = Recovery Mode
While USB connected, Power + Vol+ = Erecovery Mode
While USB connected, Vol- = Fastboot
Plug USB while holding down Vol+ + Vol- = Download Mode
Power + Vol+ + Vol- = Force Dload
Flashing LineageOS 16.0Prerequisites:
Emui Version below 9.1.0.300
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Los16 zip
Official TWRP
Stock recovery_ramdis.img
Your choice of gapps zip
Steps:
Get the Prerequisites
I recommend sending los 16 zip, recovery_ramdis.img and gapps zip to sd card if possible
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Install and select los 16 zip file
If you want to disable encryption do it now
Press Install and press Install Image
Select and flash stock recovery_ramdis.img to recovery_ramdisk partition
Press Reboot and select Recovery
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Repeat step 6-7-8
Los 16 don't need to be resized so press Install and select gapps zip
Press Reboot System
Flashing Any GSIPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
GSI image (1) (2)
Official TWRP
Stock recovery_ramdis.img in recovery_ramdisk partition
Your choice of gapps zip (Optional)
Notes:If you're gonna use Phh's AOSP11 and anything that based on it (with the exception of @eremitein's stuff), use arm64-ab-vndklite variant. For anything else use full vndk version. Full vndk version of Phh's AOSP11 does not allow you to resize system on any twrp.
Steps for gapps versions:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes
When it is done press Reboot
Steps for vanilla versions with custom gapps:
Get the Prerequisites
On current rom/gsi go to developer options and enable usb debug while you're at it enable "Enable OEM Unlock"
Connect phone to PC and allow debugging from phone
Send this command from pc : adb reboot bootloader
When you're at fastboot write fastboot flash system to console and drag & drop gsi .img over to console and press enter
If you want to disable encryption do it now
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Press Factory Reset and type yes, while it is doing that plug the phone to pc
Press Reboot and when screen is off start holding down vol- until you're at fastboot
Write fastboot flash recovery_ramdisk to console and drag & drop twrp-3.5.2_9-0-anne.img over to console and press enter
After flash is complete unplug phone and shut it down by long pressing power button
Press and hold power + vol+ buttons until short yellow warning shows up
Allow modifications
Press Wipe, press Advanced Wipe, select System, press Repair or Change File System, press Resize File System, swipe to resize then go back to main screen
Press Install, select and flash gapps zip
Press Reboot System
Disable EncryptionPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Official TWRP
Stock recovery_ramdis.img
Notes:You can disable encryption at any step, even after booting, but in order to disable it you have to do a factory reset from stock recovery_ramdis. Because of this I recommend doing between flashing gsi and flashing gapps.
Steps:
Get the Prerequisites
Flash and boot TWRP
Allow modifications
Press Mount, select Vendor
Connect phone to PC
You can do next part 2 ways, if you're good with command line interface use steps 7 through 11, if not skip to step 12
Type adb shell and press enter
Type nano /vendor/etc/fstab.hi6250 and press enter
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Press Ctrl + X then Y and press enter
Go to step 18
Type adb pull /vendor/etc/fstab.hi6250 and press enter
If you have adb in your $PATH go to your user profile folder, if not go to folder where adb.exe is
Open fstab.hi6250 via a text editor (please use notepad++)
Remove fileencryption=aes-256-xts:aes-256-cts from 16th line, make sure there's only one comma between check and reservedsize
Save file and open a command prompt
Send this command adb push ./fstab.hi6250 /vendor/etc/fstab.hi6250
View attachment 5422531
Now you need to do a factory reset with stock recovery_ramdis.img
If you have recovery_ramdis.img in your sd card, press Install and press Install Image then select recovery_ramdis.img and pick recovery_ramdisk partition
If you don't have recovery_ramdis.img in your sd card, shut down phone, connect it to pc and hold down vol- until you're at fastboot, then write this command fastboot flash recovery_ramdisk and drag recovery_ramdis.img over to console then press enter
Shut down your phone and unplug it from pc
Press and hold power+ vol+ until you see short yellow warning
Press Factory Reset and type yes
You've successfully decrypted your phone and you're good to boot up or flash gapps
Getting Stock Firmware Files And DowngradingPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Huawei Update Extractor
Firmware Zips
HiSuite
Erecovery
EMUI's System Updater (via root)
HuRUpdater Guide / HuRUpdater Download (don't work anymore)
HwOTA (don't work anymore)
Getting stock files are problematic because of huawei. Least shadiest way to get them are the hardest so bear with me.
Androidhost.ru : Click the "Firmware Zips" from prerequisites and search p20 lite. You should get a wide variety of versions to pick from. Make sure to match the Cust in the file to yours. C432 for Europe for example. After you download the zip file open it up and find a folder named "dload". You can either get this folder and paste it right into your sd card to force dload or you can open this folder and extract update_sd.zip. Inside update_sd.zip you'll find a file named UPDATE.APP. Use Huawei Update Extractor to open this file and there you'll see all the partitions you need. If HUE gives error while opening it, go to settings and untick "Verify file checksum". You can extract .img files by right clicking and selecting extract option on each partition. Normally you can't open these .img files but after pushing them through simg2img you'll be able to explore them too. But lets be real if you need guides for this, all you need is recovery_ramdis.img.
Using Dload Folder : Your sd card can't be FAT32 for this. FAT32 by nature don't allow files larger than 4gb so you can't get this folder to your sd card. Format it to ExFat via any guide on the internet then copy the dload folder to your sd card's root. It can't be inside any folders. Then shut your phone and press Power + Vol+ + Vol- all at the same time. It'll boot to erecovery which'll check the integrity of files then install them regardless of your EMUI version. So it is a good way to downgrade. Keep in mind tho you can't dload back to emui 8 from emui 9. And any successful dload will lock your bootloader back.
Hisuite : You can actually get firmware files pretty easily with hisuite but it requires real work. You see, hisuite downloads firmware files right into your documents folder. Connect your phone to pc and open up hisuite. Check for updates and if it finds one it'll download following files update_full_base.zip, update_full_ANE-L01_hw_eu.zip and update_full_cust_ANE-L01_hw_eu.zip. You only need update_full_base.zip file, others are used to work on HuRUpdater and HwOTA but they are deprecated since February. Inside update_full_base.zip you'll find UPDATE.APP which you can extract images from with Huawei Update Extractor.
Erecovery : This one requires some network knowledge and it'll only get you the latest version so I don't think it worth the hassle. You need a router that allows you to change dns address for DHCP clients. Which most of them do these days. Now you need to create and run a dns server on your pc. I recommend adguard home. Pihole works too. Use Windows Subsystem For Linux or Docker to install either of them. Once you get them up and working set them to log dns requests. I believe you know where this is going. Open your router's interface and enter adguard home/pihole ip address which maps back to your pc's local address. Check if it works or not by opening up few sites on your phone which should be connected to your wifi and isn't set up to use a different dns server. If all is good open up erecovery on your phone and connect to your wifi. If you set it up correctly it should get the latest version from huawei which will show up on your log. Use that url to download it to your pc and extract it same as others. There was a paid service that used this method to send specific versions to your erecovery.
EMUI's System Updater : This is tricky and my favorite. Get the official TWRP .img and patch it with magisk manager. Then flash it via fastboot. I know, "twrp and magisk? wtf?" just do it. It takes a long time to boot but it works don't question me right now. After you get root in EMUI allow system updater to do its job and update. It'll ask to reboot, allow it. It will throw you back to system after reboot cuz recovery is hijacked. duh. Get a file manager that allows root access. Allow system updater to download again. But this time do not allow it to reboot. First one downloaded OTA, second one downloaded FullOTA. Which is better for archival purposes. After download is done search for a folder named HwOUC in /system. Copy it to internal storage and from there to your pc. You can find our main UPDATE.APP inside update_full_base.zip. Other zips include cust and all that which HuRu and HwOTA used to require.
MagiskPrerequisites:
Unlocked Bootloader and FRP
adb and fastboot installed on pc
Stock recovery_ramdis.img
Notes:Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version. It's safe to update it afterwards from magisk manager. As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Steps to install older version:
Get the Prerequisites
No, I mean literally just get the Prerequisites and thats it
Open up your browser and find a bin service (pastebin will suffice)
Create a paste with following
Code:
{
"app": {
"version": "8.0.7",
"versionCode": "4834",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk",
"note": "https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app/src/main/res/raw/changelog.md"
},
"stub": {
"versionCode": "18",
"link": "https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/stub-release.apk"
},
"uninstaller": {
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip"
},
"magisk": {
"version": "v21.4",
"versionCode": "21400",
"link": "https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip",
"note": "https://topjohnwu.github.io/Magisk/releases/21400.md",
"md5": "ee6dd05579776e7de3a6077087846e53"
}
}
Get the paste's raw url
Take the recovery_ramdis.img to internal storage
Install magisk manager 8.0.7
Open it's settings and select custom channel
Write the raw url you just created
Allow it to check for updates and it'll find that 21.4 is the latest version
Click install and select recovery_ramdis.img
After it finishes patching get the magisk_patched.img to your pc
Get your phone to fastboot mode
After connecting to pc, write this fastboot flash recovery_ramdisk to console and drag magisk_patched.img over to console and press enter
Now if you enter recovery it'll boot to android with magisk but if you boot normally it will not detect magisk so each time you restart you have to use Power + Vol+ combo in order to get magisk
Remember to switch custom channel to stable channel if you want to receive updates.
I know that you can pretty much reduce the amount of flashing and restarting by flashing twrp to erecovery but since erecovery is a lifeline for most people here I decided not to get into that. But for those who are interested check this thread.
Edit: Grammar
Edit 2: Update about HwOTA and HuRUpdate
Edit 3: Simplify some steps and add my own mega.nz archive
Click to expand...
Click to collapse
Only now I have time to read your instructions carefully, what is this nonsense ???
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses. But hey it is still working without modifications unlike a-only devices so that's a win. New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
avenger.forsyth said:
It is long because because of procedures that are too complicated, e.g. chapter "Disable Encryption" .
Click to expand...
Click to collapse
Is it better to just link decryption zip or write what that decryption zip does?
avenger.forsyth said:
It is long because of duplicate procedures, e.g. chapter "Flashing Any GSI".
Click to expand...
Click to collapse
People use gapps versions because they don't want to waste time by flashing zips. That's why it's 2 part. Gapps one is shorter.
Frax3r said:
Officially speaking magisk support for our device is dead. Magisk decided to retire magisk-in-recovery method which our phone uses.
Click to expand...
Click to collapse
Magisk-in-recovery as in "magisk hijacking recovery" not "installing magisk using recovery". You can't even find huawei section in it's installation instructions. Look here and here. As for the nuance you asked, installing magisk in EMUI is literally same as installing it in GSI or LOS. You patch the image, flash the image, boot the image.
Frax3r said:
As a foot note, you CAN use twrp image instead of stock recovery_ramdis.img but it'll take longer to boot. Using .380's recovery_ramdis.img on .278 build will not work. Make sure to match your EMUI build with ramdisk you're flashing. Ask me how I know.
Click to expand...
Click to collapse
I added "ask me how I know" part for a reason. I tried. You CAN patch official twrp with magisk and it WILL boot. If a person unlocks their bootloader for the first time how is he supposed to get stock recovery_ramdis.img? Get the mmcblock of recovery_ramdisk? How is he supposed to do that if he flashes twrp over to recovery_ramdisk partition? We can't use "fastboot boot" so that's out of option. Use a different recovery_ramdis.img you might say. I TRIED. .380's recovery_ramdis.img patched with latest magisk won't boot if you're at .278. I created a folder where I patched .380 recovery with each different version of magisk starting from 20.4 up to latest version and none of them booted on los 16 which was installed upon .278. It is not universal as you might think.
-Alf- said:
Only now I have time to read your instructions carefully, what is this nonsense ???
I'll give you some advice if I may - don't write about things you don't understand! And this applies not only to Magisk.
Click to expand...
Click to collapse
Care to elaborate? I am open to constructive criticism. As for what I know, I do know that you won't find yourself bootlooping if you follow these steps by the letter. I saw your instructions on los 16 and other threads too. Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me. I guess twrp in erecovery could fix freezing but there's a reason why they are asking for help and you expect them to overwrite their only lifeline. 1-2 extra rebooting and flashing won't hurt anyone. When you wipe /data or factory reset with most twrps, including official one, some folders that needs to be untouched (huawei am i right) gets deleted. So you have to use stock recovery_ramdis.img or an advanced twrp which compansates it. Check the tishserg's twrp for example. I use that not the official twrp for these things. And it can write to erecovery which is exactly why I didn't advocate on using it in this guide. Have a good day...
Frax3r said:
Here's a criticism for you, do not tell people to wipe /data or factory reset with twrps and especially do not expect them to flash twrp over to erecovery. Wiping /data or factory reset from twrp always resulted in phone freezing for me.
Click to expand...
Click to collapse
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Frax3r said:
New installer for magisk kinda broken for our device, because of that I recommend installing and booting an older version.
Click to expand...
Click to collapse
Everyone knows that it is possible to install the latest version right away...
-Alf- said:
Use recommended TWRP, not 3.4.0. and above, which is not fully compatible with hi6250 devices (including official one). Did you know?
Btw, I never advised anyone to do a factory reset in TWRP, on the contrary
https://forum.xda-developers.com/t/...twrp-3-2-1-0-12-05-2018.3789306/post-85472227
Everyone knows that it is possible to install the latest version right away...
Click to expand...
Click to collapse
Yes you said that here. However my own experience says otherwise. Before my current los 16 installation I used official 3.5.2. Flashed los, flashed stock recovery, flashed phenix kernel, flashed gapps all from it. I even used nano from adb shell to edit fstab.hi6250. I used backup and restore only on kernel partition but it was successful anyway. What that incompatibility be? Is it boot override thing? If you have twrp in recovery and send reboot to recovery from android it just keeps booting to twrp in each reboot even tho you select otherwise from twrp's reboot menu. BTW tishserg's twrp have an option to remove that override if you find yourself in that loop. As for factory reset part, you said format /data here. We had a discussion here because of that. My bad on reading wrong. While writing this I realised incompatibility is probably about formating /data on twrp 3.4.0 and above. If that is the case I'll update the post. Good thing I didn't tell people to format /data from twrp. My steps might be long but they are correct. It is wrong to call all this a nonsense.
Everyone might know it is possible to install latest magisk but not everyone knows how to install an older version now that magisk's future is uncertain. After magisk removes magiskhide from its code people are gonna wanna go back to latest version that worked while waiting for module version of it. Patching twrp image with magisk is highlight of this post but it is literally what flashing magisk.zip (.apk to .zip) from twrp does with the latest version. If patching twrp is bad then why is my guide to installing an older version, which allows you to select which image to patch, is the target? + With that .json, you can make magisk manager patch the image with your own modified version of magisk should you upload it somewhere and change the links.
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
aribk said:
Hi,
Question 1: Is this correct or a misunderstanding?
Q2: Same question as above.
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
Hello,
If I understood you correctly you're asking if you can flash stock erecovery after you've modified it. Answer is yes, you can flash twrp on it and when you're done you can flash stock erecovery image over it. Fastboot won't allow you to flash anything on erecovery partition tho. So you need to use certain twrps that are capable of flashing over erecovery. s_mak and tishserg twrps should allow that iirc. First flash any one of those twrps to recovery_ramdisk then boot into it afterwards flash same twrp image to erecovery partition from inside the twrp.
Yes, if you look at last few replies in this thread that was exactly the conversation. However that is only the case with official twrp. If you use s_mak or tishserg's twrps from the mega link in the thread you should be able to wipe without a problem.
Last 2 questions are beyond me I'm afraid. PostparketOS and Ubuntu Touch are inherently very different to android and they could require some stuff that are unique to them. However I would imagine you wouldn't need to wipe anything after flashing those images.
aribk said:
Hi,
I'm building trying to port Ubuntu Touch to this device and I'm running into a few challenges. I have already reverted to stock 2 times and re-unlocked the bootloader (starting from EMUI 9). So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Installing Ubuntu Touch requires the data partition to be formatted to ext4. I can do that from twrp, but someone (maybe you) wrote that wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
I understand Huawei requires the kernel and ramdisk to reside in separate images on separate partitions. So I have used this guide (https://wiki.postmarketos.org/wiki/Huawei_P10_Lite_(huawei-warsaw)) to separate the boot.img produced in my build, and then flashed these two image files to the kernel and recovery_ramdisk partitions respectively. However, examining the LOS 16.0 rom that can be installed, I see that it contains a "boot.img".
Q3: Can I flash my boot.img without separating into kernel and ramdisk first, and if so, which partition should I flash?
Q4: After flashing the image files I built (kernel.img and ramdisk.img along with system.img), do I need to reboot to a recovery (if so, which?) and wipe something (if so, what?) before rebooting?
Click to expand...
Click to collapse
aribk said:
So far I have only flashed recovery_ramdisk with twrp as I was worried I might not be able to revert to stock if I flashed erecovery.
Question 1: Is this correct or a misunderstanding?
Click to expand...
Click to collapse
Misunderstanding. You can revert to stock via eRecovery & wi-fi.
Huawei has Recovery and eRecovery, each has different functions.
You can use the following combinations in your phone:
- Recovery + eRecovery (stock FW)
- TWRP instead of Recovery + eRecovery
- Recovery + TWRP instead of eRecovery
aribk said:
wiping the data partition with twrp was liable to create trouble.
Q2: Same question as above.
Click to expand...
Click to collapse
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Q3: All this only works on EMUI 8 as far as I know.
Q4: follow the instructions, imo.
P.S.: as you can see, mobile Linux projects such as Ubuntu Touch, postmarketOS or Sailfish OS work only partially on Hua/Ho phones,but we already talked about that .
-Alf- said:
Same answer as above. Formatting (not wiping) data with TWRP 3.4+ is dangerous (running stock EMUI).
Click to expand...
Click to collapse
Re-reading your answer above, I see I'd like to double check: Is this dangerous only if you are running stock EMUI, or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
aribk said:
aribk said:
or would it also be dangerous to use TWRP 3.4+ to format the data partition when you wish to run a different system on the device, as in my case?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hard to say, no one has experience with different system . But I don't think it matters - see Mr. Frax3r's post above (and read carefully bro ).
I'm bumping the thread, few improvements are made for android 13.
Thank you for the update.
I have modified Phenix_4.9.235-phenix-1.0 rebased on Harmonyos to make it permissive which make most A13 GSIs boot normally on my phone. I have attached the updated one.
Frax3r said:
After you set up your phone and made sure you don't need stock recovery, flash magisk:
Click to expand...
Click to collapse
magisk-patched stock recovery remains functional, available and usable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
It would be easier to build a custom rom than installing it.
VD171 said:
It would be easier to build a custom rom than installing it.
Click to expand...
Click to collapse
LMAO well, there's too much text to read. but it is totally worth it installing a custom ROM on redmi note 9
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
VD171 said:
I see many people worried about that.
But I really prefer the stock MIUI, because it's so easier to me.
So, I can spend more time on xposed/lsposed and root/magisk.
Anyway, thank you very much for useful guide.
If somebody asks me again, I will send this guide
Click to expand...
Click to collapse
I've been developing games for android, and the redmi note 9 is my primary phone for it, because it is the middle ground of performance based on the average user. so as long the game runs well most people would be fine.
The thing is, MIUI with its ram management really makes me struggle, minimizing, and multitasking re-launches the game and System UI a lot of time freezes, nothing of those things ever happens with pixelplusUI, that's why I prefer it making me focus mostly on the GPU performance without getting bottlenecked by the heavy and nonoptimized os.
Well, well.
I understand you.
I confess that I've never played nothing at any android I've ever had, since my first android in 2014.
Really interesting to know about that.
I like the ram management because I don't have to close everything by myself.
My brother and my mother keeps everything on memory and management keeps to the system.
My brother has an iphone (sadly) and my mother has a Redmi Note 10.
I agree that the management by MIUI is excessive and should be more customizable.
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Hello, i flashed miui 12.0.3 but it doesnt want to boot, stuck in bootloop, fortunately it boots into recovery, i wiped data and factory reset but it still doesnt want to boot, how do i fix it?
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
NewtonPL said:
SOLVED: step 5 is faulty, you need to go to stock fastboot using vol - and power and not using the SHRP menu! i was trying to get it to work for 3 hours and i fund the solution, happy flashing!
Click to expand...
Click to collapse
Nothing faulty there you did not read the whole step. It says "downgrade using MI-Flash software", not using a custom recovery. Read the step properly and completely.
0xSteeW said:
By the way, are we safe from ARP (Anti Rollback Protection)? I've seen both my current ROM and the target miui have an ARB version of 2 so it should be safe, but still I want to be sure.
Click to expand...
Click to collapse
Yea it's safe I've downgraded from miui 12.5.5 to miui 12.0.1 and its totally safe. You can use miflash to downgrade
0xSteeW said:
Hello again, I'm considering to follow this guide.
Does this need no special setup? No SP Flash Tool? No bypass? Just flash in fastboot directly?
Considering the amount of EDL bypass tutorials out there it looks overly simple.
Can you confirm this works for Mediatek Redmi Note 9 without previous setup?
Thanks for the guide.
Click to expand...
Click to collapse
Edl bypass is only needed of you brick your device or it doesn't boot into fastboot or for taking backup kinda stuff.
Otherwise miflash does the job
thanks.
All works, thanks for the very detailed guide!
Quick question: do I have to flash with sideload or can I flash with SHRP?
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Manjotbenipal said:
I installed miui 12.0.1. will there be any difference if I use miui12.0.1 instead of 12.0.3?
Click to expand...
Click to collapse
Any ROM before 12.5 is ok
vagelis199 said:
View attachment 5566615How to install PixelPlusUI ROM on Redmi Note 9This guide will teach you how to install PixelPlusUI into Redmi Note 9 merlin or merlin Nfc version.
This is a more detailed and straightforward guide based on the official guide of PixelPlusUI found on their Github page here.
This guide can be applied to other customs ROMs* e.g Pixel Experience etc. Yes, the process is exactly the same for pretty much any custom ROM you want to install to Redmi Note 9.
Installing GuideIn this guide, I will explain to you how and why we follow certain steps, so you can clearly understand every step, process, and risk of installing a custom ROM into a Redmi note 9. And avoid breaking your phone, bricking/hard bricking your phone: no operating system or a possible way to recover it, lost IMEI: can't make calls or receive.
In this guide, I will not explain to you how to unlock your bootloader! you can find plenty of guides online on how to do it and it's overall an easy job.
Before you start you will need to have an unlocked bootloader to be able to modify your system files. Once you have an unlocked phone you can start with the process of Flashing* a custom ROM.
The steps we have to follow are--------------------------- Mandatory steps to be able to install a ROM, 1 - 7
1. Download Platform Tools*, A Custom Recovery*, and a modified VBMeta image, Mi-Flash to be able to downgrade MIUI, and the latest PixelPlusUI ROM which as of today is PixelPlusUI 3.9 for android 11 and PixelPlusUI 4.1 for Android 12.
2. Flash* recovery and VBMeta
3. Reboot into recovery
4. Backup IMEI
5. Downgrade your fastboot* into 12.0.3 version
6. Flash recovery and VBMeta
7. Reboot into recovery
--------------------------- Steps to install pretty much any ROM to Redmi Note 9, 8 - 11
8. Flash the latest firmware
9. Reboot into recovery
10. Wipe Dalvik/Art, Cache, Format Data
11. Flash PixelPlusUI ROM
---------------------------- Updating the ROM, 12 - 13
12. Update from 3.9 to 3.10.
13. Update to Android 12 with PixelPlusUI 4.1 (Optional) (Avoid for now cause it's unstable)
1. Once you have downloaded everything extract Platform Tools enter the folder where it contains all the necessary exes and run CMD inside this folder.
Turn off your phone, press the power and volume down button hold till your phone turns on, this will boot your phone into fastboot. Connect your phone via USB cable to your pc.
In CMD type "fastboot devices" without the annotations. it would output your phone right below with an ID and a fastboot label next to it.
if you are seeing "< waiting for device >" go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android bootloader interface.
2. Now that we know fastboot is working and detecting our phone we have to flash the custom recovery.
copy the recovery file you downloaded, it should be an .img file, into the Platform Tools folder, in CMD now write "fastboot flash recovery recoveryname.img" without the annotations obviously, once its done, copy the vbmeta.img (might be named differently) also into the Platform Tools folder and write "fastboot --disable-verification flash vbmeta vbmeta.img" as vbmeta.img the file you just copied. if this throws an error do "fastboot flash vbmeta vbmeta.img" instead.
3-4. Now its time to backup our IMEI, if we don't back it up now, there's a change in the next step we lose access to make or receive phone calls, in case this happens we can flash back the IMEI and get it back to work. How do we back it up. While in fastboot, remove the usb cable, and turn off your phone, hold volume up and power till your phone turns on, wait till it boots into Recovery, if you accidentally boot normally into MIUI you will lose the recovery we installed before and it would roll back to stock xiaomi recovery, then you'll have to refollow step 2. Once in recovery, enter your pin and go to Tweaks, And tap the Imei backup, wait till its done, and then go back to the main menu, connect your phone via usb to your computer. your phone would pop up as a storage device, if nothing happens its because of the drives. go to windows device manager, you'll find your phone in the other devices section with a yellow triangle. right-click it and click the first option to update the drivers, choose to select locally then Google => Android ADB interface, Once it pop up enter into it and you'll find a folder called "imeibackup" copy that folder into your computer and keep it safe. this folder includes some partitions as img files and a zip file. the zip file is basically all the files archived into a single file, to be able to flash it later from recovery,
5. Time to downgrade your MIUI fastboot version, we have to do this, because if we don't downgrade we won't be able to install a custom ROM why? well, I actually down know, but pretty much flashing does nothing in the latest MIUI version 12.5 and so on, thankfully you can downgrade the MIUI version in the Redmi Note 9. The best version so far is the MIUI 12.0.3 and you only have to flash the fastboot image, The MIUI you gonna download has to be the same region as your phone e.g my phone is EU/Global i have to download the global fastboot image. if you miss-match them you won't be able to make or receive phone calls. Visit this page Visit this page find your regions "V12.0.3.0" MIUI version click on the very right "download" button, scroll down where it says "type:fastboot" bellow there a button "Download: Full ROM" the file ends with a tgz extension, extract the archive inside you'll find a folder named something like this "merlin_id_global_images_V12.0.3.0.QJOIDXM_20200807.0000.00_10.0_global" copy that folder into the root of your hard drive, rename it into merlin_id_global_images_V12.0.3.0.QJOIDXM
Install Mi-Flash, run Mi-Flash, click select and select the folder you copied into the root of your hard drive, on the bottom right corner flash_all_lock.bat change it into flash_all.bat this will prevent the bootloader from locking again, but it might destroy your IMEI partition, but thankfully we back it up in step 3-4. On your phone, while we left in recovery go to reboot => advanced => fastboot, once you are again in fastboot, connect your phone via a usb cable in to the computer in Mi-Flash press refresh, your phone will show up in the list, if not just follow again the drivers guide at the end of step 1. in Mi-Flash click flash next to refresh and wait till its done, the result should say success. Your phone will reboot and boot back to the old v12.0.3 MIUI version.
6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do "fastboot flash vbmeta vbmeta.img", reboot into recovery mode, by turning off your phone,
and then holding volume up and power till it turns on, now we are back into custom recovery we just installed again, in recovery now we have to flash the latest firmware of redmi note 9, this is necessary for PixelPlusUI to work properly. Download the latest firmware for your region from here, you'll get a zip file, copy the file zip into the platform-tools folder, open cmd in this folder and this time we have to sideload the zip via ADB. in your phone go to advance and then tap on sideload, tap the checkmark to start adb, on your pc in cmd you opened before type "adb devices" if it shows your device similarly as the fastboot devices step we did before you can continue if not, do the driver guide in step 3-4, once you ready type "adb sideload firmwarefilename.zip" replace firmwarefilename.zip with the firmware you downloaded name. once the sideload is done, click the X go to reboot=>advanced=>recovery, we have to avoid booting into miui now so we don't lose our custom recovery, this will reboot your back to recovery.
10-11. Now back in recovery go to wipe and tap the bottom right button Wipe with an arrow. when it's done, go to advanced and then sideload, click the checkmark,
copy the PixelPlusUI_3.9.zip into the platform-tools folder, in cmd you have open from before do "adb sideload pixelplusUI_3.9.zip" wait till its done sideloading.
once it's done, turn off your phone, and boot it normally, you will be greeted with the P logo of pixelplusui, set up your phone normally, if you see "no sim card please insert sim" its possible you flashed the wrong MIUI region or you lost your IMEI, you can flash the IMEI zip you backed up using the recovery's option of sideload or by using the flash option. if this does not fix it, redo all the steps but this time using mi-flash flash the right MIUI fastboot region and firmware region.
12. Updating PixelPlusUI from 3.9 to 3.10 which seems to be the last version before it got discontinued, in your phone, go to settings, system, update, download the update, once its done downloading, do not install it, close settings, hold the power button tap advanced => recovery, in recovery go to flash, go back in a directory and find the folder data/System Update, inside there you'll find a zip file called PixePlusUI_v3.10_something something.zip, flash that file without wiping anything, when it's done, go back and then go to wipe, tap advanced wipe, select only Dalvik/ART Cache and Cache so you don't lose any data. reboot, Done! Never update using OTA auto-update.
13. (For now avoid cause it's unstable) Time to Upgrade to Android 12 with the official build of PixelPlusUI version 4.1
Download the build, Using ADB sideload the latest official firmware, then reboot into recovery, format data and then install the ROM, you can copy it into the device or sideload it.
Every time you want to update or re-install a ROM (Any ROM) to your Redmi Note 9 you have to refollow the following steps:1. Flash the latest firmware, Reboot to recovery after flashing.
2. Wipe Dalvik/Art, Cache, Format Data ( Don't do it if you just upgrade )
3. Install desired ROM.
Platform tools is a suite made by google for developers, it contains adb and fastboot apps which help you with installing/wiping content and doing more development related stuff to your phone.
VBMeta.img is required to be flashed to allow installing custom recoveries if you don't flash it, it would reverse the installed recovery back to the default Xiaomi recovery.
Custom Recovery a custom recovery is basically a separate OS that you can use to factory reset your phone when you can't access the main OS, or in this case, install random tweaks and mess around with system files and partitions.
Flash or Flashing Basically installing system files, partitions etc. can be done using adb, fastboot or from recovery.
Fastboot Similarly to Recovery is an option where you can restore your phone when you cannot do using the recovery, which is why we use it to install the custom recovery in the first place.
Tips for people who want to mess around with custom ROMs.
Every time you want to re-install a ROM, you'll have to re-install the firmware, the best bet is the latest Xiaomi firmware. Also, formating data is necessary to avoid bugs.
Known Bugs:When the fingerprint sensor is touched it won't let you gesture swipe to close an app.
When the NFC is enabled there's a tapping sound on the microphone.
Click to expand...
Click to collapse
I'm on miui12.0.1 and want to install pixel experience android 10 with shrp.
Do I need to flash the vendor if I don't want to install pixel experience via sideload and is it necessary to disable avb 2.0 after flashing vendor and custom rom?
I cant boot into the recovery mentioned in this step, what do I do?
“6-7-8-9. Now that we downgraded our phone is back to stock recovery and rom. we have to re-do some steps like installing the vbmeta and custom recovery.
Follow again the step 1 and 2. flash recovery and instead this time when flashing vbmeta.img just do “fastboot flash vbmeta vbmeta.img”, reboot into recovery mode, by turning off your phone,“
how long it take to flash redmi note 9? already 1000 seconds passed and its still flashing