Flashing Guide for new Poco M3 buyers in 2021 - POCO M3 Questions & Answers

I have 2 poco m3 phones. The first 1 was bought in 2020 and there was no problems with flashing to another firmware.
The second one I bought in november 2021 and I faced many issues trying to flash. Xiaomi also use different touchscreen so custom firmware may not work.
This is what you should do if you have the newer problematic poco
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) INSTALLING RECOVERY
Use this Pitch Black Recovery. TWRP and Orange Fox doesnt work on this newer poco m3 hardware manufactured in 2021. The other recovery will just be a black screen. Extract the .img and flash using fastboot
[RECOVERY][UNOFFICIAL[joyeuse][v3.0.0] Pitch Black Recovery [07/08/2020]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about...
forum.xda-developers.com
UPGRADING TO ANDROID 11
If you dont upgrade to Android 11, you will face issue trying to flash, such as
"Failed to mount system_root"
"Failed to mount product. No such file or directory"
Normally TWRP can mount SYSTEM without issue but TWRP / OrangeFox is not supported with this new POCO hardware
This rom works fine with Pitch Black Recovery
xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11.zip
drive.google.com
FLASHING CUSTOM FIRMWARE
After you flash, no need to reboot, just flash your custom firmware. If you reboot to the MIUI above, it will just be stuck at MIUI logo.
Don't reboot to SYSTEM yet because touchscreen doesn't work
INSTALLING TOUCHSCREEN DRIVERS
The custom firmware doesn't support the newer touchscreen model used in POCO M3. So you need to install drivers. This can be done simply by flashing kernel in recovery which has newer touchscreen driver.
Use this kernel for POCO M3 2021: https://github.com/GZR-Kernels/Optimus_Drunk_Citrus/releases
Now, everything should work fine!

Hi man, I'm new to this device, I think that I have the problematic version of poco. I successfully managed to update to miui 12 eu and then install a custom but every time I make a clean install of any rom won't let me until I flash eu first. Is there a way to not to install eu first only flash directly any custom rom? Thanks in advance

Related

[Lollipop][5.0.2][ROM] for Moto G 2014 (2nd Gen) + Rooting guide

In this post, I’ll guide you to install Titan Prime ROM in your Moto G 2014 with rooting procedure. You might have already seen that the rooting methods depend on SuperSU flashable ZIPs and it may take a while to boot the phone once you root it. Keeping it in mind, let’s see how you can install Lollipop 5.0.2 ROM in your Moto G 2014 (2nd Gen).
Note: I have permission to redistribute this artilce without mentioning the owners' identitiy
Disclamer
HTML:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, BURNT LEDs,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications.
*/
Pre-requisites
You must have a custom recovery like TWRP. Get it from here if you don’t have already.
The ROMs are different for XT1063/64 version and XT1068/69 version. Download the appropriate version with respect to your phone model. Incorrect flashing may lead to signal lose.
Your bootloader must be unlocked.
Backup all important files in the internal memory and settings.
Charge your phone for at least 50% so the phone doesn’t die while flashing.
________________________________________________________________________________________________
Install Lollipop 5.0.2 ROM on Moto G 2014 (2nd Gen) – Titan Prime ROM
Download the latest build from here for XT1063/64 version and from here for XT1068/69 versions. (Pick the last one [most down one] )
Copy the ROM to your phone.
Boot your phone into recovery (TWRP preferred).
Do a backup of your current OS (Highly recommended).
Now do Factory Reset from TWRP (WIPE DALVIK/CACHE/DATA/FACTORY RESET).
Install the copied ROM file.
After successful flashing, wipe Cache and Dalvik from recovery itself.
Reboot system.
You have successfully flashed the Lollipop 5.0.2 ROM in your Moto G 2014. It should take up to 5 minutes to boot for the first time. The ROM is not pre-rooted as of now. So you’ve to root it manually. In case you need to root your Moto G 2014 running on Lollipop 5.0.2, follow the below procedure.
How to Root Moto G 2014 Running on Lollipop 5.0.2 – SuperSu
Download SuperSu beta v2.42 from here and copy it to your phone.
Boot your phone into TWRP recovery and install the SU zip.
After flashing, wipe Cache and Dalvik. Then reboot.
Boot may take up to 3-4 minutes after wiping the caches.
______________________________________________________________________
Screenshots of Titan Prime ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
__________________________________________________________________________
FAQ
Q. Is there any bug in rom, does wifi and dialer work fine?
A. NO Bugs!
You should point users to use last stable supersu and not that crap version that make our phones bootlooping
Sent from my XT1068 using XDA Free mobile app
I want to see screenshot of this rom

Galaxy A700FD bootloop after updating SuperSU

Hi there, I've been having problems with the Titanium Backup recently and tried some troubleshooting method such as unticking Mount namespace separation in SuperSU. They didn't work until i get to the point on updating the SuperSU from Play store. Then asked me to update the binary which i selected TWRP and it rebooted. After the installation from TWRP, it only boots to recovery. Tried turning off the phone and it still go to recovery even if i select reboot system.
Now i tried re-flashing the 'CF-Auto-Root-a7lte-a7ltexx-sma700fd.tar' via Odin3. It completed but then it's only boot looping. Sure i know it would reset multiple times but it has been more than 30mins doing like that over and over again. Tried to flash the TWRP again via Odin and wiped data/system/cache. And tried installing the Ressurection rom but it fails it gives me error "E:Error executing updater binary in zip '/external_sd/A7 Root and all/Roms/RessurectionRemix........"
Error flashing zip........
Then tried rebooting system. It said no OS installed proceed to reboot then saying device does not appeared to be rooted and asked me to install SuperSU which I did and it just restarted and still on boot loop....
Any help, please? TIA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happen when i try to flash the firmware that i downloaded from sammobile... please help.
On the recovery, whenever i try to reboot, it says No OS installed. Then SuperSU installation. Whenever i try to install a custom rom, it fails. Giving me error: error executing updater binary in zip...
gsmtec said:
flash latest version for you model, should work
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
which one? CF auto root? firmware? thanks for replying..
btw im flashing the latest ones. except the SuperSU which I will try later. But the No OS installe would be the problem i think?
gsmtec said:
flash latest 6.0.1 version for your region or for the one that phone came
Click to expand...
Click to collapse
not sure but when i clicked earlier it was all china versions. and on first click on something it selects other something like samsung camera. but now i was able to see the firmwares. guess the site have some bugs. imma try it.
there's no 6.0.1 on my region. only 5.0.2 and lower versions.. i take the 5.0.2?

[RECOVERY][TWRP]TeamWin Recovery Project for Samsung Galaxy J2 3G/SM-J200H

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS RECOVERY, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE​
About TWRP
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery
Current TWRP version- 3.1.1-0
Bug
Display output color.
How To Install
Via Custom Recovery
Download twrp.img from download section.
Boot into a old twrp then goto install and press on install images.
Find and select your downloaded twrp.img then click on recovery and swipe.
Now reboot recovery & enjoy
Via Rashr {Need Root for this method}
Download and install Rashr app From Play Store Or Download Rashr From Here
Download twrp.img file from download section and Put It In your Sdcard
Now Open Rashr And Grant For Root permission
Click on Recovery from storage and Select twrp.img file
then click Yes To Flash Recovery.
If You Get Sucsess then Hit Yes on the popup To Go in Recovery.
Downloads
TWRP-3.1.1-0
Thanks to
ashxy
Samankh
lzzy12
Md Naimur [email protected]Facebook
Hadi_K.t(t_t)t
[email protected]4pda.ru
[email protected]github
Device Tree- https://github.com/Parthib24/android_device_samsung_j23g
Its nice and functioning well
But it shows recovery is not seandroid enforcing
And I'm having yellow color theme instead of blue
WORKS
Thanks It works 100%
it shows recovery is not seandroid enforcing and I can't even reach twrp menu, reboots as normal.
Work!!!
Hi, I have a pre-rooted firmware J200HXXU0AIOB, but no TWRP installed. The last time I tried flashing TWRP (on a stock ROM) I bricked my device. It was stuck on the Samsung boot where the Logo is, with the message SEANDROID ENFORCING. So I flashed this pre-rooted ROM instead (J200HXXU0AIOB).
I understand there are risks that come with flashing custom roms and recoveries. But I would like to know if I flash my device, what are the steps I have to folllow in order to flash the custom recovery successfully with minimum risks of bricking the device again.
Any feedback would be much appreciated, thank you.
Download link not working

[PRA-LX1] Bricked AOSPExtended 9.0, bootloop, need downgrade to Stock Oreo or Nougat

Hi All,
I'm a Huawei P8Lite 2017 PRA-LX1 user and I've had Android 9.0 AOSPExtended ROM installed for months. Now I'd Like to downgrade to stock firmware (either Nougat or Marshmallow). I've followed a couple of guides and now i've rendered my phone unusable (bootloop). I have Askuccio's 3.2.2.-0 TWRP installed. The huawei firmware extractor method and flashing system, boot and recovery through fastboot seemed the best option. I can't seem to find the .zip firmware that has just the UPDATE file though.... anytime I try to extract UPDATE.APP it just gives me rubbish instead of the system, boot etc... sorry for posting here but I'm trying to do something about this now for couple of hours and im just frustrated. Is there anyone that could lead me through the process of downgrading that Custom Android 9.0 AOSPExtended to the stock Oreo or Nougat? I'm just really frustrated at this point so sorry. I've obviously searched through the forum to no avail... all the guides for un-bricking are for people that are on stock and not on 9.0 Pie. I can't even seem to get my phone connected to HiSuite (even after enabling ADB debugging). It just tries to install the software on my phone forever in a bootloop. Probably can't install cause I'm on that Android Pie. I could possibly just get away with a firmware that when I extract in Huawei Firmware Extractor that it will actually give me the system, boot etc. in it. I could try stock recovery too, but the guides talk about a "dload" folder and when I extract any firmware (update.zip, update_data.zip or HW_ru.zip) that "dload" folder is never there... The picture below is from a update.zip file. Let me know if I need the whole 3 files (update.zip, update_data_full_public.zip and update_full_PRA-L31HN_hw_ru.zip). Do I even need anything from the below image? As you can see there is no boot.img or recovery.img either..... Please advise.
Thanks for any suggestions in advance, I can provide more info if someone needs.
Thanks in Advance...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nevermind, I've finally figured it out. Found a site with firmwares that actually have the "dload" folder in them. Recovered my phone to Stock Oreo. Thread can be closed.

[ROM][LINEAGE-OS][11][UNOFFICIAL][KUNTAO]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS @Astridxx
THANKS MIKE
Download:-
LINEAGE_OS_KUNTAO
Known issues:-
• CAST
Kernel_source
Changelogs :-
• initial build
my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".
kocapomak said:
my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".
Click to expand...
Click to collapse
Try nikgapps
kocapomak said:
my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".
Click to expand...
Click to collapse
Settings > Kuntao Resurrected> Fp gestures
I found it now.
Settings-Kuntao Resurrected-Gestures-Fingerprint Gestures -- active
But it works sometimes, it doesn't works sometimes.
How is battery? Is it better than android 10?
What's is the new in new version of https://sourceforge.net/projects/roms5/files/lineage-18.1-20201229-UNOFFICIAL-kuntao.zip/download
I installed that rom. During the instalation I confirmed to update some los recovery. Then twrp was gone. I flashed twrp again, but every time I want to go to twrp, this los recovery comes up. I aslo couldnt flash gapps. Nickgapps are flashing, but system doesnt ask me to log into my Google account and I cant restore backup from Google cloud. Other version of gapps doesnt install as twrp says couldnt mount vendor.
The real issue for me now is dissapearing twrp.
@amdyss Uncheck the "Update Lineage Recovery" box when doing the setup. This fixes the issues of TWRP being replaced by the LOS
Recovery.
As for the gapps issue: For NikGApps you also need to flash the SetupWizard zip after the gapps one in order to get the account prompt.
I did a fresh install with uncheck - nothing happend, then I installed TWRP via adb again and installed some Pie rom. Then after setting up the rom I wanted to go to TWRP and install Magisk - and this LOS recovery still messes up normal TWRP.
Dont trust this build
simbanono said:
Dont trust this build
View attachment 5174713
Click to expand...
Click to collapse
then u make build
Look at the attachment (size of the rom) before you judge someone for making a joke.
simbanono said:
Look at the attachment (size of the rom) before you judge someone for making a joke.
Click to expand...
Click to collapse
So what?? I haven't manually put the size of ROM to be that, you will not have to trust lineageOS.
Stuck on boot animation plz help
bubka160195 said:
Stuck on boot animation plz help
Click to expand...
Click to collapse
Try the official version. It's much more up to date.
[ROM][11][OFFICIAL] LineageOS 18.1 for Lenovo P2
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
3volution3 said:
Try the official version. It's much more up to date.
[ROM][11][OFFICIAL] LineageOS 18.1 for Lenovo P2
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
Click to expand...
Click to collapse
I agree with You.
Furthermore the update are weekly as it was the case with LineageOS 17.1 Official.
Have a look at the changelog and You will also seen that the updates are more accurate and numerous

Categories

Resources