Phone boots only into recovery, how to fix? - Xiaomi Poco X3 NFC Questions & Answers

I've flashed 3.4.0-15][surya] recovery then flashed lineageos and havoc but the wifi wasn t working so I tried to flash the original rom but it just boots into recovery
Please help guys?

Bozdo said:
I've flashed 3.4.0-15][surya] recovery then flashed lineageos and havoc but the wifi wasn t working so I tried to flash the original rom but it just boots into recovery
Please help guys?
Click to expand...
Click to collapse
Most probable you did not Format data after you flashed the stock ROM. Download the fastboot of the stock ROM you wanna use, unzip it and flash it with MiFlash tool.

Alin45 said:
Most probable you did not Format data after you flashed the stock ROM. Download the fastboot of the stock ROM you wanna use, unzip it and flash it with MiFlash tool.
Click to expand...
Click to collapse
I did wipe system folder, cache and dalvik folders

Bozdo said:
I did wipe system folder, cache and dalvik folders
Click to expand...
Click to collapse
Nope...format data is needed (this one when you have to type ”yes”)

Even though I get this message error the phone booted the rom, weird...
So can I try flashing other roms like lineageos using this tool or do I need twrp? Could the wifi error on the other roms be from not properly formatting the folders?
View attachment 5128525

Bozdo said:
Even though I get this message error the phone booted the rom, weird...
So can I try flashing other roms like lineageos using this tool or do I need twrp? Could the wifi error on the other roms be from not properly formatting the folders?
View attachment 5128525
Click to expand...
Click to collapse
Yeah, you got that error because you did not lock your bootloader, but ROM will work just fine. You can use MiFlash for stock ROMs only.
The Wi-Fi problems are usually related by flashing the custom ROM from the wrong stock firmware and vendor version. Just read the first page (OP) of the ROM you wanna flash and see what version of the stock ROM is needed (most of them ask for 12.0.3.0 version, but some ask for 12.0.2.0 or 12.0.4.0).

Alin45 said:
Yeah, you got that error because you did not lock your bootloader, but ROM will work just fine
Click to expand...
Click to collapse
Say I lock the bootloader, but what if I want to unlock after? will I have to wait 7 days again?

Bozdo said:
Say I lock the bootloader, but what if I want to unlock after? will I have to wait 7 days again?
Click to expand...
Click to collapse
If you already unlock. Then flash with fastboot, phone will lock again. And you can instant unlock again because your Mi Account have permission to unlock your device.

Related

XT1039 bootloop after flashing CM13

Hi,
XT1039: bootloader unlocked, rooted, stock rom 4.4.4
TO: nightly
Flashed 4118 bootloader, as detailed in http://forum.xda-developers.com/moto...tions-t2996087
It was successful.
Followed https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine
unlocked bootloader
installed cm-recovery from here: https://download.cyanogenmod.org/?type=nightly&device=peregrine
tried to flash cm, got a bootloader error,
followed this guide: http://forum.xda-developers.com/showpost.php?p=59520890&postcount=233
Now using bootloader 411A
flashed cm-13.0-20160121-NIGHTLY-peregrine.zip
from here: https://download.cyanogenmod.org/?type=nightly&device=peregrine
now the phone is stuck at the boot screen.
So I flashed twrp recovery, successful and reflashed cm-13.0-20160121-NIGHTLY-peregrine.zip
I tried several different guides that included all sorts of cache deletion and format orders but the result is still the same
(I am not using an sdcard but only the internal storage.)
After rebooting, the phone is stuck on the Cyanogenmod boot icon (blinking cat face) since past half hour.
Please guide how to debug/recover.
fastboot and recovery are working
Thanks,
[edit:]
The cm-13.0-20160121-NIGHTLY-peregrine.zip was transferred by mounting the internal storage on the PC and copying it manually. Just in case this matters
Hi,
Try to flash stock rom from here : http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
satanas17 said:
Hi,
Try to flash stock rom from here : http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Click to expand...
Click to collapse
Thanks for the reply, but the goal is to get cyanogenmod on my phone. How does the stock rom help me with that??
Just for testing, I have installed the stock rom to see if it works and it does. I now have a Motorola Android 5.1 on my phone. But thats not what I wanted.
Anyone having any idea how to make cyanogenmod work?
karstenme said:
Thanks for the reply, but the goal is to get cyanogenmod on my phone. How does the stock rom help me with that??
Click to expand...
Click to collapse
Just to restoring a kernel on it...after restoring one, go to TWRP, make your wipes and flash again your CM
satanas17 said:
Just to restoring a kernel on it...after restoring one, go to TWRP, make your wipes and flash again your CM
Click to expand...
Click to collapse
WOW Thank you very much, its working
Maybe you can also explain to my why installing the custom rom mattered, since I wiped everything before installing cm again, I would assume there is nothing of the stock rom left on the device.
karstenme said:
WOW Thank you very much, its working
Click to expand...
Click to collapse
U're welcome
karstenme said:
Maybe you can also explain to my why installing the custom rom mattered, since I wiped everything before installing cm again, I would assume there is nothing of the stock rom left on the device.
Click to expand...
Click to collapse
Not really able to explain...sometimes sh*t happens...
But this procedure works almost every time.
Surely due to your bootloader error after your first flash with CM recovery...something was broken...
Most important, now, it's working...Enjoy
I install cm but google play is not working and sallular data also not working.. Plz any one help me please..

Help!My OPO cannot flash ROM with recovery.

The Screenshot is below. I got stuck in the H2OS 2.0 so I flash the cos12 to save it from bricking. Then I flash the TWRP. When I wanted to flash a CM13,the problem in the screenshot occurred. Need some Help here.
Help,PLZ
I don't have another phone.I gotta fix this as soon as possible in case I don't miss any important phone calls. plz. Somebody gives me a hand.
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
mustang_ssc said:
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
Click to expand...
Click to collapse
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
SimonYJB said:
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
Click to expand...
Click to collapse
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
mustang_ssc said:
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
Click to expand...
Click to collapse
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
SimonYJB said:
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
Click to expand...
Click to collapse
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
mustang_ssc said:
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
Click to expand...
Click to collapse
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
SimonYJB said:
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
Click to expand...
Click to collapse
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
mustang_ssc said:
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
Click to expand...
Click to collapse
Thank you very much. I really appreciate it. I'll try as you say.Hope the issues can be solved.:good:

strange! custom rom bootloops - coming from miui10.0.0.2

from MOKEE
i flashed miui10.0.0.2
the first attempt for magisk failed
but then second attempt magisk flashed successfully
I rebooted expecting miui10.0.0.2 but got in to booloops
now !
every custom rom is also giving me bootloops...
i tried RR and crdroid of Sept2018 build....
only latest mokee is working!
what is this? what am i missing?
after flashing mokee 20181103 813
i am bound to mokee only
i tried flashing
miui10.002 / miui10.001 / miui9.6.7 (all in antirollback 4)
and
I also tried flashing
crdroid4.8 / crdroid 5.0 / RR6.2 / MSM Extended
all give STRANGE BOOTLOOPS!!!!!
only mokee works now .... i tried previous version of mokee , thats working also!
but whenever i flash any thing accept mokee.. (even miui) i go in to bootloops
what seems to be wrong?
partition corrupt? if yes then how to fix this?
i wana try crdroid... but i always endup in bootloops
How did you flashed MIUI ROM ?? Recovery or fastboot method ?? I suggest you to flash fastboot ROM
Try LineageOs 15.1 official. İf it works that means the problem is about encryption.
SunilSuni said:
How did you flashed MIUI ROM ?? Recovery or fastboot method ?? I suggest you to flash fastboot ROM
Click to expand...
Click to collapse
i flashed miui via Recovery! , i usually keep skipping roms via twrp and has even flashed 9.65/9.67/10.0.01 MIUI with twrp only and everytime it works just fine untill today
MOKEE keeps releasing xperimental images, on daily bases, i had been on MOKEE since 21oct2018 and today after 3/11/2018 patch, i decided to try MIUI10
I don't have authorised account to flash edl...
can i flash EDL rom via Qualcom (Qloader? )
also feel reluctant to remove back cover.... but i wana what has happend?
i will be flashing persist.img .. just incase...
fnldstntn said:
Try LineageOs 15.1 official. İf it works that means the problem is about encryption.
Click to expand...
Click to collapse
and if yes then how one can fix encryption? / EDL flashing ?
i am gonna flash linageOS15.1
YasuHamed said:
and if yes then how one can fix encryption? / EDL flashing ?
i am gonna flash linageOS15.1
Click to expand...
Click to collapse
You will have to decrypt your device with TWRP.
fnldstntn said:
You will have to decrypt your device with TWRP.
Click to expand...
Click to collapse
i flashed lineage15.1, it didnt go in to bootloops but stuck on the main screen for forever,
went back to recovery, (redwolf) via (fastboot boot recovery )
this time it allowed me to
format and change /data /system partition to and fro ( ext4 to exFAT_) and back to ext4
now flashed CRDROID4.7
and it WORKED
YasuHamed said:
i flashed miui via Recovery! , i usually keep skipping roms via twrp and has even flashed 9.65/9.67/10.0.01 MIUI with twrp only and everytime it works just fine untill today
MOKEE keeps releasing xperimental images, on daily bases, i had been on MOKEE since 21oct2018 and today after 3/11/2018 patch, i decided to try MIUI10
I don't have authorised account to flash edl...
can i flash EDL rom via Qualcom (Qloader? )
also feel reluctant to remove back cover.... but i wana what has happend?
i will be flashing persist.img .. just incase...
Click to expand...
Click to collapse
You don't need authorised account to flash fastboot ROM. Just download fastboot ROM and flash it using MiFlash (this method requires bootloader unlock)
Authorised account is only for flashing fastboot ROM on bricked device
YasuHamed said:
i flashed lineage15.1, it didnt go in to bootloops but stuck on the main screen for forever,
went back to recovery, (redwolf) via (fastboot boot recovery )
this time it allowed me to
format and change /data /system partition to and fro ( ext4 to exFAT_) and back to ext4
now flashed CRDROID4.7
and it WORKED
Click to expand...
Click to collapse
Lineage os requires encryption.so you got stuck at logo

Bricked my Poco F2 Pro

Hi. Recently I've been trying to flash Xiaomi.eu. however, it didn't have success. My bootloader is unlocked, and I flashed the Chinese TWRP to flash it. However, upon flashing it I always had an error about my cache being corrupted or an odm error. However, I did manage to boot into xiaomi.eu before, but it randomly stopped working. Tried to flash stock as well, but everytime I do, it stops at the cache again and always gives me an error.
I'm fully defeated at this point and I haven't been able to boot into anything since. I've tried everything and that's why I'm here.
I hope anyone can help me.
Thank you.
PompoenJeroen said:
Hi. Recently I've been trying to flash Xiaomi.eu. however, it didn't have success. My bootloader is unlocked, and I flashed the Chinese TWRP to flash it. However, upon flashing it I always had an error about my cache being corrupted or an odm error. However, I did manage to boot into xiaomi.eu before, but it randomly stopped working. Tried to flash stock as well, but everytime I do, it stops at the cache again and always gives me an error.
I'm fully defeated at this point and I haven't been able to boot into anything since. I've tried everything and that's why I'm here.
I hope anyone can help me.
Thank you.
Click to expand...
Click to collapse
how did you try to flash stock rom?
try with another usb cable.
NOSS8 said:
how did you try to flash stock rom?
try with another usb cable.
Click to expand...
Click to collapse
I tried to flash stock ROM via MiFlash. Most likely the latest build. I will try with another USB cable now.
Screenshot with error
I've instead tried to unbrick it with XiaomiToolV2. However, I'm still getting the same error, just in a different way. Does anyone know how to fix this? I've had this multiple times without success.
https://imgur.com/lSGJydI
PompoenJeroen said:
I tried to flash stock ROM via MiFlash. Most likely the latest build. I will try with another USB cable now.
Click to expand...
Click to collapse
Use miflash,put the file on C:,rename the file (ex:12.04EU),Flash the rom that was on the phone when you got it,select clean all with miflash.
MIFLASH https://xiaomiflashtool.com/
NOSS8 said:
Use miflash,put the file on C:,rename the file (ex:12.04EU),Flash the rom that was on the phone when you got it,select clean all with miflash.
MIFLASH https://xiaomiflashtool.com/
Click to expand...
Click to collapse
i have the same problem and ive tried the things youve said and it finishes in about a second i think ive done something wrong right?
What rom did you have?
Which rom do you want to install?
NOSS8 said:
What rom did you have?
Which rom do you want to install?
Click to expand...
Click to collapse
both european i think i bougt if of a dutch site idk if that helps
install TWRP(chinesse)format data only->reboot system done if not download ZIP recovery(https://xiaomifirmwareupdater.com/archive/miui/lmi/ )and flash it with TWRP.
NOSS8 said:
install TWRP(chinesse)format data only->reboot system done if not download ZIP recovery(https://xiaomifirmwareupdater.com/archive/miui/lmi/ )and flash it with TWRP.
Click to expand...
Click to collapse
where do i find chinese twrp?
i always get
failed to mount '/odm' (No such device)
Mikxx said:
where do i find chinese twrp?
Click to expand...
Click to collapse
here"https://drive.google.com/drive/folders/10_nqA89FmAXNseHmLOcTeDSzfkPMn5hQ"
NOSS8 said:
here"https://drive.google.com/drive/folders/10_nqA89FmAXNseHmLOcTeDSzfkPMn5hQ"
Click to expand...
Click to collapse
you are a hero my phone works again
NOSS8 said:
here"https://drive.google.com/drive/folders/10_nqA89FmAXNseHmLOcTeDSzfkPMn5hQ"
Click to expand...
Click to collapse
please give me this recovery again!
dingila said:
please give me this recovery again!
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=318240

[HELP] After Updated to MIUI 12.5.1 Flashed TWRP and Magisk >> Resulted Bootloop

Buddies, please urgent help. I flashed V12.5.1.0.RJKMIXM without problem and it was working. I had lost twrp and magisk and thought it won't be a problem to flash them back. By a silly mind I flashed twrp and magisk 21.4.zip again. Now The phone doesn't boot and bootloop after MIUI screen. I have very important data on my phone and I can't see data partition. From twrp, When I click select storage, internal Storage (0.00 MB) seems 0 MB. I never clicked on wipe data option after flashing magisk. I only wiped dalvik and cache.
How can I save my data? It seems there is no fastboot rom to flash. I am downloading recovery ROM again to give it a try. I hope it saves me. Please give me suggestions if you have any.
thanks beforehand... :'(
Bogazicili90 said:
Buddies, please urgent help. I flashed V12.5.1.0.RJKMIXM without problem and it was working. I had lost twrp and magisk and thought it won't be a problem to flash them back. By a silly mind I flashed twrp and magisk 21.4.zip again. Now The phone doesn't boot and bootloop after MIUI screen. I have very important data on my phone and I can't see data partition. From twrp, When I click select storage, internal Storage (0.00 MB) seems 0 MB. I never clicked on wipe data option after flashing magisk. I only wiped dalvik and cache.
How can I save my data? It seems there is no fastboot rom to flash. I am downloading recovery ROM again to give it a try. I hope it saves me. Please give me suggestions if you have any.
thanks beforehand... :'(
Click to expand...
Click to collapse
Which Twrp did you use?
if you flash a fastboot rom your data is lost.
NOSS8 said:
Which Twrp did you use?
if you flash a fastboot rom your data is lost.
Click to expand...
Click to collapse
I used this: recovery-TWRP-3.4.2B-1206-REDMI_K30PRO-CN-wzsx150
I was on Android 10 and MIUI 12.0.4 ROM before flashing MIUI 12.5.1
YESSSSSSSSSSSSSSSSSSSSSSSSSSS I FIXED IT I'M SO HAPPY!!! THANK YOU FOR YOUR RESPONSE.!!!
I reflashed recovery ROM and the phone booted normally thanks to Allah.
What should I do to get TWRP and Magisk Root back again? Or is it possible at that moment?
Bogazicili90 said:
I reflashed recovery ROM and the phone booted normally thanks to Allah.
What should I do to get TWRP and Magisk Root back again? Or is it possible at that moment?
Click to expand...
Click to collapse
Do a backup
flash Twrp and reboot Twrp then flash Magisk.(delete all lockscreen security before)
NOSS8 said:
Do a backup
flash Twrp and reboot Twrp then flash Magisk.
Click to expand...
Click to collapse
How to back up before flashing TWRP?
Bogazicili90 said:
How to back up before flashing TWRP?
Click to expand...
Click to collapse
follow the link above.
Why don't you try the Xiaomi Eu roms which are much better than the stock roms?
NOSS8 said:
Why don't you try the Xiaomi Eu roms which are much better than the stock roms?
Click to expand...
Click to collapse
I tried EU ROM when I first bought the device but the ROM had a few problems on voice calls. Then I returned Stock ROM again and using it as a daily user.
Bogazicili90 said:
I tried EU ROM when I first bought the device but the ROM had a few problems on voice calls. Then I returned Stock ROM again and using it as a daily user.
Click to expand...
Click to collapse
I have been using Xiaomi EU rom for a long time and have never had this problem which can be due to Twrp and / or forgetting to format the data.
NOSS8 said:
I have been using Xiaomi EU rom for a long time and have never had this problem which can be due to Twrp and / or forgetting to format the data.
Click to expand...
Click to collapse
Yes maybe I faced the issue by my mistake... By the way I removed all screen locks and then flashed twrp and rebooted twrp again. But I can't see internal storage again after rebooting twrp. I think There is a problem with twrp on Android 11.
Bogazicili90 said:
Yes maybe I faced the issue by my mistake... By the way I removed all screen locks and then flashed twrp and rebooted twrp again. But I can't see internal storage again after rebooting twrp. I think There is a problem with twrp on Android 11.
Click to expand...
Click to collapse
V12.5.1.0.RJKMIXM is an beta stable.
Maybe flashed the last fastboot rom(V12.2.6.0.RJKMIXM) with Miflash to restore the phone correctly and then the V12.5.1.0.RJKMIXM.
NOSS8 said:
V12.5.1.0.RJKMIXM is an beta stable.
Maybe flashed the last fastboot rom(V12.2.6.0.RJKMIXM) with Miflash to restore the phone correctly and then the V12.5.1.0.RJKMIXM.
Click to expand...
Click to collapse
I was on 12.0.4 before this ROM. I searched on poco forums and everybody is experiencing the same problem after TWRP install. It seems twrp isn't compatible with A11. I found another twrp. I will try it now. It is twrp-3.5.2-0-lmi-manuelbianco.img
Bogazicili90 said:
I was on 12.0.4 before this ROM. I searched on poco forums and everybody is experiencing the same problem after TWRP install. It seems twrp isn't compatible with A11. I found another twrp. I will try it now. It is twrp-3.5.2-0-lmi-manuelbianco.img
Click to expand...
Click to collapse
Twrp work on android 11 but du to the dynamics partitions you cant have acces to the system.
Users have lot of problems with this twrp .
Why rooting?
NOSS8 said:
Twrp work on android 11 but du to the dynamics partitions you cant have acces to the system.
Users have lot of problems with this twrp .
Why rooting?
Click to expand...
Click to collapse
Yes as you said all twrp versions are the same. It is due to A11. I will try to root the device with boot.img.
I need root for backing up apps with swift backup app. I also need it for some apps.
I realized that I can see internal storage data without formatting the phone. I just changed TWRP from ManuelBlanco's to LR Team's via fastboot and the internal storage became visible. I think this is easier than formatting the whole phone every time changing ROM.
However Magisk pathched boot.img doesn't work. Phone bootloops with that boot. I reflashed original boot.img I don't know why Magisk doesn't work properly...
Bogazicili90 said:
I reflashed recovery ROM and the phone booted normally thanks to Allah.
What should I do to get TWRP and Magisk Root back again? Or is it possible at that moment?
Click to expand...
Click to collapse
HOW???
Any root method available in MIUI 12.5.1?
HValenti said:
Any root method available in MIUI 12.5.1?
Click to expand...
Click to collapse
same root method like before 12.5.1
everything works
Dadovvv said:
same root method like before 12.5.1
everything works
Click to expand...
Click to collapse
Nope!

Categories

Resources