MULTI 6.2.25


Status
Not open for further replies.
jopeko said:
Hi, i installed xiaomi.eu_multi_libra_6.2.25_v7-5.1.zip on my mi4c, but the included TWRP version gave me 2 problems:
1) when booting into TWRP recovery - after some times no touch input is accepted
2) cannot access attached usb stick for backup / restore
Flashing the "New-cofface_twrp_recovery.img" version from http://en.miui.com/thread-169401-1-1.html solved both problems.
Is there maybe a better TWRP version?
Click to expand...

Here's TWRP 3.0 for Mi 4c .

http://en.miui.com/thread-230286-1-1.html
 
Last edited:
Someone could help me and confirm this bugs in Miui Official english forums so chinese MIUI developers will discuss it and maybe quickly fix them.
Thanks guys, let's make this rom better...


Please, confirm the bug. Clicking on "CONFIRM" button in the first post. Thanks :)

Telegram notification bug http://en.miui.com/thread-172094-1-1.html
Blank screen Skype bug http://en.miui.com/thread-211719-1-1.html
Frontal camera flickering in Skype bug http://en.miui.com/thread-211718-1-1.html
Inbox not completely recognized by the system bug http://en.miui.com/thread-207203-1-1.html
Can't put names with space in battery profile bug http://en.miui.com/thread-188712-1-1.html
Choose apps automatically doesn't work with Permission Manager off http://en.miui.com/thread-216572-1-1.html
Can't save as PDF in MIUI http://en.miui.com/thread-215602-1-1.html
Cleaner definitions won't update http://en.miui.com/thread-211722-1-1.html
Impossible to revert battery mode from performance to balanced http://en.miui.com/thread-214739-1-1.html
 
  • Like
Reactions: laueugen and the_maker
ingbrzy said:
CHANGELOG

[Lockscreen, Status Bar, Notification Bar]
Fix - Viewing Daily lock screens sometimes led to black screen (02-23)

Big change in installation process of our ROMs (Must read it, otherwise you will cry on forum here and we will dont care):
- Xiaomi forced us to generate own keys for signing ROMs if we want continue to use their OTA service (again calling it "security improvement"). That means, our ROMs will not be possible to install via MiRecovery anymore (even on old devices like Mi2 or Redmi 1S) but only via TWRP/CWM...
- Our ROMs now contains TWRP which will install it automatically and overwrite your MiRecovery (If you still use it)
- For manual TWRP installation, we made a flashable ZIPs here so just install it via Updater up like any other update zip... (if it will fail, just unzip it and flash via Flashify app)
- Version 6.2.25 still can be installed via MiRecovery but it will overwrite it to TWRP
- Next versions will require TWRP for all devices

Mi3/4 / Mi4c / MiNote PRO
(Root doesn't work, install SuperSU 2.50 on Mi4c/MiNotePRO via TWRP, and SuperSU 2.65 on Mi3/4/MiNote)


Xiaomi Hongmi HM2013023 and Xiaomi Mi3TD will no more get updates from us... R.I.P.
Click to expand...

I've tried to install this update via TWRP but I've got an error:
2el8hsx.jpg


After that I had no OS installed and I had to flash the stock recovery and install the ROM with that. Do you know why that happens? Every time I try to install MIUI via TWRP I get that error.
 
kisjuhos said:
Firsf of all thanks for your work on this ROM!
I have a RN2 (prime) with TWRP "2.8.7.0 by cloud" installed. Can I update TWRP to 3.0 from my 2.8.7.0 TWRP with the following zip? Or I have to do it over USB as before?
https://www.androidfilehost.com/?fid=24421527759888153
Second question is there any advatage of 3.0? Or I can stay on 2.8.7.0?
Click to expand...


Next ROM update your downloaded recovery will be overwritten again, so no advantage because you will have to flash it every week
 
nicoff said:
Next ROM update your downloaded recovery will be overwritten again, so no advantage because you will have to flash it every week
Click to expand...

I thougt only 6.2.25 will change the recovery but the later ROMs wont. I consider to skip 6.2.25 because of some bugs mentioned (slow chaging, decreased CPU clock, missing kernel version, etc).
 
Matteo C said:
Updated my Redmi Note 2. TWRP was overwritten/updated to 3.0. Old TWRP backup not read by 3.0. Any advise for me?
Click to expand...
"Redmi note 2 Tool" from Google play store has option to migrate backup to 3

Wysłane z mojego Redmi Note 2 przy użyciu Tapatalka
 
kisjuhos said:
I thougt only 6.2.25 will change the recovery but the later ROMs wont. I consider to skip 6.2.25 because of some bugs mentioned (slow chaging, decreased CPU clock, missing kernel version, etc).
Click to expand...

Didn't know about this bug. Too late I guess :)
Well, every rom will have twrp.
 
kisjuhos said:
I thougt only 6.2.25 will change the recovery but the later ROMs wont. I consider to skip 6.2.25 because of some bugs mentioned (slow chaging, decreased CPU clock, missing kernel version, etc).
Click to expand...
not the case on cancro. My mi3 cpu z reports the nominal frequency as expected at 2.3GHz. It is on since 3 hours, still 99% battery. this is not an exhaustive test but I see no blocking issue so far.
 
I have a big big problem, I update my Mi4c to 6.2.25 and all was ok ,but supersu break my phone. I flash china dev 6.1.28 and and now I have bootloader blocked. I can´t update to china stable v7.1.6.0 because can´t verify info . I download another stable and nothing updates. I will update to stable so unblock recovery, so can install TWRP and xiaomi.eu libra 6.2.25 in spanish.

I don´t know why it no update to stable... I must wait another stable versión, no?

Sorry for my bad english and thanks for all work!
 
jc rey said:
Yes as you mentioned your system is out of date better is to start with a mi flash of the China development then you can update safely.



Just update twice 5.12.17 as you would do as before it will do the right partitioning.
Then update with 6.2.25 it will install twrp automatically.
Click to expand...
I tried doing it like you said but this happened:
upload_2016-2-27_16-26-25.png
 
i don't know , how i need to install this ROM on Mi4w

please help !

best regards
 
Everyone be very very careful with this update!!!
In a nutshell it would seem Xiaomi activated some deviceID/ bount to Mi Account checking with this release. And if your device was owned by someone previously who had it registered with xiaomi prior to selling it to you, but forgot to deregister it before selling it to you, you will need his/her password to activate it.

Prior to giving the phone(Mi3W) to my wife I used the device and had it connected to my Mi Account. Obviously I did not deregister it with xiaomi.com, but simply wiped it clean and gave it directly to my wife. She has no Mi Account and had not registered it with xiaomi.com. For the past 3 months I kept updating it without an issue until today.
Once I rebooted from the update the phone only displayed "This device is lost" and that its bound to an existing Mi Account and someone will be contacting me shortly. :cool: Since the partial ID I saw was the Xiaomi account id(which I thought was a phone number), the first thing that came to my mind was that someone hijacked my phone and holds it for ransom similar to the Linux mint website hack last week(where someone stole the website and uploaded compromised images of the distros). Immediately I logged into my Mi Account and by chance(URL at the top) found that my xiaomi ID was actually the one partially displayed on the phone. Then I input my password for my Mi Account and the device got activated.
So I got out with only a scare since I was the previous owner of the phone, but if you bought the device second hand and the previous owner did not deregister it prior to selling it to you(and you do not have it registered with Xiaomi), you might have problems with this release!
 
Last edited:
  • Like
Reactions: fernandodelvalle, davidesocci, George TIU and 2 others
Andrea Zerbini said:
I've tried to install this update via TWRP but I've got an error:
2el8hsx.jpg


After that I had no OS installed and I had to flash the stock recovery and install the ROM with that. Do you know why that happens? Every time I try to install MIUI via TWRP I get that error.
Click to expand...
I guess you just performed a wipe before flashing the ROM.
After wipe, just reboot to recovery and you'll be able to flash the ROM without errors.

Sent from my Mi 4i using Tapatalk
 
zsombi said:
take a deep breath and realax, or do it yourself :)
Click to expand...
I'd guess this was meant ironically, but supposing that I really did wish to try repackaging my own ROM - could you point out some good build procedure?


Sent from my Redmi Note 2 using Tapatalk
 
jc rey said:
Yes as you mentioned your system is out of date better is to start with a mi flash of the China development then you can update safely.



Just update twice 5.12.17 as you would do as before it will do the right partitioning.
Then update with 6.2.25 it will install twrp automatically.
Click to expand...


Rafaider said:
I tried doing it like you said but this happened:
View attachment 11487
Click to expand...
I went to my phone, got into the TWRP and in the partitions it sais that the system has a 0 MB size. Should I resize it ? If so to what value?
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.3.25
Replies
169
Views
65K
HyperOS
c4rdix
C
ingbrzy
  • Locked
HyperOS 1.0 24.3.18
Replies
115
Views
42K
HyperOS
StrangerFox
S
ingbrzy
  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
47K
HyperOS
Kwanice
K
ingbrzy
  • Sticky
HyperOS 1.0 24.4.15/16
Replies
130
Views
23K
HyperOS
Iain_B
Iain_B
ingbrzy
  • Locked
HyperOS 1.0 24.3.11
Replies
128
Views
45K
HyperOS
cyclonemax
C
Top Bottom
Back