Related
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
I have rarely had any bootloop on my previous devices, so I'm not sure if this even counts as bootloop:
An hour ago I found my Pixel 2 (stock 8.1, Magisk 14.5 unmodified, TWRP 3.1.1) restarted itself (with the internal error message it's hard to miss). So I hit OK and enter the pattern to unlock. Upon unlock it reboots and arrives at lock screen again. Another unlock would trigger another reboot, over and over.
Luckily, I had Magisk uninstaller stored on SD card so I went in recovery to flash that, which seems to have restored the backed up boot image, and the phone is properly functional again. Then I flashed Magisk and it's all fine now.
I'm not attributing this issue to Magisk but just wonder if anyone else has seen this issue before. With lock screen being properly loaded, I'm not sure if this even counts as a bootloop.
Another factor to consider is, about two hours before all this happened, I installed AdAway to modify the host file. Don't know if that could be the reason, but now I've modified the host file again, will see if this issue comes back.
I just started having the same problem about the same time. I did a complete shutdown from the lock screen and when it fully booted, it was fine overnight, but it started acting up again this morning, so I did a complete shutdown again. It hung on the shutdown screen, so I had to do the hard reboot. Doing fine again, for now. I also have Magisk and AdAway, but I'd had both of those active for a few days before this started up.
I has something similar but different happen. After updating to 8.1 with magisk, I updated my hosts with adaway. I then had it hang on shutdown (this was the first time this had happened). Hard reset and rebooted and everything seemed to be fine. I then put it on the charger overnight, only to wake up the next morning and find it in the recovery menu saying there was an error booting the system and recommending a factory reset. I ignored that and rebooted, and haven't had any other issues since, but that one was weird.
It's something to do with magisk 14.5 456 beta. I've had the same boot loops, reverted to stock boot.img and problems went away
I haven't has this issue since I posted. To be clear, the problem I had could not be solved by a hard reset - it actually reboots itself every time I try to get past the lock screen for the first time after the previous (self) reboot. It's exactly a bootloop except that the phone makes it into the OS instead of failing to boot.
It can be Magisk or Adaway, no worries. I just pray it's not a hardware issue.
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
I'm still using Magisk 14.3 on 8.1, "Flash" kernel, no issues.
I've not had this issue since I posted about it. I uninstalled one live wallpaper app, which I'm not sure did the trick or not.
froader said:
Sounds like my same experience.
Stock 8.1 rooted with Magisk 14.5.
Stock recovery too.
Internal error message on boot.
I've had multiple reboots in a row, one after the other.
Stuck at shut down screen when selecting power off.
Hold down power button for hard reboot gets me back in business until this eventually happens again exactly as above.
No AdAway for me. I'm thinking it's the patched boot.img
Is there now an alternative method for rooting with Magisk other than patching the boot image and then manually flashing it?
Click to expand...
Click to collapse
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
cswithxda said:
Just saw this. I didn't use patched image method, I used TWRP beta 1 to install the Magisk.
Click to expand...
Click to collapse
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
froader said:
I'll have to try that. Thanks!
Do you also get the internal error message after a reboot?
Click to expand...
Click to collapse
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
cswithxda said:
Yes that's a known issue of Magisk and does not affect functionality according to the developer of Magisk.
Click to expand...
Click to collapse
Thanks for confirming. I wasn't sure if that was present flashing via TWRP, but makes sense that it would.
Same exact "Internal error" warning and occasional boot loop after upgrading the Pixel 2 (not XL) to 8.1 from Magisk 14.5.1456 using TWRP 3.2.1.0. Also an AdAway user. Glad to hear I didn't mess it up and it's just a quirk of the method and the alpha/beta stages. Hopefully this resolves soon as I hate guessing whether my device will go belly up at random. Seems like Flash kernel with Magisk 14.3 may be ideal - any other confirmations that this is a stable method?
I'm having this same issue as well! Using Magisk 14.5 1456, with the latest TWRP non-beta, and the Unified Hosts Adblock module. Randomly my phone goes into a soft reboot loop like your describing. If I hard reboot using power + volume up it seems to fix it for a time, then it happens again at a, seemingly, random time. It's crazily frustrating. The only other things I have that involve root are a terminal app, Drives roid, and CoSy to sync Facebook contacts. I also had Substratum using the root method, but I uninstalled that today wondering if that was the cause.
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
cswithxda said:
Hmm not sure if we have the same issue. In my experience, I could not solve the issue and at last only uninstalling Magisk (so the boot image reverted back to stock + TWRP) solved the issue.
Click to expand...
Click to collapse
Were you able to recover from the bootloop at all without uninstalling? For me I was able to force restart it, it would be fine for a few hours then it would bootloop again.
Additionally, I uninstalled Magisk and flashed the stock boot image as well and so far it hasn't come back. I still have TWRP.
Not at all, hard reset still sees the same reboots over and over, so I had to try something. And the only thing I found was the Magisk uninstaller on the SD card lol. I then uninstalled the Magisk and reinstalled it, and the issue has not come back so far.
I'm having that boot loop. I'll try uninstalling magisk
Sent from my [device_name] using XDA-Developers Legacy app
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I have 2ea Pixel 2 phones. Work one has the camera removed.
One keeps rebooting while the other does not. I had both of them set up the same.
I've read this is due to the kernel panicking if radio doesn't have signal. How true do you all think this is?
I'm almost ready to full wipe and start from scratch. I cannot RMA it since the camera is removed.
So far I've removed in order: Andromeda, Substratum, TulsaDiver Mods, and AdAway. Since removing AdAway I've not had any reboots, though the night is still young.
Any other things other than removing Magisk?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Interesting about removing AdAway. I had a hosts adblocker as well, I wonder if that has something to do with it.
https://developers.google.com/android/images
Pixel 3XL specific changes:
Improves Voice-Unlocking performance for Google Assistant
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
Improves Bluetooth connectivity on Pixel devices
Removes screen flash when ambient display wakes for some Pixel 3 device
Improves Voice-Unlocking performance for Google Assistant
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
Improves Bluetooth connectivity on Pixel devices
Removes screen flash when ambient display wakes for some Pixel 3 device
Nothing exciting :/ waiting forward to BETA 2 of Android Q
Bryandu13 said:
Nothing exciting :/ waiting forward to BETA 2 of Android Q
Click to expand...
Click to collapse
Me too...
I dunno what y'all talking about this update has improved so much for me in terms of usability and smooth operation
For manual installing April update, it's suggest to upgrade the platform-tool from https://developer.android.com/studio...orm-tools.html or the upgrade process will fail ....
Also, don't know why after upgrade (from factory image without -W option), Magisk v19 can no longer root the system... (TWRP installation is success but when reboot into the system it's not rooted). <--Edit: I uninstalled the Magisk Manager apk and reinstall and got root again!
Anyone else has same problem?
lssong99 said:
For manual installing April update, it's suggest to upgrade the platform-tool from https://developer.android.com/studio...orm-tools.html or the upgrade process will fail ....
Also, don't know why after upgrade (from factory image without -W option), Magisk v19 can no longer root the system... (TWRP installation is success but when reboot into the system it's not rooted).
Anyone else has same problem?
Click to expand...
Click to collapse
Why u using magisk 19? Why not 18.1
masri1987 said:
I dunno what y'all talking about this update has improved so much for me in terms of usability and smooth operation
Click to expand...
Click to collapse
Yeah I noticed it after installed it.
masri1987 said:
Why u using magisk 19? Why not 18.1
Click to expand...
Click to collapse
Tried V19 and V18.1 and both has the same problem. After update the April update, it seems Magisk Manager needs to be uninstall/re-install to detect root... (even after TWRP flash zip is done ok.)
Installed April update with no-wipe. Followed up with TWRP 3.2.3-3, Magisk v19.0 and Kiriskura kernel 2.1.3
Everything seems fine.
swieder711 said:
Installed April update with no-wipe. Followed up with TWRP 3.2.3-3, Magisk v19.0 and Kiriskura kernel 2.1.3
Everything seems fine.
Click to expand...
Click to collapse
Did you experience smoother experience like others above?
EMJI79 said:
Did you experience smoother experience like others above?
Click to expand...
Click to collapse
I have had smooth operations all along thanks to the custom kernel.
why am i getting notifications that aren't disappearing? i've checked them already and they only go away after i scroll down again on notification menu
masri1987 said:
why am i getting notifications that aren't disappearing? i've checked them already and they only go away after i scroll down again on notification menu
Click to expand...
Click to collapse
If you find a solution, I'd like to know it. My wife's P3 has this issue. In fact, she had the same issue on her OG Pixel. I do not have the issue on my 3 XL nor did I have it on my OG XL. There is some info here and on reddit, but mostly it is folk throwing $hit against the wall. Google has recommended full wipe as well as deleting and adding the profile back, but I am not going to bother unless that is a known fix.
https://forum.xda-developers.com/pixel-3-xl/help/notification-icons-staying-status-bar-t3860134
https://www.reddit.com/r/GooglePixel/comments/964ham/dismissing_notifications/
https://www.reddit.com/r/GooglePixel/comments/9x0df9/notifications_reappearing_after_swiped_away/
sliding_billy said:
If you find a solution, I'd like to know it. My wife's P3 has this issue. In fact, she had the same issue on her OG Pixel. I do not have the issue on my 3 XL nor did I have it on my OG XL. There is some info here and on reddit, but mostly it is folk throwing $hit against the wall. Google has recommended full wipe as well as deleting and adding the profile back, but I am not going to bother unless that is a known fix.
https://forum.xda-developers.com/pixel-3-xl/help/notification-icons-staying-status-bar-t3860134
https://www.reddit.com/r/GooglePixel/comments/964ham/dismissing_notifications/
https://www.reddit.com/r/GooglePixel/comments/9x0df9/notifications_reappearing_after_swiped_away/
Click to expand...
Click to collapse
for me it was oneplus gestures hiding the navbar doing it... sorry bud
masri1987 said:
for me it was oneplus gestures hiding the navbar doing it... sorry bud
Click to expand...
Click to collapse
Thanks anyway!
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
spuri78 said:
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
Click to expand...
Click to collapse
I'm having the same issue. I thought it was me going crazy and overlooking something in the settings. I've tried everything.
Sent from my Pixel 3 XL
spuri78 said:
Did April flash all. The theme is not working. I've got it set at dark? I haven't installed substratum
Anyone else?
Click to expand...
Click to collapse
Eudeferrer said:
I'm having the same issue. I thought it was me going crazy and overlooking something in the settings. I've tried everything.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
this has never worked for me on stock rom. on DU and other roms yes, but stock? no.
masri1987 said:
this has never worked for me on stock rom. on DU and other roms yes, but stock? no.
Click to expand...
Click to collapse
It used to work for me on stock.
Sent from my Pixel 3 XL
... brings some new stuff and newer security patch.
And, not mentioning it in the release notes, it comes with a dark mode!
koalalump said:
... brings some new stuff and newer security patch.
And, not mentioning it in the release notes, it comes with a dark mode!
Click to expand...
Click to collapse
Changelog
koalalump said:
... brings some new stuff and newer security patch.
And, not mentioning it in the release notes, it comes with a dark mode!
Click to expand...
Click to collapse
what new stuff you noticed? i only noticed darkmode so far and security patch for may too.
koalalump said:
... brings some new stuff and newer security patch.
And, not mentioning it in the release notes, it comes with a dark mode!
Click to expand...
Click to collapse
Where is the dark mode switch?
XDRdaniel said:
Where is the dark mode switch?
Click to expand...
Click to collapse
in display options
genesismarkus420 said:
what new stuff you noticed? I only noticed darkmode so far and security patch for may too.
Click to expand...
Click to collapse
You are right. There is not really much stuff concerning the interface. Only other goodie i have seen is the customizable lock screen clock. I wonder why they mentioned this one in the change notes but did not mention the dark mode (which, i am sure, more people are interested in).
PS: Can it be they fixed the buggy auto brightness? It seems to me, as if it works better now, but i am not really sure, cause i did not use it much before.
freezes?
Hi !
Anyone else having problems with freezing phone on V10.3 versions?
Starting with V10.3.2 I had random freezes (mostly seen when updating apps), so I reverted back to V10.2.2
Now I upgraded to V10.3.3 and problems with freezes are back again.
Does anyone else have these problems or anybody knows a solution?
(freezing meens only reboot possible to get it working again)
thx
regards
I cannot root this version. Tried "fastboot flash recovery" many times but all I got is failure. Anyone?
flushbeer said:
Hi !
Anyone else having problems with freezing phone on V10.3 versions?
Starting with V10.3.2 I had random freezes (mostly seen when updating apps), so I reverted back to V10.2.2
Now I upgraded to V10.3.3 and problems with freezes are back again.
Does anyone else have these problems or anybody knows a solution?
(freezing meens only reboot possible to get it working again)
thx
regards
Click to expand...
Click to collapse
Mmm no, I've not experienced this at all, maybe there's a corrupt app on your device? Did you try a clean install?
Remuzzz said:
Mmm no, I've not experienced this at all, maybe there's a corrupt app on your device? Did you try a clean install?
Click to expand...
Click to collapse
Thx for reply.
I did a full wipe, and when I initially updated the apps included in this ROM, I had a freeze (no other apps installed)
I do not think the problem is hardware related, because I've never seen this behaviour on V10.2...
Weird.
Hey, anyone else having problems with Mi Mix 2S with front Camera on V 10.3.3.0?
i have a trouble. i did update my Mi Mix 2S to the MIUI 10.3.3.0, but now the front Camera stopped to work, when i try to start it, only make zoom. Anyone know what can i do?
will twrp-3.3.0-0-polaris work with encryption on this release?
xumixu said:
will twrp-3.3.0-0-polaris work with encryption on this release?
Click to expand...
Click to collapse
works fine for me.
flushbeer said:
works fine for me.
Click to expand...
Click to collapse
Which steps did you follow?
if i only use twrp (fastboot flash recovery), it gets deleted on reboot
if i inmediately reboot into twrp and isntall magisk, i get boot looped (rescue party gets me back into twrp, in this case twrp does not get deleted)
I tried unofficial 3.3.1.0 and does not work either
xumixu said:
Which steps did you follow?
if i only use twrp (fastboot flash recovery), it gets deleted on reboot
if i inmediately reboot into twrp and isntall magisk, i get boot looped (rescue party gets me back into twrp, in this case twrp does not get deleted)
I tried unofficial 3.3.1.0 and does not work either
Click to expand...
Click to collapse
I downloaded with MIUI updater, rebooted to TWRP and installed ROM. Can't remember if I installed from internal storage or from OTG.
(tried a lot of things due to problems with this ROM).
If file gets deleted, you can try to copy it from /sdcard/downloaded_rom to any other folder (e.g. /sdcard) after download (and before reboot), reboot and install from there.
Afterwards I hat to install TWRP and Magisk again