Bootloop V11.0.6.0.QEJMIXM - Xiaomi Poco F1 Questions & Answers

Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers

iaintken said:
Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers
Click to expand...
Click to collapse
First of all remove any password or fingerprint you have on it. Also remove your google account. Backup your data. Now try flashing zips one by one. First flash the rom, boot it. Setup everything and reboot to recovery. Now flash magisk. If that doesn't work clean flash is your only way. Dirty flashing usually causes problems.

Use pitchblack recovery.
https://sourceforge.net/projects/pi...ium-2.9.1-20200411-0512-OFFICIAL.zip/download
And forget all common problems and encryption

callmebutcher101 said:
First of all remove any password or fingerprint you have on it. Also remove your google account. Backup your data. Now try flashing zips one by one. First flash the rom, boot it. Setup everything and reboot to recovery. Now flash magisk. If that doesn't work clean flash is your only way. Dirty flashing usually causes problems.
Click to expand...
Click to collapse
Thanks i will try ot

Mezoo23 said:
Use pitchblack recovery.
https://sourceforge.net/projects/pi...ium-2.9.1-20200411-0512-OFFICIAL.zip/download
And forget all common problems and encryption
Click to expand...
Click to collapse
Great will try it

iaintken said:
Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers
Click to expand...
Click to collapse
Goto twrp and advanced wipe and type yes it will format all data and then reboot your phone must be boot

varunsngh786 said:
Goto twrp and advanced wipe and type yes it will format all data and then reboot your phone must be boot
Click to expand...
Click to collapse
Thanks

Related

Latest Cyanogenmod doesn't work.

Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !

global beta 7.2.9

As the title says global beta 7.2.9 is out. Anyone installed it?
What about twrp and root compatibility?
http://en.miui.com/download-299.html here is the link
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
mysa50 said:
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
Click to expand...
Click to collapse
Can you confirm the process please? Is it just:
1. Download the recovery version of the update to the phone.
2. Boot to recovery (TWRP).
3. Install the update zip file.
4. Re install TWRP.
5. Reinstall the SuperSU zip.
6. Reboot to system.
Do we need additional reboots between the steps? Do we need to unroot before installing the update? Does it matter if the existing global beta ROM is several versions old?
Sorry for asking so many questions. I have not updated the ROM since unlocking the bootloader and installing TWRP/SuperSU several months ago and am worried about bricking my phone.
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
mysa50 said:
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
Click to expand...
Click to collapse
That's good to know. Just to confirm, the update could be applied "dirty" without a need to reinstall all apps and data afterwards?
I am still on global beta 6.11.3 (which is MM) and twrp 3.0.2.0. Is 7.2.9 based on nougat which would require the update of twrp? I had thought that the nougat beta was on a separate thread open to a closed group only...
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Delete
Bhatyasirr said:
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Click to expand...
Click to collapse
Look in the mi5 developement thread There is twrp section and in the 3rd post the op uploaded a unofficial release of twrp 3.0.3 but stable enough to be considered as official.
mysa50 said:
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Click to expand...
Click to collapse
Thanks a lot. Shall try over the weekend.
Few screenshots
mysa50 said:
Few screenshots
Click to expand...
Click to collapse
This is on light use, with heavy use (games,messages,phone calls) battery last a day from 6.30 am to midnight and still 10-15% and ~5h30 sot
That's good
how to revert back to miui from LOS ?
it didnt boot up
harrez said:
how to revert back to miui from LOS ?
it didnt boot up
Click to expand...
Click to collapse
Did you try fastboot rom from xiaomi site? Give a look in the Q&A thread you should find how to revert back to miui
chan200606 said:
Thanks a lot. Shall try over the weekend.
Click to expand...
Click to collapse
Finally did it, but not without scare - my Mi5 was stuck at the boot logo with "Bootloader unlock" message screen after flashing the recovery version of 7.2.9 update and reflashing TWRP 3.0.3.0. Luckily managed to get the phone into fastboot mode to flash the fastboot version of 7.2.9 and get the phone back on again. Finally reinstalled TWRP and boot into TWRP before rebooting to system successfully.
The key step I had forgotten was the booting into TWRP after its installation over the 7.2.9 stock recovery, which had led to the bootloop.
So I now have updated to 7.2.9. I do notice that the boot process takes quite a bit longer than 6.11.3 (design of nougat?), but once up, the phone feels as responsive as before.

[ROM] Mi 8 Miui 10 Global Beta 8.8.21

Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Update Miui 8.8.29:
link: http://www.fshare.vn/file/KQNTVM7UGGK9
link mega: https://mega.nz/#!Ws9mXYhb!fdDQrJWY-rAQEJSidTQRnI39E2xadWaXOMZl9rA1YGs
flash with twrp or ota with accout xiaomi beta test
Update link Miui 8.8.30 from Xiaomi:
http://bigota.d.miui.com/8.8.30/miui_MI8Global_8.8.30_1e559f40ab_8.1.zip
Ziarrr said:
update link Miui 8.9.4: https://mega.nz/#!S8k2WIzA!idZKZN2q1mlW5JkhtkAD38q-_HWWxbrBy_bgPUQG7RU
Click to expand...
Click to collapse
Ziarrr said:
Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Click to expand...
Click to collapse
Hello,
Is this a fastboot rom or recovery rom?
Ziarrr said:
Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Click to expand...
Click to collapse
hugge18 said:
Hello,
Is this a fastboot rom or recovery rom?
Click to expand...
Click to collapse
Recovery rom
Wow this download page is so bad. Any other page where we can download the rom? I only understand "ding dang dong" and have no idea where to click to download.
grootooter said:
Wow this download page is so bad. Any other page where we can download the rom? I only understand "ding dang dong" and have no idea where to click to download.
Click to expand...
Click to collapse
click at testview white and wait 30s
downloading.. ETA 16 hours...
Hello,
Do I need an authorized beta account?
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
alternative link: http://bigota.d.miui.com/8.8.21/miui_MI8Global_8.8.21_fc07cb2c7d_8.1.zip
You guys will need an authorized beta account unless you want to flash the ROM via TWRP Recovery
So, I updated without an authorized account though TWRP. As soon as I tried to reboot to system, it brought me back to TWRP.
I suppose I had to disable encryption all over again so I formatted Data, installed the update again and started to move the required zip for Magisk and encryption disabling back in the internal memory. During the installation the system rebooted (I didn't ask to, the first time it didn't reboot til I asked) and something crashed on the first screen pf MIUI 10. Then it decided to reboot again to recovery... and the TWRP was gone, I have the MIUI stock recovery again. Anyway, I formatted the data once more and the system is running without problems now.
tldr: Updated, data was deleted, TWRP is gone, system seems good
Fabrz said:
So, I updated without an authorized account though TWRP. As soon as I tried to reboot to system, it brought me back to TWRP.
I suppose I had to disable encryption all over again so I formatted Data, installed the update again and started to move the required zip for Magisk and encryption disabling back in the internal memory. During the installation the system rebooted (I didn't ask to, the first time it didn't reboot til I asked) and something crashed on the first screen pf MIUI 10. Then it decided to reboot again to recovery... and the TWRP was gone, I have the MIUI stock recovery again. Anyway, I formatted the data once more and the system is running without problems now.
tldr: Updated, data was deleted, TWRP is gone, system seems good
Click to expand...
Click to collapse
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Hello, i had buy a china Version. After waiting Time toi unlock i Do it ans install xiaomi.eu rom. Now i would like to install this global.
What Can i need to do?
Just wipe data ans Factory reset and flash thé rom with TWRP ans wipe dalvik cache when finish and reboot?
Do i need to use dm-verity for twrp and to doesn't brick phone or bootloop? Sorry for my english.
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
I had the 3.2.3 and global 8.8.7, same as you. Maybe you formatted data before flashing? That's the only thing I can think of.
Anyway, an happy feedback: Gps is working after few hours, that's what pushed me to try this update
Fabrz said:
I had the 3.2.3 and global 8.8.7, same as you. Maybe you formatted data before flashing? That's the only thing I can think of.
Anyway, an happy feedback: Gps is working after few hours, that's what pushed me to try this update
Click to expand...
Click to collapse
I didn't format data, I entered my lockscreen password into twrp the first time opened it, it said data was decrypted successfully and voilq, I was able to wipe and flash without any problem
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
do i still to wipe before flashing? im on global 8.8.7
vizard101 said:
do i still to wipe before flashing? im on global 8.8.7
Click to expand...
Click to collapse
Just wipe cache & dalvik cache. No need to wipe all
No fastboot version available ?
Best regards [emoji6]
Envoyé de mon MI 8 en utilisant Tapatalk
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
Do I need to unlock bootloader first before flash?
cheehong93 said:
Do I need to unlock bootloader first before flash?
Click to expand...
Click to collapse
Here the procedure for guys who haven't unlocked their bootloader
1.unlock bootloader
2.download and flash fastboot 8.8.7 Global Beta (closed beta)
3. Download and flash TWRP 3.2.3
4.download this recovery rom 8.8.21 and flash via Twrp (no need to wipe all but cache and dalvik)
8.8.23 is out since yesterday, do someone have the download link for the Mi 8?
Hello,
but the global beta miui 10 8.8.7 and more old global beta miui 10 8.8.21 ?

Can't install Magisk via TWRP

Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
ultramag69 said:
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
Click to expand...
Click to collapse
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
fajniejest said:
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
Click to expand...
Click to collapse
I am new on this forum (pocophone) and i seee how messed up it is. You should definitly use official twrp
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
tnsmani said:
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
Click to expand...
Click to collapse
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
fajniejest said:
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
Click to expand...
Click to collapse
Well Here is how i managed it to work. After i unlocked my bootloader i launched twrp and flashed beta magisk 19.0 (not latest anymore because 19.1 just today showed up) then i reminded that i forgot about DisableForceEncryption_Treble_v18.0.zip so i flashed iit and after it flashed again magisk 19.0, after reboot it everything was fine
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'flashboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
The command is 'fastboot boot twrp-<version>.img'
tnsmani said:
The command is 'fastboot boot twrp-<version>.img'
Click to expand...
Click to collapse
Thanks for the correction. I really don't know where I got flashboot from.
Cheers!
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
So, to make it clear (and to not brick my poco... ):
1. I should use TWRP image from this link --> https://twrp.me/xiaomi/xiaomipocophonef1.html...
2. ...and I don't need to replace my recovery - just booting it once (as You described) is enough.
3. I should flash Magisk's ZIP, not MagiskManager's ZIP or Magisk.apk
4. No more flashing, clearing data and other operations needed.
Am I right?
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
guhvanoh said:
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Click to expand...
Click to collapse
Big thanks! Finally dealt with it. So grateful for Your help. :victory:
Dearminder said:
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
Click to expand...
Click to collapse
Yes, I do. I've not tried it though...

DFE: Disable Forced Encryption (version numbers? treble?)

I successfully followed a guide to rooting my phone using TWRP, DisableForceEncryption (DFE), and Magisk. I now want to flash the latest (stock) ROM and re-apply DFE.
But there seem to be many versions of DFE available, some with/without version numbers, and some with/without the word "treble". And all are anonymous uploads on file-locker sites... :-/
What does "treble" mean? Does the DFE version number correspond to the Magisk version? I couldn't find a DEF v20 anywhere...
Who produces DFE -- is there an official website/source for the latest version(s)?
Cheers
For the latest MIUI Stock Rom you don't need dfe.
ConradB said:
For the latest MIUI Stock Rom you don't need dfe.
Click to expand...
Click to collapse
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
esuhl said:
Thanks. So, I can just just flash the latest ROM in TWRP, and... it won't overwrite TWRP, or lose root access, or cause any boot/encryption problems...?
Presumably I'd need to re-flash Magisk (after flashing the ROM) to retain root access...?
Will the phone be re-encrypted after updating to the latest stock ROM?
Click to expand...
Click to collapse
Which version is at the moment installed?
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
ConradB said:
Which version is at the moment installed?
Click to expand...
Click to collapse
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
YasuHamed said:
IF by latest stockrom you mean miui 10.3.8 then when i flashed the vendor firmware and didnt flash dfe, i was locked out and I lost all the data!
Click to expand...
Click to collapse
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
ConradB said:
In Miui Roms firmware and vendor are always integrated. There is IMHO no reason to flash only the vendor.
Click to expand...
Click to collapse
What do you mean by "flashing the vendor"...?
esuhl said:
I have MIUI 10.3.7.0 and want to upgrade to MIUI 10.3.8.0. The file I have downloaded is miui_POCOF1Global_V10.3.8.0.PEJMIXM_b5d72aa3ba_9.0.zip.
Yes -- all the guides I've read say that, having installed a custom recovery to root the device, all subsequent ROM updates need to have DFE (or some similar software) applied in order to prevent a boot-loop. This article gives a lot of information, although most of it goes over my head.
https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
What do you mean by "flashing the vendor"...?
Click to expand...
Click to collapse
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
the other guy flashed the vendor partition only, without a reason in miui and ran into encryption.
Here is a very good site "Globe Rom" https://mi-globe.com/miui-firmware-rom-builder-features/65/
Click on MIUI 9.6.27 and Change to MIUI 10.3.8.0 then create your own rom with including Magisk and other nice tools.
You can flash the Globe Rom according to the same instructions as above and Magisk is after the first reeboot
immediately active.
ConradB said:
First backup your data
Flash 10.3.8.0 dirty in twrp
wipe cache, dalvik cache in twrp
reboot the device (not rooted)
reboot into twrp and flash magisk 19.3 (i don´t know if the newer Versions will work with MIUI Rom)
reboot into system
thats it
Click to expand...
Click to collapse
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
Just it of curiosity what does it say about encryption under Settings -> Security?
Sent from my POCO F1 using XDA Labs
esuhl said:
Aha! It works! :laugh: Thank you so much! :victory:
So... now I've "disabled forced encryption", do I ever need to worry about it again? Can I flash a new version of TWRP, or use a custom ROM and just use Magisk to re-root?
Click to expand...
Click to collapse
If you flash Miui-Roms than no dfe needed.
If you flash a custom rom you should flash dfe.
guhvanoh said:
Just it of curiosity what does it say about encryption under Settings -> Security?
Click to expand...
Click to collapse
Settings -> "Security status" just shows:
Find device -- Off
Security update -- 2019-09-01
Google Play Protect > (Looks fine / No harmful apps found)
"Additional settings" -> Privacy -> "Encrypted & credentials" shows as "Encrypted".
However, the sub-option "Encrypt device using lock screen password" is turned off.
So just remember that if you want to move to another custom ROM you're going to have to format data. You're system is encrypted.
Sent from my POCO F1 using XDA Labs
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
YasuHamed said:
i am using this
Disable force Encryption treble + Magisk20.2.zip (JAN 2020)
Click to expand...
Click to collapse
I only found DFE uploaded by someone. How can I get latest version? Isn't here any thread of it?

Categories

Resources