March updates are published.
https://developers.google.com/android/images
Nice
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Feature drop too.
https://9to5google.com/2020/03/02/pixel-feature-drop-march/
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
wolfeyes30 said:
Yep. I had to switch to stable magisk and it patched the boot fine for me. Odd it didn't work for you.
Click to expand...
Click to collapse
I reinstalled Magisk and it worked fine. Weird.
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Had Problem with magisk but had franco kernel installed. You have to deactivate the modules for that kernel then magisk works again. Hole that helps
gettinwicked said:
Anyone having problems with Magisk crashing while trying to patch the boot image? It crashes every time I try. Changed to stable, rebooted, nothing works. Thoughts?
Click to expand...
Click to collapse
me too
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
dave5777 said:
March updates are published.
https://developers.google.com/android/images
Click to expand...
Click to collapse
:good:
---------- Post added at 02:34 AM ---------- Previous post was at 02:31 AM ----------
murphyjasonc said:
Looks like there are a lot of fixes this month.
https://support.google.com/pixelphone/thread/32079343?hl=en
Click to expand...
Click to collapse
:good:
---------- Post added at 02:38 AM ---------- Previous post was at 02:34 AM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
Click to expand...
Click to collapse
Use This guide: Do #4 'keep data' then #9 to root. It only takes 5 minutes.
Note: Before you start disable all your Magisk modules.
Balulo_007 said:
It Is just me or they have increased the maximum brightness ? It's like they have unlocked the High Brightness Mode
Click to expand...
Click to collapse
They unlocked High. Brightness. That was one of the features in this quarters drop.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
troymz1 said:
Starting in Feb my phone no longer gets updates.. I'm not sure if it's because of Magisk or not. I search for update and for about 2 seconds it says preparing update and then it says you are up to date.
Anyone else? Any fix?
Click to expand...
Click to collapse
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
murphyjasonc said:
Just fastboot the factory image without the -w. It might just be personal preference but I think that's the easiest way to update if you are rooted.
Click to expand...
Click to collapse
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
troymz1 said:
I'm aware of how to update but I used to be able to take the ota and re root with Magisk.. but now I don't even get the ota.
Click to expand...
Click to collapse
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
murphyjasonc said:
I have automatic system updates disabled in developer options. It's probably unlikely since you were getting updates but could you have disabled by accident? Not sure what else would suddenly cause you to stop getting them. I doubt it's something that simple but I've beat my head against the wall for something similar in the past....lol
Click to expand...
Click to collapse
Disabling that toggle in developer options is a prerequisite for doing the OTA update option and retaining magisk.
wgrant said:
I'm right there with you. Very annoyed that it won't do it through normal OTA. I waited it out through February and never got it.
Click to expand...
Click to collapse
Have you tried doing the Magisk uninstall then tried taking the ota?
troymz1 said:
Have you tried doing the Magisk uninstall then tried taking the ota?
Click to expand...
Click to collapse
No, that'll be what I do this month if it doesn't pop up like it should.
wgrant said:
No, that'll be what I do this month if it doesn't pop up like it should.
Click to expand...
Click to collapse
I wanna try it but don't have time to fix right now if it goes wrong
I agree with a lot of others here: It's easier to dirty flash, no hassles and it works every time without having to figure out any secret handshakes.
Related
Just received it.
jkeith1 said:
Just received it.
Click to expand...
Click to collapse
Looks like it was just a modem update. Nothing too serious.
Only difference that I can make our is teh baseband updated from G935TUVU1APB6 to G935TUVU1APB8
Modem updates are generally about that size too if I'm not mistaken.
Binary100100 said:
Looks like it was just a modem update. Nothing too serious.
Only difference that I can make our is teh baseband updated from G935TUVU1APB6 to G935TUVU1APB8
Modem updates are generally about that size too if I'm not mistaken.
Click to expand...
Click to collapse
So this should not effect the bootloader? Its the one thing most people are afraid of messing up in fear of no future root.
Kilroy672 said:
So this should not effect the bootloader? Its the one thing most people are afraid of messing up in fear of no future root.
Click to expand...
Click to collapse
Hard to tell without looking at the actual update. They could have added something else into it that's just not showing up in the ABOUT section.
Got mine this morning as well.
Did it earlier this morning, so far so good, not noticing anything unusal.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
Kilroy672 said:
So this should not effect the bootloader? Its the one thing most people are afraid of messing up in fear of no future root.
Click to expand...
Click to collapse
Isn't the bootloader locked? I thought root was dead as it is.
Maybe its a quiet update that will allow us to unlock the bootloader . Anyone toy with it yet? Wishful thinking im sure, but stranger things have happened.
DRSdroid said:
Maybe its a quiet update that will allow us to unlock the bootloader . Anyone toy with it yet? Wishful thinking im sure, but stranger things have happened.
Click to expand...
Click to collapse
Yes still locked
duvalbmarley said:
Yes still locked
Click to expand...
Click to collapse
Doh!
Supposed to be a security update according to tmo site, but security still showing Feb security
Sent from my SM-G935T using Tapatalk
Anyone have any changes to report with new firmware?
Software Update force closing.
I did the 41mb update we all got, and now every time it checks for software updates I get a force close. I haven't tried resetting yet, it's kind of a pain, but has anyone else encountered this?
Binary100100 said:
Looks like it was just a modem update. Nothing too serious.
Only difference that I can make our is teh baseband updated from G935TUVU1APB6 to G935TUVU1APB8
Modem updates are generally about that size too if I'm not mistaken.
Click to expand...
Click to collapse
During the update, it seemed the device goes into Download mode, flashes new radios and firmware. Yay stability?
For me boot time is noticeably slower, and I have more trouble with apps on the sd card not having icons/being available for much longer at boot than before the update. Tests of sd transfer speeds are somewhat slower post update.
After the update, my wireless connection is TERRIBLE.
At first I thought my wireless router, but everything else in the house works great :-\ If I turn off the wifi, everything is normal. I'm glad I have truly unlimited LTE, because this is going to be annoying until they release an update patch.
I've already booted to bootloader and cleared the cache, no help. It's like a delay in connecting to anything wireless... Speedtest won't run because it times out on the ping test.
Hangouts works, but it's delayed. When I type a message, it says, "sending...." for about 20 seconds before it sends. :-\
If this is a nuisance at work all day today, I'll probably just backup everything and push the original stock rom from KIES.
Hey guys. New bug in the camera when trying to shoot in raw mode where the driver locks up and doesn't recover until a reboot. Video below.
Vexamus said:
Hey guys. New bug in the camera when trying to shoot in raw mode where the driver locks up and doesn't recover until a reboot. Video below.
Click to expand...
Click to collapse
I don't seem to have this issue.
Anyone know how to remove the notification? I dont wanna updatte mine ?
Sent from my SM-G935T using Tapatalk
wawaweewa said:
Anyone know how to remove the notification? I dont wanna updatte mine ?
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I would imagine force stopping the system update software would get rid of the message and then using something like Package Disabler Pro to disable it would prevent it from checking again.
I just got a "really blue" pixel XL today and I seem to have the problem that so many people are facing, I can not unlock my bootloader
The guy I bought it from said it was the google version, but not 100% sure if it is or not, and not sure how to distinguish if it is or not.
Anyway, to my question, the main reason I bought the phone was to try out Android P, but it seems I can not install it, since my bootloader is lock, correct? and I would assume there is no workaround for this, either?
Thanks!
I could be mistaken, but I think if it's stock software you should be able to flash the file provided by Google.... On a locked bootloader.
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
tember1214 said:
If it is Verizon version you can still get Android P on it by side loading the OTA. You just need adb/fastboot on your computer. Very simple process. I am running Android P on my Verizon pixel with locked bootloader now.
Click to expand...
Click to collapse
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
cms062407 said:
how are you installing it without any issues?
I am running the basic commands
adb reboot recovery
adb sideload <filename.zip>
and it keeps erroring out on me., it says
E: Signature verification failed
E: error: 21
Am I missing something?
Click to expand...
Click to collapse
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
tember1214 said:
Are you following these steps? I had no issue. Had the same error you had the first time because of bad download
Click to expand...
Click to collapse
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Dup post.
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
cms062407 said:
Yep, I am doing those exact instructions.
I have even re-downloaded the OTA file a few times.
Did you do anything with the actual 1.3GB file or just flash it as it is? Did you rename it, by chance?
It may be some sort of device driver issue, but I also think it may not be, since my device is being recognized just fine within adb commands..
Click to expand...
Click to collapse
Your sure your downloading the ota file and not the factory image ?
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
ohhhhh, that is more than likely it! I didn't see "OTA " files before..but i just googled it, and I see they are different file names...downloaded the OTA now, and about to try to install.
before, I just googled "android p pixel xl" and it brought me to this page... https://developer.android.com/preview/download.html
but the OTA downloads are on a totally different page at https://developer.android.com/preview/download-ota.html
tember1214 said:
I renamed it to ota.zip but the shouldn't matter
---------- Post added at 10:42 PM ---------- Previous post was at 10:36 PM ----------
Your sure your downloading the ota file and not the factory image ?
Click to expand...
Click to collapse
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
cms062407 said:
well, hell...looky there....it is now installing just fine! can't wait to see what P is about, now!
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
You can't with a locked bootloader haha. Glad you finally got it working
---------- Post added at 11:39 PM ---------- Previous post was at 11:31 PM ----------
Enjoy!!
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Tried side loading old version and no go.
mswlogo said:
Do you know if you can side load back to an older version or can you only go forward since they are OTA "updates".
Click to expand...
Click to collapse
Don't think so on a locked bootloader. Are there any issues in particular with P?
Sent from my Pixel using Tapatalk
cms062407 said:
Thanks for the help with making sure I was downloading the OTA file....What are those factory images for then, if you can't install them with ADB commands?
Click to expand...
Click to collapse
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
mike.s said:
Factory images are installed differently. I don't know if they'll install on a VZW device, I'd think they should because they're "official."
Click to expand...
Click to collapse
They will not install on Verizon device without unlocked bootloader.
---------- Post added at 04:38 PM ---------- Previous post was at 04:36 PM ----------
Jazznax said:
Don't think so on a locked bootloader. Are there any issues in particular with P?
Click to expand...
Click to collapse
Been using Android P since it came out. It's my daily driver. Works great. Only thing is now my Samsung gear watch won't work because the app isn't updated for new version of Android.
Pedroking78 said:
I've tried sideloading Android P but it keeps saying build date to old can not down grade??
Click to expand...
Click to collapse
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
joedeuce said:
If you're already on April security update you'll have to wait for the next preview build since preview 1 has an older timestamp than April patch.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Oh that's annoying. Any idea when that might be/how often they typically release updated builds?
Pedroking78 said:
just unlock your bootloader
and you can flash it thats want it did :laugh::laugh:
Click to expand...
Click to collapse
How do you unlock it then?
That's cool and all but personally I'd rather just wait for a new build of P.
Updates as indicated are rolling out!
What's the security patch date? August?
linuxct said:
What's the security patch date? August?
Click to expand...
Click to collapse
July... I expected August ?
Edit.
Anyone notice any of the bug fixes or performance improvements they are talking about?
Munk0 said:
Anyone notice any of the bug fixes or performance improvements they are talking about?
Click to expand...
Click to collapse
The camera went from ver. 1.8 to 1.9 but i dont know what the specifics are. The update took like 45 min. to complete.
The Dolby Atmos demo is still upside-down /wrong way around
if i'm rooted and have twrp and magisk 17 installed, will I able to update and if yes will I lose root?
majedalanni said:
if i'm rooted and have twrp and magisk 17 installed, will I able to update and if yes will I lose root?
Click to expand...
Click to collapse
There's no factory image right now so you can't use the corresponding boot image to flash magisk back, it might work with the May one but I wouldn't count on it. You can also try the A/B magisk feature (flash stock boot.img, apply OTA, install magisk to inactive slot). You will definitely lose TWRP though. This wouldn't be a problem if fastboot boot worked.. I'm sure they'll release the images soon enough.
I'm still @ feb patch lol
can never get the OTA
Can someone post the build number/build version of the update?
OPM1.171019.011-RZR-180803.6033
Android version...8.1.0
Was trying to see if I could grab the factory images...doesn't look like it.
MishaalRahman said:
Was trying to see if I could grab the factory images...doesn't look like it.
Click to expand...
Click to collapse
I'm also waiting for the factory image. I think that's all I need in order to root my device. I need the boot img. I hope they don't take too long to post it.
lyall29 said:
I'm also waiting for the factory image. I think that's all I need in order to root my device. I need the boot img. I hope they don't take too long to post it.
Click to expand...
Click to collapse
They seem to be taking their time, last time it was within a day or so.
Out in HKG, and havent gotten the update yet
versions 19 and 20 are up
https://developers.google.com/android/images
What's the difference between the two?
So I'm on 9 - could anyone tell me if I can still just remove the "-w" switch from flash-all.bat or do I need to do a totally clean install?
SinisterXReaper said:
What's the difference between the two?
Click to expand...
Click to collapse
.020 would be more.
kerobrat said:
So I'm on 9 - could anyone tell me if I can still just remove the "-w" switch from flash-all.bat or do I need to do a totally clean install?
Click to expand...
Click to collapse
You don't have to do a clean install, but I always do. I feel like I have less issues.
rooting works?
What's the current root method for 10.0? I take it there is no TWRP yet?
What is the difference between .019 and .020? The second one listed on the factory image page usually seems to be Verizon. Also, the odd numbered one seems to be Verizon. Yes I've read. Maybe I've overlooked something, but I'm at a loss.
SinisterXReaper said:
What's the difference between the two?
Click to expand...
Click to collapse
The .19 is for users on the Q betas already , the .20 are for users jumping from pie
Jiggs82 said:
The .19 is for users on the Q betas already , the .20 are for users jumping from pie
Click to expand...
Click to collapse
Thanks!
airmaxx23 said:
What's the current root method for 10.0? I take it there is no TWRP yet?
Click to expand...
Click to collapse
For TWRP check here...
https://forum.xda-developers.com/pi...pixel-3-xl-t3861623/post79995400#post79995400
Can I do a OTA with bootloader unlocked .? (No TWRP AND no ROOT)
STALKER18 said:
Can I do a OTA with bootloader unlocked .? (No TWRP AND no ROOT)
Click to expand...
Click to collapse
Yes you will be able to.
Magisk still works. For those lazy ones, here is the patched boot image (19): https://drive.google.com/file/d/1sy4jQjevqQwvGDVGw4d8sHY3bRXCXCjo/view?usp=sharing
---------- Post added at 08:36 PM ---------- Previous post was at 08:36 PM ----------
dnsmo said:
rooting works?
Click to expand...
Click to collapse
Yes, https://drive.google.com/file/d/1sy4jQjevqQwvGDVGw4d8sHY3bRXCXCjo/view?usp=sharing.
So, flashed 10 a bit ago. Just got a new OTA for 1.2MB? Anyone else?
magisk still works just need to do the manually patching method.
Flashed the 10 images and the phone wont go past the G logo. Removed the -W when i did it. Tried again to no avail. I didn't wipe anything before trying. Any suggestions?
Fuzzy13 said:
Flashed the 10 images and the phone wont go past the G logo. Removed the -W when i did it. Tried again to no avail. I didn't wipe anything before trying. Any suggestions?
Click to expand...
Click to collapse
Wipe
shiftr182 said:
Wipe
Click to expand...
Click to collapse
Backing up my internal drive just in case and that's what I'm going to try next. Thanks
Would someone who's on Android 10 release please do a simple check for me?
Go to Settings / Accessibility and check if there is an option for hearing aids / Pair new device
Thanks in advance
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Wait for the beta's
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Hi,
from what I have read, no, its not a daily driver, yet. I'd wait till the beta's are available in`May, to give it a try.
Though you could always just flash the update & see if it is OK for you. If not revert back to 10.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
Not rootable yet. Lots of changes to it that Mr. Wu is going to have to work on. He said he knows what to do, just going to take a bit of time.
ShadowJP88 said:
Hi there!
Anyone tried the android 11 beta?
Is it stable enough to be on my only phone?
Is it possible to root it?
Click to expand...
Click to collapse
I am on it and it is definitely stable enough to use as a DD but unfortunately no root yet
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
atembleque said:
I'm using it from the first day release. Stable as a rock, i didn't have any issue. I have a question, what I must do to switch from the last developer to the first beta?
Click to expand...
Click to collapse
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
wangdaning said:
Usually, you can either sideload the ota or flash the new image in fastboot after removing the -w. Who knows with google though, they might decide to change that procedure somehow, too Best bet is to just wait for it to be released and follow whatever instructions are given at that point.
Click to expand...
Click to collapse
Thanks!
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Vanschtezla said:
Can anyone upload me an android 10 rooted boot.img for march update? I can't seem to patch it using canary magisk.
Click to expand...
Click to collapse
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
sliding_billy said:
The canary Magisk is buggy to say the least. After removing it from my P3XL a while ago, I had to revert to stable on my wife's P3 because attempted patching just results in the app closing. It patched fine with stable.
Click to expand...
Click to collapse
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Vanschtezla said:
I tried patching it with stable but my phone won't boot after flashing. Was your wife's booted fine?
Click to expand...
Click to collapse
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
sliding_billy said:
Yeah, no issues. Been running it for over 12 hours now with multiple reboots and EX kernel install. Flashed factory image without -w. Attempted to patch boot. On failure (app closing), I force closed canary MM, cleared cache and data from app and then uninstalled it. Installed the stable APK and patched boot. Flashed magisk_patched to both slots, and it booted fine. Then installed EX (old one). This morning , updated EX to the new one. Not a single issue since the canary app closure (which others have reported when patching on various devices for days on the canary thread).
Click to expand...
Click to collapse
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Vanschtezla said:
I only use the fastboot flash boot magisk_patched.img command. That ought to flash the patched boot.img on both slots now wouldn't it?
Edit: Nevermind I flashed to both slots but to no avail. If you don't mind can you share me your magisk_patched.img?
Click to expand...
Click to collapse
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Vanschtezla said:
Same result. After booting sequence it just ended up with "powering off" and went to recovery after rebooting. Must have missed something. Thank you. I'll wait for your patched file then.
Edit: I found the culprit. It's my magisk modules. I removed everything and managed to get it to boot. Now just need to figure out which one is causing the bootloop. Thanks!
Click to expand...
Click to collapse
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
Click to expand...
Click to collapse
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
sliding_billy said:
Here you go. Let me know when you have pulled the file so I can delete it from GDrive.
https://drive.google.com/file/d/1Mx8F5t7kOVLUsx7P9hQ4CYCdguGpoO8_/view?usp=sharing
SHA256 7B5A116A14E7A75D6583F21CA20F7FEE9245DF2CEC457D8582AB598D994C84E1
---------- Post added at 05:34 AM ---------- Previous post was at 05:31 AM ----------
Just saw your edit. Do you have the Edge Sense Plus module installed? It normally takes J a day or so update the module for the new build. You pretty much need to disable that every month until he posts an update.
Click to expand...
Click to collapse
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Vanschtezla said:
No I don't use Edge Sense Plus. But I did use the Centre Clock module. I think it's related to the system UI crashing hence the powering off immediately after booting. Which might also explain why the animation was kind of laggy. I'm guessing something to do with the feature drop which affected the system UI which leads to incompatibility between the ui and the module. But yeah just a guess.
Click to expand...
Click to collapse
I do not use that module, but it definitely sounds like it could be an issue since you weren't actually boot looped and were able to remove it. I try to keep my module use minimal (and use well vetted ones only) to avoid wondering whether they are the root cause of issues when they happen. Best of luck. Just glad you are up and running.
sliding_billy said:
Just in case, here is the command. I need a little bit until I get back onto the machine with the patched file, and then I will send it. I am on my Linux box for a bit.
fastboot flash boot --slot all magisk_patched.img
Click to expand...
Click to collapse
Are you on Android 11 and have root?
Zehlek said:
Are you on Android 11 and have root?
Click to expand...
Click to collapse
No, this was OT from the original thread title when the question was asked about 10.
sliding_billy said:
No, this was OT from the original thread title when the question was asked about 10.
Click to expand...
Click to collapse
Sorry to stay OT, but since you mentioned EX kernel, does using it also not hide the unlocked bootloader in our "new and improved" SafetyNet world? I'm one of those for whom everything is still working so far--Pay, banking apps, device is certified, etc. I'd hate to lose all that, though, because I'm not going to unroot. I guess if I have to I can use Pay on my watch and use the banks' Web sites instead of their apps.