Ok, then I got it wrong.I dont understand, You're talking now about MIUI 12.. but I told You , i'am still on MIUI11 yet , I came from CN , then I most FORMAT EVERYTHING to go on MIUI11 EU, after that TWRP has troubles, I think MIUI11 EU , makes also as MIUI12 You're talking about, an encrytion, so my TWRP is seeing all encrypted files in my DATA OR INTERNAL STORAGE >> 0 , ANYWAY, did You find any bugs , errors on MUI12 BETA YET? IS IT A REASONABLE " DALY STABLE?
Only the language was changed, would that have worked before?Ok, then I got it wrong.
isnt working at the mi9 pro 5g toodoesnt work in mi10 series. tested it
did you format data before flashing new rom?Hello guys,
I bricked my Mi 8, ROM global V11.0.4.0.QEAMIXM + I've installed TWRP 3.3.1-2-dipper.img and flash the xiaomi.eu_multi_MI8_20.4.30_v12-10.zip
Something wrong in what I did?
Thank you
Yep I forget to write this, I did a factory reset.did you format data before flashing new rom?
you have to format data via twrp before flashing the rom...not a factory reset at the rom...Yep I forget to write this, I did a factory reset.
I will try to install the ROM via Miflash, hope it's work
Yes, you didn't "Format Data" in TWRP (button's name in Wipe menu), it's mandatory.Hello guys,
I bricked my Mi 8, ROM global V11.0.4.0.QEAMIXM + I've installed TWRP 3.3.1-2-dipper.img and flash the xiaomi.eu_multi_MI8_20.4.30_v12-10.zip
Something wrong in what I did?
Thank you
No, it's EOL.hi guys i see some videos of Redmi 4x miui 12 china beta and
also one is xiaomi.eu_multi_HM4X_20.4.30_v12-9
and on both videos it has android 9
so i ask its is true both or fake ?
if yes and have android 9 will xiaomi eu support again redmi 4x ?
05-06 13:25:54.415 31701 31701 E InputEventReceiver: Exception dispatching input event.
05-06 13:25:54.415 31701 31701 E MessageQueue-JNI: Exception in MessageQueue callback: handleReceiveCallback
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: java.lang.IllegalStateException: Invalid tracker: plataforma
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.systemui.statusbar.phone.VelocityTrackerFactory.obtain(Unknown Source:76)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.systemui.statusbar.phone.PanelView.initVelocityTracker(Unknown Source:11)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.systemui.statusbar.phone.PanelView.onInterceptTouchEvent(Unknown Source:321)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.systemui.statusbar.phone.NotificationPanelView.onInterceptTouchEvent(Unknown Source:103)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewGroup.dispatchTouchEvent(Unknown Source:72)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewGroup.dispatchTransformedTouchEvent(Unknown Source:58)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewGroup.dispatchTouchEvent(Unknown Source:309)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.systemui.statusbar.phone.StatusBarWindowView.dispatchTouchEvent(Unknown Source:309)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.View.dispatchPointerEvent(Unknown Source:9)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(Unknown Source:25)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(Unknown Source:21)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.deliver(Unknown Source:21)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.onDeliverToNext(Unknown Source:4)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.forward(Unknown Source:0)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$AsyncInputStage.forward(Unknown Source:10)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.apply(Unknown Source:2)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$AsyncInputStage.apply(Unknown Source:7)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.deliver(Unknown Source:25)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.onDeliverToNext(Unknown Source:4)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.forward(Unknown Source:0)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.apply(Unknown Source:2)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$InputStage.deliver(Unknown Source:25)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl.deliverInputEvent(Unknown Source:63)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl.doProcessInputEvents(Unknown Source:69)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl.enqueueInputEvent(Unknown Source:34)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(Unknown Source:65)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.view.InputEventReceiver.dispatchInputEvent(Unknown Source:202)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.os.MessageQueue.nativePollOnce(Native Method)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.os.MessageQueue.next(Unknown Source:17)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.os.Looper.loop(Unknown Source:67)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at android.app.ActivityThread.main(Unknown Source:98)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at java.lang.reflect.Method.invoke(Native Method)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
05-06 13:25:54.416 31701 31701 E MessageQueue-JNI: at com.android.internal.os.ZygoteInit.main(Unknown Source:275)
05-06 13:25:54.416 31701 31701 D AndroidRuntime: Shutting down VM
Don't know.when redmi 5 plus getting miui 12 update??
Format data causes no brick but removes encryption.So...
Some guys tells you to not format data cause it can brick the phone.
Some guys say you must format data to install the rom...
Which one is it? I still have an encrypted partition.
And if I want to keep encryption? What's the procedure?Format data causes no brick but removes encryption.
Same for me. Mi9In whatsapp (Second one created by dual apps), no matter what permission you allowed, the contact list needs to be refreshed every time!
Tile icons in bar won't respond well, you have to tap on them some times to act!
MI9 8/128
It will be encrypted again after you flash new romAnd if I want to keep encryption? What's the procedure?
You have Mi Mix 4 in your signature. This wasn´t released untli today. Is it a joke or a hope?I meant a new ROM could come, it doesn't always have to be that way. My MAX3 got 2 last week and none this week.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation