We know that Moto Z2 Force is not compatible with Treble. However, devs worked hard and some users got it working.
I use more than 10 hours, going and coming back, reseting, etc. and could not make it work.
Until now, I'm following the steps bellow and wish to discuss what we can do to get Treble in our device.
I've tested 4 to 5 A/B arm64 images from here and follow the general guidance from here.
I'm using XT1789-05 model (the International one, not branded) and this could be the cause of the issues.
I lost SIM card recognition in some "sucessful" attemps.
[AOSP ROM] - (tested with Magisk installed and without) and from [Stock]
Fastboot -w
Boot treble TWRP
Format data
Flash GSI image
Flash MindTheGapps.zip
Mount vendor
Flash bootSPLfix.zip
Mount vendor
Flash post 1 and post 2
Flash Permissiver
Mount vendor
Flash FBE disabler
Then format data again
Boot up
<Lost SIM card recognition>
…
I've posted the logs here: https://forum.xda-developers.com/showpost.php?p=77355827&postcount=49
The closer I could dig for some "error" are:
While flashing FBE Disabler
sed: /vendor/etc/*fstab*: No such file or directory
While flashing Trebble/POST-sGSI_2_v0.17.zip
...
sed: /vendor/build.prop: No such file or directory
grep: /vendor/manifest.xml: No such file or directory
grep: /vendor/etc/init/hw/*: No such file or directory
sed: -i requires an argument
sed: -i requires an argument
sed: /vendor/manifest.xml: No such file or directory
sed: /vendor/lib64/[email protected]_vendor.so: No such file or directory
sed: /vendor/lib64/[email protected]: No such file or directory
ls: /vendor/bin/hw/android.hardware.biometrics.fingerprint*: No such file or directory
Did you flash LineageOS before flashing the GSI image?
Marcowe said:
Did you flash LineageOS before flashing the GSI image?
Click to expand...
Click to collapse
No, thank you. I've learned to do that. But now, it's difficult to get root (https://forum.xda-developers.com/showpost.php?p=77391204&postcount=351).
Also, I'm facing a very strange thing that the screen changes color, got distorted. When using stock and AOSP ROMs, everything is normal...
Technical said:
No, thank you. I've learned to do that. But now, it's difficult to get root (https://forum.xda-developers.com/showpost.php?p=77391204&postcount=351).
Also, I'm facing a very strange thing that the screen changes color, got distorted. When using stock and AOSP ROMs, everything is normal...
Click to expand...
Click to collapse
But when you flash the sGSI image you will lose Lineage LOL
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
HACK3DANDR0ID said:
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
Click to expand...
Click to collapse
Never heard of a vbmeta.img. Where do I get this? Is it specific to this phone or is it generic?
fierogt42 said:
Never heard of a vbmeta.img. Where do I get this? Is it specific to this phone or is it generic?
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot
https://android.googlesource.com/platform/external/avb/+/master/README.md#Build-System-Integration
HACK3DANDR0ID said:
Just a suggestion to those still trying to get a GSI like, Android Q Generic GSI found here : https://developer.android.com/preview/gsi-release-notes#
We just got it to boot easier then a regular ROM would too.
-Fastboot boot TWRP
-Wipe Dalvik, Data and System.
-Flash the vbmeta.img
-Flash the system .img GSI via TWRP
-Factory Reset
-Reboot in BootLoader
-fastboot -w
-Start
-No LOS was NOT Necessary to boot this or any GSI build
Hopes this can help some of you out....
Click to expand...
Click to collapse
Can you post a complete tutorial for Moto Z2 force to install Android 10 with root access?
hi i am using note 5 ai 6/64 gb with stable chinese rom miui 10.2.1..now i want to shift to global rom..after unlocking bootloader what are the steps i should follow?
download the global rom version of 10.2.1 from
https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
if you boot is unlocked (finally) (after many days of waiting period)
put the 1.6gb rom in sdcard or otg
then using any good recovery ( i am using orange fox 8.3-2) https://sourceforge.net/projects/orangefox/files/whyred/
extract it and there will be recovery.img file
connact Rn5p in fastboot mode and boot recovery from minimal adb and fastboot window
fasboot boot (& drag drop recovery.img in the terminal window from extracted folder) and press enter ,
device will show MI logo, if your 1.6gb rom is in OTG drive then NOW is the time to connect you OTG before ORANGEFOX logo appear, otherwise it won't read properly.
for clean flash wipe /data /system /cache /internalstorage /delvik etc
then come back to install and from sdcard' or OTG flash the 1.6gb globalrom of 10.2.x once done
reboot atleast till MIUI setup screen
if you wana ROOT
boot back into recovery ( same steps) and
1. take BACKUP OF YOUR BOOT SECTOR, it may backup in your sdcard or OTG drive
and now flash the following
1. lazyflasher.zip (search for Redmi5 / note5A / Note5Pro on XDA) (its a small zip file)
2. flash magisk 17.1 (i dont recomend 18.0 since they have changed the script, and later no rcovery can extract RAMDISK folder from boot sector unless you RE-FLASH the whole rom.
first couple of boots may goto reboot but it should come to miui setup again.
if anything goes wrong,
reboot in to recovery again! and restore the BOOT sector, it will UNDO the lazyflash and Magisk
now, magisk 17x does say that it tries to disable DMvarity so try flashing ONLY MAGISK. for root.
During the last days I tried to enable encryption on my Mi Mix 2 without success.
I tried the following:
- boot to TWRP
- format data
- install latest Xiaomi.EU ROM
- flash forceencrypt.zip
- reboot to system
Result: No encryption. Enabling encryption in Miui options results in unbootable phone.
Then I tried to edit the fstab.qcom file under /system/vendor/etc. Here I failed, because I was not able to replace the original file with the TWRP file manager. Somehow, the system partition stayed read only.
Can someone here lend me a hand and tell me what I did wrong?
Gandhi70 said:
During the last days I tried to enable encryption on my Mi Mix 2 without success.
I tried the following:
- boot to TWRP
- format data
- install latest Xiaomi.EU ROM
- flash forceencrypt.zip
- reboot to system
Result: No encryption. Enabling encryption in Miui options results in unbootable phone.
Then I tried to edit the fstab.qcom file under /system/vendor/etc. Here I failed, because I was not able to replace the original file with the TWRP file manager. Somehow, the system partition stayed read only.
Can someone here lend me a hand and tell me what I did wrong?
Click to expand...
Click to collapse
MAY be You only did wrong becauser FCencrypt.zip you attached is , as what I can see, empty. Miss your modified Fstab file to be inside it (etc folder).
Without using the zip, as for test, in TWRP you drop your modified Fstab into sdcard folder and copy it to vendor/etc folder . Very easy manipulation.
Then reboot and that should perfectly give encryption with your own PW pin.
I did it and worked for me. Noob..
Now I make use of the zip tool after every rom update because system is replaced hence fstab reset-ted.
Got it working now! Mounting Vendor did the trick!
Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.
so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself
So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)