Stable 7.1.3(kxdcnck) To 7.2.8.0(mxdcndb)


Mar 26, 2016
15
2
15
#3
Hi guys, I'm trying to do this update via Twrp recovery. I've downloaded the ROm MultiCancro but seems like it isn't the correct one because when I try to flash it says error 7 and then the name of my mobile is Mi3w. How is possible? When i've downloaded the 7.1.3.0 it was cancro too
 
Likes: lucianin
Mar 2, 2016
8
3
15
#4
Hi guys. I have the same issue so i would share to you what i do to solve this. I always flash stable and personally i dont have cracking sound in headset bug. But this "tutorial" works for the next update/upgrade because xiaomi_eu ROM don't even support 2 system partition.

First of all recommend backup (local, titanium, the one you want to use) just in case.

The solution comes a few weeks ago in the post of the weekly 6.1.28/29/2.4:

How to update Xiaomi Mi3/4 and MiNote from 4.4 to 6.0:
- Install MIUI 5.12.17 2x via Updater app first to merge your system partitions (no more dual system support) - If you didn't do that already
- After reboot install current 6.1.28/29 version - let it boot and update all apps, then reboot again..
- Wipe data not needed but recommended
- No OTA this week for cancro
- First (re)Boot can take longer than usually (10-15min)​

1.- install via Updater app MIUI weekly 5.2.17 (i do it 2 times: after the reboot in 5.2.17 again go to Updater app and install the same ROM)

2.- (instead of 6.1.28/29) install via Update app MIUI weekly 6.2.9 (after the first boot, i made a reboot and then step 3)

3.- When you have the 6.2.9 installed, you can install the stable 7.2.8 via Updater

I hope this can help you.

Sorry for my english.
 
Last edited:
Mar 26, 2016
15
2
15
#5
Hi guys. I have the same issue so i would share to you what i do to solve this. I always flash stable and personally i dont have cracking sound in headset bug. But this "tutorial" works for the next update/upgrade because xiaomi_eu ROM don't even support 2 system partition.

First of all recommend backup (local, titanium, the one you want to use) just in case.

The solution comes a few weeks ago in the post of the weekly 6.1.28/29/2.4:

How to update Xiaomi Mi3/4 and MiNote from 4.4 to 6.0:
- Install MIUI 5.12.17 2x via Updater app first to merge your system partitions (no more dual system support) - If you didn't do that already
- After reboot install current 6.1.28/29 version - let it boot and update all apps, then reboot again..
- Wipe data not needed but recommended
- No OTA this week for cancro
- First (re)Boot can take longer than usually (10-15min)​

1.- install via Updater app MIUI weekly 5.2.17 (i do it 2 times: after the reboot in 5.2.17 again go to Updater app and install the same ROM)

2.- (instead of 6.1.28/29) install via Update app MIUI weekly 6.2.9 (after the first boot, i made a reboot and then step 3)

3.- When you have the 6.2.9 installed, you can install the stable 7.2.8 via Updater

I hope this can help you.

Sorry for my english.
Thank you, i followed your guide and it works. First I installed 5.12.17, after reboot I installed via updater, chising file from memory, the new stable version android 6.0.1 and it worked.
 
Mar 27, 2016
2
2
13
#8
[QUOTE = "johcf, Beitrag: 282.615, Mitglied: 137.894"] Hallo Jungs. Ich habe das gleiche Problem, so dass ich Ihnen teilen würde, was ich tun, diese zu lösen. Ich blitzen immer stabil und persönlich i dont haben Knacken im Kopfhörer Bug. Aber diese "Übung" arbeitet für das nächste Update / Upgrade weil xiaomi_eu ROM weiß nicht einmal 2 Systempartition unterstützen.

Zunächst einmal empfehlen Backup (lokal, Titan, die Sie verwenden möchten) nur für den Fall.

Die Lösung kommt vor ein paar Wochen in der Post der Wochen 6.1.28 / 29 / 2.4:

Wie Xiaomi Mi3 / 4 und MiNote 4,4-6,0 zu aktualisieren:
- Installieren Sie MIUI 5.12.17 2x über Updater App zuerst Ihre Systempartitionen (nicht mehr duale System-Unterstützung) zu fusionieren - Wenn Sie nicht, dass bereits getan haben
- Nach dem Neustart aktuellen 6.1.28 / 29-Version installieren - lassen Sie es alle Anwendungen starten und zu aktualisieren, dann wieder neu starten ..
- Reinigen Sie die Daten nicht erforderlich, aber empfohlen
- Keine OTA in dieser Woche für cancro
- Erste (re) booten kann länger dauern als gewöhnlich (10-15min)​

1.- über Updater App MIUI installieren wöchentlich 5.2.17 (ich es tun 2 mal: nach dem Neustart in 5.2.17 wieder gehen App Updater und die gleiche ROM installieren)

2.- (statt 6.1.28 / 29) installieren via Update-App MIUI wöchentlich 6.2.9 (nach dem ersten Boot, ich einen Neustart gemacht und dann wird der Schritt 3)

3.- Wenn Sie die 6.2.9 installiert haben, können Sie den stabilen 7.2.8 über Updater installieren

Ich hoffe, dies kann Ihnen helfen.

Sorry für mein Englisch. [/ QUOTE]

Vielen Dank für diese ToDo :)
 
Feb 15, 2016
1,507
461
142
#17
Testing 7.2.8.0 on my mi3 since this morning. No problem so far, stable and battery is good, found no issue.. . Will continue testing the next 3 days.
 
Mar 26, 2016
15
2
15
#18
Another problem that I found is that the Audio is lower than before.
So only me that get many problems, I think I should reflash it.
I'm flashing now, is it normal that message, failed to mount?
 

Attachments

Nov 26, 2013
53
21
18
#23
Mi4LTE, 7.2.8.0
48 hours with battery.
Statistics :
Battery just now: 55%
Screen time: 3h 5m
Using only wifi and 2G

Previously I had KK stable; I did not care for statistics then and can not compare, but this ROM seems great for me.
 
Nov 26, 2013
53
21
18
#24
1.- install via Updater app MIUI weekly 5.2.17 (i do it 2 times: after the reboot in 5.2.17 again go to Updater app and install the same ROM)

2.- (instead of 6.1.28/29) install via Update app MIUI weekly 6.2.9 (after the first boot, i made a reboot and then step 3)

3.- When you have the 6.2.9 installed, you can install the stable 7.2.8 via Updater
I did not install 6.2.9, just 7.2.8.0 after 5.2.17 and all was fine.
 
Mar 2, 2016
8
3
15
#25
I did not install 6.2.9, just 7.2.8.0 after 5.2.17 and all was fine.
Yes, i just share the steps of previous post of a weekly. The crucial thing is to merge the partition with 5.2.17 and IMHO i will recomend to wipe user data because it's a change of OS and Java VM (dalvik to ART) so maybe there are some conflicts, just in case.

Enviado desde mi MI 4W mediante Tapatalk
 
Last edited: