Search results

Oh what kind of strange problems you have... But a bit strange this new TWRP 3.5.1 seems to me, too! It takes quite long till it asks for lock pattern, but anyway, backup and flashing work well. Gesendet von meinem Redmi K30 Pro mit Tapatalk

21.3.31 no problems for the first sight at lmi / Poco F2 Pro. Gesendet von meinem Redmi K30 Pro mit Tapatalk

@Spill Same here with Poco F2 Pro 8/256 - flawless flash of recent build + Magisk v22. Gesendet von meinem Redmi K30 Pro mit Tapatalk

@Iain_B Once, I played around, too - the way I described I could successfully duplicate one F2 to another [emoji6] Gesendet von meinem Redmi K30 Pro mit Tapatalk

Hmmm, usually, I never do. Simply start into TWRP, flash ROM, Magisk, clear cache & Dalvik, delete /data/system/package_cache, reboot into system and that's it... What did you do after the failed flash? Did you try to get back to the previous build? Were you able to flash back this one...

@Spill What if you try to mount all partitions before flashing? @fmcheetah Do you also have F2 Pro and could flash the recent build successfully to it? @Iain_B I only backup super, data and boot (for Magisk patching). All the rest I would get back by flashing back the previous ROM version...

@sylar I do it the same way like @Iain_B, but in addition, I copy all the TWRP backup to a USB OTG with USB C connector before flashing a new ROM version. Even if I completely loose access to my device's internal storage (for whatever reason) or need to format data, I won't loose my backup. In...

@slobodanboshkov Did you come from last build and also flashed Magisk v22? I heard that the new TWRP which came with last build may give errors while flashing and therefore, I'm still looking for someone who can tell me if there were any problems with Poco F2 Pro coming from last build to this...

Can you tell me which TWRP you installed it with? 3.5.1? Did you also install Magisk v22? Gesendet von meinem Redmi K30 Pro mit Tapatalk

Has anybody already tried upgrading lmi / Poco F2 Pro from last build with new 3.5.1 TWRP including Magisk v22? Have read that the new TWRP may give install errors, but I don't know which devices this problem may effect... Gesendet von meinem Redmi K30 Pro mit Tapatalk

Or could you simply take logo.img from the previous xiaomi.eu build? Gesendet von meinem Redmi K30 Pro mit Tapatalk

Could you please tell the reason why you wanna downgrade? Only because of the Redmi boot logo? Gesendet von meinem Redmi K30 Pro mit Tapatalk

Flawless upgrade to 21.3.10 with Poco F2 Pro. Only thing I have noticed so far is that boot logo has become Redmi instead of Poco, but doesn't matter to me. Gesendet von meinem Redmi K30 Pro mit Tapatalk

Same problem here since last 3 builds. Try to take original charger and cable! In my case that helped to get back turbo charging. I was using another cable and suddenly only got quick charging with it. Some time ago, turbo charging was available with exactly this non-original cable. When using a...

Yeah... You're right. In this case, same here. Gesendet von meinem Redmi K30 Pro mit Tapatalk

@gkalen No problems with search function here... Gesendet von meinem Redmi K30 Pro mit Tapatalk

Flawlessly updated my Poco F2 Pro / lmi incl. Magisk 22.0. Only issue was that it didn't ask for the PIN of my 2nd SIM after 1st boot. Toggling enable for this one did the trick. Gesendet von meinem Redmi K30 Pro mit Tapatalk

Same here. Happened only once with 21.2.3 and with recent build has not occurred yet (lmi). Gesendet von meinem Redmi K30 Pro mit Tapatalk

@emap85 Have never had this long lasting reboot problem with my F2 and only once this disappearing sound issue. But I've another: Since 21.2.4, charging the battery is extremely long lasting... With original Turbo Charger more than 2 hours, even if the device is switched off. With standard...

@dexterv @Blastboom Strice @gkalen From 9%, I have just had a full charge with original charger. No significantly noticable change in duration compared with my 65W GaN charger, which someone said about I should throw away. Now it seems a poor girl should be better off throwing away her mobile...