Related
Hi guys,
I was running twrp 3.0.1-0 with the unofficial linage build, however once I flashed the office build I seem to have gone to what looks like a stock recovery (when you try to flash anything you get a white circle with various colours sliding in and out of phase). Whilst the OS seems fine, I can't seem to flash anything anymore, gapps, supersu etc even via ADB sideload. It will appear to flash successfully, but nothing will have worked. I can boot into fastboot still but that won't let me flash TWRP either.
I read that revoking that the USB privileges would help but when I do that I don't get any pop-up asking for privileges, even after I wiped it and flashed it again, via the stock recovery.
To be honest I could live without TWRP but without gapps (play store) I can't do much.
Any advise or help would be most welcomed.
Thanks!
spotter300 said:
Hi guys,
I was running twrp 3.0.1-0 with the unofficial linage build, however once I flashed the office build I seem to have gone to what looks like a stock recovery (when you try to flash anything you get a white circle with various colours sliding in and out of phase). Whilst the OS seems fine, I can't seem to flash anything anymore, gapps, supersu etc even via ADB sideload. It will appear to flash successfully, but nothing will have worked. I can boot into fastboot still but that won't let me flash TWRP either.
I read that revoking that the USB privileges would help but when I do that I don't get any pop-up asking for privileges, even after I wiped it and flashed it again, via the stock recovery.
To be honest I could live without TWRP but without gapps (play store) I can't do much.
Any advise or help would be most welcomed.
Thanks!
Click to expand...
Click to collapse
Official LOS doesn't have TWRP built-in, and never had, as i remember.
Use opengapps app to install gapps. For root use SuperSU.
If you still need twrp, use kernel (boot.img) from unofficial one.
I would certainly like to root my Poco F1. However, after reading loads of topics, I'm still not sure of which way to choose, because I have a bit of a problem with the jargon.
I want the face unlock to be working
I want to get rid of MIUI and have clean Android (for example Smart Lock doesn't work with MIUI)
I want to use gestures to navigate through the phone
Hence, I am probably looking for a custom ROM?
If I understand correctly, I need to:
Unlock the bootloader, then flash TWRP, then flash the custom ROM, then flash Magisk... and everything is done (?)
If I want to revert to stock ROM, I will just wipe everything, am I right?
Would these custom ROMs do?
https://forum.xda-developers.com/poco-f1/development/rom-pixel-experience-t3857076
https://forum.xda-developers.com/poco-f1/development/rom-nitrogen-os-beta-t3857557
Thank you all!
You need to flash the appropriate vendor as well. You can find the list of vendor firmwares for download here:
downloads. akhilnarang .me/MIUI/beryllium/
Most custom roms require a specific requirement for vendor. I'd recommend flashing the latest vendor, it shouldn't cause issues.
Magisk flashing isn't a necessary step, unless you prefer root access. Make sure to back up your data because your phone will get encrypted on first boot and all your data will be lost, not to mention the data loss during bootloader unlock. You can use force encryption disabler to disable encryption. But note that you will have to flash the zip every time you flash a new ROM/vendor or else it will get encrypted again.
Also. Pixel experience is a good ROM for stock android experience, but I would recommend lineage OS unofficial over it because of the customisation it provides. I haven't used Nitrogen OS in a long time, so I cannot judge on it.
PS: don't forget gapps. Custom ROMs don't have gapps included.
Let's correct a few things in kishore1998's post. First since the OP needs to unlock his bootloader, when he does that he'll lose all data. OP, if your data is important, backup to an external source before you start. After unlocking you'll need a recovery as stated before. Next is flashing vendor/firmware. After that , flash the rom of your choice. In it's OP it should tell you whether you need gapps or not. PE doesn't require gapps. Reboot, make sure all is fine then go back into recovery and flash Magisk. I'm on vendor/firmware 9.5.6, PE-AOSP-20180507 & Magisk 19.1. NOTE: I don't use DFE nor do I need it. You only need DFE if you want an unencrypted fone. If you do flash DFE, everytime you flash vendor/firmware your _next_ step is to flash DFE. TWRP allows you to stack zips to flash so you'll choose vendor/firmware and DFE, then flash before doing rom and gapps if needed. See this link which has a useful FAQ.
HTH
Matt.Murdock said:
I would certainly like to root my Poco F1. However, after reading loads of topics, I'm still not sure of which way to choose, because I have a bit of a problem with the jargon.
I want the face unlock to be working
I want to get rid of MIUI and have clean Android (for example Smart Lock doesn't work with MIUI)
I want to use gestures to navigate through the phone
Hence, I am probably looking for a custom ROM?
If I understand correctly, I need to:
Unlock the bootloader, then flash TWRP, then flash the custom ROM, then flash Magisk... and everything is done (?)
If I want to revert to stock ROM, I will just wipe everything, am I right?
Would these custom ROMs do?
https://forum.xda-developers.com/poco-f1/development/rom-pixel-experience-t3857076
https://forum.xda-developers.com/poco-f1/development/rom-nitrogen-os-beta-t3857557
Thank you all!
Click to expand...
Click to collapse
hey bro . you should first unlock bootloader with miunlock .you need waiting 66 hours . after that download developer rom (pejmimx) rememeber that most be pejmimx, search in google and download the final version. install twrp with minimal adb if your poco didnt connect to your pc in fastboot mode you need to change your pc (just once time ) . flash data system cache davlik (you should have micro sd or conect flash memory with otg to your phone). install rom dev pejmimx. install your favorite custome rom . install magisk and done .(donot install oxygen os because that is ported from one plus 6t and have much bugs) my suggest is crdroid rom
Matt.Murdock said:
I would certainly like to root my Poco F1. However, after reading loads of topics, I'm still not sure of which way to choose, because I have a bit of a problem with the jargon.
I want the face unlock to be working
I want to get rid of MIUI and have clean Android (for example Smart Lock doesn't work with MIUI)
I want to use gestures to navigate through the phone
Hence, I am probably looking for a custom ROM?
If I understand correctly, I need to:
Unlock the bootloader, then flash TWRP, then flash the custom ROM, then flash Magisk... and everything is done (?)
If I want to revert to stock ROM, I will just wipe everything, am I right?
Would these custom ROMs do?
https://forum.xda-developers.com/poco-f1/development/rom-pixel-experience-t3857076
https://forum.xda-developers.com/poco-f1/development/rom-nitrogen-os-beta-t3857557
Thank you all!
Click to expand...
Click to collapse
There are a lot of guides here that describe the things you want.
Some checkpoints:
-Unlock your bootloader and install twrp (all personal data will be deleted)
-make a backup of your phone (when you backup check all partitions and images). This is your original system in case you want to go back. There's no particular reason to get more.
-install a custom ROM (crdroid that was suggested above is great imho) FOLLOW THE ROM'S INSTALLING INSTRUCTIONS TO THE COMMA.
-install nano-gapps and above if you want face unlock (pico and micro won't have it)
-flash magisk if you want root (don't forget to install magisk apk after flashing it)
-last but not least regardless of what's mentioned anywhere use official twrp and DON'T flash encryption disabler. It's just going to make your life harder without any benefits whatsoever.
Thank you, very helpful and assuring!
One more thing though - I often use dual boot of some apps. This is a Xiaomi-only feature; Does that mean with a different ROM (but for a Xiaomi device) I will lose this possibility?
I mainly just want to get rid of the MIUI ballast that interferes with the clean Android, so if there is a possibility to keep the ROM and delete MIUI, it would be maybe even better (?)
Hey guys, I'm trying to install LineageOS GSI (arm64 A/B) on my Mi A3 and seem to be having some trouble getting the GSI to actually boot successfully.
I have already done my research both on XDA and elsewhere online, yet most threads focused on the device seem to be of little to no use and/or filled with spam replies that only serve to confuse people looking into this.
A quick note regarding the aforementioned threads:
I don't mean to sound disrespectful to the community, but honestly, bashing somebody over why they'd rather install anything but your own fav piece of software is completely ridiculous.
Without further ado, my case goes as follows:
I'm starting fresh with the latest stock firmware, after having unlocked my bootloader ofc (critical too), I've successfully installed TWRP, wiped, installed the system image and yet after rebooting I'm just greeted with good ol' Fastboot, at which point I either directly flash the stock firmware and try again or wipe my data and whatnot (through TWRP, if reinstalled) and still end up with Fastboot.
Therefore, I have to ask you guys:
Has anyone previously successfully installed any GSI rom on the Mi A3?
Did you flash the system img while on stock firmware or a previously flashed custom rom (ie Pixel Experience)?
Is there any need for any special patch similar to the ones used for MIUI based Xiaomi phones?
Did you face any other issues while trying to flash a GSI?
My intention is to eventually install microG using Nanodroid.
Thanks for asking. I was trying to flash Havoc, crDroid and MSM-Xtended Android 10 GSIs but I can't boot the phone.
I have flashed lots of GSIs in the past, but this is really intriguing me, I can't boot on Mi A3. Wiping or formatting data does not solve, neither Permissiver or Disable Dm-verity zips did the job... :crying:
I successfully bootet the LineageOS GSI yesterday. I was not coming from stock though. I think this process should work assuming you already bootet to TWRP:
1. flash the GSI image to system partition using TWRP
2. flash the TWRP installer to keep your recovery
3. (not sure if needed) flash no fde patch
4. optional: flash some other stuff like Magisk and gapps
5. wipe data and dalvik
I think it rebooted to recovery on my first try but worked after flashing everything again. I probably made some mistake on my first attempt but just make sure to try again before giving up.
Also there's this tutorial but it's not at all what I did to get it working:
https://forum.xda-developers.com/mi-a3/how-to/tutorial-flash-custom-rom-mi-a3-t3977169
Hello
I have a poco f1 and I tried to flash from a week ago and here are the problems I faced.
1) I have shifted from latest miui to pixel experience plus from last week and the first problem I faced was when I tried to flash disable force encryption my phone didn't boot in the room it would get stuck on the google logo I did flash dfe while after flashing twrp to permanently install it but my device was still encrypted. Because of this, I have to remove all passwords before flashing anything.
2) After I tried PEP Rom I wanted to shift to evolution x and I downloaded the last built 4.7 android 10 official for poco f1 and flashed it in twrp and it was installed successfully but when I click on reboot system twrp showed no os installed. No one faced this problem but idk y I did.
3) My twrp doesn't show any portion to wipe vendor so I planned to shift on orange fox today and saw that as I install orange fox it would get stuck on orange fox logo and doesn't boot up.
Finally, I read this on some site
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
I never installed any custom kernel before installing PEP Rom on my device and people say that we have to flash lazy flaser what is this.
plz do explain every think in detail as i tried asking many YouTubers non of them responded.
Thank You
When all fails. The only solution is to flash miui stock rom.
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