MULTI 6.2.25


Status
Not open for further replies.
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?
 
graw2 said:
I have already installed that latest TWRP 3.0.0-1 and I am still testing. All function work well. No issue so far...

Sent from my MI 2S using Tapatalk
Click to expand...
Did you update it from recovery? We can flash it via updater or flashify too?
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
716
Views
340K
HyperOS
Eclipse1991
E
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
332K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
44K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
44K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
53K
HyperOS
KGVER
KGVER
Top Bottom
Back