MULTI 6.3.17


Status
Not open for further replies.
Dear all,

I got extremely confused with either weekly or stable release, to the point I almost commit suicide today. Ok, I own a Redmi 2 device 2Gb/16Gb (model 2014813 I guess). I saw that the current weekly release is 6.3.17. Very nice. But I decided I wanted to install an stable version instead of the beta one. So I went to Stable version repositories. First issue...I see there 4 different folders, from Miuiv6, 7, 7.1 and 7.2. I assume I'm already under Miui v7....but which one should I choose? There is not anything that closely matches the 6.3.17 version. Is this number refering to the Miui version, to the weekly version or to what exactly? I did not see any files for Redmi 2 (2014813) under the 7.2 folder, so I checked under the 7.1 folder. In there I find the following:

xiaomi_eu_multi_HM2014813_v7-1-2-0-KHJCNCK-v7-4-4-zip

Which I assume must be the right file for my Redmi 2. However it is from Jan 26, so to which version corresponds? Is it an older version compared to the weekly 6.3.17?? Anyway, I tried to install it on my device, via the Updater...reboot..and PROBLEMS. It did not work properly at all. I could not even open the Settings neither the File manager, etc. Somehow I have managed to recover my phone, but my question is, what did I do wrong? How the f*** do I install an STABLE version for Redmi 2 and which one and where should I download it from?

Thanks
 
I don't understand why there's SuperLuminal Recovery for Mi 4c. It automatically allows system modifications and cause system to deox apps each time you reboot from it. Cofface 2.8.7.0 was perfect :(

cc @ingbrzy @graw2
 
nicoff said:
I don't understand why there's SuperLuminal Recovery for Mi 4c. It automatically allows system modifications and cause system to deox apps each time you reboot from it. Cofface 2.8.7.0 was perfect :(

cc @ingbrzy @graw2
Click to expand...
cofface didn't work on some Mi4c devices and caused touchscreen issue... this one works for all...
 
ingbrzy said:
cofface didn't work on some Mi4c devices and caused touchscreen issue... this one works for all...
Click to expand...

Ok got it, I had serious problems with 3.0.0 but with cofface 2.8.7.0 all was good. It just had 1-2 sec of unresponsive touchscreen rarely.
There's SuperLuminal 3.0.0-2 for Mi 4c btw.

P.S. When I tried to put a Material Splashscreen in the 2.8.7.0 I had unresponsive touch issue, Your Material 2.8.7.0 without splashscreen was perfect.
Maybe these guys put splashscreens on 2.8.7.0 by cofface.
 
Last edited:
  • Like
Reactions: mendocino
javiguzzz said:
Dear all,

I got extremely confused with either weekly or stable release,...
Click to expand...
Weekly version are named after its date... For example, 6.3.11 is 2016 March 11;

Stable, I'm not sure, but I think in a 7.1.2, 7.1 is the version of miui, and 2 is the month it was released (someone correct me if I'm wrong).

Enviado do meu Redmi 2 (2014813)
 
  • Like
Reactions: Stefano131270
Hello.
On the MI2S there is a problem in the contact application, when I want to change a profile picture of a contact, I crop a picture but when I make "ok" , the picture in the square is not what I've cropped.. Hard to explain but simple there is a bug whith the select picture option.
Also on the new gallery, the choice of sort of images dont stay in memory, I have to choice every time "sort by name".
 
  • Like
Reactions: hector_yo
tonirai said:
Weekly version are named after its date... For example, 6.3.11 is 2016 March 11;

Stable, I'm not sure, but I think in a 7.1.2, 7.1 is the version of miui, and 2 is the month it was released (someone correct me if I'm wrong).

Enviado do meu Redmi 2 (2014813)
Click to expand...
I think for the Stable the first number represents the MIUI version, the numbers later, the version number, I do not think that the month is a number, but as you I have doubts! Small curiosity, but interesting
 
Akune Media said:
Mi Note virgo still stuck in TWRP recovery when update new ROM.
I couldn't update 6.3.10 as well so I've waited for 6.3.17 in hope to be fine, but it's still the same.
I know your hardwork but can you show me a way to get out of this trouble? I already in 6.3.3 and TWRP recovery.
Click to expand...
I have the same on mi 3 cancro. I installed the recovery from cyanomod for cancro in fastboot mode and then i can install eu miui cancro rom. Problem is system unmountable in twrp. Look if cyanomod recovery exists for your device. Don't mention the errors after install. After rebooting i have the new eu miui rom each week. Hope someone can give a permanent solution so i don't have to upgrade each week this way.
 
Last edited:
I have install Hermes ROM.... at first boot device have a reboot after 3 minutes... now it is ok.... I test WIFI very fast, 4g test is OK.
I test for two days battery drain... then I give my feedback for RN2 users.
 
  • Like
Reactions: junkname and Stefano131270
On Mi4 the data usage panel is in English but I've set Italian.
Spotify after 15 - 20 min goes in stop it self and I don't know why!

Inviato dal mio MI 4W utilizzando Tapatalk
 
Installed on Mi pad 2, changing from Miui 7.2.1 Chinese stable. Everything seems to be working fine. Thank you very much for this.

Unfortunately some apps still don't work. Amazon Kindle and MX player so far.
 
Last edited:
Hello ... As I said in the posts before, I can't update leo because (am I the only one? :D) I have TWRP 3.0.0.0 -> installed by the last week update ... what is the "easy" way to flash TWRP 2.8.6.0 for leo without any loss of data or reset the phone ?! .. thank you guys !
 
Redmi note 3 kenzo works awesomely after flash/root!!! Feels so good to have this FREEDOM again! Will report back if I find bugs! I dont have 4G but that is because I have old SIMcard (can live with that for now). BT works! (i5 plus whristband)

THANK YOU to all who managed to crack the official rom! I'm sooo HAPPY!
 
[QUOTE="Aku
Please help, my virgo stuck at this. What should I do?
I tried to flash fastboot China Dev ROM and re-installed TWRP to instal Multi-Rom but it still be like this[/QUOTE]

Once again my story... I have ecaxtly the same Error on mi, 3 cancro. What i do is flashing in fast boot mode the cyanomod recovery. Then into the cyanomod recovery i flash the weekly eu cancro miui rom. It gives some errors at the end but after reboot i have each time the new eu miui rom installed. Then i flash supersu.Every week i have to repeat this scenario to update. Problem is in twrp system is not mountable but in cyanomod recovery it is mountable. Perhaps someone can edit the cyanomod recovery so the errors don't appear anymore. But it doesn't do anything wrong with the eu miui rom.
I suggest to look if there is a cyanomod recovery available for your device and try.
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
284
Views
111K
HyperOS
AndyLis
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
281K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
42K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
39K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
44K
HyperOS
KGVER
KGVER
Top Bottom
Back