Develop Bugs

Where is the July security update?

Google's schedule has been to release the latest security updates on the first Monday of the Month. Does anyone know why that didn't happen this month, or when it is scheduled to be released?

Holiday weekend, maybe?

That's what I was thinking, but I figured the update would have to be ready and it wouldn't be hard for their servers to release it at a specified time and date without human interaction. With that said, I find it hard to believe Google campus is empty on the 4th of July.
Sent from my BTV-W09 using Tapatalk

https://source.android.com/security/bulletin/
looking at the previous release dates, it may not always be on the 5th.

JimSmith94 said:
Google's schedule has been to release the latest security updates on the first Monday of the Month. Does anyone know why that didn't happen this month, or when it is scheduled to be released?
Click to expand...
Click to collapse
I can just hope that it's because they're fixing the bluetooth stutter that people are having with playing music through bluetooth. That's the only thing that I can find fault with.....that's pretty good.

It's out. Downloading it now. Hoping the July bootloader doesn't require AVB like Mays BL did.

3aucla1r3 said:
I can just hope that it's because they're fixing the bluetooth stutter that people are having with playing music through bluetooth. That's the only thing that I can find fault with.....that's pretty good.
Click to expand...
Click to collapse
FWIW I have not had the stutter, I enabled developer options and selected "enable optional codecs" under Bluetooth Audio codec and "AVRCP version 1.6" under Bluetooth AVRCP Version with no issues. I'm currently using the default codec with AVRCP 1.6 selected at this moment with no issues.

Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.

TonikJDK said:
Installed. Booted to TWRP, flashed SU 2.79 RC3. All is well, no bootloader signing needed. It did reboot twice after SU install. I did not install TWRP.
Click to expand...
Click to collapse
Just got done checking the bootloader/radio versions. They are exactly the same as the June release.

@TonikJDK, did you fastboot into TWRP? Out of curiosity from your statement of success, I decided to try updating without installing TWRP and lost TWRP accessibility as a result. I needed to reinstall TWRP so that I could install SuperSU, so the previous method of updating (boot recovery>flash OTA, TWRP>reboot recovery>flash SuperSU (if the version includes the boot signer)>reboot normally) appears to still be the appropriate method.

Jon8RFC said:
@TonikJDK, did you fastboot into TWRP? Out of curiosity from your statement of success, I decided to try updating without installing TWRP and lost TWRP accessibility as a result. I needed to reinstall TWRP so that I could install SuperSU, so the previous method of updating (boot recovery>flash OTA, TWRP>reboot recovery>flash SuperSU (if the version includes the boot signer)>reboot normally) appears to still be the appropriate method.
Click to expand...
Click to collapse
I dont install TWRP, yes I just fastboot boot it So for my needs the modified flashall method is clean and easy.

TonikJDK said:
I dont install TWRP, yes I just fastboot boot it So for my needs the modified flashall method is clean and easy.
Click to expand...
Click to collapse
Gotcha, thanks for the clarification.

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Updates fail to install

I have a Sprint Moto Z2F, BL unlocked, rooted running the stock ROM
I've tried to return back to stock, recovery and not rooted but bootloader is still unlocked and tried to take the update but it always fails to install. What am I doing wrong?

hello....Bueller, .Bueller

Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates

TwoBuells said:
Well reading other threads, if you unlock your bootloader and root, then go back to stock you can't get OTA updates
Click to expand...
Click to collapse
From another post I read from @Uzephi just recently there are some users who have been able to return to stock and receive the updates but IIRC there is a certain procedure to follow for it to work. Search @Uzephi's post and you'll be able to find it.
Sent from my Moto Z2 Force using XDA Labs

To add to what @fast69mopar said, here is the thread you should check out.

thanks

Yes, follow that thread. I have never had an issue getting updates on my sprint variant.

Uzephi said:
Yes, follow that thread. I have never had an issue getting updates on my sprint variant.
Click to expand...
Click to collapse
I've tried three times, I'm not wiping or formatting data, mounting the right way or order, when I get some time I'll try again. phone is running fine now, I just have updates frozen now so the notifications don't bug me.
Flashall works great,
I fastboot boot the TWRP.img file
then boot into TWRP, flash the TWRP zip and Magisk zip files.
I get a " can't mount system error", I'm not sure what to have checked when I wipe after installing TWRP
I tried to install the TWRP 3.2.2.0 but could never get the phone to boot after installing twrp zip
TWRP 3.2.1.0 is the only TWRP I can get to install and boot.
I have something overwriiten or not installed correctly \
I have to do some more reading of these threads and see where I'm doing wrong.
this slot a and b is confusing, maybe I did something wrong there. ( I really have not done anything with slot a or b, just installed files like those slots are not there. maybe one of them is corrupt

I tried a few more times but still can't get the OTA update to install.
I put my phone in the fastboot mode
I run Flashall
Flashall does its thing then when I reboot I sign in to my Google account, the phone is activated to my carrier. I get a notification for the system update, then it fails.
I go back to fastboot, flash and setup TWRP then root and restore my data and I'm back to normal
after Flashall my phone is back to stock, I tried to let the OTA update install and it fails everytime.
Maybe I should try some different ROM's since its so easy to get back to stock if something goes wrong.

Galaxy S9 (Only official released binaries are allowed to be flashed)

Samsung Galaxy S9 (SM-G960F) New Zealand
Hi, I'm new here, new to flashing ROMs, and I'm lost...
Today I flashed TWRP using Odin, then booted to system.
I then rebooted to TWRP, copied a no-verity zip to the internal storage, and installed.
Booted successfully to system again. Nice.
I'm on my way to LineageOS .
I rebooted again, as a test, yet it resulted in a BRICKED STATE!! Only official released binaries are allowed to be flashed.
Now I can only get into download mode, not recovery. Nice... I'm so disappointed.
I will post my results here, after flashing a stock ROM. I assume this will take me back to square one.
But what had I done wrong here, that I can alter next time I attempt to simply install TWRP?!
Luther

LutherChelm said:
Samsung Galaxy S9 (SM-G960F) New Zealand
Hi, I'm new here, new to flashing ROMs, and I'm lost...
Today I flashed TWRP using Odin, then booted to system.
I then rebooted to TWRP, copied a no-verity zip to the internal storage, and installed.
Booted successfully to system again. Nice.
I'm on my way to LineageOS .
I rebooted again, as a test, yet it resulted in a BRICKED STATE!! Only official released binaries are allowed to be flashed.
Now I can only get into download mode, not recovery. Nice... I'm so disappointed.
I will post my results here, after flashing a stock ROM. I assume this will take me back to square one.
But what had I done wrong here, that I can alter next time I attempt to simply install TWRP?!
Luther
Click to expand...
Click to collapse
sorry I only know for stock firmware

leap_ahead said:
flash stock rom with odin ,
go to software update
and check for update …
flash twrp,...
keep read only
format data type YES
reboot to recovery
keep read only
copy the patch
flash patch
reboot to system
go to software update
and check for update …that's fix the problem !
Click to expand...
Click to collapse
Thank you for the clear reply!
But what is the patch you speak of? LineageOS?
Luther

LutherChelm said:
Thank you for the clear reply!
But what is the patch you speak of? LineageOS?
Luther
Click to expand...
Click to collapse
no-verity-opt-encrypt-samsung-1.0.zip

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.

Bootloop in logo S9

RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up

Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961

https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me

S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q

viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.

it stucks for me on the samsung logo

aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod

omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it

viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?

Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.