Problem on Any custom ROM - Xiaomi Poco F1 Questions & Answers

Hello,
I need some suggestion,
I have installed AOSPExtented and after a vendor upgrade i cant boot on any rom.
Tried AOSP, PixelEx, LineageOS..
Clean instal, dirty install, fastboot format userdata/cache
Every single one get stuck on boot animation (most i waited was 1 hour)
Any idea how to fix?
Ty

If you had installed magisk, try unistalling magisk from recovery.
Try clean flash for any rom, meaning wipe cache, dalvik cache, data and system.
This should resolve boot loop.

Amarjeet28 said:
If you had installed magisk, try unistalling magisk from recovery.
Try clean flash for any rom, meaning wipe cache, dalvik cache, data and system.
This should resolve boot loop.
Click to expand...
Click to collapse
Tried all that, nothing worked.
The solution was flash DisableEncryption as last flash..
Dont know why, Never needed this, but well, now everything is ok. Ty

hi i have install pixel os in poco f1 i have an mobile data issue

Related

Phone Will Not Boot Past Motorola Logo

I recently rooted my phone using this tool: http://forum.xda-developers.com/showthread.php?t=1255548
I tried flashing MIUI and ICS after doing full wipes, but when rebooting the phone, it won't go mast the Motorola logo where it says "Unlocked." Is there a way to fix this?
wipe data/factory reset, cache, and dalvik in recovery
ovitz said:
wipe data/factory reset, cache, and dalvik in recovery
Click to expand...
Click to collapse
I always do that before I flash a rom. I've done it at least 5-6 times now as I try to reflash the roms.
Sorry, early morning brain fart!
What do you consider a full wipe?
How long are you leaving your phone rebooting after flashing the ROM on the initial first reboot?
You could try flashing a kernel after flashing the ROM. You shouldn't have to, but I would try flashing the appropriate kernel from Faux.
Try wiping cache and dalvic cache. After do a factory reset. Then flash the ROM twice! As in back to back without doing anything else.
Personally I would flash another Rom, Some like Nottach or Cm7.2 and see if it boots, if so then recharge the battery and then try fresh again doing the wipes like others have said.
I had issues before where my recovery wouldnt boot but reflash did and was able to redo things and all is well.
For MIUI you need a separate kernel I tried flashing before and was stuck too, then flashed a kernel and it worked (jokers v3 kernels work well)
I have just tried installing CM7 from this thread: http://forum.xda-developers.com/showthread.php?t=1257574
I made sure to do a wipe all data, cache, and dalvik cache. Then rebooted and waited for it go past the logo for 10-15 minutes (which it didn't).
This is the same process I go through for each rom, but it still doesn't work.

[Q] No KitKat (4.4.X) Rom will boot on Galaxy S3

HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
tallman43 said:
Format data and system and cache (full wipe) also intstall the rom then boot it then flash gapps after see if that helps.
Click to expand...
Click to collapse
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Hey
When it bootloops, have you tried to goto recovery and see what us the cwm version??
Also try re-flashing the ROM without wipes..
Sent from my GT-I9300 using xda app-developers app
I just flashed EHNDROIX V (based on CynogenMod 4.4.2 KitKat) last night and it worked just fine.
Rooted the device with Odin, install TWRP from playstore, install TWRP recovery from TWRP, clean dalvik, clean data, clean cache, flash ROM and then flash Gapps (spesific Gapps for the ROM) and voila it worked right away.
Note:
You see, I am not using CWM but TWRP. I dunno if CWM is the one causing the problem.
Most of the weird flashing issues are due to the recovery used, you could also try the latest version of Philz recovery which has an option to wipe for new firmware.
Sent from my GT-I9300 using Tapatalk
divoom12 said:
I've already done that every time. As I said - Its not my first time flashing roms on my device. I know how to fix the general errors. This is something unusual tho.
Click to expand...
Click to collapse
Quote " Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system" You said nothing about formatting data that is why i suggested it! Next time please include all details on how you flashed the rom then It cuts down on useless post's like mine
Like everybody suggested try a different recovery ( latest one) which if you have flashed roms many times before you should have done anyway
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
divoom12 said:
Thanks guys, but I've already tried these things. CWM, TWRP and three other recoveries (not famous ones) haven't been able to help.
Click to expand...
Click to collapse
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
RazorMC said:
If a rom is stuck in a loop, I would go to recovery and wipe dalvik and wipe data then reboot into same rom. This has worked for me when I've been stuck after a flash.
~ RazorMC
Click to expand...
Click to collapse
I said that I've already done that in my First post.
divoom12 said:
HI.
I've changed roms before countless times, but now I'm trying to install a 4.4.2 rom on my Galaxy S3, and I have some problems. The installation (flash) passes with no problems, but after that, the phone won't boot. It sticks on whatever the rom's boot animation is. I've tried to wipe data, cache, wipe dalvik after this but it's still not working. Before I flash every rom, I do a factory reset, wipe the dalvik cache, and format system. I've tried with 15+ 4.4.X roms, and these are some of them: CyanogenMod, OmniROM, SlimKat, AOKP, Pacman and so on. As I said, I've flashed roms before a lot of times, without any problem. Only 4.4+ roms wont work. I tried to change the recovery, still the same result. I flash gapps with every rom too. Any idea what can be causing the problem? I'm using the latest Clockwork recovery, Sorry for my bad english and thanks.
Click to expand...
Click to collapse
Did you update your bootloader? When I flashed 4.4.2 from 4.4.1 on my s3, I had to update mine to get it to work. http://forum.xda-developers.com/showthread.php?t=2321310 hope this helps.
Sent from my unknown using XDA Premium 4 mobile app

[Q] Bootloop on any rom, after wiping cache, data, etc.

Hi,
Last night my I9300 decided to randomly reboot and get stuck in a bootloop. This morning I took the time to wipe my cache, data, etc. through CWM but it still would not boot. I did a wipe data/factory reset, wiped cache again and installed the latest AOKP nightly, but it still will not boot.
I can start the bootloader through CWM and I can also get into download mode, but it just won't boot Android.
ADB does list my device while in the bootloop, but I get a "device unauthorized" message.
I've had bootloops before and wiping cache/data/factory reset/installing a new rom always worked, but in this case I am clueless.
What can I do? Is there maybe a way to connect logcat without unauthorizing, or authorizing from CWM, or something?
Do you have the newest CWM?? Or try any other custom recovery
As above, use the latest recovery then manually format system, data, cache preload and data/media/0
Sent from my GT-I9300 using Tapatalk
verny94 said:
Do you have the newest CWM?? Or try any other custom recovery
Click to expand...
Click to collapse
How can I do this if I cannot authorize a ADB connection?
If yours recovery works flash the newest version
If not flash a stock ROM via Odin
dalvik cache
art0rz said:
Hi,
Last night my I9300 decided to randomly reboot and get stuck in a bootloop. This morning I took the time to wipe my cache, data, etc. through CWM but it still would not boot. I did a wipe data/factory reset, wiped cache again and installed the latest AOKP nightly, but it still will not boot.
I can start the bootloader through CWM and I can also get into download mode, but it just won't boot Android.
ADB does list my device while in the bootloop, but I get a "device unauthorized" message.
I've had bootloops before and wiping cache/data/factory reset/installing a new rom always worked, but in this case I am clueless.
What can I do? Is there maybe a way to connect logcat without unauthorizing, or authorizing from CWM, or something?
Click to expand...
Click to collapse
On Cwm click advance and try wiping dalvik cache if that doesn't work install your stock rom

problem with encryption

hi today i unlock my poco, and try to flash recovery and mi globe, i flash the orange fox 9.0, and flash the rom, the problem its when i boot to system, a message of my phone was encrypted and i need to perform a wipe data, i try wiping data, and wipe sd, and nothing change, also i flash again and flash then the disableencryptiontreble 17.3, and the same things happen, some solution??
have you tried to format data? not just wipe data
chanta96 said:
hi today i unlock my poco, and try to flash recovery and mi globe, i flash the orange fox 9.0, and flash the rom, the problem its when i boot to system, a message of my phone was encrypted and i need to perform a wipe data, i try wiping data, and wipe sd, and nothing change, also i flash again and flash then the disableencryptiontreble 17.3, and the same things happen, some solution??
Click to expand...
Click to collapse
i have the same issue, tried different recovery projects, OFRP and TWRP. both seem to have the same issue, with the message "encryption unsuccessful" and if i tried to press the "RESET DEVICE" button i get stuck in a boot loop.
i also factory reset my device, formatted everything via the recovery project menu then booted into recovery and installed the CUSTOM ROMS.
tried also to DFE but nothing seem to change even with encryption disabled.
but i scarcely manged to bypass this issue by; after wiping everything boot into recovery and install whatever rom you want and install gapps after it, better still install firmware vendor if the rom of your choice doesnt include them.
never mind, i fixed it.
in my case i was trying to flash LineageMicroG 16 on my Device and i kept getting that error and i did the following to fix it;
wiped everything and wrote "yes" to format the date and swiped for a factory reset through recovery wipe option then i booted into recovery and flashed LineagemicroG 16 after that i flashed optimus drunk kernel and booted into system and everything seemed to work fine, the kernel is what fixed the problem.

Bootloop even after Miflash reset.

Hi everyone
After a normal reboot, from a working system (12.0.1 Stable Miui), my phone got stuck in a bootloop.
Tryed this so far.
Wipe cache
Wipe cache data
Wipe all (cache data ssytem storage
Flash same rom
Wipe all
Flash other miui.
Format Data
Tryied again the same steps again
Nothing
Tried on MiFlash with fastboot rom.
Nothing
Flash TWRP
Flash some miui.eu
Nothing.
Even with no errors on all steps, it continues on bootloop...
Anyone has any ideia?
Update;
Flashed some Custom Rom.
The charging animation has changed, but it is still on bootloop.
Almost giving up

Categories

Resources