Can somebody help me please! - Xiaomi Poco F1 Questions & Answers

So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!

GGerniWhite said:
So hey! I successfully booted into the TWRP and used it to flash the DISABLEFORCEENCRYPTION file, right after. I decided to reboot to recovery (Cause I think that would be great just after you flash something in TWRP) but then after it finishes showing the pocophone booting screen rather than showing TWRP recovery. It showed the stock MIUI recovery! someone please help! I just finished flashing magisk and a custom rom by using the method of: Everytime I need to flash something using TWRP I would just open adb and fastboot boot recovery it again so that I could use the TWRP!
Thank you in advance!
Click to expand...
Click to collapse
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.

GGerniWhite said:
I decided to fix this problem after I flashed a rom cause I think I would run into future problems involving magisk and it's use of the TWRP recovery.
Click to expand...
Click to collapse
If you already have the ROM installed, use adb to flash TWRP and without booting flash Magisk and then boot to system. If you are on stock ROM, follow THIS.
For entering into TWRP, use the key combination of volume up + power buttons.
You can use the encryption compatible TWRP (search for it) instead of the official one.

Related

Change of custom kernel and installation of new recovery

Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
asl0501 said:
Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
Click to expand...
Click to collapse
To boot to recovery in the z5c you gotta pudg the volume up while booting over and over until you see the notification LED go red-yellow-orange
Once you're in recovery you could restore your old kernal if you made s bsckup
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
asl0501 said:
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
Click to expand...
Click to collapse
Try flash tool to push anew kernel maybe.I've never done it but from what j have read, download your firmware from xperia firmware and use flash tool to only flash kernel.
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
spikeyhair said:
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
Click to expand...
Click to collapse
Sorry to resurect this old thread. Can you or anyone provide a boot.img or how to go about creating one? I am in same situation (stuck at boot screen) and only have access to fastboot. Thanks.
For which version of rom? I can give you 32.0.A.200 boot.img and twrp recovery.
Are you sure you're clicking volume up when booting? It doesn't work when you hold the volume up button down.
If y'all go to the twrp thread there is a modified boot.IMG that allows booting to recovery now.

Flashing recovery - keeps reverting to stock after reboot

Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Do following, instead of flashing your recovery.
Use this method boot and flash Magisk. Reboot back to your system and install Flashify and install your choosen Recovery with it
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
in stock rom you need to flash magisk right after flashing twrp else it will get replaced by stock
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
What the post above says is correct. However, if you don't want Magisk, after flashing TWRP, reboot into recovery and then into system. You may retain TWRP. However, this doesn't work for everyone.
Hi all, I fixed the issue by completely wiping my phone via TWRP and clean flashing pixel experience ROM. After rebooting on pixel rom TWRP persists.
It appears that MIUI rom has something that keeps reverting it to stock MI-recovery.
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP once more. That's it! You have just overwritten the stock recovery and are now on TWRP!! Now you can reboot to system and TWRP will remain on your device. There's no need to flash Magisk etc if you want just TWRP and nothing else.
Rowdyy Ronnie said:
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP again. That's it! You have just overwritten the stock recovery and are now on TWRP!! There's no need to flash Magisk etc if you just want TWRP and nothing else.
Click to expand...
Click to collapse
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
jonske said:
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
Click to expand...
Click to collapse
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Rowdyy Ronnie said:
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Click to expand...
Click to collapse
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
jonske said:
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
Click to expand...
Click to collapse
How did you fix it?

Unofficial TWRP now available

Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914

Is there any latest stock boot img for Mi A3?

I accidently upgraded my phone to Android 10 11.0.14 ( prehaps ). I want to install TWRP on this phone, and I attempted to install it without flashing the boot img, and it caused to entirely be bricked and stuck on fastboot, and I did also attempt to change the slot, but ****** off. I tried using MiFlash, ****** off, reinstall, ****** off. I still kept my OnePlus rom and I succeed to install and normally use it, and it still remained TWRP. I installed the stock rom for it cuz Oxygen is so unstable, and I did, but the TWRP is lost. I reinstalled it, but it bricked, again. I entered TWRP, wipe all data, and enter again, but lost TWRP. I figured that I did miss flashing boot img, thanks to a thread I accidently read. And I also figured how stupid I was when I just did upgraded my phone to the latest version, and there is no boot img compatible to that version, and I did searched entire internet for it. I didnt try to flash the boot img of the early version cuz I am afraid it bricked again cuz of the compatibility. So when will I expect for a boot img file to flash TWRP and when can I download and use it? Or technically I dont need that boot img file and just simply change the slot and flash it? Ty.
try this boot img, its compatible with android 10 also twrp is already installed in the boot img.
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download (its for official android 10 rom)
then flash whatever rom you like then flash this zip, it will install shrp recover
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
gamernayeem said:
try this boot img, its compatible with android 10 also twrp is already installed in the boot img.
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download (its for official android 10 rom)
then flash whatever rom you like then flash this zip, it will install shrp recover
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Click to expand...
Click to collapse
Hang on. What do you mean by TWRP is already installed ? Does it mean that boot img file already contained TWRP or I do need to install it as a boot img to get the phone boot and work normally?
And btw, is installing SHRP Recovery an opinion or a must?
PNT5V said:
Hang on. What do you mean by TWRP is already installed ? Does it mean that boot img file already contained TWRP or I do need to install it as a boot img to get the phone boot and work normally?
And btw, is installing SHRP Recovery an opinion or a must?
Click to expand...
Click to collapse
the boot img already contain twrp, and the boot img should be able to boot your rom (stock android 10) and no shrp is not a must you can use any recovery you like, but if you want to keep your recovery after installing a rom you have to install the recovery installer zip
gamernayeem said:
the boot img already contain twrp, and the boot img should be able to boot your rom (stock android 10) and no shrp is not a must you can use any recovery you like, but if you want to keep your recovery after installing a rom you have to install the recovery installer zip
Click to expand...
Click to collapse
Boot img not working
oseraphaels said:
Boot img not working
Click to expand...
Click to collapse
Then you have to flash fastboot rom then flash this boot img
gamernayeem said:
Then you have to flash fastboot rom then flash this boot img
Click to expand...
Click to collapse
Thank you very much
It works
oseraphaels said:
Thank you very much
It works
Click to expand...
Click to collapse
No problemo
Big Thanks
gamernayeem said:
try this boot img, its compatible with android 10 also twrp is already installed in the boot img.
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download (its for official android 10 rom)
then flash whatever rom you like then flash this zip, it will install shrp recover
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Click to expand...
Click to collapse
I was also stuck like this so i flashed that boot img rebooted and everything came back.

Question I badly tampered my redmi note 10. Please Suggest me what can i do!

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

Categories

Resources