I read that flashing custom ROMs will mess up this partition and some sensors will stop working. Why do sensors depend on a empty partition??
I experienced this myself after flashing MIUI 8.5 with TWRP.
Then I had to flash MIUI 9.1.1 dev and the sensors started working again.
I want to flash more stuff, because MIUI sucks - the notification system is a huge mess and Volte is not working ...but how can I prevent stuff from breaking again?
I've flashed different versions if MIUI, audio mods and various other crap and I've never experienced this problem...
Well, if you want to try it yourself here is what I did:
- had MIUI 8.2..something initially
- upgraded through OTA to MIUI 9
- unlocked, installed TWRP and rooted
- backed up MIUI 9 and flashed RR with TWRP
- backed up RR and restored MIUI 9 with TWRP, sensors still worked
- flashed MIUI 8.5 with TWRP, sensors stopped working (compass)
- restored MIUI 9 with TWRP, sensors were still not working
- searched google and followed steps here http://en.miui.com/thread-478922-1-1.html
- flashed MIUI 9 dev version in EDL mode, sensors working again
- installed TWRP and rooted again
- flashed RR and Gapps with TWRP, sensors still working yey
so now I'm on RR and it's good, but what if I want to back it up, flash something else and restore it later?
i really don't want to deal with that sensor stuff again
Btw, what is the size of your persist partition? I noticed that the image file from MIUI 9 dev is 4 MB, but in TWRP my persist partition shows 0 MB. And after flashing RR and Gapps it increased to 1 MB.
onestoploser said:
I've flashed different versions if MIUI, audio mods and various other crap and I've never experienced this problem...
Click to expand...
Click to collapse
same for me . I change rom in every 2 to 3 days nothing happened to my device .
Related
Hi previously i have tried all the roms and all were working properly without any issues then i switched to Stock miui again (Indian Firmware flashed via MiFlash Tool)
then again i flashed twrp and now trying to install custom roms but all roms having the same issue
i.e. - wifi doesn't turns on, Flashlight doesn't work and camera doesn't work.
P.S. - i have india varient device and i always installl 10.3.16 firmware before flashing roms and also i have formatted data (internal storage)
Edit:- everything fixed after i installed miui eu (10.3.16 )
And then flashed roms now everything is fine
pritish sahoo said:
Hi previously i have tried all the roms and all were working properly without any issues then i switched to Stock miui again (Indian Firmware flashed via MiFlash Tool)
then again i flashed twrp and now trying to install custom roms but all roms having the same issue
i.e. - wifi doesn't turns on, Flashlight doesn't work and camera doesn't work.
P.S. - i have india varient device and i always installl 10.3.16 firmware before flashing roms and also i have formatted data (internal storage)
Click to expand...
Click to collapse
Try extracting the persist.img file from the latest fastboot ROM, then flash this to the persist partition in TWRP. You'll need a TWRP that can access the persist partition, regular TWRP doesn't allow access to it. LR.Team TWRP should be OK.
Did you try using Android 10 beta? Many people had issues when returning from beta.
Try installing MIUI 10.3.16.0 CN using MiFlash first? Many custom ROMs are based on lastest CN MIUI and using it firmware.
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
AZ_Miss_Murder said:
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
Click to expand...
Click to collapse
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Laptapper said:
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Click to expand...
Click to collapse
I'm actually going to follow the Evolution instructions (just missed the part about flashing EEA)
So i'm using MiFlash with the MIUI11 EEA boot rom file, then I'll do the normal TWRP -> format data -> install Evolution ROM and test.
Thanks!
So it seems like I'm completely out of luck at this point - I've tried basically everything I can think of, and I think something big must be wrong with the phone's file system.
I've followed Evolution's steps to a T (minus MiFlash having an error at the end of the EEA flashing, but the firmware seeming to load fine) and still run into the no Mic issue.
"Flash MIUI11 eea with miflash
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (Download here)
Flash TWRP
Wipe (dont wipe system/vendor)
Format data
Reboot recovery
Flash rom
Reboot system"
Wipe (don't wipe system/vendor) I assume means just a normal factory reset wipe via TWRP, which I've tried.
I've tried both fw+vendor files (the newest for Android 10 and newest from Xiaomi.eu)
Any other last suggestions before I assumed the phone is broken?
Try to flash xiaomi.eu_multi_MI9_9.11.7_v11-10.zip
With miflash and after factory reset.
https://sourceforge.net/projects/xi...iaomi.eu_multi_MI9_9.11.7_v11-10.zip/download
SO! Update here
I was able to use Evolution X's Android 9 instructions to get everything working fine....but everytime I try to duplicate that for MIUI 11 it does not work.
Reboot to recovery
- Flash the latest 9.8.1 vendor image or full stock ROM.
- Reboot to twrp and format data
- Wipe cache/dalvik
- Reboot back to recovery and flash
I tested using the newest Xiaomi.EU Vendor for Android 10 and the stock one with no luck....more thoughts?
Did you try turning off the VoLTE?
I've tried a couple of 10 ROM but, as far as i see, there're still too many bugs that makes very unpractical for me to use android 10 as a daily driver.
I'm planning to revert back to a pie custom ROM but I'm worried that I might overlook something.
I know that I have to backup some partiotins (persist? EFS? something else? in 10 in order to restore them in Pie, but I'm not sure wich partiotions and how to restore them (before flasing the new ROM, after flashing the new ROM, should I change the active slot?)
Can someone please give me some advices?
Thank you in advance
Don't do anything you Use mi flash tool for android 10 to move android 9 i do tow time and it working for me know am using android 9 pie.
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Malobestino said:
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Click to expand...
Click to collapse
to start backup everything and put on pc with usb cable ..
better just flash a recovery.zip of miu pie or oreo or even custom
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
custom pie and stock pie are pretty stable ..
remember if going for miu get recovery flashable zip and flash twrp image again after flashing rom..boot straight into recovery ...flash magisk ..use stock
Thank you for your detailed answer
Just a couple of more questions
KevMetal said:
better just flash a recovery.zip of miu pie or oreo or even custom
Click to expand...
Click to collapse
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
Click to expand...
Click to collapse
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
Click to expand...
Click to collapse
Can I just restore my persist backup from within TWRP?
Thank you again for your patience
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
KevMetal said:
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
Click to expand...
Click to collapse
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Malobestino said:
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Click to expand...
Click to collapse
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
KevMetal said:
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
Click to expand...
Click to collapse
Im' also quite convinced that is something related to the ROM or the kernel. Fro the time being isn't that big of an issue. I will look into it in the next days
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
Click to expand...
Click to collapse
Apparently this issue resolved during nightime by itself.
My theory is that the autobackup during last night realigned automagically the app (which doesn't make a lot of sense, but I don't really know how whatsapp's backup works, what it writes or read to the gdrive backup).
Anyway I really appreciated your help, thank you again
So i already did some searching, but nothing yet, maybe i' m overlooking something
Soi did a full recovery with mi flash tool, no dice, then took the persist out of it and flashed it with twrp, no dice, so now i reverted back to Lineage since i can't stand MIUI, but yeah, now i still don't have sensors running
The fastboot image i used is 11.8, which is the euro image as far as i know (got my device here in europe), is there something i'm completely overlooking?
Had this issue with my Pixel Experience rom - do sensors work in Miui? If so, perhaps your method of flashing is dodgy/ the rom has issues.
Flash the permissive zip. It happens sometimes when it's set to enforcing. People were talking about it on Syberia 3.6 post, check it out, there's a link to download there.
I had this same issue as well. I solved it by reflashing back to stock with MiFlash tool and using V11.0.5.0 Stock MIUI ROM.
After that boot the phone and go through the initial phone setup process.
Then you can flash TWRP Recovery (twrp-3.3.1-0-cepheus.img).
In TWRP flash vbmeta.img. After that you can flash and boot your Custom ROM with sensors working.
Do not flash any other firmware file in TWRP. I have seen other ROM threads mentioning the need to flash a fw file but don't do that.
When I try to install a ROM, no problem installing TWRP and flashing a ROM.
But when I restart, whatever the ROM it systematically restarts on TWRP.
Everything is back to normal when I reinstall the MiUi ROM.
I installed vbmeta, TWRP is kept even with the MiUi ROM.
I tried to install a ROM on MiUi but nothing happened, TWRP is launched systematically after restarting.
I tried with several versions of TWRP but nothing worked.
Also with LOLz kernel with and without; and Magisk too.
Sleep on it !
you have to format DATA and not Wipe !
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
1999romelx said:
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
Click to expand...
Click to collapse
wrong subforum, heres the poco x2 subf
Xiaomi Poco X2
The Xiaomi Poco X2 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SDM730 Snapdragon 730G chipset is paired with 6/8GB of RAM and 64/128/256GB of storage. The main camera is 64+8MP and the selfie camera is 20+2MP. The battery has a 4500mAh capacity.
forum.xda-developers.com
sounds like your data got wiped, thats why theres only a twrp folder in internal. you should prolly full flash a fastboot rom since you mightve missed a few important steps
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
johndaog said:
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
Click to expand...
Click to collapse
sorry for the super late response
its supposedly for bypassing android verfied boot (avb). it blocks unauthorized roms from booting. if you search for 'what is vbmeta', we literally get no info at all and mainly speculations (no official docs etc). imho it does seem true