Database Develop

Issues with android security patch level

Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?

Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.

You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.

Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.

fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.

I manually update mine every update and have yet to have an issue.

I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...

Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!

By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.

How to update R1 to the latest OTA Update?

Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!

KyleStilkey said:
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
Click to expand...
Click to collapse
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here

mrmazak said:
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
Click to expand...
Click to collapse
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.

KyleStilkey said:
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
Click to expand...
Click to collapse
Will be redoing the patch again and making not pre-rooted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.

mrmazak said:
Will be redoing the patch again and making not predicted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
Click to expand...
Click to collapse
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.

KyleStilkey said:
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
Click to expand...
Click to collapse
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom

mrmazak said:
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
Click to expand...
Click to collapse
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.

KyleStilkey said:
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
Click to expand...
Click to collapse
I have seen it mentioned that Google + does not work on 8.3 in general not just this modified one.
That recovery is the one I use and has advantage over the other one (lopestom's versio) in that in recovery you can use external sdcard and also mtp connection.

Update OP3 from 3.1.2 to OOS 5.0.1 (process and files required)

Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.

AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/

hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP

AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?

hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.

[ROM] TMO Z2 Force 27.1.5 / 27.1.7 FlashAll (Mar/Aug 2019)

This is a Motorola Z2 Flash T-Mobile FlashAll. It is based on @texasaggie1's October 2018 version and does not wipe user data.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Similarities to @texasaggie1's:
The image was downloaded from https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/,
ADB + Fastboot are included
Windows Only (FOR NOW)
Differences:
Updated for 27.1.5 / 27.1.7
Updated included TWRP
Cleaned up batch files
Upcoming Changes:
Bash script version for Linux/Mac
Include TWRP 3.3.1-0 instead of TWRP 3.2.3-2
Batch prompt to install black logo fix
Prerequisites:
Windows
Oreo or newer
Unlocked bootloader
(bootloader) _______: not found OR FAILED (remote: unknown command):
This is a known issue with Motorola devices. Here are some steps you should try:
Try another USB port
Use another ADB version
Try another USB cable
Use Windows 7
How To:
Unzip the Flashall
Open a command prompt in the folder it created
Connect the phone with ADB debugging enabled
Follow the section below based on what you would like to do
Return to Stock
Run flashall.bat
Return to Stock with Root
Run flashall_then_recovery.bat
Choose Install, then select the TWRP installer .zip
Choose Reboot, then Recovery
Choose Install, then the Magisk (recommended), or another SU .zip
Choose Reboot, then System
Return to Stock and Wipe All Data
Run flashall_erase.bat
Downloads
27.1.5 March Flashall
27.1.7 August Flashall - WARNING: USE 27.1.7 AT OWN RISK. Reports of WIFI+DATA bricking on LineageOS
Updated Flashall scripts - Updated 8/28/19, drop into an existing flashall above.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.

Can't Wait to Try It
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?

texasaggie1 said:
I will download it later and attempt to update my Z2 (now my wifes )
Thanks for doing this!
What command do I run if I just want to update the phone, but keep all of my data?
Click to expand...
Click to collapse
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)

rcmaehl said:
Assuming your on an older build of stock (e.g. 27.1.3) and want to update to this version, flashall.bat will update you. flashall_then_recovery.bat will also upgrade and also setup for installing root. For non-stock builds and newer android versions (Pie) there may be some issues with database versions and other niche issues (e.g. Camera and root based apps storing files in different locations because of new Pie limitations). I always back up all my apps+data using Titanium backup before any changes, helps prevent a lot of hassle.
Edit: Additionally, if you've checked for updates before the updater may still think you have an update. It's best to clear the updater's appdata once the flashall completes. (I may add this to a future version)
Click to expand...
Click to collapse
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?

tr4sh80 said:
Didn't work for me....it hangs and fails to flash. Here is a screenshot showing how far it gets for me. Ideas?
Click to expand...
Click to collapse
I've replied to you in the Z2 discord. I may need to make the file a bit more verbose. I'll update it after work today.

Worked for me, thank you OP. Said update unsuccessful after booting, but the build number shows 27.1.5 now.

Hi, isn't there Screenshot of the rom ?

mf2fx said:
Hi, isn't there Screenshot of the rom ?
Click to expand...
Click to collapse
Define screenshot? A screenshot of the version info? Or are you referring to a system image?

stuck
Mine is stuck like this. Any ideas?

I know this is for T-Mobile, but does anyone have the Verizon one? I am running a Sprint Z2 with Verizon and the update is failing for me :|

Same here
pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
I get the exact same. On 27.1.3

How would I install this coming from Lineage 16.0

Thanks so much for this!!

pacotort said:
Mine is stuck like this. Any ideas?
Click to expand...
Click to collapse
Commands aren't being fully sent to the device and are being cut off past a certain point. You can tell because of things like
slot-suffi: not found
partition-typ: not found
Click to expand...
Click to collapse
Do you have another version of fastboot and ADB installed somewhere? Additionally try another cable/USB port.

I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?

papadelogan said:
I was trying to go with LineageOS 16.0 (to get me some PIE!!!) but it kept borking on me... and then I was in boot-loop hell!!! This FlashAll got me back to functional and I may just stick with it. Pie might be newer, but stable & reliable are most important for me. Thanks so much for putting this package together! Maybe T-mobile/ATT/Sprint should hire the devs from this forum to help them 1) get Pie out for the Z2 Force and 2) honor their commitments. Boohoo... it's too much work for them to build & test the package.... but it wasn't too much for them to hold our their hand and take hundreds of $$$ from each of us, was it?
Click to expand...
Click to collapse
Thanks for the feedback! I do agree that it's extremely disappointing only the Verizon variants are getting Pie, but hey, they gotta upsell that 5G mod somehow...

I am aware of the 27.1.7 update and will be creating an flashall for it soon

Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
What sort of networking issues? WiFi or issues with service?

rcmaehl said:
Various users have reported 27.1.7 is causing networking issues. I will not be releasing a flashall for this until this is fixed
Click to expand...
Click to collapse
Can you post the link to 27.1.7?
I looked on mirrors.lolinet.com and it is not posted there yet.
I will try my own flashall and report back

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched

Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.

Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.

Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.

falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.

i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.

I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*