MIUI 10 8.10.18

[Soukai]

Mi6x with the camera error too .
I can only take pictures with quick snap

 

[gianca]

do bug reports and complaining here: https://en.miui.com/forum.php?mod=bugfeedback&fid=5&page=1
they have to fix it !!

it's not a bug, they want notifications to last 1 second and then disappear, it's awful

 

[topstarnec]

just fixed my mi8 after paid CNY 160 to chinese xiaomi professional to have an official account to flash.

the reason which caused the black brick was that the downloaded file was corrupted (it may cause by the Free Download Manager or the anti-virus program) and the corrupted rom file activated Mi 8's Anti Rollback Mechanism, then black brick (9008 mode) the phone. We wouldn't do anything in this situation without Xiaomi's official intervention.

Since i'm living in Australia and i am a chinese. i had to go to taobao.com and search and pay a professional by a Xiaomi official maintenance account to remote flash the phone from black brick.

Suggestion: we must use a tool such as Winrar to test the compressed rom file to make sure the file alright before flashing. Otherwise the phone would be a black brick (anti-roll back, even if you not rolling back/flashing an old version)

Next time i will not buy any Xiaomi phone. I have not bricked any iphone and/or samsung phone. This was the first time a phone got bricked in my more than 10 years mobile phone flashing experience.

 

[stetor]

Did somone installed it on Mi8? Notifications fixed?

Installed from 8.8.30 ... have had great problem ... the install goes well as usually but the MI8 after some minutes with the three dots running, restart in TWRP ... tried more time, nothing. Checked the MD5 and it match ... reinstalled the 8.8.30 and now the camera don't work and also the gyroscope ! very sad ...
I've tried again to reinstall the 8.8.30 and don't work ... i don't know why but previously worked ... really strange

P.S: obviously wiped the dalvik cache after every reinstall

 

[Izarsha]

just fixed my mi8 after paid CNY 160 to chinese xiaomi professional to have an official account to flash.

the reason which caused the black brick was that the downloaded file was corrupted (it may cause by the Free Download Manager or the anti-virus program) and the corrupted rom file activated Mi 8's Anti Rollback Mechanism, then black brick (9008 mode) the phone. We wouldn't do anything in this situation without Xiaomi's official intervention.

Since i'm living in Australia and i am a chinese. i had to go to taobao.com and search and pay a professional by a Xiaomi official maintenance account to remote flash the phone from black brick.

Suggestion: we must use a tool such as Winrar to test the compressed rom file to make sure the file alright before flashing. Otherwise the phone would be a black brick (anti-roll back, even if you not rolling back/flashing an old version)

Next time i will not buy any Xiaomi phone. I have not bricked any iphone and/or samsung phone. This was the first time a phone got bricked in my more than 10 years mobile phone flashing experience.

To make it simply, the devs should put md5 checksum on each of the rom so we can check the validity of the file. Anyways about the ARB that you mention, did you understand how actually the ARB mechanism works? Actually if the downloaded file was corrupted twrp usually give an error that the file could not be flashed or bla bla bla. I guess you are trying to reflash official rom without realizing you actually downgrading the rom. Thats how arb works, you cannot flash older version of your current firmware. If for example you are on the latest developer rom official before you flash xiaomi eu or any kind of roms, if you want to restore to official xiaomi rom or fastboot, you cannot fastboot your phone using global roms as it is an act of downgrading your current(developer) firmware. If you are on latest official global stable version before flashing xiaomi eu or any kind of roms, you could simply restore by flashing the current available stable roms. By that means, if you are flashing custom roms, ARB was not an issue. It never has unless you are trying to downgrade your current firmware using fastboot that is when ARB come into the game.

 

[fmcheetah]

Hello, I have a mi6 with the latest version and another one in version 7.12.7 and I want to update the latter to the last version of miui 10. My question is if I have to do format date or simply download and update by the updater? Thank you

Would recommend to format data, latest TWRP requires it anyway.

 

[pack21]

Great rom for PoCophone F1. Thanks


Just don't like colored notification icons on bar.

 

[deepblue2000]

If the upgrade from 8.8.30 did not work, you need to wipe and format data. If you flashed 8.8.30 over 8.10.18

Installed from 8.8.30 ... have had great problem ... the install goes well as usually but the MI8 after some minutes with the three dots running, restart in TWRP ... tried more time, nothing. Checked the MD5 and it match ... reinstalled the 8.8.30 and now the camera don't work and also the gyroscope ! very sad ...
I've tried again to reinstall the 8.8.30 and don't work ... i don't know why but previously worked ... really strange

P.S: obviously wiped the dalvik cache after every reinstall

thats always a bad idea to downgrade to an older version, that causes the problems that
you have no, non-working apps !

I was one of the few people who could upgrade with dirtyflash from 8.8.30 to 8.10.18 without wipe or format anything.

If your Mi8 boots to twrp after minutes, you have to format and wipe data in twrp and
flash 8.10.18 again.

now you did downgrade to 8.8.30 and have now a "corrupt" system with non-working apps.

so the only thing you can do, wipe/format data and flash 8.10.18 to get a working Mi8 again

https://xiaomi.eu/community/threads/8-10-18.47060/page-4#post-450862
https://xiaomi.eu/community/threads/8-10-18.47060/page-4#post-450885

 

[deepblue2000]

just fixed my mi8 after paid CNY 160 to chinese xiaomi professional to have an official account to flash.

the reason which caused the black brick was that the downloaded file was corrupted (it may cause by the Free Download Manager or the anti-virus program) and the corrupted rom file activated Mi 8's Anti Rollback Mechanism, then black brick (9008 mode) the phone. We wouldn't do anything in this situation without Xiaomi's official intervention.

Since i'm living in Australia and i am a chinese. i had to go to taobao.com and search and pay a professional by a Xiaomi official maintenance account to remote flash the phone from black brick.

Suggestion: we must use a tool such as Winrar to test the compressed rom file to make sure the file alright before flashing. Otherwise the phone would be a black brick (anti-roll back, even if you not rolling back/flashing an old version)

Next time i will not buy any Xiaomi phone. I have not bricked any iphone and/or samsung phone. This was the first time a phone got bricked in my more than 10 years mobile phone flashing experience.

every User (windows) can install the tool "HashTab" then you can right click properties on every file and check the md5/sha5/crc and can compare
it with the online sha5 (sourgeforge link click "i" to show sha5)

 

[joaonctm]

I have this ROM on my Poco F1 and so far it is such a great ROM for such a great phone

I was wondering if it is possible in a future update making notifications stay longer or like stay until we tap on them?

Keep up the good work dudes.

Thank you for your work every day.

 

[hamayan]

Sometimes Wifi gets stuck and I cannot turn it off. (Mi note 3) I was previously using 8.9.20 and now flashed the latest firmware but it still persists.

 

[muharrem1961]

[QUOTE = "OldGamer, gönderi: 451132, üye: 212339"] Xiaomi Mi6x Miui Miui 8.10.18 Xiaomi.eu Android 8.1.0 Kamera, kullanıcı (eyiieyi) ile aynı hatayı veriyor. kamera) Ne yapılabilir ??? [/ QUOTE]

+1

 

[gianca]

Poor you

the fk you want little farmer

 

[Parunzel]

I'm on Mi 8 and can't find the NFC button on the shortcut bar.
Is this a bug or normal behavior?
Special thanks to all developers. You do a great job.

 

[topstarnec]

To make it simply, the devs should put md5 checksum on each of the rom so we can check the validity of the file. Anyways about the ARB that you mention, did you understand how actually the ARB mechanism works? Actually if the downloaded file was corrupted twrp usually give an error that the file could not be flashed or bla bla bla. I guess you are trying to reflash official rom without realizing you actually downgrading the rom. Thats how arb works, you cannot flash older version of your current firmware. If for example you are on the latest developer rom official before you flash xiaomi eu or any kind of roms, if you want to restore to official xiaomi rom or fastboot, you cannot fastboot your phone using global roms as it is an act of downgrading your current(developer) firmware. If you are on latest official global stable version before flashing xiaomi eu or any kind of roms, you could simply restore by flashing the current available stable roms. By that means, if you are flashing custom roms, ARB was not an issue. It never has unless you are trying to downgrade your current firmware using fastboot that is when ARB come into the game.

No. i had 8.10.12 xiaomi.eu Mi 8 rom in the phone. i download the 8.10.18 xiaomi.eu rom by Free Download Manager in a widnows PC. Then i copy the corrutped file to a USB-c flash drive. I inserted the flash drive to MI 8, flashed the corrupted rom and flashed magisk 17.2 and wiped cache/dalvik by using TWRP (L.R. TEAM 0908 version). Then the phone screen would not lighted up again, black brick. Phone connected to PC shown in 9008 mode. Miflash tool need an official maintenance account to flash.

There were not any error, stop nor warning information by twrp.

You can corrupt a latest rom fiile to flash for testing if you like to.

 

[stetor]

Hi there,

I tried to do the same, also coming from 8.8.30 on MI 8, but didnt work;
The phone cannot boot on system and will reboot on TWRP.

I have installed the latest TWRP (yours) and cleaned cache / dalvik.

I am reverting to 8.8.30 (thx god I was able to revert).
I guess full format is still necessary, how did you manage ?

HI, same problem here but after the rollback to 8.8.30 my camera don't work anynore and also the gyroscope (so the compass or the screen rotation don't work) ... very sad

luckily the anti rollback don't apply (never full started) otherwise we must risk the hard brick !

bye

 

[stetor]

Hi DeepBlue2000 and thank you for your reply,

If the upgrade from 8.8.30 did not work, you need to wipe and format data. If you flashed 8.8.30 over 8.10.18

thats always a bad idea to downgrade to an older version, that causes the problems that
you have no, non-working apps !

i know but the new firmware never started otherwise the antirollback apply so i thinked that i can also revert without problem ...

I was one of the few people who could upgrade with dirtyflash from 8.8.30 to 8.10.18 without wipe or format anything.

If your Mi8 boots to twrp after minutes, you have to format and wipe data in twrp and
flash 8.10.18 again.

why ?
other times i've upgraded (also from major andorid release) and always mainteined my app and data ... why this time it's different ?

now you did downgrade to 8.8.30 and have now a "corrupt" system with non-working apps.

so the only thing you can do, wipe/format data and flash 8.10.18 to get a working Mi8 again

*sigh* hope itsn't true ...

https://xiaomi.eu/community/threads/8-10-18.47060/page-4#post-450862
https://xiaomi.eu/community/threads/8-10-18.47060/page-4#post-450885

i check this post

thank you

 

[topstarnec]

No. i had 8.10.12 xiaomi.eu Mi 8 rom in the phone. i download the 8.10.18 xiaomi.eu rom by Free Download Manager in a widnows PC. Then i copy the corrutped file to a USB-c flash drive. I inserted the flash drive to MI 8, flashed the corrupted rom and flashed magisk 17.2 and wiped cache/dalvik by using TWRP (L.R. TEAM 0908 version). Then the phone screen would not lighted up again, black brick. Phone connected to PC shown in 9008 mode. Miflash tool need an official maintenance account to flash.

There were not any error, stop nor warning information by twrp.

You can corrupt a latest rom fiile to flash for testing if you like to.

I opened a thread for this specific MI8 anti-roll back brick topic. https://xiaomi.eu/community/threads/warning-a-corrupted-rom-file-could-brick-mi-8-completly.47108/

 

[stetor]

what I did:

- local backup and copied it to my PC (for security if something goes wrong)
- copied the 8.10.18 zip to the internal memory
- put the phone in flightmode (I dont know why I did it)
- started the updater, choosed the 8.10.18.zip and ok
- waited... done.
- happy that I did not have to wipe/format anything

I did the same (only not activated the flighmode but i don't think this make the difference) ... unlucky the mi8 restarted again the twrp when tried to load the new firmware ... maybe the difference is in the language or in some app installed because the restart is after some minutes when the UI must start i think

 

[Izarsha]

No. i had 8.10.12 xiaomi.eu Mi 8 rom in the phone. i download the 8.10.18 xiaomi.eu rom by Free Download Manager in a widnows PC. Then i copy the corrutped file to a USB-c flash drive. I inserted the flash drive to MI 8, flashed the corrupted rom and flashed magisk 17.2 and wiped cache/dalvik by using TWRP (L.R. TEAM 0908 version). Then the phone screen would not lighted up again, black brick. Phone connected to PC shown in 9008 mode. Miflash tool need an official maintenance account to flash.

There were not any error, stop nor warning information by twrp.

You can corrupt a latest rom fiile to flash for testing if you like to.

Hmm. Thats weird that twrp can flash corrupted file. What twrp did you use? I just checked the twrp that you mention but it was not on xda thread. I didnt have mi8 to try anyways.

 

[mandamum]

Would recommend to format data, latest TWRP requires it anyway.

Thank you very much for your help

 

[cobben]

Hmm. Thats weird that twrp can flash corrupted file. What twrp did you use? I just checked the twrp that you mention but it was not on xda thread. I didnt have mi8 to try anyways.

There is no 100% certainty in any CRC check or other hash check, or any other data transmission situation.

There cannot be, mathematically - there is always that last 0.000....00001% chance that something is wrong and yet missed by the check.

 

[Izarsha]

There is no 100% certainty in any CRC check or other hash check, or any other data transmission situation.

There cannot be, mathematically - there is always that last 0.000....00001% chance that something is wrong and yet missed by the check.

In my experience, this error usually comes up if you had a bad or corrupted file or something like error 7. I never had a success install if the file were corrupted. TWRP can detect it.

 

[DanielFG]

Do you remember current official version before you flash xiaomi.eu? Global or dev? If you did remember, stick to that rom if you want to flash official rom. Higher than your official version rom is okay but not lower version than your official roms. For the google solution, i havent had any issue so far. Maybe you can try reinstall the rom with clean flash using fastboot. The command is

fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase cache.

Reboot into twrp and flash the rom once again.

Not exactly but when i flash xiaomi.eu even dont exist global dev rom for mi8 so i think that any version now its newer rigth brother?

 

[DanielFG]

Your issue doesn't have to do anything with antirollback protection. Requiring google account credentials after a full wipe is an Android protection mechanism.

but when the phone start even dont ask me for google account just xiaomi acount password and fingerprint... any fix?