Unbrick Realme 7 PRO UI 1.0 - Android10 - Realme 7 Pro Guides, News, & Discussion
[Unbrick Realme 7 PRO RMX2170 128GB with NFC - softbrick - bootloader unlocked UI 1.0 - Android10]
This tutorial works only in soft brick devices, for hardwre bricks only flashing with MSM Download and it I don't know how this works.
I don't know if this tutorial will works with other devices.
Try this if you don't have another way.
------------------------------------------------------------------------------------------------------------------------------------------
- I not responsable for your decision to try. -
- I'm not responsible for your device (hard brick or other things that might happen) -
------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- IMPORTANT NOTE -
- Unlocked Bootloader devices only (It's very important) Only Android 10 -
- If your device have locked bootloader only realme repair shop can help you, or flashing with MSM -
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Let's Start
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Flash the PBRP 3.0
[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
**** Don't change the name this image to recovery using anyway
PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img****
Download the ROM (of the official channel, I'm using RMX2170 A.41 PU) ozip format
Software Update - realme (India)
Update the latest software version on your realme phone.
www.realme.com
Download the rom OFP format
Search on google for your ROM, generally this type have 7GB
Put the rom ozip in device (external sdcard) the rom can be send to device for USB conection normally.
In PBRP goes in wipe menu and select Data (It's very important too) change partition Ext2 wait finish and select again to ext4 to remove any block on /Data partition.
Reboot menu and select reboot to recovery.
-----------------------------
Now proceed to PC
Download and opens the MCT ofp extract tool to extract the ofp to files img. (Only works on windows, in Linux use a VM)
The user nirmago alerted me over a virus in this file, thanks nirmago. Proced with caution with file. I used a new way to decrypt the ofp files
oppo_decrypt
Is free and developed in python, works very well in linux and I believe what this not have worms.
Is very simple to use
choose the OFP file
select a ouput folder to extract the files
and click on EXTRACT and wait finish.
*************
Important: After extract you will have 124 files in folder and this folder have 11.8GB.(See in baseboard of window). And the super file have 8GB. like picture below. See in pictures below, the first image to show how many files have in folder and the second picture the size of super file, see too what I have only one Super file.
Image 1 - 124 files extract and the folder with 11.8Gb. See in baseboard of window.
{
"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"
}
Image 2 - The Super file have 8Gb.
*************
Meanwhile remove the sd of your device (you don't need shutdown the device only remove)
Put the sdcard on pc and copy the folder of generate with MCT extract tool folder to root (Not move this folder to device for USB bcz some files not will be copied)
Put the ozip too (download the ozip that you had before RMX2170XX_11_A.XX)
Remove sdcard of your PC and put again on device. (Here I recommend security removal with using windows 10 or 11)
-------------------------------------
Proceed again on device
After you puted the sdcard on device goes to Mount menu in PBRP and select mount your external sd again.*
And the PBRP will reconect the sdcard.
* if you shutdown to remove the sdcard it's not necessary.
Open the folder that you copied (generated by MCT) on sdcard
Open flash menu and seek for img files above:
Boot.img
Super.img (This file is the key to recovery the system)
Recovery.img
Persist.img
Vbmeta.img
Vbmeta_system.img
Vbmeta_vendor.img
Touch on each one at a time, select the respective name on selection box and flash.
Now reboot to system, the system will crash on load, but not have bootloop, don't worry it's normal.
Reboot to bootloader again with procedure above.
*** vol+ + power at device reboot and fastly push vol- right after the device vibrate ***
In bootloader.
Now put de PBRP image again with the command above. Sometimes the device keeps restarting constantly
be quick to put the command.
fastboot flash recovery PBRP-RMX2170-3.0.0-20210113-1340-UNOFFICIAL.img
In PBRP
Wipe data, cache, dalvik
Install the ozip file that you downloaded before
and then the system will goes normal and the device is live again, [in my case the wifi not working after start system]
If you wanna the official recovery again, or have problems like wifi not works.
On PC open a terminal inside the folder created by MCT with the uncompressed OFP rom and use the commands above:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Press vol- at show up on screen reboot to recovery and will have the official recovery again
*If you have the wifi issue like me put the ozip (the same that you downloaded) on device for USB cable on download folder.
Reboot to official recovery (It not work on custom recovery)
Flash for file, search the ozip file and install normally.
It will solve the problem.
* You will not lose the IMEI
* The fingerprint sensor doesn't works. I will try to solve this issue now.
EDIT:
I used a new software to decrypt the ofp
GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter - GitHub - bkerler/oppo_decrypt: Oppo .ofp Firmware decrypter and oneplus .ops de-/encrypter
github.com
Works very well in Linux, in Windows I don't know.
Open a terminal in directory os unzip the downloaded code
The command used was (in Linux):
./ofp_qc_decrypt.py <your file.ofp> <place to extract/decrypt>
And now I used OTG USB instead SdCard and works too.
OBS:
For fingerprint issue the only way yet is to restore the Persist partition backup generated by PBRP to but I haven't my persistent partition (original) to try, my realme was bricked before that I make it.
I study for a week to recovery my device, and I appreciate each one here what contribuited of a little tool or with your knowledge of the Android system.
I wish what this tutorial help you.
Good luck for all.
"MCT ofp extract tool" is a virus
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
You can search this tool of another site, or using another tool what extract OFP images, feel free to use since what the tool extract the files cited in tutorial. I used this tool and works fine for me.
I used the VM to extract all files bcz I use linux, but you can use VM too and after you can delete the VM.
Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
lapist said:
Isn't it easier to flash those extracted IMG files directly from fastboot, rather than flashing PBRP and working with SD card? Wipe and flashing OZIP can be done thru stock recovery too.
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hello man!
Yep it is easier in theory, but doesn't works in practical.
In my case the device lose the stock recovery, I had /boot/recovery not found and the sotck recovery is dependent of super partition to works, if you flash only official recovery will have the error /boot/recovery not found. I did not have system, boot, vendor, nothing anymore in my device. When you have the total softbrick you have 2 things only the bootloader menu (if you unlocked it) and EDL, the EDL in Oppo/realme is complicated why they don't developer any tool to help us in flash for EDL, like Samsung (ODIN) Xioami (XiaomiFlashTool) or OnePlus. And to get worse the ozip and ofp only is used for Oppo/Realme any tool works.
Why not flash the partitions directally with fastboot?
The fastboot when transfering files with USB have some limitations when you work with bigger files 3GB or higher. And many limitations too with partitions, when I talk about open partitions of MB like recovery, boot, and vbmeta ok, the flash done with success, but the partition vendor and system in oppo/realme have the name Super, (\system+\vendor) and fastboot doesn't got write in this partition when your device is in softbrick, then unfortunately the last chance to flash this partition is PBRP this tool use the device like root permissions, I try with SHRP and Orange fox too, but give me errors like mount failed /system_root, and /vendor and SHRP don't flash img files.
The only way what I founded was PBRP flash the img direct to super partition, its solved my problems with don´t flah any zip file with PBRP, the super.img is the key to solve most problems.
I try flash with fastboot, and give me the error "Error: not is possible to format with RAW partitions, check the device terminal." It's happen bcz the fastboot could,t get write in partition system and vendor (or super) bcz the partitions for security are close to fastboot or adb. Was it is all what I discovered in some russian forums. And thanks to developers of PBRP and my efforts I got using my device again.
Why PBRP is good and why I used this tool?
PBRP transform ozip in zip, then he have the capacity of work with ozip very well
PBRP uncrypted my data files
Works with zip and img very easy
Your file explorer is great, better than TWRP, (and remember we don't have TWRP to Realme 7 pro).
Well is it.
I think I managed to explain everything.
Good luck!
I hope I've helped u man.
nirmago said:
"MCT ofp extract tool" is a virus
Click to expand...
Click to collapse
Thanks man. The file really have a virus.
I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????
p1w3xxx said:
I did according to this guide.
But i have a few file super??
I do this .bat file (
"@Echo off
fastboot flash boot boot.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
"
)
and working recovery and install .ozip
and now i have bootloap to fastboot.. i flash recovery and not working(stock and custom) all time restart to bootloader why???????
Click to expand...
Click to collapse
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
xxx8086 said:
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
View attachment 5473915
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
Click to expand...
Click to collapse
Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??
p1w3xxx said:
Hello,
i do not understand.. i can't upload recovery.. in cmd everything is okey.. when i want open recovery, phone do restart bootloader.. now when i want open recovery, bad file flash or i don't know what, my phone "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
My question: how should i upload recovery and run it??
Click to expand...
Click to collapse
Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).
But be quick before the device reboot.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
xxx8086 said:
Press vol- + power at the device turn on in fastboot after flash a good vbmeta.img, and a boot image, I recommend search it in the original rom, and after flash a recovery image (orangefox or PBRP).
But be quick before the device reboot.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
p1w3xxx said:
Can u upload for me this file ? Maybe my computer has problem with this.. idk..
Click to expand...
Click to collapse
Rename PBRP to recovery before to flash.
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Link to download PBRP if necessary.
[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Link to OrangeFox
Mayur - marshmello projects - Browse /RMX2170/OrangeFox at SourceForge.net
sourceforge.net
after use this command:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot recovery
my phone (attach file)
second attach file bootloader.
what i do wrong??
EDIT1:
install fox recovery and working recovery..
but when i want install custom .zip i see error(attach file 3)
You have an error of partitions!
Error 1 in zip describes a permission error and this error is bcz orangefox, try pbrp to try solve it. Some Orange recovery have an error about permissions in Android.
But other recovery not working..
Realme have a good hardware but bad softwares. All it is easilly solved if they had a tool like miflash or samaung Odin.
But...How they don't have... Let's go.
Are you tried write PBRP directally for Orangefox? Inside OrangeFox have a option to write files and partitions, but I don't remember where is it.
Note - You can't install any custom rom before you have a system working with all partitions defined and all running fine. Bcz the custom roms don't create a new partitions, only rewrite over the same system partitions. In your case you have't any system partitions.
And you
yes, tried a few recovery update for OrangeFox and nothing..
I can install a few .img, which files i need install from shapeshiftOS.zip to working my devices???
xxx8086 said:
Hello man!
Something was wrong, bcz after extraction of rom you will have just one super file not all this in your image, how do you make the extraction of rom?
And after extract you have a lot files of 124 files in a folder.
Note that you have a divided super file image, with many sizes, the extraction should join all in only one, see the picture below to see, 124 files and 1 super.img file.
The problem is how you is making the extraction, if you dont use the correct tool you never extract the filer correctly, and in some point you have errors in partitions write. Try to use the tool that I used in tutorial, I search a lot and try many others ways to unbrick and only this tool solved my problem of extract.
This is your first problem.
The second problem is write the partitions, never write partitions with size up 1GB for abd or fastboot, this a limitation of reading and writing.
Ever ever EVER use the TWRP.
And you can use the MCT ofp extract tool, but this files and all that I download have a virus harder to get out the system, this works too. But is very dangerous , use this MCT ofp extract tool if you have another old machine with windows, or a pc that you can format after extraction process, bcz this virus attack the file manager of windows, if you don't have another old pc to try, I don't recommend the MCT ofp extract tool.
The files below was extract with oppo_decrypt using python 3.8 version. I use Linux system, it know what it works in windows too, but don't question me how, I don't know.
View attachment 5473915
Can u see in image? 124 files, and only one super file!
Use the tool what I'd tested in this tutorial using with python. I think what you have a problem with extraction. See well you have two points very importants here:
1 The rom what you is using and the Android version what you system have before brick.
2 The super file, this file have up 8GB and have all system root separate by internal partitions. Why this? Simple, the android have a lot of partitions now, and the super rewrite then on your real locations, if you have a lot of super is wrong. I will post an image to illustrate what you see after extraction, and size of super file.
Please review your extraction. and don't use batch methods, make all changes in realme directly in TWRP, I recommend the PBRP to modify these files.
See the images what I posted now in tutorial. Remember after extract you will have 124 files in a folder with 11.8Gb of files. And a super file sizing 8Gb.
The fact that you have a loop is for your super.img the file was write incorrect or incomplete, and the system don't can charge to another partition. An analogy to you undertstanding it is:
"You try to turn on a car but the car doest have a battery doesnt matter how many times you try turn the key the car never will pass to turn on stats."
The first thing to do to fix the bootloop is write the first partition of android, the android have 2 essencial first partitions, vbmeta and recovery, and no they don't stays in same partitions, the vbmeta controls the part of turn on, and recovery controls recovery.
Then I think that your device stay in a infinite recovery/system bootloop, whats is this? if you enter in fastboot the smartphone restarts automacally, and the system is same.
Well when you writed the files you writed the wrong files this is the cause of boobtloop. Another analogy is:
"You try to turn on the car with a wrong key"
To solve it, first and very quick enter in fastboot, I don't remember if vol+ + power or vol- + power, and insert the correct vbmeta image, the device will reboot again, its normal, and after put the recovery, orangefox or PBRP to stop the fastboot bootloop, and after make the process again but now correctally, with the right files and step by step with calm, and attention. Make it quick bcz the smartphone is in infinite bootloop, then you have some seconds to do it.
Sorry for redundancy in reply but is very important to you understand all process for no have errors.
Click to expand...
Click to collapse
hi, i repaired my device, but now i have other problem
don't working any bank application.. need latest version rom..
phone don't look new update.. i try change vpn (nord vpn) inida, deutchland NOTHING
i have this rom: RMX2170PU_11.A.41
i will try a few ofp file with android 11 but every have a few super.img... : attach 1
i have files: attach 2 and 3
only in rom ...A37... one files super.img but not working any bank application
Thanks man it's really helpful for me.
Related
Idol tools Suite for 4.7 [6039] version 21-11-2016
Hi! I update the Idol suite for 4.7 6039 phone version, it is a Windows tools ( sorry). Log: It use ADB tools Can unlock bootloader Flash TWRP 3.0.0-0 for Idol 4.7 Backup yur phone ROM (need root) Can boot in bootloader mode Can reboot from bootloader mode Can boot in to recovery Can simply reboot the phone Can extract the files from a ext4 image, like system.img Can flash a single image Can pull to edite the build.prop file and create a flash zip for it Can boot in to twrp 3.0.0-0 with out flashing ( useful to recover the phone) Can pull the apks from system and create a flash zip ( If you want to change something in apps or change a pp for another than you want to flash it again ) Can edite the apk files and create a flash zip Can create a new Splash image and a zip to flash it It have idol drivers for windows NOTE: Some tools are not mine, I simply put everything together in one place! I am not responsible for any damage they may cause to your device. Use it at your responsability Extract the folder from zip in to descktop and execute the Idol_Suite_V3.exe file. New_Idol_4.7_Suite.zip Any issue please tell me! Enjoy it!
The tool is update: Now you can modify boot and recovery to.
thank you dude.
You can upload the file again
Thanks!!!
Hi Persona78, first can i say what a fantastic job you have done, most of my research on the idol 3 4.7 points back to you, hats off sir! I'm still having a problem and i'm really at a loss here after about a week of no returns. adb refuses to recognise my 6039y when in bootloader so i cannot flash recovery, or ROM, or any command. I have all drivers installed correctly, vendor id of 0x1bbb is set in a.ini file in adb_usb.ini, i keep search for different approaches but turning up nothing! Are there anything to suggest? I would be most appreciative! Thanks, Marlin
unbrick Nokia 3.2
Hello together, after many tries to get my nokia 3.2 rooted, i end up now with a black screen. Only the Qulacomm mode is working. Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread? I always end up with "sahara fails". Every help is welcome! Thanks!!!!
After many tries I have finally put my phone back to life. My instructions how to do it will come soon!
page1875 said: After many tries I have finally put my phone back to life. My instructions how to do it will come soon! Click to expand... Click to collapse please do, i encountered a similar problem.
HowTo Flash STOCK 00WW 1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841) 2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206) - This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html . - Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears. 3. Flash all the user images again manually with fastboot. fastboot flash boot boot.img fastboot flash dtbo dtbo.img fastboot flash system system.img fastboot flash vendor vendor.img flastboot flash vbmeta vbmeta.img Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b. Then the bootloop is finished. The phone boots normally to Android ONE. The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg). I get it managed to restore the imei, but still no service available. In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware. My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer. Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said: 1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841) 2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206) - This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html . - Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears. 3. Flash all the user images again manually with fastboot. fastboot flash boot boot.img fastboot flash dtbo dtbo.img fastboot flash system system.img fastboot flash vendor vendor.img flastboot flash vbmeta vbmeta.img Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b. Then the bootloop is finished. The phone boots normally to Android ONE. The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg). I get it managed to restore the imei, but still no service available. In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware. My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer. Then i will flash this software to my phone and look if this software will run on my phone! Click to expand... Click to collapse Thank you for your reply, it seems that your problem is more complicated than mine. I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that. Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem. I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time. My phone only showed black screen and it was always possible to connect in EDL Mode and flash again. Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206) Click to expand... Click to collapse What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ? My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing. But i saw, that in the xml file rawprogram0.xml a few files are missing. The linux programm jump over these files but perhaps QFIL do not. For example is there a picture.img listed which is not available.. Try to remove them manually from the rawfile and test again.
page1875 said: Okay. I used the linux program QDL for flashing. But i saw, that in the xml file rawprogram0.xml a few files are missing. The linux programm jump over these files but perhaps QFIL do not. For example is there a picture.img listed which is not available.. Try to remove them manually from the rawfile and test again. Click to expand... Click to collapse @update: Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing. Remove them from the XML file and try again!
@update Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello, my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back? I get this: FAILED (remote: partition table doesn't exist) P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens. The only thing that helped was flashing the complete firmware again in EDL-mode. You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread. I uploaded this files for you, because you don't will find the europe files in internet yet. Here is the link: https://transfernow.net/81iti7q21s0s Good luck!
Hi, Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone. No, that are not all firmware files, which you need to do a full EDL-Flash. But with this files you can first try a fastboot flash! If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206. Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me. thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said: thanks so much i was able to put my phone back to life. i had almost given up. Click to expand... Click to collapse Hello to ervery one how you flashed your phone. can you please guide? i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Dirty flash Realme UI V 2.0
I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11. Links available in telegram channel for Rm5p. Anybody can do it...just dont forget to flash vbmeta with disable verity......
SShots
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Kristopher28 said: Do you have steps how to do it? I didnt actually get the steps in the telegram. Click to expand... Click to collapse Yes, I will post now
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned) Things you will need. 1. A PC to use fastboot command. Will definitely need adb and fastboot drivers installed. (folder C:/ADB) 2. You need to be on stock firmware V c.14, the latest one. 3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned) Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 ) I am going to use Orangefox recovery as base here. Download from telegram: Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now) Download and place the vbmeta.img in your ADB folder. Reboot phone to recovery and DO NOT WIPE anything. Inside recovery find the entry called TERMINAL (under MENU), open it and type this first: -------------------------------------------------------------------------------------------- setprop ro.separate.soft 19691 -------------------------------------------------------------------------------------------- xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx -[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line] xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Press enter Back to ROM installation under FILES browse to UI V2 ozip. Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip) CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode. Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE In the command window type or paste this command (copy below command from here and in the command window mouse-right-click and select paste) then press enter: -------------------------------------------------------------------------------------------- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img -------------------------------------------------------------------------------------------- You should see SUCCESS message in your PC command window. Then reboot your phone by selecting START in orangefox recovery. I really love UI 2. Everyone should try this----safely. Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved. I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
jijojamie said: Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned) Things you will need. 1. A PC to use fastboot command. Will definitely need adb and fastboot drivers installed. (folder C:/ADB) 2. You need to be on stock firmware V c.14, the latest one. 3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned) Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 ) I am going to use Orangefox recovery as base here. Download from telegram: Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now) Download and place the vbmeta.img in your ADB folder. Reboot phone to recovery and DO NOT WIPE anything. Inside recovery find the entry called TERMINAL (under MENU), open it and type this first: -------------------------------------------------------------------------------------------- setprop ro.separate.soft 19691 -------------------------------------------------------------------------------------------- xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx -[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line] xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Press enter Back to ROM installation under FILES browse to UI V2 ozip. Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip) CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode. Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE In the command window type or paste this command (copy below command from here and in the command window mouse-right-click and select paste) then press enter: -------------------------------------------------------------------------------------------- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img -------------------------------------------------------------------------------------------- You should see SUCCESS message in your PC command window. Then reboot your phone by selecting START in orangefox recovery. I really love UI 2. Everyone should try this----safely. Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved. I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation. Click to expand... Click to collapse Is your phone rooted?
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Kristopher28 said: I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now Click to expand... Click to collapse If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11. Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
jijojamie said: If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11. Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others. Click to expand... Click to collapse Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.
Kristopher28 said: Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851 Click to expand... Click to collapse After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.
I dont know but the early access of 2.0 seems a little bit buggy for me
Kristopher28 said: " but there's another bug where a specific files cant read by the phone." Click to expand... Click to collapse This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager. Or else did you mean you got into bootloop. After custom rom installation we have to do a data format to actually boot into it. Try doing a factory reset or wipe data. By the way i am using rm5p Indian variant.
Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.
jijojamie said: After custom rom installation we have to do a data format to actually boot into it. Try doing a factory reset or wipe data. By the way i am using rm5p Indian variant. Click to expand... Click to collapse Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.
jijojamie said: This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager. Click to expand... Click to collapse Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Kristopher28 said: Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically. Click to expand... Click to collapse Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.
Please be more specific which ROM did you dirty flash?
Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.
Point number 2. Stock firmware latest.
Cant find the files . Which telegram channel. Link plz
How To Guide How to flash ROM and TWRP on POCO F3 / k40 / mi11x. And an explanation. A very important guide
Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3Prerequisite, unlocking the bootloaderFor questions, if something is not clear, please write to "Conversations", I will try to correct it in a post with a simpler explanation. And I will answer the question (I am not a 24/7 support service, so duplicate your question in the ROM discussion thread in order to give an answer if I'm busy) This is your last chance. After this, there is no turning back. You take the blue pill - the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill - you stay in Wonderland and I show you how deep the rabbit-hole goes Click to expand... Click to collapse !!! The spoiler below is a must-read before doing anything with your device. !!! Spoiler: Let's discuss several points at once Spoiler: 1. Drivers and utilities - download immediately and install so that there are no further questions 1. Fastboot and adb - Tools_r31.0.3 2. Miflash or Mi Flash Tool 3. USBDrivers - QDloader Spoiler: 2. Features and disadvantages of our device 2.1 We have a so-called A/B partition structure - this is when two spaces are used for system partitions (read more in google) the essence is that there are "Firmware" partitions Spoiler: code Code: "dsp.img", "/dev/block/bootdevice/by-name/dsp_a" "dsp.img", "/dev/block/bootdevice/by-name/dsp_b" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_a" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_b" "modem.img", "/dev/block/bootdevice/by-name/modem_a" "modem.img", "/dev/block/bootdevice/by-name/modem_b" "tz.img", "/dev/block/bootdevice/by-name/tz_a" "tz.img", "/dev/block/bootdevice/by-name/tz_b" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_a" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_b" "abl.img", "/dev/block/bootdevice/by-name/abl_a" "abl.img", "/dev/block/bootdevice/by-name/abl_b" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_a" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_b" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_a" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_b" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_a" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_b" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_a" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_b" "xbl.img", "/dev/block/bootdevice/by-name/xbl_a" "xbl.img", "/dev/block/bootdevice/by-name/xbl_b" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_a" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_b" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_a" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_b" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_a" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_b" "hyp.img", "/dev/block/bootdevice/by-name/hyp_a" "hyp.img", "/dev/block/bootdevice/by-name/hyp_b" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_a" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_b" "aop.img", "/dev/block/bootdevice/by-name/aop_a" "aop.img", "/dev/block/bootdevice/by-name/aop_b" and there are partitions directly ROM /data, /system /system_ext, /vendor, /product, /odm, /vendor_boot, /boot 2.2 miui based ROMs update all of these sections. In the case of firmware, they are put in both slots at once. Although this is not necessary in essence. ROMs of a custom type, those based on a "pure" android are often flashed for only partitions of the ROM, but not in 100% case 2.3 For our device, there are 3 types of ROM installation files, 2 of which are divided into two types of installation methods 2.3.1 Let's start simple, Official miui image for fastboot - installation is recommended via miflash, has all partitions inside the archive. There are also 3 files inside - for easy installation of all partitions, for installing all partitions and formatting the memory, as well as for installing all partitions and locking the bootloader (the memory is formatted automatically), the name of the .bat files speaks for themselves 2.3.2 Next - the installation .zip archive of unofficial MIUI for TWRP. Not all partitions, but the main ones (always stitched into section A), including firmware (stitched into both slots A and B) 2.3.3 Sideload type firmware (99% of all custom ROMs) are divided into two installation methods. Inside the archive there is a payload.bin file in which the rom and sometimes firmware sections are packed Installation always goes to the adjacent NOT active memory slot, and after completion, makes the adjacent slot active to load the firmware Installation via PC, via ADB (on the phone, AOSP recovery adb sideload/twrp adb sideload mode) or installation via TWRP directly from the device 2.4 Custom ROMs for fastboot, usually used for a clean installation, which implies cleaning and data from memory (pictures, etc.) inside sometimes have firmware sections and always rom sections. Inside, as the author saw fit, there are .bat launchers for updating (does not erase all data) and for a clean installation (erases all data) 2.5 Another very important feature of the AB structure in our case is two types of fastboot mod. It is called bootloader - official miui is completely flashed through it, and there is a fastbootD mode that is built into the boot sector in aosp recovery or in twrp, it is also needed for flashing img images. Ask what are the differences if this and that fastboot? The answer is idiotic Bootloader can flash all main partitions only in both A and B sections at the same time command type - "fastboot flash system_ab system.img" He knows how to essentially flash a couple of partitions into a certain slot, we only need in this case vendor_boot and boot command type "fastboot flash boot_a boot.img" or instead of A you need to write B FastbootD, on the other hand, can flash img images separately into the desired slot A or B 2.6 Poco f3/k40/mi11x does not have a separate partition for recovery/twrp,the whole thing is stored in the boot sector in the ramdisk, and the kernel is also stored there. Several factors follow from this knowledge. 2.6.1 To install TWRP, you must first boot into a temporary TWRP, the command type is "fastboot boot twrp.img". Inside TWRP, in the Advanced tab, click install recovery ramdisk, and select the img twrp image on the phone 2.6.3 To install aosp recvoery, you need to flash boot "fastboot boot boot.img" 2.6.4 After installing magisk, as it is stored in the RAMDISK. If you install TWRP again in ramdisk, the magisk will be deleted 2.6.5 When installing the magisk, TWRP does not crash 2.6.6 When installing kernel.zip via TWRP, TWRPis not deleted. 2.6.7 After updating the ROM, or changing the ROM, the TWRPis deleted, since the boot sector is bundled with all the ROMs as a whole and mainly with aosp recovery included, some romodels can immediately push TWRP into it. But it's better to play it safe and flash it yourself 2.6.8 When entering TWRP, it writes the installation .zip archives to the active slot, and always works with the active slot A or B, the exception concerns firmware, wrote above in paragraph 2.3 2.6.9 install recovery ramdis on surveillance writes TWRP to both slots Spoiler: 3. Regarding TWRP and AOSP recovery 3.1 There are currently only 2 TWRPs from Nebrassy and from vasishath. What is the difference? God knows. In fact, they are bugged equally strongly, so I will write instructions using the example of Nebrassy, from experience there are no problems with it. 3.2 AOSP recovery is like it was 10 years ago cwm recovery if anyone remembers. Serves only for switching to fastbootD and ADB sideload mode, updating the firmware over the air, and sometimes cleaning the data. Supplied by many ROM developers as a necessary component (in fact, not so) Now, based on the knowledge above, we have an understanding of how and what works. Now we need to disassemble the installation procedure. Here, too, not everything is so simple. There are two options for each installation. And in addition, we have 10 ways to install firmware. Why 10? And all due to the fact that I was unaware and had to write a small script called DFE. Isn't there a ready-made one on the Internet? According to my tests, they simply don't work. Spoiler: Briefly about DFE Somewhere 90% of ROM Developers out of the box have such a function as data encryption, DFE removes "flags" from one file in the /vendor section so that the system encrypts the data "Entire /data section" at startup therefore, just like with TWRP, after changing or updating the firmware, you need to flash it through TWRP. - Why should I remove encryption? - ask a question I will answer, in fact, there is no need, if only you are ready to always back up all data to a flash drive or PC from the internal memory of the phone when changing the firmware, because not all firmware have the same encryption keys, and you can install the firmware, but it is simply will not start at best, at worst everything will be encrypted over a new one and all files will be lost. But literally all the instructions from the developers of the ROM are written precisely taking into account the fact that you will format the date when installing their firmware. Also, if encryption is disabled, TWRP will not ask for a password to see the memory, and therefore your data is at risk when the phone is stolen, since it will not be difficult to pull them out. For all cases, you cannot do format data before installing the firmware, otherwise the PC will not see the memory, format data is done only at the end of the installation. Spoiler: Installing temporary TWRP Method 1: 1. We drop twrp.img into the folder with adb 2. In windows, hold down shift + right mouse button in an empty space in the folder, open a shell or cmd 3. The console will open, in the case of win10 / 11, if this is a shell, you need to register cmd 4. Reboot the phone into fastboot mode / bootloader (volume down + power button) and connect it to the computer via the wire 5. We write to the command "fastboot boot twrp.img" 6. TWRP will start by itself Method 2: 1.Download TWRP Autoruner https://drive.google.com/file/d/1HsA1XAEzFgEo0n7K1Vf0QqPlyEICzkpd/view?usp=sharing 2. Unpack anywhere 3. Boot into FastBoot 4. Run the batch file in the folder Spoiler: Setting TWRP to "permanent" - within the same ROM (Before the first ROM update, or before the first ROM change) Method 1: Works ALWAYS 1. Go to the advanced tab and select install recvoery ramdisk 2. Find the twrp.img file on your phone and select it 3. If TWRP shows "Error opening: No such file or directory" then you need to change the active slot in the Reboot contribution, then back and flash TWRP into the ramdisk again Method 2: For TWRP from Nebrassy does not work 100% of the time In the same place, in the advanced tab, click flash current TWRP Method 3: For TWRP from Vasishath. does not work 100% In the same place, in the advanced tab, click Inject TWRP Before flashing custom, it is recommended to install a miui stock or a custom miui. It is advisable to drain through a fastboot by analogy with the spoiler instruction, from point 1 to point 9 This is done in order to update all sections in memory, remove tails from other ROMs. Refresh the markup of the sections. Otherwise, there may be errors, not working conditional nfc, lags, whatever. In the best case, the ROM simply won't be installed. At worst, there will be a bad opinion about the ROM because of your own wrong actions and an extra day for flashing and configuring another or the same ROM. All files are additional here Spoiler: If the memory in TWRP is not visible 1. You saw that the PC does not see the memory on the device, or the TWRP is empty (this already means that all the data has been erased) 2. Download one of these TWRO to your computer recovery_vasishath_nonflags.img or recovery_nebrassy_nonflags.img 3. Through that TWRP where everything is empty, we do format data (yes) 4. Reboot bootloader 5. On the PC we prescribe "fastboot boot twrp.img" any of the post 6. TWRP is loaded (the computer and TWRP sees the memory, but this is not all, nothing will work) 7. In the advanced tab, click fix context 8. In the mounts tab, remove the checkbox from the date and put it back. 9. Now you can upload files from your computer 10. You flash the ROM, you can not do the date format again, when the system boots, it will erase everything from memory, and if you did not set dfe, then the date itself will be encrypted, if you set the data in the same way, it will be erased, but there will be no encryption. Note: These TWRPs will not see the date (files in memory) if the data is encrypted, usually TWRP asks for a password when entering it, or you can see it in the security tab. This TWRP works fine with the already decrypted date, if you use the DFE patch, everything works normally In this TWRP, the encryption flags are simply removed, so that after the date format when entering TWRP, the date is not encrypted with keys from TWRP and does not break from this Spoiler: Installation using DFE patch (HentaiOS and Proton AOSP excluded) When using DFE, you should not use internal methods of updating in ROM, when the firmware is updated in the background, and when you reboot it is already updated, as I wrote earlier, the sections are updated, and therefore the DFE stops working, and it is rather difficult to predict when the system has updated itself, and if DFE will stop working, all data will be deleted, and the ROM simply will not start, so it's better to manually set everything. Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. You need to go to the folder, and look for the flash_all_except_storage.bat file there 4. You need to open it with a text editor and delete the last line with the text "fastboot reboot" 5. Now, through miflash, we look for the directory with this file 6. We transfer the phone to fastboot mode (Hold the power button + volume rocker down) 7. We connect the device with a wire to the computer and, in the program, select the bottom right flash_all_except_storage.bat, press flash 8. After the end of the process, you need to boot into TWRP 9. In TWRP, if you did everything correctly, then the memory is not erased. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. in 99% of cases, an inscription will come out that you need to pre-flash SystemRW_1.32. Then we do it. 11. In the case of SystemRW, you need to reboot into TWRP, then either put it in RamDisk and just reboot, or click reboot bootloader and boot from the computer back to TWRP. 12. Repeat step 10. 13. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Reboot into TWRP 5. Flash DFE.zip 6. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Then, according to the instructions from the developer, you can flash the vendor and vendor_boot ROM provided by the developer, or load into the temporary TWRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in AOSP recovery select Install update through ADB 6. In the console from the adb folder in which the archive from the ROM is located, write "adb sideload name_file_PZU.zip" 7. Flash DFE.zip 8. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP in ramdisk 5. Reboot into TWRP 6. Flash DFE.zip 7. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file there, you need to open it with a text editor and delete the last line with the text "fastboot reboot" 3. We transfer the phone to fastboot mode (Hold the power button + volume down) 4. Run update.bat and wait for the end of the procedure 5. After the end of the process, you need to boot into TWRP 9. In TWRP, if you did everything right, then the memory is not erased. Otherwise, I recommend using this method so that the memory appears. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. 11. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: Standard installation methods Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. Now, through miflash, we look for the directory with this file 4. We transfer the phone to fastboot mode (Hold the power button + volume ring down) 5. We connect with a wire to the PC and first select in the program at the bottom right flash_all_except_storage.bat (For updating), flash_all.bat (For Clean installation) flash_all_lock.bat (for clean installation and locking the bootloader) or press flash 6. The system will reboot itself. Ready 7. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 7.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 7.2 Flash temporary TWRP 7.3 If you need a TWRP on an ongoing basis, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of the TWRP must be on the device 7.4 Flash the zip archives you need 7.5 You can make Wipe data to set up your phone again 8. If you updated your phone, you can do steps 7.2-7.4 Immediately after installing the update Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Make Format Data as indicated in the instructions of the firmware developer, or wipe date if you change it from custom to custom (does not always work), or just boot into the system (Risky !!) 5.Additional (Magisk, gapps and other zip): 5.1 If you have updated the ROM, you can flash additional files 5.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into TWRP, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Further, you can follow the instructions either from the developer, flash the vendor and vendor_boot provided by the developer, or boot into the temporary TWRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in aosp recovery select Install update through ADB 6. In the console, from the adb folder in which the archive with the firmware is located, write adb sideload_file_name.zip 7. At the end of the process, make Format Data as indicated in the developer's instructions, or wipe the date, if you change it from custom to custom (it does not always work), or just boot into the system 8.Additional (Magisk, gapps and other zip): 8.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 8.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 8.3 If you need a TWRP for a constant, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of a TWRP must be on the device 8.4 Flash the zip archives you need 9. If you updated your phone, you can do steps 8.2-8.4 Immediately after installing the update Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP to ramdisk 5. Reboot into TWRP 6. Make Format Data as indicated in the Developer's instructions, or wipe date, if you change miui to miui (does not always work), or just boot into the system 7.Additional (Magisk, gapps and other zip): 7.1 In case you have updated the ROM, you can flash additional files 7.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into TWRP, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file and installformat.bat there FirestInstall.bat 3. Go into fastboot mode, connect the device to the PC and select the desired installer, or update, to update, or for a clean install installformat.bat or FirestInstall.bat (all data will be erased, including memory 4. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 4.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 4.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 4.3 If you need TWRP for Permanent then we do it 4.4 Flash the zip archives you need 4.5 You can make Wipe data to set up your phone again 5. If you updated your phone, you can do steps 4.2-4.4 Immediately after installing the update
Thank you VERY much for the fantastic guide. Just one question: what are the differences between the two available TWRP for Alioth: Nebrassi and Vasishath ?
Thanks man
michelD said:
Thank you VERY much for the fantastic guide.
Just one question: what are the differences between the two available TWRP for Alioth: Nebrassi and Vasishath ?
Click to expand...
Click to collapse
{
"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"
}
please read the entire section of the paragraph
LeeGarChat said: Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3Prerequisite, unlocking the bootloaderFor questions, if something is not clear, please write to "Conversations", I will try to correct it in a post with a simpler explanation. And I will answer the question (I am not a 24/7 support service, so duplicate your question in the ROM discussion thread in order to give an answer if I'm busy) !!! The spoiler below is a must-read before doing anything with your device. !!! Spoiler: Let's discuss several points at once Spoiler: 1. Drivers and utilities - download immediately and install so that there are no further questions 1. Fastboot and adb - Tools_r31.0.3 2. Miflash 3. USBDrivers - QDloader Spoiler: 2. Features and disadvantages of our device 2.1 We have a so-called A/B partition structure - this is when two spaces are used for system partitions (read more in google) the essence is that there are "Firmware" partitions Spoiler: code Code: "dsp.img", "/dev/block/bootdevice/by-name/dsp_a" "dsp.img", "/dev/block/bootdevice/by-name/dsp_b" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_a" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_b" "modem.img", "/dev/block/bootdevice/by-name/modem_a" "modem.img", "/dev/block/bootdevice/by-name/modem_b" "tz.img", "/dev/block/bootdevice/by-name/tz_a" "tz.img", "/dev/block/bootdevice/by-name/tz_b" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_a" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_b" "abl.img", "/dev/block/bootdevice/by-name/abl_a" "abl.img", "/dev/block/bootdevice/by-name/abl_b" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_a" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_b" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_a" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_b" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_a" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_b" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_a" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_b" "xbl.img", "/dev/block/bootdevice/by-name/xbl_a" "xbl.img", "/dev/block/bootdevice/by-name/xbl_b" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_a" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_b" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_a" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_b" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_a" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_b" "hyp.img", "/dev/block/bootdevice/by-name/hyp_a" "hyp.img", "/dev/block/bootdevice/by-name/hyp_b" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_a" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_b" "aop.img", "/dev/block/bootdevice/by-name/aop_a" "aop.img", "/dev/block/bootdevice/by-name/aop_b" and there are partitions directly ROM /data, /system /system_ext, /vendor, /product, /odm, /vendor_boot, /boot 2.2 miui based ROMs update all of these sections. In the case of firmware, they are put in both slots at once. Although this is not necessary in essence. ROMs of a custom type, those based on a "pure" android are often flashed for only partitions of the ROM, but not in 100% case 2.3 For our device, there are 3 types of ROM installation files, 2 of which are divided into two types of installation methods 2.3.1 Let's start simple, Official miui image for fastboot - installation is recommended via miflash, has all partitions inside the archive. There are also 3 files inside - for easy installation of all partitions, for installing all partitions and formatting the memory, as well as for installing all partitions and locking the bootloader (the memory is formatted automatically), the name of the .bat files speaks for themselves 2.3.2 Next - the installation .zip archive of unofficial MIUI for TWRP. Not all partitions, but the main ones (always stitched into section A), including firmware (stitched into both slots A and B) 2.3.3 Sideload type firmware (99% of all custom ROMs) are divided into two installation methods. Inside the archive there is a payload.bin file in which the rom and sometimes firmware sections are packed Installation always goes to the adjacent NOT active memory slot, and after completion, makes the adjacent slot active to load the firmware Installation via PC, via ADB (on the phone, AOSP recovery adb sideload/twrp adb sideload mode) or installation via TWRP directly from the device 2.4 Custom ROMs for fastboot, usually used for a clean installation, which implies cleaning and data from memory (pictures, etc.) inside sometimes have firmware sections and always rom sections. Inside, as the author saw fit, there are .bat launchers for updating (does not erase all data) and for a clean installation (erases all data) 2.5 Another very important feature of the AB structure in our case is two types of fastboot mod. It is called bootloader - official miui is completely flashed through it, and there is a fastbootD mode that is built into the boot sector in aosp recovery or in twrp, it is also needed for flashing img images. Ask what are the differences if this and that fastboot? The answer is idiotic Bootloader can flash all main partitions only in both A and B sections at the same time command type - "fastboot flash system_ab system.img" He knows how to essentially flash a couple of partitions into a certain slot, we only need in this case vendor_boot and boot command type "fastboot flash boot_a boot.img" or instead of A you need to write B FastbootD, on the other hand, can flash img images separately into the desired slot A or B 2.6 Poco f3/k40/mi11x does not have a separate partition for recovery/twrp,the whole thing is stored in the boot sector in the ramdisk, and the kernel is also stored there. Several factors follow from this knowledge. 2.6.1 To install TWRP, you must first boot into a temporary tvrp, the command type is "fastboot boot twrp.img". Inside TWRP, in the Advanced tab, click install recovery ramdisk, and select the img twrp image on the phone 2.6.3 To install aosp recvoery, you need to flash boot "fastboot boot boot.img" 2.6.4 After installing magisk, as it is stored in the RAMDISK. If you install tvrp again in ramdisk, the magisk will be deleted 2.6.5 When installing the magisk, tvrp does not crash 2.6.6 When installing kernel.zip via TWRP, TWRPis not deleted. 2.6.7 After updating the ROM, or changing the ROM, the TWRPis deleted, since the boot sector is bundled with all the ROMs as a whole and mainly with aosp recovery included, some romodels can immediately push TWRP into it. But it's better to play it safe and flash it yourself 2.6.8 When entering TWRP, it writes the installation .zip archives to the active slot, and always works with the active slot A or B, the exception concerns firmware, wrote above in paragraph 2.3 2.6.9 install recovery ramdis on surveillance writes TWRP to both slots Spoiler: 3. Regarding TWRP and AOSP recovery 3.1 There are currently only 2 TWRPs from Nebrassy and from vasishath. What is the difference? God knows. In fact, they are bugged equally strongly, so I will write instructions using the example of Nebrassy, from experience there are no problems with it. 3.2 AOSP recovery is like it was 10 years ago cwm recovery if anyone remembers. Serves only for switching to fastbootD and ADB sideload mode, updating the firmware over the air, and sometimes cleaning the data. Supplied by many ROM developers as a necessary component (in fact, not so) Now, based on the knowledge above, we have an understanding of how and what works. Now we need to disassemble the installation procedure. Here, too, not everything is so simple. There are two options for each installation. And in addition, we have 10 ways to install firmware. Why 10? And all due to the fact that I was unaware and had to write a small script called DFE. Isn't there a ready-made one on the Internet? According to my tests, they simply don't work. Spoiler: Briefly about DFE Somewhere 90% of ROM Developers out of the box have such a function as data encryption, DFE removes "flags" from one file in the /vendor section so that the system encrypts the data "Entire /data section" at startup therefore, just like with TWRP, after changing or updating the firmware, you need to flash it through TWRP. - Why should I remove encryption? - ask a question I will answer, in fact, there is no need, if only you are ready to always back up all data to a flash drive or PC from the internal memory of the phone when changing the firmware, because not all firmware have the same encryption keys, and you can install the firmware, but it is simply will not start at best, at worst everything will be encrypted over a new one and all files will be lost. But literally all the instructions from the developers of the ROM are written precisely taking into account the fact that you will format the date when installing their firmware. Also, if encryption is disabled, TvRP will not ask for a password to see the memory, and therefore your data is at risk when the phone is stolen, since it will not be difficult to pull them out. For all cases, you cannot do format data before installing the firmware, otherwise the PC will not see the memory, format data is done only at the end of the installation. Spoiler: Installing temporary TWRP Method 1: 1. We drop twrp.img into the folder with adb 2. In windows, hold down shift + right mouse button in an empty space in the folder, open a shell or cmd 3. The console will open, in the case of win10 / 11, if this is a shell, you need to register cmd 4. Reboot the phone into fastboot mode / bootloader (volume down + power button) and connect it to the computer via the wire 5. We write to the command "fastboot boot twrp.img" 6. TWRP will start by itself Method 2: 1.Download TWRP Autoruner https://drive.google.com/file/d/1HsA1XAEzFgEo0n7K1Vf0QqPlyEICzkpd/view?usp=sharing 2. Unpack anywhere 3. Boot into FastBoot 4. Run the batch file in the folder Spoiler: Setting TWRP to "permanent" - within the same ROM (Before the first ROM update, or before the first ROM change) Method 1: Works ALWAYS 1. Go to the advanced tab and select install recvoery ramdisk 2. Find the twrp.img file on your phone and select it 3. If TWRP shows "Error opening: No such file or directory" then you need to change the active slot in the Reboot contribution, then back and flash TWRP into the ramdisk again Method 2: For TWRP from Nebrassy does not work 100% of the time In the same place, in the advanced tab, click flash current TWRP Method 3: For TWRP from Vasishath. does not work 100% In the same place, in the advanced tab, click Inject TWRP Before flashing custom, it is recommended to install a miui stock or a custom miui. It is advisable to drain through a fastboot by analogy with the spoiler instruction, from point 1 to point 9 This is done in order to update all sections in memory, remove tails from other ROMs. Refresh the markup of the sections. Otherwise, there may be errors, not working conditional nfc, lags, whatever. In the best case, the ROM simply won't be installed. At worst, there will be a bad opinion about the ROM because of your own wrong actions and an extra day for flashing and configuring another or the same ROM. All files are additional here Spoiler: If the memory in TWRP is not visible 1. You saw that the PC does not see the memory on the device, or the tvrp is empty (this already means that all the data has been erased) 2. Download one of these TVRPs to your computer recovery_vasishath_nonflags.img or recovery_nebrassy_nonflags.img 3. Through that TWRP where everything is empty, we do format data (yes) 4. Reboot bootloader 5. On the PC we prescribe "fastboot boot twrp.img" any of the post 6. TvRP is loaded (the computer and TWRP sees the memory, but this is not all, nothing will work) 7. In the advanced tab, click fix context 8. In the mounts tab, remove the checkbox from the date and put it back. 9. Now you can upload files from your computer 10. You flash the ROM, you can not do the date format again, when the system boots, it will erase everything from memory, and if you did not set dfe, then the date itself will be encrypted, if you set the data in the same way, it will be erased, but there will be no encryption. Note: These TWRPs will not see the date (files in memory) if the data is encrypted, usually TWRP asks for a password when entering it, or you can see it in the security tab. This TWRP works fine with the already decrypted date, if you use the DFE patch, everything works normally In this TWRP, the encryption flags are simply removed, so that after the date format when entering TVRP, the date is not encrypted with keys from TWRP and does not break from this Spoiler: Installation using DFE patch (HentaiOS and Proton AOSP excluded) When using DFE, you should not use internal methods of updating in ROM, when the firmware is updated in the background, and when you reboot it is already updated, as I wrote earlier, the sections are updated, and therefore the DFE stops working, and it is rather difficult to predict when the system has updated itself, and if DFE will stop working, all data will be deleted, and the ROM simply will not start, so it's better to manually set everything. Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. You need to go to the folder, and look for the flash_all_except_storage.bat file there 4. You need to open it with a text editor and delete the last line with the text "fastboot reboot" 5. Now, through miflash, we look for the directory with this file 6. We transfer the phone to fastboot mode (Hold the power button + volume rocker down) 7. We connect the device with a wire to the computer and, in the program, select the bottom right flash_all_except_storage.bat, press flash 8. After the end of the process, you need to boot into TWRP 9. In TVRP, if you did everything correctly, then the memory is not erased. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. in 99% of cases, an inscription will come out that you need to pre-flash SystemRW_1.32. Then we do it. 11. In the case of SystemRW, you need to reboot into TWRP, then either put it in RamDisk and just reboot, or click reboot bootloader and boot from the computer back to TWRP. 12. Repeat step 10. 13. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Reboot into TWRP 5. Flash DFE.zip 6. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Then, according to the instructions from the developer, you can flash the vendor and vendor_boot ROM provided by the developer, or load into the temporary TVRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in AOSP recovery select Install update through ADB 6. In the console from the adb folder in which the archive from the ROM is located, write "adb sideload name_file_PZU.zip" 7. Flash DFE.zip 8. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP in ramdisk 5. Reboot into TWRP 6. Flash DFE.zip 7. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file there, you need to open it with a text editor and delete the last line with the text "fastboot reboot" 3. We transfer the phone to fastboot mode (Hold the power button + volume down) 4. Run update.bat and wait for the end of the procedure 5. After the end of the process, you need to boot into TWRP 9. In TWRP, if you did everything right, then the memory is not erased. Otherwise, I recommend using this method so that the memory appears. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. 11. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: Standard installation methods Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. Now, through miflash, we look for the directory with this file 4. We transfer the phone to fastboot mode (Hold the power button + volume ring down) 5. We connect with a wire to the PC and first select in the program at the bottom right flash_all_except_storage.bat (For updating), flash_all.bat (For Clean installation) flash_all_lock.bat (for clean installation and locking the bootloader) or press flash 6. The system will reboot itself. Ready 7. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 7.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 7.2 Flash temporary TWRP 7.3 If you need a TVRP on an ongoing basis, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of the TVRP must be on the device 7.4 Flash the zip archives you need 7.5 You can make Wipe data to set up your phone again 8. If you updated your phone, you can do steps 7.2-7.4 Immediately after installing the update Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Make Format Data as indicated in the instructions of the firmware developer, or wipe date if you change it from custom to custom (does not always work), or just boot into the system (Risky !!) 5.Additional (Magisk, gapps and other zip): 5.1 If you have updated the ROM, you can flash additional files 5.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into tvrp, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Further, you can follow the instructions either from the developer, flash the vendor and vendor_boot provided by the developer, or boot into the temporary TWRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in aosp recovery select Install update through ADB 6. In the console, from the adb folder in which the archive with the firmware is located, write adb sideload_file_name.zip 7. At the end of the process, make Format Data as indicated in the developer's instructions, or wipe the date, if you change it from custom to custom (it does not always work), or just boot into the system 8.Additional (Magisk, gapps and other zip): 8.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 8.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 8.3 If you need a TVRP for a constant, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of a tvrp must be on the device 8.4 Flash the zip archives you need 9. If you updated your phone, you can do steps 8.2-8.4 Immediately after installing the update Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP to ramdisk 5. Reboot into TWRP 6. Make Format Data as indicated in the Developer's instructions, or wipe date, if you change miui to miui (does not always work), or just boot into the system 7.Additional (Magisk, gapps and other zip): 7.1 In case you have updated the ROM, you can flash additional files 7.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into tvrp, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file and installformat.bat there FirestInstall.bat 3. Go into fastboot mode, connect the device to the PC and select the desired installer, or update, to update, or for a clean install installformat.bat or FirestInstall.bat (all data will be erased, including memory 4. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 4.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 4.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 4.3 If you need TWRP for Permanent then we do it 4.4 Flash the zip archives you need 4.5 You can make Wipe data to set up your phone again 5. If you updated your phone, you can do steps 4.2-4.4 Immediately after installing the update Click to expand... Click to collapse Many thanks for making this complete and detailed guide. It was really needed! Good job!
LeeGarChat said: Mandatory instructions for beginners (and not only beginners) to install ROM and other on poco f3Prerequisite, unlocking the bootloaderFor questions, if something is not clear, please write to "Conversations", I will try to correct it in a post with a simpler explanation. And I will answer the question (I am not a 24/7 support service, so duplicate your question in the ROM discussion thread in order to give an answer if I'm busy) !!! The spoiler below is a must-read before doing anything with your device. !!! Spoiler: Let's discuss several points at once Spoiler: 1. Drivers and utilities - download immediately and install so that there are no further questions 1. Fastboot and adb - Tools_r31.0.3 2. Miflash 3. USBDrivers - QDloader Spoiler: 2. Features and disadvantages of our device 2.1 We have a so-called A/B partition structure - this is when two spaces are used for system partitions (read more in google) the essence is that there are "Firmware" partitions Spoiler: code Code: "dsp.img", "/dev/block/bootdevice/by-name/dsp_a" "dsp.img", "/dev/block/bootdevice/by-name/dsp_b" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_a" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_b" "modem.img", "/dev/block/bootdevice/by-name/modem_a" "modem.img", "/dev/block/bootdevice/by-name/modem_b" "tz.img", "/dev/block/bootdevice/by-name/tz_a" "tz.img", "/dev/block/bootdevice/by-name/tz_b" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_a" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_b" "abl.img", "/dev/block/bootdevice/by-name/abl_a" "abl.img", "/dev/block/bootdevice/by-name/abl_b" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_a" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_b" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_a" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_b" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_a" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_b" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_a" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_b" "xbl.img", "/dev/block/bootdevice/by-name/xbl_a" "xbl.img", "/dev/block/bootdevice/by-name/xbl_b" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_a" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_b" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_a" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_b" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_a" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_b" "hyp.img", "/dev/block/bootdevice/by-name/hyp_a" "hyp.img", "/dev/block/bootdevice/by-name/hyp_b" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_a" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_b" "aop.img", "/dev/block/bootdevice/by-name/aop_a" "aop.img", "/dev/block/bootdevice/by-name/aop_b" and there are partitions directly ROM /data, /system /system_ext, /vendor, /product, /odm, /vendor_boot, /boot 2.2 miui based ROMs update all of these sections. In the case of firmware, they are put in both slots at once. Although this is not necessary in essence. ROMs of a custom type, those based on a "pure" android are often flashed for only partitions of the ROM, but not in 100% case 2.3 For our device, there are 3 types of ROM installation files, 2 of which are divided into two types of installation methods 2.3.1 Let's start simple, Official miui image for fastboot - installation is recommended via miflash, has all partitions inside the archive. There are also 3 files inside - for easy installation of all partitions, for installing all partitions and formatting the memory, as well as for installing all partitions and locking the bootloader (the memory is formatted automatically), the name of the .bat files speaks for themselves 2.3.2 Next - the installation .zip archive of unofficial MIUI for TWRP. Not all partitions, but the main ones (always stitched into section A), including firmware (stitched into both slots A and B) 2.3.3 Sideload type firmware (99% of all custom ROMs) are divided into two installation methods. Inside the archive there is a payload.bin file in which the rom and sometimes firmware sections are packed Installation always goes to the adjacent NOT active memory slot, and after completion, makes the adjacent slot active to load the firmware Installation via PC, via ADB (on the phone, AOSP recovery adb sideload/twrp adb sideload mode) or installation via TWRP directly from the device 2.4 Custom ROMs for fastboot, usually used for a clean installation, which implies cleaning and data from memory (pictures, etc.) inside sometimes have firmware sections and always rom sections. Inside, as the author saw fit, there are .bat launchers for updating (does not erase all data) and for a clean installation (erases all data) 2.5 Another very important feature of the AB structure in our case is two types of fastboot mod. It is called bootloader - official miui is completely flashed through it, and there is a fastbootD mode that is built into the boot sector in aosp recovery or in twrp, it is also needed for flashing img images. Ask what are the differences if this and that fastboot? The answer is idiotic Bootloader can flash all main partitions only in both A and B sections at the same time command type - "fastboot flash system_ab system.img" He knows how to essentially flash a couple of partitions into a certain slot, we only need in this case vendor_boot and boot command type "fastboot flash boot_a boot.img" or instead of A you need to write B FastbootD, on the other hand, can flash img images separately into the desired slot A or B 2.6 Poco f3/k40/mi11x does not have a separate partition for recovery/twrp,the whole thing is stored in the boot sector in the ramdisk, and the kernel is also stored there. Several factors follow from this knowledge. 2.6.1 To install TWRP, you must first boot into a temporary tvrp, the command type is "fastboot boot twrp.img". Inside TWRP, in the Advanced tab, click install recovery ramdisk, and select the img twrp image on the phone 2.6.3 To install aosp recvoery, you need to flash boot "fastboot boot boot.img" 2.6.4 After installing magisk, as it is stored in the RAMDISK. If you install tvrp again in ramdisk, the magisk will be deleted 2.6.5 When installing the magisk, tvrp does not crash 2.6.6 When installing kernel.zip via TWRP, TWRPis not deleted. 2.6.7 After updating the ROM, or changing the ROM, the TWRPis deleted, since the boot sector is bundled with all the ROMs as a whole and mainly with aosp recovery included, some romodels can immediately push TWRP into it. But it's better to play it safe and flash it yourself 2.6.8 When entering TWRP, it writes the installation .zip archives to the active slot, and always works with the active slot A or B, the exception concerns firmware, wrote above in paragraph 2.3 2.6.9 install recovery ramdis on surveillance writes TWRP to both slots Spoiler: 3. Regarding TWRP and AOSP recovery 3.1 There are currently only 2 TWRPs from Nebrassy and from vasishath. What is the difference? God knows. In fact, they are bugged equally strongly, so I will write instructions using the example of Nebrassy, from experience there are no problems with it. 3.2 AOSP recovery is like it was 10 years ago cwm recovery if anyone remembers. Serves only for switching to fastbootD and ADB sideload mode, updating the firmware over the air, and sometimes cleaning the data. Supplied by many ROM developers as a necessary component (in fact, not so) Now, based on the knowledge above, we have an understanding of how and what works. Now we need to disassemble the installation procedure. Here, too, not everything is so simple. There are two options for each installation. And in addition, we have 10 ways to install firmware. Why 10? And all due to the fact that I was unaware and had to write a small script called DFE. Isn't there a ready-made one on the Internet? According to my tests, they simply don't work. Spoiler: Briefly about DFE Somewhere 90% of ROM Developers out of the box have such a function as data encryption, DFE removes "flags" from one file in the /vendor section so that the system encrypts the data "Entire /data section" at startup therefore, just like with TWRP, after changing or updating the firmware, you need to flash it through TWRP. - Why should I remove encryption? - ask a question I will answer, in fact, there is no need, if only you are ready to always back up all data to a flash drive or PC from the internal memory of the phone when changing the firmware, because not all firmware have the same encryption keys, and you can install the firmware, but it is simply will not start at best, at worst everything will be encrypted over a new one and all files will be lost. But literally all the instructions from the developers of the ROM are written precisely taking into account the fact that you will format the date when installing their firmware. Also, if encryption is disabled, TvRP will not ask for a password to see the memory, and therefore your data is at risk when the phone is stolen, since it will not be difficult to pull them out. For all cases, you cannot do format data before installing the firmware, otherwise the PC will not see the memory, format data is done only at the end of the installation. Spoiler: Installing temporary TWRP Method 1: 1. We drop twrp.img into the folder with adb 2. In windows, hold down shift + right mouse button in an empty space in the folder, open a shell or cmd 3. The console will open, in the case of win10 / 11, if this is a shell, you need to register cmd 4. Reboot the phone into fastboot mode / bootloader (volume down + power button) and connect it to the computer via the wire 5. We write to the command "fastboot boot twrp.img" 6. TWRP will start by itself Method 2: 1.Download TWRP Autoruner https://drive.google.com/file/d/1HsA1XAEzFgEo0n7K1Vf0QqPlyEICzkpd/view?usp=sharing 2. Unpack anywhere 3. Boot into FastBoot 4. Run the batch file in the folder Spoiler: Setting TWRP to "permanent" - within the same ROM (Before the first ROM update, or before the first ROM change) Method 1: Works ALWAYS 1. Go to the advanced tab and select install recvoery ramdisk 2. Find the twrp.img file on your phone and select it 3. If TWRP shows "Error opening: No such file or directory" then you need to change the active slot in the Reboot contribution, then back and flash TWRP into the ramdisk again Method 2: For TWRP from Nebrassy does not work 100% of the time In the same place, in the advanced tab, click flash current TWRP Method 3: For TWRP from Vasishath. does not work 100% In the same place, in the advanced tab, click Inject TWRP Before flashing custom, it is recommended to install a miui stock or a custom miui. It is advisable to drain through a fastboot by analogy with the spoiler instruction, from point 1 to point 9 This is done in order to update all sections in memory, remove tails from other ROMs. Refresh the markup of the sections. Otherwise, there may be errors, not working conditional nfc, lags, whatever. In the best case, the ROM simply won't be installed. At worst, there will be a bad opinion about the ROM because of your own wrong actions and an extra day for flashing and configuring another or the same ROM. All files are additional here Spoiler: If the memory in TWRP is not visible 1. You saw that the PC does not see the memory on the device, or the tvrp is empty (this already means that all the data has been erased) 2. Download one of these TVRPs to your computer recovery_vasishath_nonflags.img or recovery_nebrassy_nonflags.img 3. Through that TWRP where everything is empty, we do format data (yes) 4. Reboot bootloader 5. On the PC we prescribe "fastboot boot twrp.img" any of the post 6. TvRP is loaded (the computer and TWRP sees the memory, but this is not all, nothing will work) 7. In the advanced tab, click fix context 8. In the mounts tab, remove the checkbox from the date and put it back. 9. Now you can upload files from your computer 10. You flash the ROM, you can not do the date format again, when the system boots, it will erase everything from memory, and if you did not set dfe, then the date itself will be encrypted, if you set the data in the same way, it will be erased, but there will be no encryption. Note: These TWRPs will not see the date (files in memory) if the data is encrypted, usually TWRP asks for a password when entering it, or you can see it in the security tab. This TWRP works fine with the already decrypted date, if you use the DFE patch, everything works normally In this TWRP, the encryption flags are simply removed, so that after the date format when entering TVRP, the date is not encrypted with keys from TWRP and does not break from this Spoiler: Installation using DFE patch (HentaiOS and Proton AOSP excluded) When using DFE, you should not use internal methods of updating in ROM, when the firmware is updated in the background, and when you reboot it is already updated, as I wrote earlier, the sections are updated, and therefore the DFE stops working, and it is rather difficult to predict when the system has updated itself, and if DFE will stop working, all data will be deleted, and the ROM simply will not start, so it's better to manually set everything. Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. You need to go to the folder, and look for the flash_all_except_storage.bat file there 4. You need to open it with a text editor and delete the last line with the text "fastboot reboot" 5. Now, through miflash, we look for the directory with this file 6. We transfer the phone to fastboot mode (Hold the power button + volume rocker down) 7. We connect the device with a wire to the computer and, in the program, select the bottom right flash_all_except_storage.bat, press flash 8. After the end of the process, you need to boot into TWRP 9. In TVRP, if you did everything correctly, then the memory is not erased. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. in 99% of cases, an inscription will come out that you need to pre-flash SystemRW_1.32. Then we do it. 11. In the case of SystemRW, you need to reboot into TWRP, then either put it in RamDisk and just reboot, or click reboot bootloader and boot from the computer back to TWRP. 12. Repeat step 10. 13. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Reboot into TWRP 5. Flash DFE.zip 6. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Then, according to the instructions from the developer, you can flash the vendor and vendor_boot ROM provided by the developer, or load into the temporary TVRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in AOSP recovery select Install update through ADB 6. In the console from the adb folder in which the archive from the ROM is located, write "adb sideload name_file_PZU.zip" 7. Flash DFE.zip 8. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP in ramdisk 5. Reboot into TWRP 6. Flash DFE.zip 7. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file there, you need to open it with a text editor and delete the last line with the text "fastboot reboot" 3. We transfer the phone to fastboot mode (Hold the power button + volume down) 4. Run update.bat and wait for the end of the procedure 5. After the end of the process, you need to boot into TWRP 9. In TWRP, if you did everything right, then the memory is not erased. Otherwise, I recommend using this method so that the memory appears. 10. We transfer DFE from the computer to the phone, or if you did it in advance, then we flash it. 11. If you have not used DFE before, then you need to do format DATA (yes). If you have updated the firmware in this way, then you do not need to do Format data. If you have changed the firmware, it is recommended to do wipe data, otherwise either the firmware will not boot, or it will not work correctly Spoiler: Standard installation methods Spoiler: ROM Type Official MIUI Fastboot 1. Download zip with fastboot image MIUI 2. Unpack it to a convenient place 3. Now, through miflash, we look for the directory with this file 4. We transfer the phone to fastboot mode (Hold the power button + volume ring down) 5. We connect with a wire to the PC and first select in the program at the bottom right flash_all_except_storage.bat (For updating), flash_all.bat (For Clean installation) flash_all_lock.bat (for clean installation and locking the bootloader) or press flash 6. The system will reboot itself. Ready 7. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 7.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 7.2 Flash temporary TWRP 7.3 If you need a TVRP on an ongoing basis, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of the TVRP must be on the device 7.4 Flash the zip archives you need 7.5 You can make Wipe data to set up your phone again 8. If you updated your phone, you can do steps 7.2-7.4 Immediately after installing the update Spoiler: ROM type Pyaload.bin for TWRP 1. Install TWRP in ramdisk and / or go into it 2. Flash .zip ROM file 3. Install TWRP in ramdisk 4. Make Format Data as indicated in the instructions of the firmware developer, or wipe date if you change it from custom to custom (does not always work), or just boot into the system (Risky !!) 5.Additional (Magisk, gapps and other zip): 5.1 If you have updated the ROM, you can flash additional files 5.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into tvrp, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Payload.bin for ADB sideload via PC 1. Download the .zip ROM to your PC. Upload the archive to the adb folder 2. Further, you can follow the instructions either from the developer, flash the vendor and vendor_boot provided by the developer, or boot into the temporary TWRP from nebrassy "fastboot flash boot twrp.img", or through the autoinstall script 3. Further, in the case of AOSP recovery fastboot --set-active = a and fastboot reboot recovery 5. In twrp, select the advanced section and click adb sideload. in aosp recovery select Install update through ADB 6. In the console, from the adb folder in which the archive with the firmware is located, write adb sideload_file_name.zip 7. At the end of the process, make Format Data as indicated in the developer's instructions, or wipe the date, if you change it from custom to custom (it does not always work), or just boot into the system 8.Additional (Magisk, gapps and other zip): 8.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 8.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 8.3 If you need a TVRP for a constant, then we flash it into a ramdisk (Imstall recvoery ramdisk), the img image of a tvrp must be on the device 8.4 Flash the zip archives you need 9. If you updated your phone, you can do steps 8.2-8.4 Immediately after installing the update Spoiler: ROM Type Custom MIUI (For example Xiaomi.eu) 1. Download CustomMIUI.zip 2. Install TWRP in ramdisk and / or go into it 3. Flash CustomMIUI.zip ROM file 4. Install TWRP to ramdisk 5. Reboot into TWRP 6. Make Format Data as indicated in the Developer's instructions, or wipe date, if you change miui to miui (does not always work), or just boot into the system 7.Additional (Magisk, gapps and other zip): 7.1 In case you have updated the ROM, you can flash additional files 7.2 If you have made format data, you need to boot into the system, go through the setup, put the lock key and reboot into tvrp, after that you can put an additional zip. and make wipe data to configure it again Spoiler: ROM type Custom fastboot image. 1. Download fastboot ROM on PC 2. Unzip to a convenient place, and go to the folder, find the update.bat file and installformat.bat there FirestInstall.bat 3. Go into fastboot mode, connect the device to the PC and select the desired installer, or update, to update, or for a clean install installformat.bat or FirestInstall.bat (all data will be erased, including memory 4. Additionally (Magisk, gapps and other zip) after a clean install with all files removed: 4.1 After loading into the system, we go through the device configuration, and we must put a pin or a graphic key 4.2 Reboot the phone into fastboot mode (volume down and hold down the power button) connect the computer, flash the temporary TWRP 4.3 If you need TWRP for Permanent then we do it 4.4 Flash the zip archives you need 4.5 You can make Wipe data to set up your phone again 5. If you updated your phone, you can do steps 4.2-4.4 Immediately after installing the update Click to expand... Click to collapse I would propose to add and / or replace in the 1st spoiler "diriver and utilities" the link to this site to download "miflashtool" Xiaomi Flash Tool - Official Mi Flash Tool Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website. xiaomiflashtool.com where the latest version of the software is present.
RollDload said: I would propose to add and / or replace in the 1st spoiler "diriver and utilities" the link to this site to download "miflashtool" Xiaomi Flash Tool - Official Mi Flash Tool Download the latest and Official Xiaomi Flash Tool from the Official Xiaomi Flash Tool Website. xiaomiflashtool.com where the latest version of the software is present. Click to expand... Click to collapse Okey, I'll do it later
I hope everything in this guide is clear. I just used Google translator. I do not speak English myself ideally
LeeGarChat said: I hope everything in this guide is clear. I just used Google translator. I do not speak English myself ideally Click to expand... Click to collapse Apparently yes, although I don't speak fluent English either. I can understand it while reading, but not everything, so I use the translator too and I was able to read and understand your guide without any problems. Some native speakers will probably disagree with me .
Very Informative Guide ! A must read for everyone
LeeGarChat said: in 99% of cases, an inscription will come out that you need to pre-flash SystemRW_1.32. Then we do it. 11. In the case of SystemRW, you need to reboot into TWRP, then either put it in RamDisk and just reboot, or click reboot bootloader and boot from the computer back to TWRP. Click to expand... Click to collapse Hi @LeeGarChat thanks for your interest in my SystemRW / SuperRW feat. MakeRW script Does it work well on your Poco F3 device? You never sent me your log files... If you're going to use my SystemRW / SuperRW feat. MakeRW project (or parts thereof) in your thread and make a video about it could you please at least have the decency to include a visible link (not hidden inside of spoiler tags!) to the official SystemRW / SuperRW feat. MakeRW by lebigmac project threadin the first post of this thread as well as in your video description? Thanks And please keep in mind that unauthorized, unverified re-uploads of my SystemRW project files are not allowed! The official download links in the official SystemRW / SuperRW feat. MakeRW by lebigmac thread work just fine! I can't offer any customer support for old, unofficial, deprecated, unverified versions of my script which were reuploaded by 3rd parties but I can only offer support for the latest official version of my script downloaded directly from the official SystemRW / SuperRW feat. MakeRW by lebigmac project thread Thank you! Good news! New version of © SystemRW / SuperRW feat. MakeRW™ by lebigmac ® coming soon! Stay tuned!
Hey Guys i need your help, i followed all the steps in that post but i could not find the " Onekey injection" so i ignored that step and installed the xiaomi eu rom. Everything went well, now when i want to boot in recovery mode it shows up the stock recovery So my question is when i want to update my phone in the future, i have to install it through TWRP and if my data will be lost or no?
Kaddy2727 said: Hey Guys i need your help, i followed all the steps in that post but i could not find the " Onekey injection" so i ignored that step and installed the xiaomi eu rom. Everything went well, now when i want to boot in recovery mode it shows up the stock recovery So my question is when i want to update my phone in the future, i have to install it through TWRP and if my data will be lost or no? Click to expand... Click to collapse which version did you flash of xiaomi eu, the weekly or the stable? The latest versions should flash twrp as well. However, if you only upgrade there is no need to format data, so you do not lose your data, I always recommend that you do a backup before any modding operation because you never know what can happen. To flash twrp download the image from here: [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added... forum.xda-developers.com put the image filenametwrp.img in the folder where there is adb and fastboot go to the folder where there is adb and fastboot, rename the filenametwrp.img to twrp.img then go to the address bar and type cmd and press enter, (a prompt window should open) (In the phone) make sure you have enabled usb debug in developer settings and have authorized the pc. now turn off the phone and start it in fastboot, then connect it to the pc via the usb cable in the cmd you opened before type this Code: fastboot deviced to check if it is recognized if the phone code appears you can boot twrp by typing this Code: fastboot boot twrp.img hit enter and the phone should boot into twrp now in twrp go to advanced and search "install current twrp" in the options at the bottom below and flash. you should now have twrp.
lebigmac said: Hi @LeeGarChat thanks for your interest in my SystemRW script. Does it work well on your Poco F3 device? You never sent me your log files... Could you please include a link to my project in first post of this thread? Thank you! Click to expand... Click to collapse I'll reply in his stead .... As of now - latest Xiaomi betas for global 12.5.4 it does not work correctly doing it the way he described ( flashing 1.32rw inside twrp has to be done twice lol ) After flashing it twice you have to flash his patch then reboot the phone and format data. Now phone will say decrypted but for who knows what reason everything is broken. Lots of silent crashes from the systemui and overall slowdown of the system/several apps refusing to work. Fast charging is gone as well.... Strangely much less stuff appears to be broken in EEA version of the miui , still needs flashing twice the main script but at least fast charging works afterwards. System is slightly more stable but still overall suffering from slowdown. I personally found that manual method of creating image from booted android does work somewhat. You only need to do it once by executing systemrw.sh then flashing the super.img . What's the catch? You can't flash super.img through "fastboot flash super" command , it mangles partitions to the point where /vendor and /odm can't mount inside twrp. I am curious tho maybe I don't need to enter twrp after flashing super image via fastboot? Maybe his fix is not necessary then and I just need to wipe and boot system to fix /vendor and /odm not being able to mount.... Hmmm I'll try this when I'm free sometime , but for now I'm not using this due to performance issues mainly. His script does let you at least get that decrypted status but for who knows what reason lots of stuff is broken... Could be magisk being flashed onto phone before partitions are extracted or overall twrp not being anywhere close to stable enough to handle all of this?
@Rstment ^m^ I can nowhere read sth. about this rw Script . Where does it play a role ? I just wanna flash a xiaomi.eu Rom. Are you talking about the official weekly/stable ?
Eclipse1991 said: @Rstment ^m^ I can nowhere read sth. about this rw Script . Where does it play a role ? I just wanna flash a xiaomi.eu Rom. Are you talking about the official weekly/stable ? Click to expand... Click to collapse Nah , it's related to decrypting rom. Not something you should worry about...
@Kaddy2727 @RollDload @Rstment ^m^ @Eclipse1991 @__halvar__ I wrote my SystemRW/SuperRW feat. MakeRW script for all Android power users out there that wish to make their stock read-only Android 10+ device read/write-able again to remove annoying bloatware and make more thorough customizations to their device. If you like my SystemRW / SuperRW feat. MakeRW script and want to share your feedback with me (the original developer of SystemRW / SuperRW feat. MakeRW) or have any questions related to my script then please feel free to ask me in the official SystemRW / SuperRW feat. MakeRW by lebigmac project thread Rstment ^m^ said: As of now - latest Xiaomi betas for global 12.5.4 it does not work correctly doing it the way he described ( flashing 1.32rw inside twrp has to be done twice lol ) After flashing it twice you have to flash his patch then reboot the phone and format data. Click to expand... Click to collapse @Rstment ^m^ I do NOT recommend formatting /data after running my SystemRW / SuperRW feat. MakeRW script in recovery! You will lose all your personal files if you do this! You just have to make sure that /data partition is properly decrypted and mounted in your custom recovery before running my SystemRW / SuperRW feat. MakeRW script. That's all.
im on miui global 12.5.6 do i need to flash the stock rom before flashing custom rom?
I tried the Custom MIUI Process with OneOS and when flashing ROM and after Recovery to Ramdisk and reboot, the internal storage contents disappear. What is the reason ? Caused both on 3.5.2 TWRP and 3.6.0 Official one.
Can be used as reference for xiaomi 11t pro? Cause I didn't see any custom rom for this device
Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)
Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening. Things that I have Tried: So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. " [GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". [GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and... forum.xda-developers.com ". The one that works: Things that you needed: 1. Download Mi Flash Tool(https://www.xiaomiflash.com/) 2. Minimal ADB and Fastboot 3. 7zip or BreeZip 4. TWRP A12( TWRP A12.rar drive.google.com ) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device. 5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/) warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work. Steps to follow. 1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11. 2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca" 3. Using the Mi Flash Tool, just pick the clean all and start the flashing. 4. After flashing the rom set up the phone but do not update it. 5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone. 6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom. 7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery". 8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd. 9. run the following commands: fastboot devices (then press the enter) warning: make sure that the fastboot devices is able to see your device. after seeing the device run this command: fastboot boot recovery.img (then press enter) the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery. 10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone. After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter) Summary guide: 1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img" 2. Put persist.img into your device's internal memory and go to TWRP 3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition 4. Restart the device, it should work fine
uvzen said: You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter) Summary guide: 1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img" 2. Put persist.img into your device's internal memory and go to TWRP 3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition 4. Restart the device, it should work fine Click to expand... Click to collapse Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
mizuhored said: Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp. Click to expand... Click to collapse If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
uvzen said: If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently). Click to expand... Click to collapse Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
mizuhored said: Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it. Click to expand... Click to collapse Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.