Related
OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
derei said:
OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
Click to expand...
Click to collapse
You need to download the full package and install it from recovery, then set up your root and Magisk again
https://www.oneplus.com/uk/support/softwareupgrade/details?code=7
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
I used this method when i first got my S9+, and didn't want to wait, can confirm it works..
FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Could you try it with earlier official firmware? Saw in comments to video, that it helps.
Increase the date rather than decrease
fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Pretty sure
---------- Post added at 08:24 PM ---------- Previous post was at 08:15 PM ----------
fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Thought you couldn't unlock Snapdragon S9 or is that only SM-960/5U?
I tried to flash TWRP to a S9plus with the information in this thread, but it does not work for me.
- G965F/DS
- heimdall v1.4.2
- TWRP twrp-3.3.1-0-star2lte.img
- I made a build of Lineage 15 for star2lte, but as this tries to extract some files from the Android 8 S9plus, that I do not have, replaced the missing files with placeholder files to get a build.
- I did OEM unlock, but have since then made a number of resets, OEM unlock does no longer show up in menu
- S9+ came with latest version of Android 9 and updated to 10 nearly immidiatly
- Downgraded to july 2019 version of Android 9 (modem to Android 8 latest version)
- shows security patch october 2019 in preferences
- set date to 20 sept 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
- set date to 22 oct 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
still no TWRP installed, still no way to flash Lineage
RMM STATUS, I can't unlock it. So I can't flash twrp to phone.
will this trigger knox?
mobile in video is triggered but maybe on a "clean" one not
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.
Hey everybody,
I'm currently running a custom ROM and would like to go back to a stock ROM and then on to the xiaomi.eu ROM but after downloading the latest MiFlashTool from the site in the title and extracting it, Windows didn't like it when I wanted to run it and when you run it as admin UAC says it has an unknown publisher (shouldn't it be Xiaomi?).
Even after I proceed it asks me to install 5 drivers (google, nvidia, microsoft, microsoft & qualcomm) so I got a bit nervous and cancelled the driver installation.
Just want to confirm if I'm using the right site and that it's ok to install the drivers that it wants me to install. With the latter, I was wondering if they are necessary because even if I cancel the driver installation the MiFlashTool application doesn't close.
Just looking for some advice, thanks!
What do you mean "Windows didn't like it"
Yes the drivers are trustable. ^^
I'd say Recovery-route is more safe:
You can use TWRP / OrangeFox Recovery to flash MIUI.zip -> Format Data -> Boot System
Then you can flash Xiaomi.eu.zip -> Format Data.
Get the MIUI Stock ROM from xiaomifirmwareupdater.com
You can also go the Fastboot route, by using Mi Flash & Fastboot-flashable MIUI Stock ROM.
The previously mentioned website also has MIUI Fastboot ROMs.
o3266013 said:
Hey everybody,
I'm currently running a custom ROM and would like to go back to a stock ROM and then on to the xiaomi.eu ROM but after downloading the latest MiFlashTool from the site in the title and extracting it, Windows didn't like it when I wanted to run it and when you run it as admin UAC says it has an unknown publisher (shouldn't it be Xiaomi?).
Even after I proceed it asks me to install 5 drivers (google, nvidia, microsoft, microsoft & qualcomm) so I got a bit nervous and cancelled the driver installation.
Just want to confirm if I'm using the right site and that it's ok to install the drivers that it wants me to install. With the latter, I was wondering if they are necessary because even if I cancel the driver installation the MiFlashTool application doesn't close.
Just looking for some advice, thanks!
Click to expand...
Click to collapse
I believe that MiFlashtTool ver. 20200314 works perfectly on windows 10. This link provides ROM files directly from Xiaomi servers.
cyanGalaxy said:
What do you mean "Windows didn't like it"
Yes the drivers are trustable. ^^
I'd say Recovery-route is more safe:
You can use TWRP / OrangeFox Recovery to flash MIUI.zip -> Format Data -> Boot System
Then you can flash Xiaomi.eu.zip -> Format Data.
Get the MIUI Stock ROM from xiaomifirmwareupdater.com
You can also go the Fastboot route, by using Mi Flash & Fastboot-flashable MIUI Stock ROM.
The previously mentioned website also has MIUI Fastboot ROMs.
Click to expand...
Click to collapse
Thanks for the reply.
This is an example of what Windows would show when I ran the app.
Why do you say that recovery is more safe? As someone who is pretty new to custom roms, are recovery ones always safer to install than fastboot ones?
I noticed that you're using Arrow OS 13, I'm actually currently using Arrow 11 and was looking to install Arrow 13 initially but it hasn't shown up on the forum yet. I assumed they were working on it but haven't released the offical version to the public yet.
o3266013 said:
Thanks for the reply.
This is an example of what Windows would show when I ran the app.
Why do you say that recovery is more safe? As someone who is pretty new to custom roms, are recovery ones always safer to install than fastboot ones?
I noticed that you're using Arrow OS 13, I'm actually currently using Arrow 11 and was looking to install Arrow 13 initially but it hasn't shown up on the forum yet. I assumed they were working on it but haven't released the offical version to the public yet.
Click to expand...
Click to collapse
You can safely continue on the Windows SmartScreen Dialog.
>Why do you say Recovery is more safe?
With Fastboot Mode, there are outside factors: E.g. the USB-connection may cut off, your PC may hang, or Power Loss... those things would abort the flash...
But this is just an extreme end.
If it does happen, that the Fastboot Flash aborts due to an outside-factor (e.g. Power Loss etc.), then *do not* attempt to reboot your phone. Simply fix those outside-factors and start the Flash again. You may need to disconnect and reconnect your phone to your PC.
I say "Do not attempt to reboot Fastboot Mode after an aborted Flash", because during the Flash, critical partitions (like for Fastboot Mode) may have been erased off of the phone, but not successfully reflashed (because of the Abort).
But like I said that's only an extreme end. An extreme end which I had to experience tho unfortunately, because I have a PC with a motherboard with faulty USB-ports (common issue on AMD X570 motherboards). What was very wrong from my part tho, is that I rebooted my phone and it got hardbricked, because it couldn't load Fastboot or Recovery (due to the aborted Fastboot Flash). I fixed it, but it was a huge pain in the butt.
But you could have the same thing happening using Recovery + ADB Sideload. In that case you could just redo the ADB Sideload Flash.
About ArrowOS: I use the latest unofficial v13 version from the Telegram Group "mipa_lab", it's Palaych's group, who is the maintainer of ArrowOS for Poco F3.
But he said that he may not do Official ArrowOS ROMs anymore, but will only do unofficial ArrowOS v13 builds. - Or he may move away from ArrowOS, he wasn't clear about that. He did confirm the December Security Patch is in the works tho!
Note that for all devices ArrowOS v12.1 Updates are discontinued due to the small infrastructure of this small project. So they are focusing on v13.
About his ArrowOS v13 builds tho, I can say they are very stable and don't feel unofficial at all. Almost all features are available.
However Fonts & WiFi/Signal custom icon-styles are missing, and also the Bluetooth Audio Codecs LDAC and "AptX Adaptive" specifically. Normal AptX is integrated tho.
I do feel like switching to CrDroid 9 tho, because it's another Vanilla-type ROM but instead with lots of Customisability. One thing that was bothering last time I tried CrDroid tho, was that Dolby wasn't working on headphones, only over the speakers.
But ArrowOS 13, I can vouch for, as a minimalistic AOSP ROM ^^ very stable.
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?