Hi,
this is just a little report about the flashing history and the current status of my redmi 6:
history:
- received redmi6 (supposedly) international running Miui global 9.something
- got an OTA update to Miui global 9.something+
- activated device localisation and all the miui cloud stuff including my cellphonenumber, gave away all my data
- unlocked bootloader after waiting period of 15 days using MI Unlock Tool
- flashed TWRP as decribed here
- formated data
- flashed DFE-Magisk-v16.7.zip
- flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip which seems to be the official rom provided my xiaomi
- downloaded Magisk 1.71 zip via magisk app and flashed it via TWRP (had to copy it to my sd-card because my data partition still seems to be encrypted
- received 2 other OTA updates, afterwards I had to reflash TWRP via fastboot
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
- downloaded and flashed miui10 global stable
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
The only problem i recognized, is that i'm not able to choose another region then chinese for some reason. This seems to be problem, many users have. I tried some region fixes via twrp but they didn't do their job. Help would be appreciated
snoerme said:
Hi,
this is just a little report about the flashing history and the current status of my redmi 6:
history:
- received redmi6 (supposedly) international running Miui global 9.something
- got an OTA update to Miui global 9.something+
- activated device localisation and all the miui cloud stuff including my cellphonenumber, gave away all my data
- unlocked bootloader after waiting period of 15 days using MI Unlock Tool
- flashed TWRP as decribed here
- formated data
- flashed DFE-Magisk-v16.7.zip
- flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip which seems to be the official rom provided my xiaomi
- downloaded Magisk 1.71 zip via magisk app and flashed it via TWRP (had to copy it to my sd-card because my data partition still seems to be encrypted
- received 2 other OTA updates, afterwards I had to reflash TWRP via fastboot
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
- downloaded and flashed miui10 global stable
- reflashed DFE-Magisk-v16.7.zip and Magisk 1.71
The only problem i recognized, is that i'm not able to choose another region then chinese for some reason. This seems to be problem, many users have. I tried some region fixes via twrp but they didn't do their job. Help would be appreciated
Click to expand...
Click to collapse
I used to rewrite this on build.prop every time I flash/update ROM even OTA:
audio.safemedia.bypass=true
ro.miui.region=ID
ro.miui.cust_variant=en
persist.camera.HAL3.enabled=1
persist.camera.eis.enable=1
1. Used for Nougat, I never had a volume limitation in Oreo. But, I wrote that anyways.
2. Change to your region. Mine is Indonesia, ID
3. Leave it be... it's fine to have that.
4 and 5. To activate camera's manual mode.
Hope it helps
MIUI Cloud is malware!
Related
hi, i accidentally updated to miui10 global beta 8.7.12 (i thought is was stable since it got to the miui mix download page)
i am using twrp 3.2.1 with a mouse for upgrade (since that version have touchscreen issue)
and i can not upgrade with 3.0.2 smarty which i usually use it shows eror 7
after i have sucessfully upgraded to miui 10 global beta 8,7,12
i flash the 3.0.2 smarty twrp and then i realized it had 0mb internal
i just wanted my mi mix to be rooted and do NOT want the factory wipe (since i read that fixing the 0mb problem is to factory wipe)
i am using this phone for work and do not want to lose any data on this phone.
can anybody please give me a suggestion?
i am flashing the 3.2.1 twrp via fastboot
in my case, the twrp did not even ask for password, it just wouldnt read the internal.
does rolling back to miui 9 9.5.60 via flashboot will do the trick? because i tried to roll back once via system update to 9.6.10
at the first it had notification that my data would be lost(so i cancel itu). but when i try again, it recognise the official 9.6.10 as custom room.
update : i have upgraded to miui10 8.7.19 and flash with raupe-blunden 15.1 TWRP
the after the fasboot reboots to twrp, it works fine and the internal is fixed.
so i install superSU, and it worrks
BUT after reboot to system, the root is gone and the recovery reverts to stock miui recovery
since i have able to enter internal storage (even if it is only the first time)should i revert to miui9 9.5.60 (the last stable rom for nougat)? some say taht the oreo miui can not be roll back, it will brick your device
please advise,
warm regards,
ziggy
Each time you Run MIUI it will encrypt the device again.
Try installing the no-verity-opt-encrypt and try......
If u switch to a different ROM it doesnt encrypt the phone so hence allowing you to use the TWRP again.
I recommend the RR rom / Pixel ROM
Hello guys, I really need your help!
I've just spent 5 hours trying to fix my Xiaomi Mi 8 bootloop.
Everything began this morning when I started a common update. After the reboot I got just an infinite bootloop on the white word "MI" that i get every time I turn the phone on.
I bought the phone from China with a Global rom already installed and the bootloader unlocked. I can access fastboot.
Here what I did today, until now:
-I decided to install a TWRP, only the 3.2.3.0 worked after many attemps with other versions.
-From twrp I flashed the last xiaomi eu stable. Result? Bootloop was still there.
-I flashed the last xiaomi eu weekly. Result? Bootloop there.
-I decided to go through Mi Flash.
-I installed the tool and downloaded the last Global Stable for fastboot installation.
-I flashed the global from Mi Flash. Result? Bootloop is here.
I don't really know what to do. Every time i did factory reset from twrp. I tried also to make the factory reset from fastboot command. I tried everything I could find online. No solution, same infinite bootloop.
Any suggestion? Thank you very much
Simone
Did your find a solution? I have the same problem.
Odoslané z MI 8 pomocou Tapatalku
Hi, after many attemps I installed the xiaomi.eu!
I could install china stable from mi flash, but I was not satisfied with a lot of Chinese apps. After that I installed again the twrp and I could put the ROM pixel experience. After pixel experience if I am not wrong I tried another twrp (I need to check) with which I could install the Xiaomi EU!!! Now I don't want to update anymore
If you need help I can check the version of the last twrp I have used! I guess it was an anti backroll protection because I could install the last china dev but nothing else, neither from that twrp.
If you need help ask,
Bye bye
is it because of encryption issue? from the first day i use mi8, i always on decrypt.
my step to flash any rom is:
1. flash rom
2. magisk
3. flash dm-verity
never had bootloop issue
flashing dm-verity should fix it.
simoooo17 said:
If you need help I can check the version of the last twrp I have used! I guess it was an anti backroll protection because I could install the last china dev but nothing else, neither from that twrp.
Click to expand...
Click to collapse
Hi I have/had the same problem!
- The only rom I got working was the "xiaomi.eu_multi_MI8_V10.0.11.0.OEACNFH_v10-8.1." which I stil use.
- I also can get the the official "dipper_global_images_V10.0.2.0.OEAMIFH_20180912.0000.00_8.1_global" rom working but it stil keeps updating to the latest version after a while. If that happends I get the bootloop problem.
So I'm stuck at an android 8.1 .EU rom and I'm scared to update to the latest stable android 9.0 rom because of the bootloops and/or to brick it and to lose al my data again.
So my questions:
1 - do you use the latest stable ROM, (which one) at the moment?
2- how did you install it?
3 - which TWRP did you use to flash the .EU rom?
4 - I use an 8.1 .EU rom. Do you think I can update without losing al data again (my wife will kill me if I have to reinstall again)?
5- Any idea why we have this problem?
I really like to update to android 9.0
I just saw (!) that they released an official version of TWRP for the Mi 8 at https://twrp.me/xiaomi/xiaomimi8.html
Thanks in advance!
Hello, I have solved using a different TWRP with which I could install the xiaomi.eu weekly! I tried a lot of twrp until that one worked
Where can I find this twrp version? Anders on which exact version are you on?
Okay, I'm convinced that most of people that are able to help me are already familiar with this problem.
It occured when I've attempted to OTA upgrade my firmware (it was one of MIUI 9 stable versions) as I
have only used OTA before. However I had TWRP (mrraines version) installed and also magisk root
(everything from tutorial on xda, in order to install gcam).
So when I tried to OTA upgrade it stopped almost immediately after beginning with failure message and
fingerprint sensor options dissapeared.
I have an International version of MI MIX.
Since then I have tried:
-full wipe + MIUI 10 global (OAHMIHF) flash (via mrraines TWRP) - it didn't work (error 7)
-MIUI 10 global (OAHMIHF) flash via fastboot (didn't help)
-MIUI 10 global (OAHMIHF) flash via fastboot + newest global firmware (8.12.20) + reverse order
-MIUI 10 global (OAHMIHF) via TWRP (the new version with working decryption) found in this topic:
https://forum.xda-developers.com/mi...y-official-twrp-xiaomi-mi-mix-t3498960/page67
-reflash same firmware for non-global version
-full wipe + MIUI 10 from xiaomi.eu (OAHCNFK) via the same TWRP + non-global firmware (in this exact order)
-after reading this topic: https://forum.xda-developers.com/mi-mix/how-to/miui-9-stable-magisk-xposed-t3705951
I have flashed firmware advised there (8.8.3)
-of course I have tried changing pin/unlock pattern resetting, hard reboots and so on
Right now I'm about to try reflashing the same firmware and MIUI 10.2.1 afterwards. Then perhaps developer version.
I also have full recovery from before upgrade, however it was made after I've attempted to OTA upgrade and failed.
In diagnostic options self test is "FAILED!" and checkerboard test is: "NO RESPONSE FROM SENSOR!"
Aida64 recognizes sensor as FPC.
Can it be related to something I have not yet reflashed? I can't live without fp sensor
Please help!
Okay I have found information that fp sensor problems are caused by persist partition.
However flashing China stable 10.1 in EDL mode didn't fix the issue.
Could anyone post a file for fp sensor that is located in persist partition so I would replace mine?
Thanks in advance
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.
hello
It's been a while since I wrote anything on XDA, so please be gentle
Let's get the ball rolling.
I have been using MI9 since launch. I bought mine directly at the store in Shanghai, and brought it with me to Europe. After 2 weeks i unlocked the bootloader, and was able to flash TWRP + xiaomi.eu ROM (current beta at that time).
For a couple of months I received OTA updates (all firty flashes), up until introduction of beta android Q (miui 11).
I downloaded the ROM, and flashed, everything worked fine. after some time I had an issue with google pay, so thought of reverting to android Q. I checked, and dirty flash was not recommended option, so I prepared Android P ROM (not sure if exact version is relevant), booted to TWRP (3.3.1.42), wiped the data and tried to flash the ROM (from USB OTG).
Sadly - received error 7, some info about system partition.
I tried reflashing android Q - only to receive the same error.
Stuck at TWRP or fastboot, I used miflash and returned to a global stable.
then I reflashed twrp hoping to remove the error, but had the same error while flashing. Tried to flash from both internal memory, and usb OTG.
returned with miflash to stable, to use the phone..
bootloader is still unlocked, I can flash twrp again, but it will be wiped once I restart the system (as global roms "reflash" recoveries when they boot up).
I looked on some guides how to deal with error 7, but most of them aren't applicable (removing asses lines from config files, as there is no assess line in the ROMs).
Perhaps I am missing some files that I should flash, such as "vendor" files, or something ?
I thought that miflash restores fully to factory state, so TWRP shouldn'[t give any more errors.
There might be something wrong about either the rom, or the twrp.
> Since error 7 is the updater script checking for the phone model, it's either a bad script, or you missed an asserts file when flashing with MiFlash, as even the "factory" roms might not contain all partitions.
> Some partitions can't be seen by Mauronofrio's TWRP, but that shouldn't be a problem tho...
- Try using TWRP 3.3.1-1001 by a chinese team
- Try using the latest 10.10.2019 MIUI11 Rom from xiaomi.eu, I'm using in on an EEA phone and quite satisfied with it