MIUI 11 MIUI 11.0 STABLE RELEASE


Status
Not open for further replies.
Redmi Note 7 latest stable MIUI 11 EU Android 10, split screen not working, any solution? or should wait for fix? thx
 
Last edited:
djahugen said:
I updated from weekly rom to stable on my Mi8 explorer, I did a wipe off me cache etc and I reinstalled all sorts from backup on Google and all worked just fine, till this morning the icon of my WhatsApp disappeared, I still get messages and notifications, but the icon is nowhere to be found, if I open appstore and search for WhatsApp I just get the option to open WhatsApp (that is a really long workaround to send a message )

Verstuurd vanaf mijn MI 8 Explorer Edition met Tapatalk
Click to expand...
I still have the problem, I deleted the app, reinstalled it and it worked again for about a week, yesterday it started disappearing again.. if I restart my phone it reappears at it's original position, to stay there for about day.. (I think it disappears when the local backup is made)

Verstuurd vanaf mijn MI 8 Explorer Edition met Tapatalk
 
Ting Ting said:
Some are not encrypted if coming from stable pie
Make sure format data,not wipe data.
Since it android 10,you might need update your twrp.
Orangefox did release latest for targeting miui android 10,you should try and maybe encrypted issue solved.

And noooo,splitscreen not working
I was planning to flash now
Click to expand...
yes i did format data a couple of times ( not wipe data ). And I got no encrypted after that but when I reboot to recovery after the forst boot from the clean flashed ROM I got encrypted again. Did a couple of times and still persist.

And yes, Split Screen is not working on lavender this time.
 
  • Like
Reactions: Ting Ting and Fifamaniac
mackyme001 said:
yes i did format data a couple of times ( not wipe data ). And I got no encrypted after that but when I reboot to recovery after the forst boot from the clean flashed ROM I got encrypted again. Did a couple of times and still persist.

And yes, Split Screen is not working on lavender this time.
Click to expand...

Either on the split screen problem... I have writhen also yesterday about the laggy problem on the same model after update from android 9 to 10...
 
Camera crashes on Mi 10 pro global with the latest ROM http://xiaomi.eu_multi_mi10pro_v11.0.17.0.qjacnxm_v11-10.zip/. Dirty flashed over previous release

Code: 
05-01 10:07:42.020 23011 23011 E QSPOWER : A t7b6ae46ed0 /local/mnt/workspace/pcgbait/docker.ci.tmp/build/aarch64-android-clang6.0/SecondParty/qspower/src/qspower/core/src/internal/soc/qti_soc_freqs.h:27 Unable to read from /sys/class/kgsl/kgsl-3d0/gpu_available_frequencies                                                                                                                                                     
05-01 10:07:42.068 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.068 23011 23011 E linker  : normalize_path - invalid input: "\tools\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.069 23011 23011 E linker  : normalize_path - invalid input: "E", the input path should be absolute
05-01 10:07:42.069 23011 23011 E linker  : normalize_path - invalid input: "\Working\Code\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.069 23011 23011 E linker  : normalize_path - invalid input: "E", the input path should be absolute
05-01 10:07:42.069 23011 23011 E linker  : normalize_path - invalid input: "\Working\Code\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "\tools\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "E", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "\Working\Code\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "E", the input path should be absolute
05-01 10:07:42.070 23011 23011 E linker  : normalize_path - invalid input: "\Working\Code\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.113  7672  7676 E subsystem_ramdump: Uevent msg overflow; ignoring
05-01 10:07:42.118 23011 23011 E CHIWATERMARK: ChiNodeEntry():532 WaterMarkNode ChiNodeEntry
05-01 10:07:42.118 23011 23011 E CHIWATERMARK: WaterMarkNodeQueryVendorTag():154 WaterMarkNodeQueryVendorTag
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "\android_tools\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "\User\user\AppData\Local\Android\Sdk\ndk-bundle-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "\User\user\AppData\Local\Android\Sdk\ndk-bundle-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.122 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.123 23011 23011 E linker  : normalize_path - invalid input: "\android_tools\android-ndk-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.123 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.123 23011 23011 E linker  : normalize_path - invalid input: "\User\user\AppData\Local\Android\Sdk\ndk-bundle-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.123 23011 23011 E linker  : normalize_path - invalid input: "D", the input path should be absolute
05-01 10:07:42.123 23011 23011 E linker  : normalize_path - invalid input: "\User\user\AppData\Local\Android\Sdk\ndk-bundle-r18b\toolchains\llvm\prebuilt\windows-x86_64\lib64\clang\7.0.2\lib\linux\aarch64", the input path should be absolute
05-01 10:07:42.138 23011 23011 E CHI_NODE_MIBOKEH: ChiNodeEntry():537 MiBokeh, ChiNodeEntry func=ChiNodeEntry, version=5
05-01 10:07:42.139 23011 23011 E libc++abi: terminating with uncaught exception of type std::bad_cast: std::bad_cast
05-01 10:07:42.139 23011 23011 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 23011 (android.hardwar), pid 23011 (android.hardwar)
05-01 10:07:42.171 23035 23035 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-01 10:07:42.171 23035 23035 F DEBUG   : Build fingerprint: 'Xiaomi/cmi/cmi:10/QKQ1.191117.002/V11.0.17.0.QJACNXM:user/release-keys'
05-01 10:07:42.171 23035 23035 F DEBUG   : Revision: '0'
05-01 10:07:42.171 23035 23035 F DEBUG   : ABI: 'arm64'
05-01 10:07:42.172 23035 23035 F DEBUG   : Timestamp: 2020-05-01 10:07:42+0200
05-01 10:07:42.172 23035 23035 F DEBUG   : pid: 23011, tid: 23011, name: android.hardwar  >>> /vendor/bin/hw/android.hardware.camera.provider@2.4-service_64 <<<
05-01 10:07:42.172 23035 23035 F DEBUG   : uid: 1047
05-01 10:07:42.172 23035 23035 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
05-01 10:07:42.172 23035 23035 F DEBUG   : Abort message: 'terminating with uncaught exception of type std::bad_cast: std::bad_cast'
05-01 10:07:42.172 23035 23035 F DEBUG   :     x0  0000000000000000  x1  00000000000059e3  x2  0000000000000006  x3  0000007fde0f6b90
05-01 10:07:42.172 23035 23035 F DEBUG   :     x4  fefefefefefeff47  x5  fefefefefefeff47  x6  fefefefefefeff47  x7  7f7f7f7f7f7f7f7f
05-01 10:07:42.172 23035 23035 F DEBUG   :     x8  00000000000000f0  x9  4647aa7b9319fb01  x10 0000000000000001  x11 0000000000000000
05-01 10:07:42.172 23035 23035 F DEBUG   :     x12 fffffff0ffffffdf  x13 000000005eabd8ce  x14 00081b3157c27800  x15 000039e55ed4f67a
05-01 10:07:42.172 23035 23035 F DEBUG   :     x16 0000007b68c468c0  x17 0000007b68c22a40  x18 000000000000000a  x19 00000000000059e3
05-01 10:07:42.172 23035 23035 F DEBUG   :     x20 00000000000059e3  x21 00000000ffffffff  x22 00000000ffffff80  x23 00000000ffffffc8
05-01 10:07:42.172 23035 23035 F DEBUG   :     x24 0000007fde0f6df0  x25 0000007fde0f6cc0  x26 0000007fde0f6d00  x27 0000007ab8ad02c0
05-01 10:07:42.172 23035 23035 F DEBUG   :     x28 0000007ab8acffd0  x29 0000007fde0f6c30
05-01 10:07:42.172 23035 23035 F DEBUG   :     sp  0000007fde0f6b70  lr  0000007b68bd40c4  pc  0000007b68bd40f0
05-01 10:07:42.194 23035 23035 F DEBUG   :
05-01 10:07:42.194 23035 23035 F DEBUG   : backtrace:
05-01 10:07:42.194 23035 23035 F DEBUG   :       #00 pc 00000000000830f0  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 54fe8fe20e3310b8b5134c7771015f99)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #01 pc 000000000011f250  /vendor/lib64/libmialgo_ie_preview.so (BuildId: 1f9099b4dcec5c6f6b3bc27d63f490a54982c5c1)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #02 pc 000000000011f3b0  /vendor/lib64/libmialgo_ie_preview.so (BuildId: 1f9099b4dcec5c6f6b3bc27d63f490a54982c5c1)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #03 pc 000000000011c1cc  /vendor/lib64/libmialgo_ie_preview.so (BuildId: 1f9099b4dcec5c6f6b3bc27d63f490a54982c5c1)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #04 pc 000000000011b8f0  /vendor/lib64/libmialgo_ie_preview.so (BuildId: 1f9099b4dcec5c6f6b3bc27d63f490a54982c5c1)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #05 pc 000000000011b870  /vendor/lib64/libmialgo_ie_preview.so (__cxa_throw+120) (BuildId: 1f9099b4dcec5c6f6b3bc27d63f490a54982c5c1)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #06 pc 0000000000083994  /vendor/lib64/libc++_shared.so (std::__ndk1::locale::use_facet(std::__ndk1::locale::id&) const+216) (BuildId: ef6e7301b33650c6ab99d63132badbf97c1a64a8)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #07 pc 0000000000056eb8  /vendor/lib64/libvideofilter_only.so (BuildId: 48907e8ad4b85b57d133f41e8ae95c969630584a)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #08 pc 0000000000137f0c  /vendor/lib64/libvideofilter_only.so (BuildId: 48907e8ad4b85b57d133f41e8ae95c969630584a)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #09 pc 0000000000139078  /vendor/lib64/libvideofilter_only.so (BuildId: 48907e8ad4b85b57d133f41e8ae95c969630584a)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #10 pc 0000000000028dac  /vendor/lib64/libvideofilter_only.so (BuildId: 48907e8ad4b85b57d133f41e8ae95c969630584a)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #11 pc 0000000000052358  /apex/com.android.runtime/bin/linker64 (__dl__ZL10call_arrayIPFviPPcS1_EEvPKcPT_mbS5_+276) (BuildId: 76470291f716c9af59bfe28f472b6c6d)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #12 pc 0000000000052574  /apex/com.android.runtime/bin/linker64 (__dl__ZN6soinfo17call_constructorsEv+376) (BuildId: 76470291f716c9af59bfe28f472b6c6d)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #13 pc 0000000000052480  /apex/com.android.runtime/bin/linker64 (__dl__ZN6soinfo17call_constructorsEv+132) (BuildId: 76470291f716c9af59bfe28f472b6c6d)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #14 pc 000000000003cc34  /apex/com.android.runtime/bin/linker64 (__dl__Z9do_dlopenPKciPK17android_dlextinfoPKv+2416) (BuildId: 76470291f716c9af59bfe28f472b6c6d)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #15 pc 0000000000038160  /apex/com.android.runtime/bin/linker64 (__loader_dlopen+68) (BuildId: 76470291f716c9af59bfe28f472b6c6d)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #16 pc 0000000000001020  /apex/com.android.runtime/lib64/bionic/libdl.so (dlopen+12) (BuildId: eaf850ad282e2aa45253983f09c5a3aa)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #17 pc 00000000005d2f54  /vendor/lib64/hw/camera.qcom.so (CamX::OsUtils::LibMap(char const*)+44) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #18 pc 0000000000721294  /vendor/lib64/hw/camera.qcom.so (CamX::ProbeChiComponents(CamX::ExternalComponentInfo*, unsigned int*)+4652) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #19 pc 000000000074d2f8  /vendor/lib64/hw/camera.qcom.so (CamX::HwEnvironment::GetInstance()+6056) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #20 pc 0000000000323ee8  /vendor/lib64/hw/camera.qcom.so (CamX::HAL3Module::HAL3Module()+712) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #21 pc 00000000003224c0  /vendor/lib64/hw/camera.qcom.so (CamX::HAL3Module::GetInstance()+64) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #22 pc 000000000031a5dc  /vendor/lib64/hw/camera.qcom.so (CamX::get_number_of_cameras()+76) (BuildId: cca50e3c98b3ef333568ba0e3fbeba94)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #23 pc 0000000000028598  /vendor/lib64/android.hardware.camera.provider@2.4-legacy.so (android::hardware::camera::common::V1_0::helper::CameraModule::init()+152) (BuildId: 985b8d76c47ade51882ad33d8a70e5c4)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #24 pc 0000000000019f30  /vendor/lib64/android.hardware.camera.provider@2.4-legacy.so (android::hardware::camera::provider::V2_4::implementation::LegacyCameraProviderImpl_2_4::initialize()+148) (BuildId: 985b8d76c47ade51882ad33d8a70e5c4)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #25 pc 0000000000019e84  /vendor/lib64/android.hardware.camera.provider@2.4-legacy.so (android::hardware::camera::provider::V2_4::implementation::LegacyCameraProviderImpl_2_4::LegacyCameraProviderImpl_2_4()+156) (BuildId: 985b8d76c47ade51882ad33d8a70e5c4)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #26 pc 00000000000030a4  /vendor/lib64/hw/android.hardware.camera.provider@2.4-impl.so (HIDL_FETCH_ICameraProvider+144) (BuildId: 7a5a2d4810610d204dffc12bf8b54238)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #27 pc 00000000000519a8  /system/lib64/vndk-sp-29/libhidlbase.so (_ZZN7android8hardware25PassthroughServiceManager3getERKNS0_11hidl_stringES4_ENKUlPvRKNSt3__112basic_stringIcNS6_11char_traitsIcEENS6_9allocatorIcEEEESE_E_clES5_SE_SE_+96) (BuildId: 1a9b3560209d8a8f748b136ff94e1808)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #28 pc 000000000004db04  /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::PassthroughServiceManager::openLibs(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::function<bool (void*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&)> const&)+1196) (BuildId: 1a9b3560209d8a8f748b136ff94e1808)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #29 pc 00000000000501b0  /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::PassthroughServiceManager::get(android::hardware::hidl_string const&, android::hardware::hidl_string const&)+96) (BuildId: 1a9b3560209d8a8f748b136ff94e1808)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #30 pc 000000000004eb1c  /system/lib64/vndk-sp-29/libhidlbase.so (android::hardware::details::getRawServiceInternal(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, bool, bool)+1364) (BuildId: 1a9b3560209d8a8f748b136ff94e1808)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #31 pc 00000000000154ac  /system/lib64/vndk-29/android.hardware.camera.provider@2.4.so (_ZN7android8hardware7details18getServiceInternalINS0_6camera8provider4V2_418BpHwCameraProviderENS5_15ICameraProviderEvvEENS_2spIT0_EERKNSt3__112basic_stringIcNSB_11char_traitsIcEENSB_9allocatorIcEEEEbb+204) (BuildId: 7c1c05ef95729c3d02a3df6e5d296d8f)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #32 pc 0000000000001170  /vendor/bin/hw/android.hardware.camera.provider@2.4-service_64 (BuildId: b59abc0ff66afed3a23a84879a9c4a6f)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #33 pc 00000000000010e8  /vendor/bin/hw/android.hardware.camera.provider@2.4-service_64 (main+152) (BuildId: b59abc0ff66afed3a23a84879a9c4a6f)
05-01 10:07:42.194 23035 23035 F DEBUG   :       #34 pc 000000000007e898  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 54fe8fe20e3310b8b5134c7771015f99)
05-01 10:07:42.238 23035 23035 E crash_dump64: cannot open libmiuindbg.so: No such file or directory
05-01 10:07:42.239 23035 23035 E crash_dump64: AM data write failed: Broken pipe
05-01 10:07:42.240  1217  1217 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_07
 
  • Like
Reactions: ingbrzy
ray-b said:
Redmi Note 7 latest stable MIUI 11 EU Android 10, split screen not working, any solution? or should wait for fix? thx
Click to expand...

I'm on the latest stable too. but the device always auto reboots. Have this problem with your device?

Please tell me how to fix it?
 
Kane W. said:
I'm on the latest stable too. but the device always auto reboots. Have this problem with your device?

Please tell me how to fix it?
Click to expand...

I dont have any problems at all, but before i updated to latest stable, i update my recovery first (orangefox) to orangefox 10.1_2. the only problem i have is just split screen not working.

Can you switch back (clean flash) to previous stable, just in case it will work, then update your recovery before flash to latest stable
 
ray-b said:
I dont have any problems at all, but before i updated to latest stable, i update my recovery first (orangefox) to orangefox 10.1_2. the only problem i have is just split screen not working.

Can you switch back (clean flash) to previous stable, just in case it will work, then update your recovery before flash to latest stable
Click to expand...

I update from twrp to orangefox after I installed the latest stable. (cause of twrp is encrypt)
Then now, I'm on oragefox and can I reflash latest stable without losing data
 
Last edited:
Kane W. said:
I update from twrp to orangefox after I installed the latest stable. (cause of twrp is encrypt)
Then now, I'm on oragefox and can I reflash latest stable without losing data
Click to expand...
so it still auto reboots? is your orangefox 10.1_2 ?
 
ray-b said:
so it still auto reboots? is your orangefox 10.1_2 ?
Click to expand...

1. I use twrp to update to the latest stable.
2. I update twrp to orange fox.
3. I wipe cache/davik, cache via orange fox
4. auto reboots
5. I wipe cache/davik, cache via orange fox again
6. still auto reboots
 
Hello
i am in trouble with my cc9 mi9lite
I had xiomi.eu miui11 3.26 installed with twrp 3.3.1 installed and i tried to install miui11 stable 11-10 but after install the miui starts, the home app starts but after 10 seconds it reboots.
I made a dirty flash
What can i do ?
Any suggestions?
Thank you
 
Supermax_xam said:
Hello
i am in trouble with my cc9 mi9lite
I had xiomi.eu miui11 3.26 installed with twrp 3.3.1 installed and i tried to install miui11 stable 11-10 but after install the miui starts, the home app starts but after 10 seconds it reboots.
I made a dirty flash
What can i do ?
Any suggestions?
Thank you
Click to expand...
You have to format data when switching form beta to stable,you can not dirty flash.your lucky the phone even started

Sent from my unknown using Tapatalk
 
  • Like
Reactions: LOLO9393
Hi guys, do you have an idea when the MIUI 12 is coming for us ?? they already have it on beta !!
 
Hello! I got redmi 6 pro with ARB1 and want to keep it that way. But I assume the roms by xiaomi.eu do have ARB=2... So does anyone know how to proprely flash rom via twrp without touching bootloader files (sbl1.mbn and emmc_appsboot.mbn). I think I tried just delete those 2 files from zip, but was getting some error trying to flash it, replacing files with arb1 also didn't work. So how to edit archive with rom and make it work?
upd. Deleting these 2 files from archive worked now.
 
Last edited:
Kane W. said:
1. I use twrp to update to the latest stable.
2. I update twrp to orange fox.
3. I wipe cache/davik, cache via orange fox
4. auto reboots
5. I wipe cache/davik, cache via orange fox again
6. still auto reboots
Click to expand...

there was a fix (reupload stable file), have you try to redownload the stable rom? perhaps you were using the old stable version (before fix)
 
The Stable ROM of Android 10 xiaomi.eu on Redmi Note 7 (Lavender) has some problems like:
1-The mobile is frozen when you run whatsapp, youtube or any other app.
2-The battery does not give you 5h of screen in the first cycle, then it improves.
3-the rom feels very lags and has many obstacles.
4-The system launcher is broken, it works if you close it 2 times forcibly.
 
The problem with home screen, device Redmi K30 5G, the same with EU rom v11.1.23Stable and v20.4.30Developer.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
I just updated to last stable on mi 9 lite, clean update. I have 3 problems.
1. I use always on display during the day and battery optimization at night. In the morning always on display is off and I have to turn it on manually.
2. WiFi is only 72mbps.
3. The third problem is on file explore. As you can see the screen is all dark, and I can see the info on the top.

Thanks for your hard work.
 

Attachments

  • Screenshot_2020-05-03-13-20-30-688_com.android.fileexplorer.jpg
    Screenshot_2020-05-03-13-20-30-688_com.android.fileexplorer.jpg
    209.5 KB · Views: 228
Last edited:
I am using miui eu v.11 stable rom in my note 7 pro.But i want to migrate stable to weekly update.But i have failed.After install the weekly rom it stuck on boot loop.
I tried also to fastboot the original china version of my note 7 pro but there i have faced a problem that is vendor error.
Now how can i moved to weekly from stable without facing any brick and how will fixed the vendor problem.
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Sticky
HyperOS 1.0 24.4.8/15
Replies
141
Views
33K
HyperOS
huliganboy
huliganboy
ingbrzy
  • Locked
HyperOS 1.0 24.3.25
Replies
169
Views
63K
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.11
Replies
128
Views
44K
HyperOS
cyclonemax
C
ingbrzy
  • Locked
HyperOS 1.0 24.3.4
Replies
150
Views
46K
HyperOS
Kwanice
K
Top Bottom
Back