I don't think so.The fastboot package method is so convenient. Just download, unzip, and run.
Why change to TWRP.....
is it difficult to prepare fastboot package ?
Nobody changed to TWRP. That's how it's always been and should be. The fastboot method was a workaround until the developers managed to find a solution to the A12 encryptions. Fastboot flashing is usually used in official firmware or for TWRP flashing. For everything else ...people use TWRP. I'm assuming you don't use root...or custom roms...hence the "hassle" with custom recoveries. You should learn how to use it...once you get the hang of it...it makes flashing and tinkering so much easier.The fastboot package method is so convenient. Just download, unzip, and run.
Why change to TWRP.....
is it difficult to prepare fastboot package ?
I may attempt to update again todayHey there, the mix 4 (odin) also has a working twrp build now, so updates could be delivered as recovery package now.
BTW anything new on Mix 4 front regarding notifications?
change to TWRP means there is no more fastboot ROM.Nobody changed to TWRP. That's how it's always been and should be. The fastboot method was a workaround until the developers managed to find a solution to the A12 encryptions. Fastboot flashing is usually used in official firmware or for TWRP flashing. For everything else ...people use TWRP. I'm assuming you don't use root...or custom roms...hence the "hassle" with custom recoveries. You should learn how to use it...once you get the hang of it...it makes flashing and tinkering so much easier.
Did you rename the magisk manager app?Hey, can't seem to manage to get root lately, tried fastbooting a few patches images in different weekelys and even flashing with twrp, am I'm doing soemthing wrong?
Actually packing a fastboot ROM takes 5 minutes less than packing a recovery ROM, due to compression, but we always prioritized OTA support and more brick-proof method of flashing. Fastboot is notoriously unreliable due to random things like USB port, cable, driver etc.The fastboot package method is so convenient. Just download, unzip, and run.
Why change to TWRP.....
is it difficult to prepare fastboot package ?
Hi @OrjonStarting from this update, if you choose the file right now (on 22.7.13) it will be installed automatically after decrypting the storage in TWRP. You don't need to choose the package in TWRP.
If so, maybe OTA update should be used for weekly beta ROMs also, the same as stable version.Actually packing a fastboot ROM takes 5 minutes less than packing a recovery ROM, due to compression, but we always prioritized OTA support and more brick-proof method of flashing. Fastboot is notoriously unreliable due to random things like USB port, cable, driver etc.
OTA is used...If so, maybe OTA update should be used for weekly beta ROMs also, the same as stable version.
After all, TWRP for k40p/11i came out just this week. Before that fastboot ROMs worked well (I guess) for more than one year .
Good news is that there are some rumors about that weekly ROMS will use OTA update in the future.
The same happened to me. I didn't receive any update via updater app. POCO F3. Brazil.
Same problem I am moving to 22.6.22 hoping to solvePoco F2 Pro here. For the third week in a row...video clips...audio clips and audio messages freeze when playing in any video player or in WhatsApp. Had to rollback again... I'm gonna wait for next week...Might have to go stable if this isn't fixed since weekly builds are basically done with for this device. It's been a good run....had a lot of fun with you guys. See you around
Simply dirty flash the old buildIs there any way to revert to an old version of .eu by rewriting a newer build? The new version has too many problems and I would like to switch to an old one...
POCO F2 Pro
That device doesn't have a recovery partition...device is in fastboot menu and when i use this cmd ( fastboot flash recovery twrp.img ) to flash twrp from #2 post i got this error :
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (196608 KB)...
OKAY [ 4.219s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 4.234s
fastboot boot twrp.img
That was that, the hidden manager. When I deleted it, started working. Thank you!Did you rename the magisk manager app?
No issues here, try to find and uninstall the hidden manager.
Regards
Sent from my Mi 11 Ultra.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation