Develop Bugs

Where is the OTA update??????

Ok
The first time it showed up (when activating), it offered the OTA update and I declined. Then I took it home, rooted the phone, and everything went well...
BUT I can't find the OTA update anymore... and the SD card bug is killing me!!!!
Is there any other way of installing it?????

From the main screen
Menu - Settings - System Updates
Check all 4 to see if any updates are available but im pretty sure "HTC software update" was the OTA

Actually go over to android central and download rvu 1.1 its based on the newest ruu with that update included and its still rooted
Btw this should be in general section not development

I know, but it keeps telling me that there is no update available!!!
And I am running
Baseband: 1.39.00.04.26
Build: 1.32.651.1 CL171253 test-keys
Software: 1.32.651.1
And it keeps telling me YOUR PHONE IS UP TO DATE
Is there any way to force it????

Settings > System Updates > HTC software update

dchamero said:
I know, but it keeps telling me that there is no update available!!!
And I am running
Baseband: 1.39.00.04.26
Build: 1.32.651.1 CL171253 test-keys
Software: 1.32.651.1
And it keeps telling me YOUR PHONE IS UP TO DATE
Is there any way to force it????
Click to expand...
Click to collapse
I don't recommend updating if you like root

bcnice20 said:
Actually go over to android central and download rvu 1.1 its based on the newest ruu with that update included and its still rooted
Btw this should be in general section not development
Click to expand...
Click to collapse
But, that ruu is missing may of the included apps (all the sprint and HTC ones, and I need them). Also, it wipes all the information....,
So, no other way?

Besides I read that that particular ruu kills the 4g radio...
So, I am the only one or most of you are running without the OTA update?
I like to root, in fact the wifi tethering is working great, but the SD issue is really annoying....

dchamero said:
Ok
The first time it showed up (when activating), it offered the OTA update and I declined. Then I took it home, rooted the phone, and everything went well...
BUT I can't find the OTA update anymore... and the SD card bug is killing me!!!!
Is there any other way of installing it?????
Click to expand...
Click to collapse
i too couldn't get the update to re-show up after not accepting it the first time. i went to system updates and tried both htc and firmware, and the OTA update still wouldn't show. Then i enabled wifi, soft reset, and boom, it showed up. Give it a try, worked for me....

vinscuzzy said:
i too couldn't get the update to re-show up after not accepting it the first time. i went to system updates and tried both htc and firmware, and the OTA update still wouldn't show. Then i enabled wifi, soft reset, and boom, it showed up. Give it a try, worked for me....
Click to expand...
Click to collapse
Well, I had it on wifi all the time, and no luck.... now... when you say "soft reset", how exactly? I just turn it off, and then turn it on again... Is there a soft reset option that I am missing somewhere?

If the root changed your recovery you likely won't get OTA's anymore.

bluehaze said:
If the root changed your recovery you likely won't get OTA's anymore.
Click to expand...
Click to collapse
Ok, that's what I was suspecting...
So.. what are my options now? Is there a way of getting the updates manually? or is there a way of changing the recovery back or modifying some settings to re-allow updates?

I had the same problem after installing one of the custom firmware images. Never could get the OTA to show up. I ended up installing the stock .6 firmware using the RUU.
Look for the "[ROM]RUU_Supersonic_1.32.651.6" thread in EVO 4 Android Development. (sorry, new user account on the forums, it won't let me post links yet).

dchamero said:
Well, I had it on wifi all the time, and no luck.... now... when you say "soft reset", how exactly? I just turn it off, and then turn it on again... Is there a soft reset option that I am missing somewhere?
Click to expand...
Click to collapse
No, you're not missing anything, I meant the same as you, power off, power on.....

SafeNet Android Pay fail after OOS 3.2.4 OTA

Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.

cadbomb said:
Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.
Click to expand...
Click to collapse
I have the issue with a freshly wiped, never rooted system (http://forum.xda-developers.com/showpost.php?p=68162872&postcount=59)
So I think something is broken with this update when it comes to SafetyNet.
Other people have the same issue on a never rooted system:
http://forum.xda-developers.com/showpost.php?p=68163301&postcount=8

I can confirm that android pay doesn't work.. even when you are not rooted. something is messed up with this update it seems

Yes, I concur. Android Pay is broken in 3.2.4 in the UK too. Very disappointed. I'm beginning to think the OnePlus name really means plus one new bug with every software update.

CTS profile match is "false" after getting the OOS 3.2.4 OTA update, breaking Android Pay

cadbomb said:
Has anyone else experienced this with their unrooted OP3? About two hours after my phone got the update it alerted me that the safenet check failed...
Only thing I can think is that I changed my DPI with fastboot some time before this update. Not sure if that caused it or not, but heads up if you've changed your DPI on an otherwise stock phone.
Click to expand...
Click to collapse
I saw it somewhere that OP is going to Breng another update 3.2.6 which is going to fix that

They seems to have fixed it in the backend, it is working now.

bluetooth closes immediately

I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?

ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!

ndd53 said:
I've seen a lot of posts about bluetooth issues, but I can't find anything about this: when I start BT on my pixel XL running 8.1 (the April security patch), it immediately closes. I'm fairly sure that it was okay in January, and maybe February; I think the trouble started with the March update. I have an unlocked and rooted (Magisk) phone, so I've been flashing my own updates. I thought about trying to flash an older version, but I'd rather not lose the security patches. where is the BT code? I know about the radio and modem images; is it one of those? any caveats?
Click to expand...
Click to collapse
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.

sliding_billy said:
Are you updating with an OTA or with the full system image? I am on the April update (full image with flash-all with -w removed) and rooted with Magisk. I use BT every day and have no issues at all. If you haven't done a full image, I would start there without the -w. If still an issue, I would suggest doing a complete image including the -w and doing a complete reset.
Click to expand...
Click to collapse
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?

bcradu69 said:
Hi!
I'm having the same issue here, but i tend to think that Magisk is guilty, on non-rooted March update everything worked ok.
I'm still looking for something Magisk-Bluetooth related, maybe there is a fix somewhere.
Goodluck!
Click to expand...
Click to collapse
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.

ndd53 said:
yeah, I do the full image without -w, and it's the April image that I'm having trouble with. I guess a wipe might work, although I was hoping to avoid it. would you happen to know where the bluetooth code is?
Click to expand...
Click to collapse
I don't, but to make sure... I am using 16.0 of Magisk.

ndd53 said:
Hmmm. I think I tried it on the April update before re-rooting; I might give that a shot when the May update comes out.
Click to expand...
Click to collapse
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.

bcradu69 said:
It seems that for me one of the Magisk modules was the problem, not sure which, but one of these two: Greenify or Crossbreeder lite, after i uninstalled these two my bluetooth started to work again.
Click to expand...
Click to collapse
that was it! I turned off Crossbreeder lite (didn't have Greenify) and now bluetooth is working again. thanks!

ctsProfile: false after March firmware

Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?

djy said:
Pixel 3 XL ctsProfile: false after adb flash-all (no wipe) with Google March firmware and patching boot.img with Magisk 20.3 on Beta channel. Never had an issue passing SafetyNet with this procedure until March firmware.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page286
Tried using this module but no luck.
Tried flashing back to February without wiping but I get an infinite animated google boot animation. Flashed back to March and rooted again but ctsProfile is still false. Anyone have an idea why I can't flash back to February and get it to boot? Should I flash the stock March boot.img before going back to February?
Click to expand...
Click to collapse
The SafetyNet issue had nothing to do with March update and occurred Thursday night into Friday morning on devices of all varieties and versions. There are plenty of other conversations going on including on the thread you linked. Looks like Google is finding unlocked BL again, and Play Store fails certification on reinstall even dirty from what I have seen. You can't flash back to Feb dirty. Going back to previous updates requires a full device reset as far as I know.

I just went in to magisk manager and saw that I also failed cts. I am on the lastest patch, patched with magisk; on beta. It was fine when I was on February

I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?

TonikJDK said:
I too am failing, but so far Google Pay is still working. Are we failing, or is the test in Magisk failing?
Click to expand...
Click to collapse
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.

I personally had to factory reset my Pixel 3 XL and root it again. I'm passing SafetyNet but the Play store is not certified.

TonikJDK said:
We are failing, the other half of this is an update to the play store. As soon as we get that update Google Pay will fail.
Click to expand...
Click to collapse
I paid with GPay at two vendors this morning with filed CTS and "not certified" Play Store. Of course that did not include adding a card, but can't be certified since a couple of dirty flashes this week.,

Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.

fonixmunkee said:
Getting the same error in Magisk since the March update, too. I didn't know there was other discussions going on about it. Got a link to share for the thread you're following?
I've tried dirty and clean flashing the March update and get the same error. I'm not brave enough to re-lock my bootloader to see if the error goes away, but I've pretty much trouble-shooted it down to that.
Click to expand...
Click to collapse
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311

sliding_billy said:
Here are a few (the 1st one has the most info), but there are others.
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228/page295
https://forum.xda-developers.com/ap...canary-channel-bleeding-edge-t3839337/page311
Click to expand...
Click to collapse
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?

Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Nope, stock kernel, rooted. Still fails.

Avasta said:
Thank you for this.. Thought I screwed something up while updating to the newest patch (from feb patch). I am not sure I can rule out the "kernel update" that was bundled into this new factory image for the pixel series. I see that according to these links, it seems to be wide spread across other devices and just is a coincidence that this occurred as we updated to the new factory image.
anyone able to get CTSprofile true on March 2020 image with magisk?
Click to expand...
Click to collapse
Again, this did not happen as a result of anything March update related. Tons of devices that were not updated (including two of mine that haven't seen an update in almost a year and a half) started failing CTS as something that Google pushed automatically like Play services or whatever. Nothing to do with Magisk or able to be fixed with Magisk right now. Looks like they are searching for unlocked BL, and nothing is able to obscure it or know what exactly it is looking at yet (kernel, Magisk).

See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author

sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.

sliding_billy said:
See John's recent Twitter posts. This explains a lot, and we are pretty well F'd. https://twitter.com/topjohnwu?ref_src=twsrc^google|twcamp^serp|twgr^author
Click to expand...
Click to collapse
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987

Exokan said:
Wow, this is one of the most disheartening (non-super-serious) things I've read in a while. Luckily, it seems like my current set of apps isn't affected by the failed ctsProfile, although that's probably going to change in a hot minute.
Click to expand...
Click to collapse
bobby janow said:
Since this is not really device (Pixels) specific you might want to consolidate the discussion rather that having to flip between threads. This one is in the 4XL forum.
https://forum.xda-developers.com/pixel-4-xl/help/march-update-ctsprofile-false-clean-t4062987
Click to expand...
Click to collapse
I was just posting this because I saw it a lot earlier than others and was trying to quash any more threads about CTS failing. I find the whole thing funny how Google tries to placate app vendors who don't really want fake security but want ad revenue (IMO of course).

Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.

djy said:
Just flashed April firmware, patched boot.img with Magisk 20.4, and ctsProfile = true now. "She falls down a well, her eyes go cross. She gets kicked by a mule. They go back. I don't know."
Edit: If you long press power button, a GPAY "add a payment method" balloon appears. This is new.
Click to expand...
Click to collapse
This is odd. I flashed my 3 XL also with the April update, patched boot.img with Magisk 20.4 last night. Safety Net failed until I deleted the Safety Patch module. I rebooted and was able to have Google Pay working again (used it this morning to make sure). I'm thankful it's working again. Now I can't update MagiskHide Props Config in Magisk. And if I remember correctly, the quick access to GPay with the power button was a feature drop a while ago.

Question issue with AA incremental update

I am on 11.2.4.4 (AA) and after reading about the success others were having I decided to take an incremental update, which shows up as 11.2.6.6 (unlocked/verizon). I followed the instructions found in many places, which consisted of restoring image in magisk, taking the incremental update, when finished I did not reboot, and then installed magisk to inactive slot. upon reboot my system still shows 11.2.4.4, and in the system update page it is still asking me to reboot, as if I needed to hit the system restart button in system update, which is very odd. also, I was running omega kernel, and after installing the update the kernel is back to stock, but for some reason the system has not updated and is still stuck on 11.2.4.4, and still has system reboot button on update setting screen. has anyone ran into this issue, and does anyone know how I should proceed? I am afraid if I hit reboot on the update setting screen that I will have some issue. I have also rebooted multiple times, yet the system has not updated. any help with this issue will be greatly appreciated!

When rooted you need the full update, not an incremental

You need to install 11.2.4.4 full update again in local update then the incremental will install

ryantf420 said:
You need to install 11.2.4.4 full update again in local update then the incremental will install
Click to expand...
Click to collapse
I've never heard of this method, where did you do this yourself and it worked? reinstalling a full update via local update actually forced your incremental update to take? also, how would this work when I would be installing things to different slots?

avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4

thirtythr33 said:
so you are basically in the same boat as me? an incremental update is not taking? yeah thanks for reporting that, I was skeptical about that method, but I'm thinking I'll try it anyway. if not, guess I'll have to wait until AA releases a full update other than 11.2.4.4
Click to expand...
Click to collapse
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.

Nathan.7118391 said:
Maybe you can download the full version of the 11 .2.4.4 from here and start over. The custom kernel combined with root may have messed it up. Happy modding!
Edit: only take full updates when rooted.
Click to expand...
Click to collapse
I know the thing is up until this point I've always went for full os updates, never incremental, but after reading many posts about other members taking incremental updates successfully, (restore images in magisk - take update - don't reboot - then install magisk to inactive slot) I decided to try it myself, and I should have never bothered. I'll just wait until a new full update comes out for AA and never bother with incremental again. thing is I followed instructions to the T, yet it didn't work, so I don't know how others have been successful with this.

avid_droid said:
Yeah that don't work. Didn't reinstall but I wiped and tried again. Still failed. Even edited craznazn package to fix model number and still that didn't work. Back to BA and have no issues updating
Click to expand...
Click to collapse
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....

ryantf420 said:
Yeah it does work
Or I wouldn't have gave advice
ota 11.2.4.4 twice, and 11.2.7.7 will install....
Click to expand...
Click to collapse
so since the incremental update I tried to apply is somehow "stuck" you are saying to local update 11.2.4.4 and then upon reboot 11.2.6.6 will be installed? and are you saying to ota 11.2.4.4 twice because of the slot I am on and would need to get back to that slot for the incremental update to apply? I am willing to try this but I've never heard of it, but hey if it works man then I am grateful

avid_droid said:
Don't get your panties in a bunch with that mad face haha. Just found it odd. I also wasn't rooted for the other gentlemen who said about root.was completely unrooted and fresh system update from BA to AA. Since there isn't a huge difference between 11.2.7.7 and 11.2.6.6 I'll just wait it out. Thanks guys
Click to expand...
Click to collapse
all good hdr is add to video but that's basically it. but method does work, did it on both my 9pro's

Hi, I just wanted to add that on the AA version(unlocked US version from OnePlus) the boot image have to match for the inc to install. Also I'm using props hide module and to manually select the OTA this has to be disabled (reverted). I ran into some issues at first but hopefully have it figured out.

So I decided to go to the EU version of the OS.
I did that on my 7 Pro and didn't have any issues.
So I'm on 11.2.6.6, running on Verizon with no issues.

Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.

dkcats3 said:
Here is my theory on why people are failing OTA. I think maybe their A and B slots dont have matching content before they OTA. Try using the lineageOS script to duplicate the active to the inactive slots first. I'm curious if that does the trick.
Click to expand...
Click to collapse
yes local update needs to be down twice...

ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
Would I have to wipe everything if I'm already on 6.6?

ryantf420 said:
yes local update needs to be down twice...
Click to expand...
Click to collapse
I decided to take your advice bro but I'm getting update installation error. I've tried a few times now and the full 11.2.4.4 I have will not install. so I'm unable to even install the full ota, did this happen to you? thing is the 11.2.6.6 incremental ota that didn't install is no longer in system update, now 11.2.7.7 is, so I don't know what is exactly going on bc my system still reports 11.2.4.4. any help is appreciated