Related
After updating to android n the lockscreen has become incredibly laggy. Is there anyway (root or no-root) to fix this?
Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
ChARCOOL said:
Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
Click to expand...
Click to collapse
Ah, okay. I might wait off a bit because I've just recently flashed my phone, and it's kinda a pain in the ass, especially since apparently I have no idea how titanium backup works lol.
ChARCOOL said:
Kudret Davudov:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
Click to expand...
Click to collapse
Hi,
I followed this through the final instructions (bold) wihtout the phone booting into android (rebooted into download once the blue install screen finished). I wasn't sure what I needed to do in TWRP once I rebooted there, so I tried flashing su-config and an sbin 2.82 sr5 supersu install - then rebooted finally into android, and the unlock lag was back.
what needs to be done once twrp flashed and user has rebooted immediately into twrp?
[edit - further experimenting suggests supersu 2.82 versions all cause pattern unlock lag, while 2.79 does not but cannot be hidden via suhide]
thanks, sure I am missing something obvious here.
DullPeon said:
Hi,
I followed this through the final instructions (bold) wihtout the phone booting into android (rebooted into download once the blue install screen finished). I wasn't sure what I needed to do in TWRP once I rebooted there, so I tried flashing su-config and an sbin 2.82 sr5 supersu install - then rebooted finally into android, and the unlock lag was back.
what needs to be done once twrp flashed and user has rebooted immediately into twrp?
[edit - further experimenting suggests supersu 2.82 versions all cause pattern unlock lag, while 2.79 does not but cannot be hidden via suhide]
thanks, sure I am missing something obvious here.
Click to expand...
Click to collapse
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags
ChARCOOL said:
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags
Click to expand...
Click to collapse
thanks. I am surprised this isn't a more common complaint - do you know if there are recent samsung models with 7.0 that don't have this issue? It seems like anyone with an affected model that tries to run suhide, for example, would run into this immediately.
alternately, does this create the same problem on 6.0?
EDIT - this thread suggests maybe (not verified) it wasn't a problem on nougat 7.1.1 as well https://forum.xda-developers.com/galaxy-j7/how-to/approach-to-rooting-7-1-1-t3709414
I have posted there to try to verify.
I just rooted my phone again with magisk using my method and i didn't got verity error and there is no lock screen lag
ChARCOOL said:
I just rooted my phone again with magisk using my method and i didn't got verity error and there is no lock screen lag
Click to expand...
Click to collapse
thanks. i have rooted with magisk recently and didn't have a lag error either - but the app I need to use for this claims to requre supersu, and in fact seems to not like magisk at all.
also regardless of the 7.1.1 question, neither of the possible phones have a 7.1.1 available.
still looking for a 3rd way to handle this and get suhide, but looks grim for now. maybe simply moving up to the latest 7.0 firmware (my current build is a u2 build from ~~october, so haven't put the U3's on due to what I read about locking the bootloader etc) would fix it. It just seems to be an uncommon problem and that makes me think that there is some way to use a samsung with 7.0 with supersu 2.82 without this issue. Otherwise the number of questions about it from samsung users should be overwhelming.
do you know if it is disabling dm verity, or disabling forced encryption, that is causing the lag? if it is dm verity, would re-enabling dm verity via adb be a work-around? (I dug around for a script to enable verity and encrypt, no dice so far).
thanks for your help.
ChARCOOL said:
Unfortunately supersu has built-in no verity patch, that is why you still get lock screen lag. I use magisk and it works perfect for me with no lags
Click to expand...
Click to collapse
follow-ups to your method -
why is it necessary to let the blue install screen process run before booting back to download to install twrp? if one just goes from download firmware and reboots to download immediately, what changes?
i played around with the no-verity-no-encrypt issue (both with the patch and with aroma su config) and it appears the no-encrypt is what is leading to the lag.
one drawback I am running into with the method above (flash firmware, run blue install screen, download-twrpflash, then immed. to recovery, then install in my case aroma & 2.82su is that i cannot mount data again in twrp once android has loaded, but that seems to be expected as it is not fully decrypting (even though it isn't encrypted, as I understand it?)
DullPeon said:
follow-ups to your method -
why is it necessary to let the blue install screen process run before booting back to download to install twrp? if one just goes from download firmware and reboots to download immediately, what changes?
i played around with the no-verity-no-encrypt issue (both with the patch and with aroma su config) and it appears the no-encrypt is what is leading to the lag.
one drawback I am running into with the method above (flash firmware, run blue install screen, download-twrpflash, then immed. to recovery, then install in my case aroma & 2.82su is that i cannot mount data again in twrp once android has loaded, but that seems to be expected as it is not fully decrypting (even though it isn't encrypted, as I understand it?)
Click to expand...
Click to collapse
Its working so well for me and you need to go to download mode after blue install because it installs csc and cleans old stuff that is why you need to do it if you don't want broken phone
Anyone wants to test multirom it seems to work fine for me so far. I've got my device encrypted and it seems to work fine still.
Flash recovery.img :https://drive.google.com/open?id=1zRny9vDBRRcqxFVjMapemZuuQhJwoYH1
Flash multirom zip : https://drive.google.com/open?id=17lXEdiWCYv_pGnNw7eKir13tZiPoQa9O
Add rom using MR menu in recovery.
In MR settings change brightness to 255.( Otherwise there is no boot screen)
ReBoot to system.
Select rom to boot
Bugs: make sure you set brightness to 255 in settings.
I've tested on my phone with live data and lost nothing.
I take no responsibility for anything that happens to yours if you test this.
This was based off the work done by Vasishath the Beryllium dev. I've used his multirom patches and changes so the credit for that goes to him. I've used his work and made it work on the Android 9.0 omnirom tree although its not finished yet as DRM is still f'd.
If sh1t goes south uninstall by using:
https://drive.google.com/open?id=1hS0XWRRh850Jh2lU6EqvkYb9Qx0sjKbj
Thanks to arifqur for the reminder that people may need this.
Kernel source: https://github.com/LineageOS/android_kernel_xiaomi_sdm845
Also can the multi rom Manager app be used to boot into the other roms?(Tried it and says like Device not supported and stuff)
Edit: Tried and added a rom but the auto boot settings are a bit confusing as I can't seem to find the setting if I want to boot into the internal rom. It has options to boot into the last booted rom or one of the secondary rom that I have installed. No setting to boot into the internal rom
Edit 2: After rebooting into recovery it is now showing the option for both internal and the secondary rom. Although thebooting into secondary rom is giving problems at the moment as it is boot looping and went back into recovery
Edit 3: First tried installing citrus-caf rom which boot looped back into recovery. Next flashed PE rom and it booted and am currently setting it up.
Edit 4: Tried installing a secondary rom by restoring a backup and it also booted fine.
Edit 5: Made the mistake of updating the Magisk from the secondary rom which was restored from a previous backup and then none of the roms would boot and go to fastboot after a while of boot looping. Since you did not post an uninstaller for the Multirom, I downloaded the one from the Beryllium thread and removed the asserts line and removed the Multirom and again restored from a previous backup and was good to go.
Again went back and re-installed Multirom and added the latest PE build and set it up. So every thing is nice and dandy now.
Better post an un-installer for Multirom in this thread.
I am attaching the Uninstaller that I used here till you post one
Exciting stuff man. You are awesome dude
arifqur said:
Also can the multi rom Manager app be used to boot into the other roms?(Tried it and says like Device not supported and stuff)
Edit: Tried and added a rom but the auto boot settings are a bit confusing as I can't seem to find the setting if I want to boot into the internal rom. It has options to boot into the last booted rom or one of the secondary rom that I have installed. No setting to boot into the internal rom
Edit 2: After rebooting into recovery it is now showing the option for both internal and the secondary rom. Although thebooting into secondary rom is giving problems at the moment as it is boot looping and went back into recovery
Edit 3: First tried installing citrus-caf rom which boot looped back into recovery. Next flashed PE rom and it booted and am currently setting it up.
Edit 4: Tried installing a secondary rom by restoring a backup and it also booted fine.
Edit 5: Made the mistake of updating the Magisk from the secondary rom which was restored from a previous backup and then none of the roms would boot and go to fastboot after a while of boot looping. Since you did not post an uninstaller for the Multirom, I downloaded the one from the Beryllium thread and removed the asserts line and removed the Multirom and again restored from a previous backup and was good to go.
Again went back and re-installed Multirom and added the latest PE build and set it up. So every thing is nice and dandy now.
Better post an un-installer for Multirom in this thread.
I am attaching the Uninstaller that I used here till you post one
Exciting stuff man. You are awesome dude
Click to expand...
Click to collapse
Thanks for the feedback and the link for the uninstaller.
:good:
Dear @infrag is there a possibility of getting haptic feedback in the twrp. Really miss that.
Otherwise everything else is working nicely.
Great work thanks for sharing,
Which kernel did you use?
Is it Pie?
So you are the guy I've been waiting for! Bravo Infrag, I was looking after this. I'm gonna try it right now. Thank you very much for putting your time on this.
reevdre said:
Is it Pie?
Click to expand...
Click to collapse
I have Havoc and Syberia both of them Pie and everything seems to be fine.
All the kernels seem to work
I managed to run Havoc as internal + Syberia as secondary and China Developer as internal + Havoc as secondary. Plus Magisk 17.1 and Sphinx kernel in both cases and everything seems to be fine.
The only "problem" I'm facing is the impossibility to use lock protection in internal and secondary ROMs at the same time. Once I set a lock pattern for one of them I'm unable to pass through the lock security in the other, even being the same pattern. The only solution then is to flash a lock security remover zip but this makes impossible to set back a protection.
The other issue I'm facing is that Play Services FC in custom ROM but I have no clue about the reason, this is probably not related to the multirom, no idea.
Edit: Uninstalled Play Services with TiBu and installed a previous build from apkmirror, it got updated through Play Store and FC,s seem to have disappeared.
Anyway it's an excellent work and I rally thank you Infrag.
Thank you Infrag, I remember you from the good old leeco days lol. Glad to see a pro like You working on the mi8
descarao81 said:
The only "problem" I'm facing is the impossibility to use lock protection in internal and secondary ROMs at the same time. Once I set a lock pattern for one of them I'm unable to pass through the lock security in the other, even being the same pattern. The only solution then is to flash a lock security remover zip but this makes impossible to set back a protection.
Click to expand...
Click to collapse
for the pin problem i've restored my primary rom pin with in this way:
Using adb:
Code:
adb devices
adb shell
cd /data/system
su
rm locksettings.*
adb reboot
then i've rebooted my internal rom, now without a pin protection, and i've set a new pin from settings
descarao81 said:
The only "problem" I'm facing is the impossibility to use lock protection in internal and secondary ROMs at the same time. Once I set a lock pattern for one of them I'm unable to pass through the lock security in the other, even being the same pattern. The only solution then is to flash a lock security remover zip but this makes impossible to set back a protection.
Click to expand...
Click to collapse
Is it also the same for pin code instead of a pattern?
infrag said:
Bugs: Boot screen doesnt work due to DRM issues.
Click to expand...
Click to collapse
Dosn't seems a DRM issue, seems only that the default brightness is too low,
under "MultiRom Menu" -> "Settings" -> i've set "Screen Brighness" to 255, and in "AUTO BOOT" i've set a time-based boot with a delay (5 sec is ok). Afer a reboot now i can see and use the MultiRom Boot Menù :good:
gulp79 said:
Dosn't seems a DRM issue, seems only that the default brightness is too low,
under "MultiRom Menu" -> "Settings" -> i've set "Screen Brighness" to 255, and in "AUTO BOOT" i've set a time-based boot with a delay (5 sec is ok). Afer a reboot now i can see and use the MultiRom Boot Menù :good:
Click to expand...
Click to collapse
Hahahahahaha thanks :good:
hi infrag, its seem if my primary rom is encrypted, it goes bootloop, after install secondary rom, but secondary rom is work fine..
Edit : apologize, its work now. multirom must be installed before encrypt process
I flashed the recovery img and installed the multirom.
I can add new roms with no problem.
When I reboot the phone it doesn't boot into any rom. It boots in my primary system.
In settings I can see only the roms I have installed, not the internal rom.
There is no error message, it just don't boots into the new roms.
Edit: I am trying to upload screenshots from my TWRP but I don't have permission in this forum. My TWRP version is 3.2.3.0
Sent from my MI 8 using Tapatalk
escrifonife1 said:
I flashed the recovery img and installed the multirom.
I can add new roms with no problem.
When I reboot the phone it doesn't boot into any rom. It boots in my primary system.
In settings I can see only the roms I have installed, not the internal rom.
There is no error message, it just don't boots into the new roms.
Edit: I am trying to upload screenshots from my TWRP but I don't have permission in this forum. My TWRP version is 3.2.3.0
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Try to boot once into the internal rom and then back into recovery and now you will see the option for internal rom
arifqur said:
Try to boot once into the internal rom and then back into recovery and now you will see the option for internal rom
Click to expand...
Click to collapse
I have done it already. I can boot into my internal rom. After when I go back to recovery I can see only the rom I have installed in Multirom. I select it to boot, restart and it still starts in my internal rom.
Sent from my MI 8 using Tapatalk
Okay! Maybe try installing Multirom zip again
---------- Post added at 12:43 PM ---------- Previous post was at 12:30 PM ----------
gulp79 said:
Dosn't seems a DRM issue, seems only that the default brightness is too low,
under "MultiRom Menu" -> "Settings" -> i've set "Screen Brighness" to 255, and in "AUTO BOOT" i've set a time-based boot with a delay (5 sec is ok). Afer a reboot now i can see and use the MultiRom Boot Menù :good:
Click to expand...
Click to collapse
Maybe the no-vibrate problem has a similar ridiculously simple solution.
Another thing that I noticed was if I install a secondary rom by restoring a backup, it almost always bootloops to the fastboot mode. If you reflash the rom.zip after restoring from a backup, it boots normally.
The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks
Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work
Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.
Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.
Do you know what issues remain after flashing the latest vendor image?
Does the face unlock on Pixel Experience work with IR camera or front cam?
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?
Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one
Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.
tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it
Has anyone been offered the Global version by their phone and updated ?
If Yes - what is your experience with MIUI 14 and does Dark mode work for individual apps listed separately in dark mode options?
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Today monring i make an update, it is super. System is faster, but Leica cam app is not possible instal, have anybody newer version of leiaca cam app fo A13? THX
thecumbackkid said:
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Click to expand...
Click to collapse
@thecumbackkid - Please tell me in settings - display - more dark mode options - does it list all the individual apps to choose dark mode for each app ? (it may take a second or 2 to list them)
This is what it shows for me.
Thanks for the info thecumbackkid
Looks like its time to upgrade I was stuck on Miui 12.5 as when I updated to 13 all individual dark mode apps options disappered.
Someone stole my phone on holiday so I bought a new one and stuck on 12.5 as Dark mode for individual apps is essential for my over sensitive eyes!
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
snyfear said:
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
Click to expand...
Click to collapse
@snyfear
Thanks for the info - if you notice anything else let us know
Awful battery drain here. Charged to 100% barely did some basic browsing and half is already gone in a short amount of time. Noticed whenever I have it charged to 100% at night and by the middle of the next day where I barely use it for nothing but just to check for notifications on stuff it's already down to 80%...
AFAIK, this appears to be some pilot program build? I never asked to participate in it so how did I get this update?
Does any one know how to Facemoji keyboard in MIUI 14 for Lisa ?
I am not rooted. its plain stock MIUI.
Tried ADB shell uninstall, it gave me failure.
Also tried Xioami debloater tool. That also didnt work.
I still haven't received the update for some reason and i tried to update it manually but it didn't work what should I do
Updated to 14.0.4 EUXM and can't get root to work anymore.
Patched the boot image via Magisk 25.2 and then tested via fastboot, as always.
I run directly into a bootloop, which after a while sometimes returns to the bootloader or automatically deletes the temporary boot and boots with the normal image.
It's also strange that during the bootloop the device vibrates once every 3-5 seconds briefly. I've never had that before either.
Update:
I found a solution without wiping my device.
I remembered that I had a problem during the last update with shamiko and I didn't uninstalled magisk or removed any modules before the update. So in order to remove the modules without access to /data/adb and wihtout root rights you need to do the following, maybe it's interesting for you folks.
1. Open shell with command: "adb wait-for-device shell magisk --remove-modules"
2. Open second shell and boot with patched boot.img: "fastboot boot boot_patched.img"
The short time at boot, where root is present, was enough to remove the modules via the CLI during the boot loop.
Lessons learned:
Before the next major update definitely remove all Magisk modules before, if not root entirely.
Saves the work afterwards.
Btw:
Update is running smoothly so far. No battery drain noticed.
can anyone link me to a tutorial on how to rollback from custom rom (currently AOSPA) to stock MIUI ROM? want to move to MIUI 14 eventually. greatly appreciate it!
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
telefoongids said:
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
Click to expand...
Click to collapse
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
theanik said:
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
Click to expand...
Click to collapse
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash the rom with fastboot first, to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
telefoongids said:
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash it first with fastboot to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
Click to expand...
Click to collapse
thank you!
any one from Philippines received the update?