Just going to dump all the info I've found about this device into this thread. All the threads pertaining to this thread are in Russian and I can't read Russian, so this might be helpful to any English speaking owners of this tablet.
Special thanks to Telegram user @SSDD_1744 (don't know your XDA/Reddit user, I'm sorry) for basically spoonfeeding me all these instructions!
WARNING: If you need to flash to stock for whatever reason, be sure to download a image file specific to your country. If you don't, you'll hard brick your device that can only be fixed QPST (supposedly).
Rooting:
(Tested on 5.0.2)
Install KingRoot. Let it root your device.
Install Super-SU Me, to get rid of the bloatware that comes with KingRoot.
Installing Xposed:
I used Flashify to flash TWRP. Be sure to flash the right version though (2.8.7.7 v2) or else you won't be able to mount cache.
Then download Xposed (version sdk21 ARM) and flash it.
WARNING: Flash v1 of the modded TWRP and you won't be able install any apps after flashing Xposed.
Unbricking:
Still working on it. Downloaded QPST but have not been able to get QPST 2.7 to read the tablet.
Links:
Discussion:
https://translate.googleusercontent...690491&usg=ALkJrhiWSlkbZ-tUofZx68NPSGIv8pjIPA
Root:
https://translate.googleusercontent...JrhhQszcRvUo8HILThvz57JmsLj4L9g#entry44556703
https://translate.googleusercontent...JrhiCt__6apcRhk-gtcBExYJCnC9nGQ#entry41676452
Instructions for obtaining the rights to Ruth phones / tablets.
Tested on Android 4.4+
perhaps this algorithm works on Android 5+, I have no way to verify
All transactions with their phones / tablets are performing at your own risk !!!
To get started, read this post from start to finish and only then proceed to action!
Introduction
This instruction is written based on my own experience obtaining root on their plates, and then on the Xperia M2, bought plemyashki. For instructions attached versions of applications that were relevant at the time, the new version can download the relevant topics on the forum, there will find all information on how to work with the proposed programs and algorithms for their actions (links to topics added).
For all the action with your phone / tablet you are responsible for yourself!
Download all the necessary tools to obtain Root (of instructions / topics on the forum), obespechte for phone / tablet access to the Internet (Wi-F / mobile data) and let the phone settings / tablet installation from unknown sources.
Needed Downloads
KingRoot_V4.5.0B202.apk (6.76 MB)
Me_5.9.apk-SuperSU (9.07 MB)
V2.49 Beta.apk SuperSU (5.63 MB)
eu.chainfire.supersu.pro.205.apk (52,88 KB)
Next in series:
1. Install KingRoot .
Get Ruth's right, in the device may reboot.
2. Set SuperSU-Me, .
Run the grantor, the program deletes KingRoot and Chinese KingUser with replacement SuperSu.
Remove the longer SuperSu-Me the desired program.
3. Obnovyaem SuperSu to the latest version. Then set PRO-key .
Installing Pro-key Optionally !!! Use Cases SuperSu without installing key .
4. Open SuperSu and on-demand update binary SU normal way. After a successful update, confirm the request to restart.
5. To make sure that everything is done correctly, check the correct installation and operation of Ruth (mount the system partition on the record), I used the Root Checker Pro and Root Explorer , respectively.
The output is a complete rut without kitayschiny with SuperSu Pro. We use and enjoy
Click to expand...
Click to collapse
Unlocking bootloader (haven't tried this):
https://translate.googleusercontent...Jrhh6g4wI-8Hb_LzAcPnIUxYvWNzZ0A#entry46711087
Stock firmware:
https://translate.googleusercontent...?s=&showtopic=703414&view=findpost&p=45272695
Damn, development has really boomed on this little tablet! Finally got it back after a few months (I sent it into Asus to repair it for me).
Stock ROM:
https://www.asus.com/ru/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (I can't get the English version to load, delete the /ru/ and you'll be redirected to the English site)
https://www.asus.com.cn/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (Chinese site)
==== REMEMBER TO DOWNLOAD THE CORRECT COUNTRY OR YOU'LL BE BRICKED) ====
https://yadi.sk/d/b1NMLXHBsNV8C (latest software for the worldwide model)
[http://4pda.ru/forum/index.php?showtopic=703414&st=320#entry50270292]
http://4pda.ru/forum/index.php?showtopic=703414&st=200#entry49389176 (Asus Flash Tool and stock ROM v4.8.2 WW [WorldWide])
Unlocking bootloader:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48200665 (use fastboot oem device-info to check if it's unlocked)
Root:
http://4pda.ru/forum/index.php?showtopic=690491&st=580#entry44778545 (KingRoot - you'll need a 4PDA.ru account to download this)
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (last section of the post)
CM13:
http://get.cm/?device=P024&type=nightly
https://vasy.ru/CM13/
http://forum.xda-developers.com/android/help/asus-zenpad-8-z380kl-custom-rom-t3370277
http://forum.xda-developers.com/android/development/kernel-asus-z380kl-p024-kcal2-t3405595 (Kernel)
Recovery:
https://vasy.ru/TWRP/P024/
http://4pda.ru/forum/index.php?showtopic=690491&st=1220#entry48094504 (TWRP 2.8.7.0)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051
Guides:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (this has a lot of instructions: root, recovery, boot partition restore, adb drivers etc.)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051 (this has a bunch of files, Resurrection Remix [I haven't tested it yet tho], and instructions on getting out a bootloop)
http://4pda.ru/forum/index.php?showtopic=690491&st=1640#entry49724823 (flashing stock software)
If you want to open the engineering menu, type " * # * # 4636 # * # * "
To boot into fastboot, restart/turn on the device and hold volume up. It'll pop you into a menu with three options.
To boot into recovery, from the fastboot screen (three options), use the volume buttons and navigate to the second option "factory reset" and hit power to confirm. It'll boot into recovery.
=====================================================================================
Recommended way to flash ROMs:
1) Download TWRP. Use adb to boot (NOT flash) into TWRP. Flash ROM there.
2) use KingRoot to root. Use Flashify to flash the ROM.
======================================================================================
If you want to go look up some more info or guides, go here:
http://4pda.ru/forum/index.php?act=...=rel&subforums=0&query=z380kl&forums=570&st=0
and use GTranslate to translate the page. The first page is the earliest posts with the keyword, the last page are the latest post.
please add these ROM's for this Device:
Ressurection Remix:
https://www.androidfilehost.com/?w=files&flid=121811
AICP 12.1:
https://www.androidfilehost.com/?w=files&flid=136181
The latest Official ROM P024 model:
http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.109506565.1670552787.1483182775
ZenPad 8 Z380KL Firmware: V5.9.0.0 (WW SKU version only)
Improved Item:
1. Update Google security patch
2. Support unlock tool
9008 brick info:
https://4pda.ru/forum/index.php?showtopic=643084
Pertaining to p024:
https://4pda.ru/forum/index.php?showtopic=643084&st=5740
https://4pda.ru/forum/index.php?showtopic=643084&st=3660 (page 179 - 180, 183 - 185 discusses the files needed to unbrick and how you would - CTRL + F Russ and read the people who quote him)
How I bricked: https://4pda.ru/forum/index.php?showtopic=703414&st=180#entry49329798
https://4pda.ru/forum/index.php?showtopic=690491&st=1420#entry48527044 (unbricking files - dead link though)
https://4pda.ru/forum/index.php?showtopic=703414&st=140 (discussing how to fix using the images from the dump)
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
ROMs
LineageOS: https://download.lineageos.org/P024
AICP: https://saki-sss.blogspot.com.by/2016/12/z380k-aicp-121.html
Resurrection Remix: https://androidfilehost.com/?w=files&flid=121811
(made by https://androidfilehost.com/?w=profile&uid=457095661767100043, found from http://andmem.blogspot.jp/2016/05/asus-zenpad-8-z380kl-root-rom.html#chapter-19) - abandoned?
seities said:
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Click to expand...
Click to collapse
probably not. I think it's only compatible with the SD 410.
xDark_ said:
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
Click to expand...
Click to collapse
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
jutphaas said:
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
Click to expand...
Click to collapse
I don't think unlocking the BL is necessary for flashing LOS. But yes, that's how I get into TWRP as well.
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
Can you still access fastboot, then at least you can flash twrp as described before in this thread and install from twrp lineageos p024 (lineage-14.1-20180105-nightly-P024-signed.zip) and Open gapps to get google playstore etc , select Arm, (not 64) then version 7.1, then Pico would work.
If you have twrp, you at least can still use your asus... I have found no way to flash original stock... stock must not be flashed from twrp.
Since you mention twrp already used, you can try: turn your device off, then press volume up then the bootloader menu comes, select 2: reset to enter twrp(where it says reset. if you had flashed twrp, that is how you can get into twrp) from there, install lineage os and gapps from micro sd card
My rom is MMB29M.WW_P024-V5.9.4-20170613
xDark_ said:
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
Click to expand...
Click to collapse
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
jutphaas said:
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
Click to expand...
Click to collapse
Yes it was. I flashed 15.2 on both stock and LOS. I've heard of some issues with 15.x so you can try .2 or 14.x.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
What error was given? What do you see when you connect it to a computer? What does "tablet locked" mean? Would help if you gave some pictures too.
I'm currently in the process of getting the RAW files/service ROMs for AFT but I don't have an ETA on when I'll be able to get that.
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
pucci2 said:
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
Click to expand...
Click to collapse
Does it respons to adb devices of fastboot devices in this stage?
no, it is not recognized
This is the new thread for Pie & 10 TWRP Recovery 3.3.1-x
Feature list:
- Pie stock ROMs are fully decryptable with this TWRP, either protected with secure startup or without :good: OREO encrypted userdata is not decryptable with 3.3 . However, if you're on encrypted oreo and update to pie stock, either via zip or kdz, crypto gets migrated and you're good to go in terms of access to your encrypted data with 3.3. So, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't really there anymore
- everything working: backup & restore even with encrypted userdata, no matter if it's from oreo or pie. If you restore a backup containing an encrypted userdata, you'll need to format userdata before, for crypto removal. But only when coming from another encrypted ROM, otherwise you can just restore, boot up (it will use the encryption settings you"ve set up) ; decryption; time & dat; mtp; adb; installing of ROMs and zips in general; themeable; .........
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you were forced to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings ≠ encryption pin/pw/pattern.)
- Time and date is shown correctly, independent of /data. This should work after a few boots of ROM and TWRP, TWRP needs to get the data once and later on it will then be calculated from persist's settings file.
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or diskdump. Same for OP partition (not present on USA and some others possibly)
- For removing encryption completely you can now do it as already known, via format userdata. Crypto is removed with it now again.
- busybox instead of toolbox/toybox, for better zip compatibility as it looks for now
- Pie 3.3.1-x: compiled with full 9.0 TWRP sources
- capable of installing every ROM and zip files
- some extra partitions (see below)
Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already too (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a backup of a ROM which had encrypted userdata, when you'd installed any other ROM in between. There are some points to remember when restoring, a little guide is available in old thread's third post (https://forum.xda-developers.com/showpost.php?p=77839649&postcount=3), and some tipps too.
Some instructions:
How to flash?
If starting fresh with an unmodified phone, this thread should help you installing it
When you already have TWRP installed, you can flash this recovery from within TWRP:
- Copy the new image file to one of your phone storages
- Tap "Install"
- Tap "Install image" button, located down right
- Locate your downloaded image and select it
- Select "recovery" from the list which shows up then
- Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
fastboot flash recovery <twrp-image-name.img>
How to (re)boot to TWRP?:
If your phone is rooted:
- Magisk has options to reboot to different targets like bootloader or recovery, but this menu is a little bit hidden: you can access it by starting Magisk.Manager, going to the "Module" menu, tapping on the three dot menu on the top right. Then select your target
- If a terminal emulator is installed, open it, type "su" followed by enter and type "reboot recovery"
- You can do the same with an adb shell, open a shell and type the commands from above, they're the same
- There also are apps for rebooting to recovery or other targets. Just search around in PlayStore
- The good old "button dance" When phone is powered off, press the volume down key and power button at the same time. When a first sign of life is seen on display, immediately release the power button, but just to instantly press it again. A menu will show, which wants you to do a factory reset: do it You have to confirm this two times, and afterwards TWRP will boot without performing a factory reset. TWRP is compiled with a flag which recognizes this procedure and hinders the bootloader to pass the command for factory resetting.
This time no optional version of TWRP is available, it's "one for all". This TWRP works for every V30 model, and only for them. I removed vendor partition too btw, there isn't any active development about that, so it's useless and only confuses ppl. DataImage function is available.
If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).
CHANGELOG:
February 23rd, 2020, TWRP 3.3.1-2:
- corrected blocksize for formatting crypto related partitions
- included timezone data, maybe helps some ppl with time still not showing correct; should speed up time calc
- used pre-compiled full mke2fs and e2fsdroid binaries
- enabled ntfs experimental support (rw in kernel, NTFS_3G flag in twrp / ofox)
- minimal tweaks
- enabled F2FS and NTFS support
January 1st, 2020, TWRP 3.3.1-1:
- Formatting problem solved, TWRP now removes crypto as it should when user initiates a data format
- small fixings like checkbox layout in restore menu
- Moved a LOGERR to LOGINFO: "E: Unable to decrypt FBE device". Couldn't get rid of it with our needed config...
Dec. 30th, 2019, TWRP 3.3.1-0:
- initial first version
- almost everything working like in 3.2 oreo TWRP
- Formatting your device doesn't remove crypto from disk, so a "fresh" (formatted) userdata gets disturbed by old security lock
DOWNLOADS:
Nougat, Oreo and Pie capable 3.3.1-0 TWRP, but decrypting support only for PIE (AOSP untested, stock confirmed):
Download links below (always the latest and newest only; one version for all):
File name: TWRP-JOAN-3312_2020-02-23.img
MD5sum: 2fd78a606b65274977f1cd63080d5f23
MAIN Download: MEGA, TWRP-JOAN-3312_2020-02-23.img
As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.
All you need to compile this yourself:
[url]https://github.com/seader/android_device_lge_joan-twrp[/url]
[url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
[url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
[url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with the stuff added. Pie is "encrypt-9.0" branch. omni's android-9.0 branch almost fully compatible, beside not being able to remove crypto (dirty hack, sry )
Much appreciated for your hard work. Twrp after all is the base for all customization
Thanks!
sure, enjoy it
btw, is there someone with oreo encrypted...? would be nice to know if it's decryptable with this new twrp too, and we therefore only need this one (and the other one can be archived...?)?
which is spoken very early, there's a lot left to do for 3.3 running really flawlessly. but, of course, this will be continued and being further worked on :good: starting right now xD
@ChazzMatt: it will take a while until wtf can be updated with this new one here. this is in an late beta stage, it works but has some quirks left. nothing that can destroy a phone but this twrp isn't fully working at this point of time and therefore not possible to use "in productive threads".
Everything works as well as the previous stable recovery.
I have tried:
1. backing up and restoring ROMs
2. Flashing, ROMs(stock pie and aosp Q), kernels and other mods.
Big thanks ??
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
kanehun said:
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
Click to expand...
Click to collapse
it needs some boots and reboots to recovery. after setting up everything it showed in twrp as it should :good: i'll add the tzdata back, a registry of all timezones, used for calculation of time, maybe it helps.
Time zone is beyond screwed up, 3 hours off without DST. Also, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
ldeveraux said:
, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
Click to expand...
Click to collapse
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash JohnFawkes Root Checker disabler,
Reformat data (where you type yes),
Reboot to recovery from within TWRP,
Flash Magisk AGAIN,
Reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
ChazzMatt said:
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash Root Checker disabler,
reformat data (where you type yes),
reboot to recovery from within TWRP,
flash Magisk AGAIN,
reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
Click to expand...
Click to collapse
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
:victory: thank you seadersn!
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
We needed new Encryption Disabler and we needed new Root Checker Disabler and we needed to flash Magisk twice.
The order of steps had to be rewritten besides new files.
Those have been in effect ever since EU H930 got Pie. Works on Oreo AND Pie bootloader unlocked KDZ.
drewcu said:
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
Click to expand...
Click to collapse
I'm on the TWRP flashable US99820H, so no clue
ChazzMatt said:
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
Those have been in effect ever since EU H930 got Pie.
Click to expand...
Click to collapse
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
drewcu said:
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
Click to expand...
Click to collapse
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
ChazzMatt said:
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
ChazzMatt said:
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
it's only formatting data switched to "fastboot -w" (reformats cache and data) or "fastboot erase userdata" (reformats data). both remove eventually present encryptions. everything else works like in the default wtf recovery :good: and that's really an enerving point... i want to simply format my userdata in twrp and not have to switch to fastboot...
formatting now works :good:
drewcu said:
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
Click to expand...
Click to collapse
it's the first: flashing image easily. only thing is, as described above, removing encryption requires fastboot. atm not possible to do this in recovery as usual. therefore nod suitable for wtf thread, but for anybody else, especially the ones who have pie installed and want to acces their data in twrp when encrypted. i'll test oreo decryption compatibility soon, zip needs downloading time lol
oreo decryption compatibility not given with 3.3 but: you can easily migrate from encrypted oreo via fw zip to pie, it adopts the storage encryption then and 3.3 is able to unlock :good: i've got a solution for 3.3 not being able to remove encryption: i keep a copyof 3.2.3-7 image on external sd and install it when formatting needed xD then back to 3.3 and good to go.
workaround no more needed, working now
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