I updated to the October update of android 11 and ever since then, my phone has what I can only describe as a hard crash. The power button won't turn on the screen. The finger print scanner in the back won't respond to unlock it.
I cannot recover from it unless I have a usb cable plugged into it with the other end plugged into a computer or charger, and then I'm able to hold down the power button to hard reboot it.
But if I'm unable to plug in a usb cable because it I'm out at the time, there's no way to hard reboot it.
It has happened twice so far. Second time was today. My battery was at 100% full charge at the time.
I am currently rooted using magisk 21.0 (21000) using the boot img patch method.
Is anyone else experiencing this with their pixel 3a? Is this a hardware problem? I've had it around 8 months. Never experienced this on Android 10.
I also read about the bug in Android 11 where it's slower in gpu intensive processes like when playing some games.
Yes I get that when launching any office365 apps, either from the full suite or individually
That's the only time that occurs though - if you hold down the power button for long enough it should reboot - I used to get a warning saying that android system was corrupt, try again or format user data but selecting try again would boot my phone.
Bit sh*t really but hey-ho
A11 October Factory Image
Magisk 21.10 Manager 8.10
ElementalX p3a-3.07
I'm having the exact same problems. Initially I thought this had to do with upgrading from Android 10 so I reinstalled fresh but the problem persisted. I have not found a solution and am currently unrooted. Magisk modules I had installe were
Active Edge Mod
Advanced Charging Controller
Cross Compiled Binaries
Daily Job Scheduler
F-Droid Privileged Extension
Disable systemless hosts.
https://github.com/topjohnwu/Magisk/issues/3171
going to remove the systemless hosts module.
I also just updated to the android 11 November release. It's fixed the slowdown issues in some games.
I'm also wondering, why does magisk manager release channel still have 20400 for the magisk release? I thought the magisk release 21000 was released on october 3rd.
xp99 said:
I'm also wondering, why does magisk manager release channel still have 20400 for the magisk release? I thought the magisk release 21000 was released on october 3rd.
Click to expand...
Click to collapse
You need to switch to the Beta channel on Magisk Manager
I'm still getting it randomly freezing where I have to hard boot it.
Related
I really don't know what I'm doing here.
I've been using CM11 for probably 6 months now, when I originally installed it I followed cynagenmod's wiki and used recovery-clockwork-6.0.4.4-xt926. Since then I'd updated several times using the phone menu. That quit working on the past couple versions I tried, something like "Unfortunately, CMUpdater has stopped".
I've been having some problems for about a week connecting to google+ (and my location is no longer sharing which annoys my wife), probably unlreated, but I decided I better figure out how to update my phone to the latest CM11, which looks to have stopped a month ago, but still newer than what I was running. I vaguely recalled something about pushing a volume button and power (when powered off) to load recovery bootloader or something... I figured I'd try that and see if there what was on those menus then go from there (hoping to install the CMupdate from there).
I couldn't remember if it was volume up or down or both or what, so I just tried volume up + boot. I figured I'd get a menu options, nothing would happen by itself. I was wrong. It showed a screen with an android with open belly for a while, then rebooted, said something about updating android then updating apps 1-62 or something... went on for a while... then finishing booting.
All seems normal. I was a little worried it was doing some type of reset or wipe or I dunno what. But not only does it appear normal, it updated to latest CM version. All by itself. I'm happy with results actually, but I have no idea what happened.
I would recommend using the latest TWRP.
The absolute latest compiled for our device can be found here.
The latest official TWRP is 2.7.1.2, which is also fine - but I believe it will not flash CM12 properly. At least it won't take advantage of the new F2FS file system.
I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Ctrl_Alt_Del said:
I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Click to expand...
Click to collapse
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
NaminatoR1254jaime.sier said:
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
Click to expand...
Click to collapse
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Ctrl_Alt_Del said:
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Click to expand...
Click to collapse
Unfortunately I'm in the same boat. I never rooted my shield tablet so the lack of otg support and always having the optimizing app on reboot sucks.
I hope nvidia puts a pach out soon
OTG should work if you power on the tablet with the OTG plugged in...pain in the butt...but better then nothing until they fix it.
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed
Hi,
last week I successfully installed LineageOS as of March 15 on my OP6 and it worked perfectly.
This morning, I applied the system update to the latest version as of March 22. It took a long time to process (about 5 minutes), then rebooted as usual, but then surprisingly stuck in Crashdump mode.
After some switching off and on again with the same result, I found I still could boot into recovery by VolDown + Power (it’s the simple lineage recovery, not TWRP).
Since then, I tried several times to reinstall both Lineage versions as of 15th and 22nd the usual way, but the phone never would boot any system. The recovery works perfectly, system can be flashed by ADB sideload and reports success, but after rebooting from recovery into system, it either runs into Crashdump or back into fastboot.
Bootloader is unlocked.
I have applied the copy-partition tool to make sure there is no bad software in the other slot but that didnt help either.
I have done factory reset / format all and re-flashed Lineage (latest and older version) but same result - fastboot or Crashdump.
Any hints what I can try to get a working Lineage again?
--ks
Update: It was possible to flash OxygenOS by MsmDownload, which booted perfectly and is running through its setup procedure now. Though I prefer LineageOS by far, I won’t switch back unless I am sure this won’t happen again
Browsing a bit further through this forum, I got the impression this is quite common on OnePlus phones from OP6 on, and so might happen at random intervals even with the manufacturer’s OS. In other words, a built-in fault. I want my wonderful OP 5T back
--ks
So summary
OOS 9
Magisk 19
Disabled I think is quickswitcher module
Now I just get animation going forever on booting, if I leave it long enough about 20 minutes or so, it reboots itself and goes back to loop.
TWRP is accessible.
I tried MM recovery tool in core only mode but still doesnt boot.
Ideally I need a solution that doesnt involve a factory reset.
Ok the core only mode didnt stick I think, so did it again and the phone is booted.
With no phone app , completely gone off the phone.
It shuts down after about 20 seconds after booting up.
Backing up what I can over USB from TWRP, and this might force me to migrate to my Oneplus 8 pro which has been sitting in its box, but I will still appreciate any input on how to get this running again without a reset so I can properly migrate app settings etc even if its losing magisk.
I managed to keep the phone bpoooted up for ages, and have done things like titanium backups, app setting backups etc.
I then tried to reinstall the phone app from the play store but got a vague "cannot install phone from google".
But at least now I can access settings etc. Take screenshots of settings also. So better baseline for the new phone.
Pretty crazy how all this broke so easily though.
So I dont know how this happened but I managed to recover the phone.
The xXx rom magisk module got wiped when I deactivated the recents module, this removed the google dialer framework and some build.prop changes the rom module puts on the phone.
I initially just added the framework magisk module which allowed the google phone app to reinstall, all my call logs were intact. But the phone was still unstable on booting so had to reinstall xXx which seems to have fixed that, albeit now with added lag.
But I have backed up everything now anyway so will migrate to my newer phone its long overdue, but this post is here now in case anyone else has the same issue.