MIUI 8.2 6.12.8


Do you like this MIUI version?


  • Total voters
    334
Status
Not open for further replies.

standbyme91

Members
Oct 14, 2016
10
13
Look that youtube video, in that way you can get your PC regonize that dead Mi5 and then you can flash rom with Miflash.
the Man make this video is my old friend :D. He live in Viet Nam
And That's finally way to save your phone
The Problem in here is: NEED REBOOT TO RECOVERY AFTER FLASH TWRP.
 

Frankguzz

Members
Dec 9, 2016
7
13
I rebooted back into recovery. But it still bricked. I have flashed this phone many times. I made sure TWRP was updated and everything. Yet it still ended up in a hard brick
 

kato46

Members
Mar 13, 2016
2
13
Hi! I've the same problem as some others with my Mi5 32GB, coming from a miui . it ROM (the latest one, 6.11.10).
Installed TWRP 3.0.2.3 with TWRP, rebooted (I checked the TWRP was correctly installed), wipe dalvik/cache/system and data for this nougat ROM.
Flashed with the error "E: unknown command [log]", next screen was the "No OS installed".
I thus reinstalled the miui . it ROM I had, no errors there, but again the "No OS installed". But this works fine.

O.T.: I have the same error on my OPO (the unkown command [log]) when I tried to install with TWRP the latest CM 14.1 nighlty (coming from another CM 14.1 noghtly). My phone is now in the shelf dead (tried everything, it only boots in fastboot).
 

kriszut

Members
Mar 29, 2016
105
40
What time did the people who bricked their MI5 downloaded the rom,and from what site?

And what version before?rooted?xposed?

Maybe corrupt file,or first upload was corrupt?!
 

aimcr7

Members
Aug 12, 2016
8
15
Flashed nougat update on top of 6.11.10 on my Mi5 32GB and all working well so far, the only issue I got is after booting it takes awhile for my mobile signal to connect but after it got connected it works without issue.

My steps are,
Reboot to recovery, flashed official twrp mi5 3.0.2.3 reboot to recovery, then flashed the 6.12.8 rom on top of 6.11.10.

Sent from my MI 5 using Tapatalk
 
  • Like
Reactions: Motox

Your-Android.de

Members
Dec 9, 2016
9
15
I rebooted back into recovery. But it still bricked. I have flashed this phone many times. I made sure TWRP was updated and everything. Yet it still ended up in a hard brick

If you are able to boot into recovery, it isn't a hardbrick. If you are just in a bootloop, flash that ROM again without SuperSU or Xposed or something else wipe cache and dalvik afterwards. If you are still in a bootloop, try to wipe the data partition.
 

viktor0610

Members
Jun 12, 2014
3
13
Does anyone know why the security patch is sooooo old for markw (Redmi 4 Prime). 2016-07-01...:confused:
My previous device (Redmi 3 Pro) was on 2016-11-01.
 

mcHammer T

Members
Aug 4, 2016
108
30
What time did the people who bricked their MI5 downloaded the rom,and from what site?

And what version before?rooted?xposed?

Maybe corrupt file,or first upload was corrupt?!

Corrupted file normally will not get passed update.

Do we know now what causes the hardbrick? Has everyone with a hardbrick wiped the system partition before updating?

Does the updater check for TWRP version before it goes ahead to perform update ? That will remove one factor, the TWRP versioning factor.
 

akrukau

Members
Dec 17, 2012
50
30
MI5 Pro: after installing with TWRP 3.0.2.3 Simcards not detected. Tried to go back to previous version but I am now in a bootloop :-(
Also reinstalling via TWRP Backup ends in bootloop.
 
Last edited:

Frankguzz

Members
Dec 9, 2016
7
13
If you are able to boot into recovery, it isn't a hardbrick. If you are just in a bootloop, flash that ROM again without SuperSU or Xposed or something else wipe cache and dalvik afterwards. If you are still in a bootloop, try to wipe the data partition.

I was replying to the comments about rebooting to recovery after the flash. I tried to do so but instead the phone wouldnt start and will not power on. It is a hard brick, no fast boot, no EDL. no light when charging, no nothing.
 

noel-forester

Members
Dec 9, 2016
5
11
1. I updated TWRP 3.0.2.3 (Twrp select install then choose image and those to recovery and done)
2. Reboot
3. Install xiaomi eu 6.12.8 in TWPR
4. Then just wipe cache/dalvik
5. Reboot

My MI5 works ok :)

thanks!
My Mi5(32G) is just work nougat!
 

kriszut

Members
Mar 29, 2016
105
40
1. I updated TWRP 3.0.2.3 (Twrp select install then choose image and those to recovery and done)
2. Reboot
3. Install xiaomi eu 6.12.8 in TWPR
4. Then just wipe cache/dalvik
5. Reboot

My MI5 works ok :)


Same here,MI5 64GB

BEFORE on 6.12.1 with Supersu 2.78(NOT SR5) and xposed by solarwarez (xposed-v86-sdk23-arm64-Miui)
 

Manoj.Rollo

Members
Nov 21, 2016
21
15
Hi guys!
Thanks to the team for this release
...on redmi 4 prime via TWRP it gives me an ERROR 7. I made WIPE cache e dalvik before to install the update but then it returns me the error..
I flashed successfully the other two release, but this time I can't...any fix or solutions without wiping everything?
 

Zlenci

Members
Jun 26, 2016
16
13
Installed on mi5, no issues so far.

Ingbrzy, thanks for your awesome service!

P.S. change gemini Android Version to 7.0 in the table above.
 

Your-Android.de

Members
Dec 9, 2016
9
15
I was replying to the comments about rebooting to recovery after the flash. I tried to do so but instead the phone wouldnt start and will not power on. It is a hard brick, no fast boot, no EDL. no light when charging, no nothing.
Ah...okay. Than i have misunderstood that.
 
Status
Not open for further replies.

Similar threads