Related
I have rooted GSM Dev Edition Moto X. With the latest OTA updates, and GravityBox installed. Whenever I try to record my screen, either through the power menu or a nav bar shortcut, the screen recording ends immediately and a 0 byte files is save to the sd card. Obviously, this file cannot be played. Anybody know why this happens?
http://forum.xda-developers.com/showthread.php?t=2554049&page=436
Scroll halfway down and check OP's post.
From the thread:
Looks like new screenrecord binary is not compatible with some devices. I will probably have to add option for choosing whether to use stock binary (without audio) or the one that comes with GB. For now, there's a workaround:
1) Copy /system/bin/screenrecord to /data/data/com.ceco.kitkat.gravitybox/files/ (replace the one that's there)
2) Set permission of /data/data/com.ceco.kitkat.gravitybox/files/screenrecord to 755
3) Disable "Use microphone", set Time limit to 3 minutes (this is the max stock binary allows)
Click to expand...
Click to collapse
This worked for me.
For some reason i cant install a number of apps. One being Handcent SMS. I've read that it's currently blocked from Play store due to a false copyright claim (or something along those lines).
The other one is a game installer.
In both cases i open the file explorer > select APK > open with package manager > it shows the usual permissions sceen with Cancel and Next/Install buttons but the Next/Install button does not react. It's not greyed out either. Cancel button works so it's not a touch issue with the screen (also doesent work in landscape).
Also certain built in features are not working and im not sure why. For example:
Settings > Accesibility > Switch Access > Ok (again Ok is not greyed out but not responding either). Cancel works.
I did find a few lines in logs that could explain this problem but im having trouble understaning what i can do to fix the problem:
Code:
W/AppSecurityPermissions(18100): Couldn't retrieve shared user id for: com.handcent.nextsms
W/ResourceType(18100): No package identifier when getting value for resource number 0x00000000
W/ResourceType(18100): Found multiple library tables, ignoring...
W/PackageManager(18100): Failure retrieving resources for com.handcent.nextsms: Resource ID #0x0
Current Firmware: 23.1.A.1.28
Model: D5803
Root: Yes (SuperSU 2.46)
Recovery: Yes (NUT's triple recovery ft. PHILZ/TWRP/CWM)
http://forum.xda-developers.com/xperia-z/help/unable-to-install-apps-apk-t2361942/page2 look at #12
MCBuhl said:
http://forum.xda-developers.com/xperia-z/help/unable-to-install-apps-apk-t2361942/page2 look at #12
Click to expand...
Click to collapse
Yep i figured that out some time ago. Tho i dont have Lux installed so it's another app most likely. Thankfully xposed+xinstaller module helps me to workaround this issue without disabling any apps.
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
Hi,
I have a Pixel 5 (Android 11 stock, but rooted) with Magisk (canary) version 6d88d8ad (21201). I also have the Developer setting for "Automatic system updates" turned off.
It seems to me like the phone is not able to detect (and thus never notifies about) any available OTA, such as the Dec 2020 "201205" OTA, since it has been out for a long time now. Note: I am not talking about installing OTA updates. Just checking for them and getting notifications of them being available.
Is this a known issue? If so, is it documented in an easy-to-find official up-to-date place, such as:
1) Within the Magisk manager app
2) On the Magisk github readme, github site, or github issues list (edit: in an OPEN issue, not a closed one)
3) In the official locked release thread
Hard-to-find or unofficial or outdated places where this would be documented would include:
1) Some XDA forum post somewhere (like this one. hypocrisy noted
2) A tweet by topjohnwu
Is it related to MagiskHide or hiding Magisk Manager? I didn't enable those until just now. Is there a specific package/app that can be toggled in the MagiskHide list to allow OTA update checks/notifications to work?
EDIT: Possible theories discussed below and elsewhere include:
1) Having your bootloader unlocked (independent of Magisk) prevents OTA updates from being made available to you [which to me is absolutely in conflict with my personal experience in the past]
2) Having Magisk installed prevents OTA updates from being made available to you [consistent with my experience]
3) Even after uninstalling Magisk, OTA updates are not made available to you for either some time or forever due to a theory that Google knows you had Magisk and penalizes you (either on purpose or perhaps as a protection from update failures including some time buffer for extra safety) [consistent with my experience]
4) If you ever manually check for updates while Magisk is installed, it prevents them from being made available to you then and subsequently (for how long I dunno). But for a Pixel device I find this to be nonsensical, since even with "Automatic system updates" turned off, a Pixel device will still check for updates (daily?) and notify about them. It just won't install them and prompt for reboot. With this setting on (the default), it will actually install them and prompt for reboot.
5) "if you even have magisk zip on your sd card, the update will detect and prevent OTA check/notification. This stays set until the next month's update"
6) "took a logcat while checking for updates and saw the update program errored complaining about a corrupt partition"
7) The carrier has actually delayed the update, and as usual very rarely is this information proactively posted in an official public place by the carrier even if the update is over a month delayed. See here for fun details on how carriers can delay updates that are created by, led by, and distributed by Google.
8) If you somehow have a current update from one carrier installed but your SIM card is for another carrier, this can prevent updates.
9) If you don't have the latest "Google Play system update" (Under Settings->Security), which is perhaps indicated by the icon next to it being red, that may stop OTA updates from coming. But this presents another issue if the "Google Play system update" can't be updated either. This type of update is also known as "Project Mainline".
10) Devices that say their "Play Protect Certification" is uncertified (Play Store Settings) may not receive OTA updates. In fact Google has a help page on this that actually says "Devices that aren't Play Protect certified may not get Android system updates or app updates"
11) Google has delayed or staggered the rollout of the update more than usual, but in my case this delay was longer than 1 month and I would imagine that this would be covered by the media if the delay took that long on Pixel devices, since it actually went past the release date of the next month's update.
Thanks
There's nothing official, but there has been similar reports here in the Magisk forums from time to time (you'll likely find finding if you search for a bit).
There's also been Github issues opened, like here:
No OTAs available with Magisk · Issue #2657 · topjohnwu/Magisk
Please see a reddit discussion I created for this issue. Since owning my Pixel 4XL since launch, and being rooted with Magisk, I've yet to receive one OTA update via the settings app. When a monthl...
github.com
I do not have any answers to your closing questions, but there are some tips and hints found here and there (like in the above linked GitHub issue).
Didgeridoohan said:
There's also been Github issues opened, like here:
No OTAs available with Magisk · Issue #2657 · topjohnwu/Magisk
Please see a reddit discussion I created for this issue. Since owning my Pixel 4XL since launch, and being rooted with Magisk, I've yet to receive one OTA update via the settings app. When a monthl...
github.com
Click to expand...
Click to collapse
Thanks! Actually after uninstalling Magisk (restoring stock boot image), I still have no OTA update showing as available, so for now it does seem that for whatever reason it really is not available for me and I presume it is unrelated to Magisk.
However, if you look at the comments on that github issue and the related reddit thread, several overlapping/conflicting theories are presented, including:
1) Having your bootloader unlocked (independent of Magisk) prevents OTA updates from being made available to you [which to me is absolutely in conflict with my personal experience in the past]
2) Having Magisk installed prevents OTA updates from being made available to you [consistent with my experience]
3) Even after uninstalling Magisk, OTA updates are not made available to you for either some time or forever due to a theory that Google knows you had Magisk and penalizes you (either on purpose or perhaps as a protection from update failures including some time buffer for extra safety) [consistent with my experience]
4) If you ever manually check for updates while Magisk is installed, it prevents them from being made available to you then and subsequently (for how long I dunno). But for a Pixel device I find this to be nonsensical, since even with "Automatic system updates" turned off, a Pixel device will still check for updates (daily?) and notify about them. It just won't install them and prompt for reboot. With this setting on (the default), it will actually install them and prompt for reboot.
5) See the first post for other items. The list in this post is no longer being updated.
But in general I wish this were better understood with supporting evidence on what is really happening, and can certainly try to contribute to that research myself if someone has suggestions on how.
Yes. I haven't seen anyone with any proper info on what is actually going on. Only (more or less credible) theories... But I haven't actually looked into it.
If I had a Pixel device I might have been tempted to do some research myself. The only possible piece of info I've got that could be remotely related is that OnePlus (at least used to, I haven't used an OEM build in years) detect root with their OTAs and would only offer the full ROM package unless you added the OTA service to MagiskHide.
I found that if you even have magisk zip on your sd card, the update will detect and prevent install of system updates. This stays set until the next month's update (at least that was my experience with pixel 3xl and my current 1+ 8 5g.)
Cheers,
B.D.
BostonDan said:
prevent install of system updates
Click to expand...
Click to collapse
Prevent the installation, or the OTA check/notification?
Didgeridoohan said:
Prevent the installation, or the OTA check/notification?
Click to expand...
Click to collapse
Didgeridoohan, you are correct. Prevent OTA check/notification. Sorry for my misleading verbiage.
Cheers,
B.D.
I have a Pixel 3, and I've had the problem off and on for the last 18 months or so. I've never been able to find any pattern on what causes it to start or stop working. I received OTA notifications and updates for several months after rooting my phone, then one month OTA notifications just stopped working (no longer detecting updates). I took a logcat while checking for updates and saw the update program errored complaining about a corrupt partition.
That continued until the end of September. The Android 11 update came out at the beginning of September, and I was still getting "no updates available". I delayed manually installing the update, and near the end of September the updater suddenly notified me of the update and was nagging me to install it.
I installed the update, and for a couple of months after that, I could check and install OTA updates by restoring the stock boot image. That stopped working after two or three months, and OTA notification has not worked since.
If you want to investigate further, check logcat for the OTA error.
Didgeridoohan said:
... OnePlus (at least used to, I haven't used an OEM build in years) detect root with their OTAs and would only offer the full ROM package unless you added the OTA service to MagiskHide.
Click to expand...
Click to collapse
Anybody know the package that is responsible for this on a Pixel? Is it com.android.google.gms?
dcarvil said:
... I took a logcat while checking for updates and saw the update program errored complaining about a corrupt partition.
...
If you want to investigate further, check logcat for the OTA error.
Click to expand...
Click to collapse
It's possible that "corrupt partition" just means a partition that is checked for integrity before an update has been modified, which could mean if you were rooted that the rooting (and for example magisk's modification of the boot partition on a pixel) was detected somehow. I'll try checking logcat too.
BostonDan said:
I found that if you even have magisk zip on your sd card, the update will detect and prevent install of system updates. This stays set until the next month's update (at least that was my experience with pixel 3xl and my current 1+ 8 5g.)
Click to expand...
Click to collapse
Thanks. In my case I do have the magisk apk and a magisk patched boot image in /sdcard/Download/, so I guess I could try removing those, but...
I checked with my carrier, who did in fact confirm that the update is delayed using language like:
"As of right now there is a delay and we don't have any additional info on it just yet"
"It is defiantly [sic] a delay. We are working with Google to resolve . You are able to check back for updates"
So I guess I would say I am like 75%+ confident that this is accurate and the cause of the delay for me.
After even more discussion with the carrier, they have revoked their prior statement and now say that because they do not sell the pixel 5 themselves, they do not ever delay updates for it and they are 100% up to google.
Since the January update is out, I got another logcat of my OTA update error. When I manually did the "Check for Update", the updater found the update, said it was starting the download, then said "Your system is up to date" without doing the update.
If I am interpreting this correctly, the reason for the update failure is system_b does not have the expected checksum. Magisk does not modify system, so whatever caused this is not Magisk. As far as I know, I have never modified system. I've never encountered any problems other than these OTA failures, so I am not convinced there really is a problem with system_b.
The same error occurs with both the stock boot image and the magisk patched image.
Code:
[ 01-05 11:51:13.144 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/system_b
[ 01-05 11:51:13.151 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(938)] boot_b is not in super partition metadata.
[ 01-05 11:51:13.153 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/system_b
[ 01-05 11:51:13.162 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1158)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[ 01-05 11:51:13.163 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1163)] Expected: sha256|hex = CC6CD98FB684FDEE9B4E8253338D4E8B34CAEC90FA533E638C45132C89DAA175
[ 01-05 11:51:13.164 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1166)] Calculated: sha256|hex = 8950BA8882AE17BC240BA54603811E50AC22FFE7E54706004F4D42ECF41FF24B
[ 01-05 11:51:13.165 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1177)] Operation source (offset:size) in blocks: 0:1,7916:1
[ 01-05 11:51:13.190 3159:14736 E/SystemUpdate ]
[Execution,PreDownloadValidateAction] UpdateEngine.verifyPayloadMetadata() failed.
@dcarvil That's different from the described issue in this thread though. Here, the update isn't even found at all...
dcarvil said:
[INFO:dynamic_partition_control_android.cc(938)] boot_b is not in super partition metadata.
[ 01-05 11:51:13.153 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/system_b
[ 01-05 11:51:13.162 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1158)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[ 01-05 11:51:13.163 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1163)] Expected: sha256|hex = CC6CD98FB684FDEE9B4E8253338D4E8B34CAEC90FA533E638C45132C89DAA175
[ 01-05 11:51:13.164 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1166)] Calculated: sha256|hex = 8950BA8882AE17BC240BA54603811E50AC22FFE7E54706004F4D42ECF41FF24B
Click to expand...
Click to collapse
You could probably look in /data/system/system-update-info.xml or maybe see here to find the URL of the OTA update zip that it is attempting to install.
Then download the zip somewhere, open it, and find where in the update script in it looks for the quoted expected checksum and verify what partition it is looking at.
And then you could just try to re-flash that partition from a factory image to get it back to normal.
Didgeridoohan said:
@dcarvil That's different from the described issue in this thread though. Here, the update isn't even found at all...
Click to expand...
Click to collapse
Correct. In my case, I don't see any error like this in logcat when checking for an update.
Although @dcarvil's symptom is that it seems to only say there is an update available for a split second and then go back to saying there isn't one.
scootley said:
You could probably look in /data/system/system-update-info.xml or maybe see here to find the URL of the OTA update zip that it is attempting to install.
Then download the zip somewhere, open it, and find where in the update script in it looks for the quoted expected checksum and verify what partition it is looking at.
And then you could just try to re-flash that partition from a factory image to get it back to normal.
Click to expand...
Click to collapse
The control.installation.current_update_url tag in the xml file is empty. I got a checksum of the system.img file in the December factory image, which is currently installed, and it does not match the expected checksum. That makes me a bit reluctant to try to fix system_b, as I am used to manually installing updates anyway.
Thanks for the suggestion, though.
dcarvil said:
I got a checksum of the system.img file in the December factory image, which is currently installed, and it does not match the expected checksum.
Click to expand...
Click to collapse
Is it possible that you have the December update installed for one carrier and your phone is checking for the OTA for another carrier? Did you switch SIMs or carriers? Looks like Verizon has its own OTA and other carriers use a separate one.
scootley said:
Is it possible that you have the December update installed for one carrier and your phone is checking for the OTA for another carrier? Did you switch SIMs or carriers? Looks like Verizon has its own OTA and other carriers use a separate one.
Click to expand...
Click to collapse
I suppose it is possible, but I don't think so. I have a non-carrier branded phone purchased directly from Google, with a Verizon SIM from an MVNO. I've always thought my OTA updates came from Google, but don't know how I would confirm that. I've never switched SIMs. All my manually applied updates have been Pixel Factory images (the non-Verizon version) direct from Google at https://developers.google.com/android/images.
Since I have had successful OTAs at times in the past, that doesn't seem likely.
dcarvil said:
I've always thought my OTA updates came from Google, but don't know how I would confirm that. I've never switched SIMs. All my manually applied updates have been Pixel Factory images (the non-Verizon version) direct from Google at https://developers.google.com/android/images.
Click to expand...
Click to collapse
Yes they come from Google but you can see on that link you sent that there are Verizon-specific Pixel 3 images (lately).
So if you you manually applied the non-verizon one from that page for a month when there was a verizon one (on the same site, listed right below/above the other images for that month), then later OTAs would presumably fail due to a checksum mismatch.
See here too.
EDIT: I don't think it matters where you bought your phone, but I could be wrong. In other words if you are on Verizon and there is a Verizon pixel image then that is the image that your phone will install even if you bought that phone from Google unlocked and without a carrier designation at purchase.
scootley said:
Yes they come from Google but you can see on that link you sent that there are Verizon-specific Pixel 3 images (lately).
So if you you manually applied the non-verizon one from that page for a month when there was a verizon one (on the same site, listed right below/above the other images for that month), then later OTAs would presumably fail due to a checksum mismatch.
See here too.
EDIT: I don't think it matters where you bought your phone, but I could be wrong. In other words if you are on Verizon and there is a Verizon pixel image then that is the image that your phone will install even if you bought that phone from Google unlocked and without a carrier designation at purchase.
Click to expand...
Click to collapse
That's interesting. Thanks for the info.
I downloaded the Verizon December factory image, but the system.img checksum in that image does not match the expected checksum either. I'm just going to stick with my manually applied updates for now. I do not want to get any Verizon software on my phone, even if that resolves the OTA issue.
Here's an update:
I got an OTA update notification for the December 2020 Pixel 5 update on 13-January 2021. This is about 7 days after re-rooting and enabling "MagiskHide Props Config" and using it to get SafetyNet to pass and to get my device to be Play Protect certified.
My regular MagiskHide settings have it enabled for:
1) com.android.dynsystem (including every sub-item within it)
2) com.google.android.gms (including every sub-item within it)
3) com.android.vending (including every sub-item within it)
I have no idea if those things are connected or if it's just a coincidence and something else (see my original post at the top of the thread) caused the delay.
Anybody out there who rooted their Pixel 5 with Magisk ever receive an OTA update notification?
I rooted mine during initial setup after I got it and never received a notification for the December 2020 or Jan 2021 update. Checking for an update says there isn't one available.
(The November 2020 update was out when I got the phone and I installed it before rooting)
I also have the Developer setting for "Automatic system updates" turned off and didn't enable MagiskHide or hiding Magisk Manager until a few days ago. But have since unrooted with no luck either.
My "Google Play system update" says "September 1, 2020" and has a red icon and I assume is also out of date.
I asked about this before here but in a different way. Not trying to spam.
See this thread and use it for discussion of more details, causes and solutions.
But you can reply here if you ever received an OTA update notification, or if you are like me and haven't.
The main reason I am asking about this is purely a curiosity on the cause and interest in whether there are other issues that result from the same underlying cause, whatever it is.
Also incremental OTA updates are faster to download/install, can be done without a PC, and nobody consistently publishes their URLs anymore (lots of permutations) so the only practical way to find yours is via the normal process. The OTA images google publishes online are not incremental. They are full. Just like the system images.
Note:
1) I would not intend to try to install the OTA while rooted
2) I know I can download the install the OTA image myself. My main concern is the OTA update check/notification here.
Here's an update:
I got an OTA update notification for the December 2020 Pixel 5 update on 13-January 2021. This is about 7 days after re-rooting and enabling "MagiskHide Props Config" and using it to get SafetyNet to pass and to get my device to be Play Protect certified.
My regular MagiskHide settings have it enabled for:
1) com.android.dynsystem (including every sub-item within it)
2) com.google.android.gms (including every sub-item within it)
3) com.android.vending (including every sub-item within it)
I have no idea if those things are connected or if it's just a coincidence and something else (see here) caused the delay.
I get OTA updates regularly. However, I can't find where the downloads reside. Since these are large files, if I don't delete them, they will grow big time, unless of course, the updater deletes them automatically after installation. My googling tells me they should be under /data/lineageos_updates, but I simply don't see this directory on my phone.
luckysoul777 said:
I get OTA updates regularly. However, I can't find where the downloads reside. Since these are large files, if I don't delete them, they will grow big time, unless of course, the updater deletes them automatically after installation. My googling tells me they should be under /data/lineageos_updates, but I simply don't see this directory on my phone.
Click to expand...
Click to collapse
Your Googling is flawed. Are you running LineageOS?
Android OTAs are stored in a temp directory. They aren't going to fill up your storage.
xunholyx said:
Your Googling is flawed. Are you running LineageOS?
Android OTAs are stored in a temp directory. They aren't going to fill up your storage.
Click to expand...
Click to collapse
Yes, I'm running LOS. I am also glad to know the OTA downloads don't go under /data/lineageos_updates, though it's mentioned all over the Internet. In fact, I haven't come across anyone else mentioned that the downloads go under a temp directory. If this is indeed the case, great. I am just surprised why no one else has mentioned if you google with keywords, "LineageOS OTA download directory"