Im stuck on poco boot screen and after few seconds it reboots to fastboot.
I did a twrp backup (system, vendor, data and boot) when everything was working but now after i try to restore the twrp backup, it still doesnt fix the problem.
before this, i flashed a new PE build and that had a boot loop for some reason.
wtf?
How does my twrp backup restore doesnt fix it ?
Do i have to miflash a fastboot rom ? is it the only fix for me now ?
You may find your solution here : https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004/page42
You can also install latest ROM and restore data only.
fmcheetah said:
You may find your solution here : https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004/page42
You can also install latest ROM and restore data only.
Click to expand...
Click to collapse
i dont have a firmware zip in my storage and i cant push it through adb because i didnt have debugging enabled. So i cant cleanflash because i dont have the firmware zip. Looks like i will need to use the mifash method.
flash the original Vendor image!
if you have flashed PE over MIUI10.2.x
, this mean you have used MODIFIED VENDOR IMAGE
poco supports Treble!
you cannot flash PE/ or any other custom rom over modified vendor image
take the latest vendor image from mirror.akhilnarang.me/MIUI/beryllium/
and flash it view twrp
and reboot
you wil lbe fine
i fixed the problem. I put firmware - vendor zip in sd card and flashed it through sd card. All good now. Thanks for trying to help my dumb ass.
i guess there might be some magisk module thats causing the bootloop after i flash a new build of rom . Maybe.
If thats the case. There's a flashable zip file that lets you disable a magisk module via TWRP.. ehehehe.. happened to me too. I flash gl tools via magisk systemless then it got stuck on pocofone f1 loading screen.. so i flashed that magisk module disabler.. hit some commands via TWRP TERMinal emu.. then it boot right away..
KabalLV said:
Im stuck on poco boot screen and after few seconds it reboots to fastboot.
I did a twrp backup (system, vendor, data and boot) when everything was working but now after i try to restore the twrp backup, it still doesnt fix the problem.
before this, i flashed a new PE build and that had a boot loop for some reason.
wtf?
Click to expand...
Click to collapse
Always uninstall Magisk before flashing new update if you are on official twrp cuz it doesn't support ota, update then reinstall it. If you have did so wipe encrypted internal storage , wait a bit it will boot .
aikhhk8 said:
Always uninstall Magisk before flashing new update if you are on official twrp cuz it doesn't support ota, update then reinstall it. If you have did so wipe encrypted internal storage , wait a bit it will boot .
Click to expand...
Click to collapse
Thanks. Didn't know about this.
Tell someone to call you, it was glitchy for me for the first 2-3 mins after the call but later works fine.
Related
Hey guys ,
I unlocked bootloader and flashed official twrp via fastboot . I successfully booted into twrp but when I click reboot my phone stuck on mi boot logo . I personally tried many thing to tackle this problem. But every time I got same thing . Can anyone solve this ?
Redwolf twrp is working fine .
Yes, happend the same to me, basically what's happening is that your phone can't decrypt itself in the boot.
What's the fix? Flash twrp, go into it
Then wipe EVERYTHING,even format.
That will be you new partitions (new encryption) in your phone.
Then with everything formated, plug your phone in twrp and copy whatever you want, and viola.
You're done, copy the rom you want to flash and will boot.
Please let me know when your phone is fixed.
Or you can just root your device
I had the same issue as you yesterday.
You can try lazyflasher to prevent bootloop
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
selemine said:
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
Click to expand...
Click to collapse
Just install the latest stock rom then install recovery and restore all the backed up partitions.
Now install magisk and reboot.
If that doesn't work (u get into fastboot again) then just flash the boot.img file via fastboot and then reboot.
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
selemine said:
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
Click to expand...
Click to collapse
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
selemine said:
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
Click to expand...
Click to collapse
Don't install magisk with the rom, just restore the data, flash the stock boot.img file and then reboot.
After boot uninstall the magisk manager app and reboot to recovery and then flash magisk again.
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Use Sharp by the old process! Dont have to use twrp made for Android 9
Is a problem with a new security patch, i have one only and functional..
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Return at the v10.xxx rom stock, and can i flash twrp or orange fox recovery, but not all the version can i flash new's rom android 10 i have the same problem about 1 month & this is my solution :crying:
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
SidRose01 said:
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
Click to expand...
Click to collapse
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
ovi2901 said:
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
Click to expand...
Click to collapse
I only used the files from that link. I did not read it anything. But Thanks, you pointed this out.
This means that the next time I wipe data in TWRP, then I should first enable "use rm -rf instead of formatting" in TWRP settings
I have never tried 'wipe data' on this phone. But I'll remember this the next time I 'wipe data'. Thanks, you just saved me.
I tried the latest twrp from the official website, but to no avail
Anyway, i installed PE+ with their official recovery, but now i can't flash magisk or any module
I'm wondering if it can be done (twrp or orange fox) without having to lose all my rom data, as i am alredy settled with my current ROM
Ps: when i tried i flashed at partition be, i have no clue as to why i didn't want to boot to recovery even tho the installer said it actually said it was flashed
Thanks in advance
Hugask said:
I tried the latest twrp from the official website, but to no avail
Anyway, i installed PE+ with their official recovery, but now i can't flash magisk or any module
I'm wondering if it can be done (twrp or orange fox) without having to lose all my rom data, as i am alredy settled with my current ROM
Ps: when i tried i flashed at partition be, i have no clue as to why i didn't want to boot to recovery even tho the installer said it actually said it was flashed
Thanks in advance
Click to expand...
Click to collapse
Yes you can flash any recovery without loosing any of your data
Check the current partition and flash recovery in that partition
ABHINAV-ACHHA said:
Yes you can flash any recovery without loosing any of your data
Check the current partition and flash recovery in that partition
Click to expand...
Click to collapse
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
SidRose01 said:
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
Click to expand...
Click to collapse
May be you are trying to boot with incompatible twrp or maybe you are twrp be corrupted
I had flashed twrp in september build also.
Try using 3.4.0.0 or 3.3.1.7
SidRose01 said:
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
Click to expand...
Click to collapse
Oh, so an update broke it
And yeah, you pretty much described the problem, that's exacly what i'm facing
Install TWRP correctly, but ignores me when i try to boot into it and goes to fastboot
ABHINAV-ACHHA said:
May be you are trying to boot with incompatible twrp or maybe you are twrp be corrupted
I had flashed twrp in september build also.
Try using 3.4.0.0 or 3.3.1.7
Click to expand...
Click to collapse
I don't think so, i made sure to download (latest) it from the oficial website, also, i'm not the only one having this issue
Hugask said:
Oh, so an update broke it
And yeah, you pretty much described the problem, that's exacly what i'm facing
Install TWRP correctly, but ignores me when i try to boot into it and goes to fastboot
I don't think so, i made sure to download (latest) it from the oficial website, also, i'm not the only one having this issue
Click to expand...
Click to collapse
Try using SHRP recovery it is also a great option
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img