MULTI 7.1.19/20


Do you like this MIUI version?

  • Total voters
    517
Status
Not open for further replies.
Hey guys ! i need some help here . I have been using my mi5 with the official global dev rom. unlocked my bootloader via xiaomi's unlock method and then went back to official stable rom. now that the mi5 have received nougat "almost stable" (or stable, im not sure) i wanted to move onto this rom . i installed the latest twrp (3.0.2-3) and then flashed 6.11.10 as mentioned in the installation guide but here's the thing : it never ends ! i waited for like 40 minutes and the bar was completely filled with the blue bar .. so i had to force the shutdown of the device and obviously it didn't boot anymore. so i flashed it with miflash the official global stable rom and it booted ... so i decided to flash everything again to see if this time was going to work but it bricked the device again :/ . i wiped cache, dalvik and data the first brick. The 2nd one i wiped cache, dalvik, data and system .. any suggestions :/? (also worth to mention is that i tried to update to official dev rom via updater and it says "unable to verify, you're allow to....etc") Thanks in advance
 
Redmi Note 3 Pro users : What SOT are you getting on this? And whats the difference between this ROM and official MIUI ROM Global ??

Sent from my Redmi Note 3 using Tapatalk
 
Mi 5 VoLTE working but dial tones are not transferred to the receiving end during the call and can't use dialpad. Disabling VoLTE enabled option prior to the call works.

Sent from my MI 5 using Tapatalk
 
Xiaomi mi5s - 7.1.19/20

VOLTE not working since the first day
TouchScreen intermittent not working
 
VoLTE is malfunctioning. Sending/Receiving calls hanged up after 90 seconds.
It seems like there's no SIP update signal after call set up. '90 seconds' is same time as a limit for SIP update retry.
 
Reforcus fc on Mi 5s plus, vietnamese
dd2371258db7ee9f2712ed23a0def137.jpg


Gửi từ MI 5s Plus của tôi bằng cách sử dụng Tapatalk
 
Hi. I use Mediatek SmartDevice app to connect my Aiwatch C5 to my phone via Bluetooth.
With 7.1.19/20, my ap crashes. This is the text I get :

java.lang.IllegalStateException: Bad magic number for Bundle: 0x2f0068
at android.os.Parcel.readException(Parcel.java)
at android.os.Parcel.readException(Parcel.java)
at com.google.android.gms.internal.jt$a$a.a(Unknown Source)
at com.google.android.gms.internal.lv.a(Unknown Source)
at com.google.android.gms.internal.jl.N(Unknown Source)
at com.google.android.gms.internal.jl$f.onServiceConnected(Unknown Source)
at com.google.android.gms.internal.jn$a$a.onServiceConnected(Unknown Source)
at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java)
at android.os.Handler.handleCallback(Handler.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)

Any help please ?
 
I love this version, because the battery consumption is verly low. The only bug on Mi%S i´ve found is, that i´m unable to send pics directly from gallery via mail.
 
  • Like
Reactions: Dr.MTR
sbor-si said:
4 hours SOT, 1 day between charging. With this latest version and radon 3.6 kernel. Still high percent of Android and Android System.
Click to expand...
I am on Resurrection Remix now with 3.6 kernel ..I guess I am ok with this as I am getting 6Hours SOT..

Sent from my Redmi Note 3 using Tapatalk
 
Mr.KiLLeR said:
Redmi Note 3 Pro users : What SOT are you getting on this? And whats the difference between this ROM and official MIUI ROM Global ??

Sent from my Redmi Note 3 using Tapatalk
Click to expand...
7-8 hours SOT, on latest 7.1.19. Go for xiaomi.eu
 
Mr.KiLLeR said:
Which Kernel are u using??

Sent from my Redmi Note 3 using Tapatalk
Click to expand...
I just unlocked bootloader on the Redmi Note 3 Pro, and from global developer, moved to xiaomi.eu developer... Didn't touch anything else - so I guess it's defoult xiaomi.eu installation (don't have the phone at moment to see kernel version).
 
  • Like
Reactions: Mr.KiLLeR
mnikolce said:
I just unlocked bootloader on the Redmi Note 3 Pro, and from global developer, moved to xiaomi.eu developer... Didn't touch anything else - so I guess it's defoult xiaomi.eu installation (don't have the phone at moment to see kernel version).
Click to expand...
Ok I guess I have to test it now ... Will flash it soon ...

Sent from my Redmi Note 3 using Tapatalk
 
Here is bug report for Redmi Pro if KLO bug report crashed
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/omega/omega:6.0/MRA58K/7.1.19:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 2652, tid: 2652, name: i.klo.bugreport >>> com.miui.klo.bugreport <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'art/runtime/java_vm_ext.cc:440] JNI DETECTED ERROR IN APPLICATION: java_class == null'
x0 0000000000000000 x1 0000000000000a5c x2 0000000000000006 x3 0000000000000000
x4 0000000000000000 x5 0000000000000001 x6 0000000000000000 x7 0000000000000000
x8 0000000000000083 x9 0000000000019d00 x10 00000000034cec98 x11 00000000034cedd8
x12 0000000000000000 x13 0000007fa2c7e000 x14 0000000000000000 x15 0000000000000000
x16 0000007fa2c70570 x17 0000007fa2c01c2c x18 0000007fa2c81f50 x19 0000007fa3088380
x20 0000007fa30882c0 x21 0000000000000000 x22 0000000000000006 x23 0000007f9f23c400
x24 0000007f9efd9d00 x25 0000000000000000 x26 0000007f9efe9000 x27 0000000000000000
x28 0000007f9f23c400 x29 0000007fe48e3070 x30 0000007fa2bff3c8
sp 0000007fe48e3070 pc 0000007fa2c01c34 pstate 0000000020000000

backtrace:
#00 pc 000000000006ac34 /system/lib64/libc.so (tgkill+8)
#01 pc 00000000000683c4 /system/lib64/libc.so (pthread_kill+68)
#02 pc 0000000000023ae4 /system/lib64/libc.so (raise+28)
#03 pc 000000000001e284 /system/lib64/libc.so (abort+60)
#04 pc 0000000000432280 /system/lib64/libart.so (_ZN3art7Runtime5AbortEv+324)
#05 pc 0000000000136204 /system/lib64/libart.so (_ZN3art10LogMessageD2Ev+3136)
#06 pc 000000000030e1a8 /system/lib64/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+2288)
#07 pc 000000000030e774 /system/lib64/libart.so (_ZN3art9JavaVMExt9JniAbortFEPKcS2_z+224)
#08 pc 000000000034cc64 /system/lib64/libart.so (_ZN3art3JNI21RegisterNativeMethodsEP7_JNIEnvP7_jclassPK15JNINativeMethodib+4528)
#09 pc 0000000000001f40 /system/lib64/libklobugreport_jni.so (_Z55register_com_miui_klo_bugreport_AutoDebugProfileProcessP7_JNIEnv+68)
#10 pc 0000000000001a6c /system/lib64/libklobugreport_jni.so (JNI_OnLoad+108)
#11 pc 000000000030f450 /system/lib64/libart.so (_ZN3art9JavaVMExt17LoadNativeLibraryEP7_JNIEnvRKNSt3__112basic_stringIcNS3_11char_traitsIcEENS3_9allocatorIcEEEEP8_jobjectPS9_+1428)
#12 pc 00000000003ad9e4 /system/lib64/libart.so (_ZN3artL18Runtime_nativeLoadEP7_JNIEnvP7_jclassP8_jstringP8_jobjectS5_+296)
#13 pc 00000000028fbb8c /data/dalvik-cache/arm64/system@framework@boot.oat (offset 0x2605000)


Poslano sa mog Redmi Pro koristeći Tapatalk
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
Replies
170
Views
62K
HyperOS
Shimmy
S
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
268K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
38K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
42K
HyperOS
KGVER
KGVER
Top Bottom
Back