Database Info

Phone rooted - How about the monthly security patches ?

I was wondering, I have rooted my phone using Chainfire's CF-Autoroot.
Normally this will disable OTA updates, I'm aware of that.
But is there some way to manually flash the monthly security updates that Samsung releases each month ?
(or at least they say they are going to release them each month).
Is there a source somewhere where we can download them and flash then using Odin or TWRP ?

No you didnt root. There isnt full root for s7 yet

vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
Are you sure ? Because when I check manually for updates, I get the message stating that my phone has changed (root) and so updates cannot be downloaded and installed. It says that I need to try to download it via a PC tool from Samsung.

vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There is for the International version.

vipercoyote said:
No you didnt root. There isnt full root for s7 yet
Click to expand...
Click to collapse
There very well is for the Exynos version/type and the reason I'm tempted to get it after prices have dropped a bit :
Check it here: http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770

Ok guys, now that we have established that root is available and working for the European version (which I have)...
Anyone know if the monthly patches from Samsung/Google will be available for download somewhere, so we can flash it manually and still be up-to-date ?

I would like to know this as well. I would guess they could be flashed with Odin?

I would like to know this. I am on the W8 variant rooted with autoroot and wondering how will I go about updating to new patches.
Sent from my SM-G930W8 using Tapatalk

I love Android.

you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.

exploreresp said:
you should flash your firmware via Odin to unroot, apply OTA, root again with auto root.
Click to expand...
Click to collapse
Yes, I am aware of this possibility.
I was just hoping in applying the monthly patch without full flash (which completely wipes the phone).

Indeed, flashing will reset the phone...I found that the hard way last night.
There is a topic on S7edge forum about Chainfire's FlashFire app. It claims that can flash without resetting the phone.
Did not try it but I will follow the discussions there. Would be perfect to flash a new f/w and not have the phone reset. ( like good old times

Maybe it is possible to prevent the userdata and internal storage to be wiped by flashing the official firmware ?
Anyone has succeeded to do so ?

I managed to download the complete new firmware G935FXXU1APD3 from Sammobile and flashed it with ODIN with the phone in download mode.
It did not overwrite any of my personal data or apps and the phone worked as before however you will need to root again afterwards, but that doesn't take long anyway.
The only other thing I had to do was copy the mixer_paths and mixer_gain files to the SD card then replace them as the new firmware overrides the volume hack if you have it in place.
Keith

I guess that's what Chainfire trying to achieve with Flashfire. To be able to directly flash the Updates without having to manually backup/restore anything. Let's see how this goes. As of today you could flash the full oding images within flashfire.
Will definitely try when the next update for my phone variant comes.

I did take a TWRP backup just in case but was pleasantly surprised when the phone booted back to where it was.

I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!

databoy2k said:
I can confirm that the Flashfire method can be used for updates. Grab the update package, flash it through flashfire, and even select the "ever root" option to maintain root. Works great!
Click to expand...
Click to collapse
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?

brotbuexe said:
How did you get the update package? When trying to search for an update on the phone it says I modified it.
Or did you load an full stock rom?
Click to expand...
Click to collapse
Grabbed a full stock rom, extracted the modem and system packages, and flashed them specifically through flashfire. A link to the full stock rom was posted on the Canadian S7 thread in the discussion forum.

All things Marshmallow

All the other threads are kind of scrambled, so I made this thread to discuss all things marshmallow.
OTA
The OTA is rolling, many of us have gotten it, and those who haven't should get it very soon.
WHAT'S NEW
-Wifi Calling
-Android 6.0.1 Marshmallow
-Good Lock Support
-Battery Improvements with Doze
-Now on tap
-New app icons
-1 more bloat app
DOWNGRADE STATUS
I am happy to announce that after taking the Marshmallow OTA update, I have had NO ISSUES downgrading to PB1 using Odin.
ROOT
Root is here - only for unlocked bootloaders. Go to muniz_ri's thread for more info.
Locked bootloaders will probably never get root - Samsung have implemented dm-verity in the kernel - so modified system partitions will bootloop. The only way to get around this is systemless root - which requires a mod to the boot img, which is not possible on locked bl.
STOCK TAR
The stock tar is not available yet, but we're patiently waiting
UPDATE: It's on SamMobile.
PF4
Another OTA is rolling. This just fixed a small issue with unlock, and nothing else.
Post any questions/comments about MM below.

thank you very much for the information and work PD1 Root.

Good luck, I read ur all staring discussion, u were desperate. I hope we will find the easy step by step solution with no errors.
Sent from my SM-G900V using XDA-Developers mobile app

[email protected] said:
Good luck, I read ur all staring discussion, u were desperate. I hope we will find the easy step by step solution with no errors.
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Me too
thanks for the good luck

anyone have the file to flash through ODIN? I am not getting the update, and I wanted to get it installed before I travel tomorrow for the WiFi calling.
Thanks

ret4425 said:
anyone have the file to flash through ODIN? I am not getting the update, and I wanted to get it installed before I travel tomorrow for the WiFi calling.
Thanks
Click to expand...
Click to collapse
The .tar is not available. I am uploading the update.zip that you can flash via stock recovery atm.

ret4425 said:
anyone have the file to flash through ODIN? I am not getting the update, and I wanted to get it installed before I travel tomorrow for the WiFi calling.
Thanks
Click to expand...
Click to collapse
nevermind its at http://forum.xda-developers.com/ver...n-galaxy-s5-marshmallow-coming-t3389367/page8

Nandr0idC0nsumer said:
DOWNGRADE STATUS
I am happy to announce that after taking the Marshmallow OTA update, I have had NO ISSUES downgrading to PB1 using Odin.
Click to expand...
Click to collapse
Great news!
Is a wipe needed after downgrading? (Like it was with lollipop)
Sent from my Moto E using XDA Labs

yossijoe said:
Great news!
Is a wipe needed after downgrading? (Like it was with lollipop)
Sent from my Moto E using XDA Labs
Click to expand...
Click to collapse
Yes.

Nandr0idC0nsumer said:
All the other threads are kind of scrambled, so I made this thread to discuss all things marshmallow.
OTA
The OTA is rolling, many of us have gotten it, and those who haven't should get it very soon.
WHAT'S NEW
-Wifi Calling
-Android 6.0.1 Marshmallow
-Good Lock Support
-Battery Improvements with Doze
-Now on tap
-New app icons
-1 more bloat app
DOWNGRADE STATUS
I am happy to announce that after taking the Marshmallow OTA update, I have had NO ISSUES downgrading to PB1 using Odin.
ROOT
Root should be coming to MM very, very soon. I'm almost done.
STOCK TAR
The stock tar is not available yet, but we're patiently waiting
Post any questions/comments about MM below.
Click to expand...
Click to collapse
TheMasterMindGT said:
thank you very much for the information and work PD1 Root.
Click to expand...
Click to collapse
There won't be root for 6.0. As of 5.1 and continuing with 6.0, Samsung implemented a kernel check for any system modifications. The device will not boot when system is modified. A custom kernel is required in order to override the kernel checks which is out of the question for locked boot loader devices.
If you need root on this device you will have to stick with 5.0 or lower.

muniz_ri said:
There won't be root for 6.0. As of 5.1 and continuing with 6.0, Samsung implemented a kernel check for any system modifications. The device will not boot when system is modified. A custom kernel is required in order to override the kernel checks which is out of the question for locked boot loader devices.
If you need root on this device you will have to stick with 5.0 or lower.
Click to expand...
Click to collapse
Then how does jrkruse's note5 port work on locked bootloaders and still allow root - while being 5.1.1? does it still use a 5.0 kernel?

Nandr0idC0nsumer said:
Then how does jrkruse's note5 port work on locked bootloaders and still allow root - while being 5.1.1? does it still use a 5.0 kernel?
Click to expand...
Click to collapse
It would have to use the G900V Stock 5.0 kernel in order to boot.

muniz_ri said:
It would have to use the G900V Stock 5.0 kernel in order to boot.
Click to expand...
Click to collapse
Oh, dm-verity. Or, damm-verity
Us with unlockable bootloaders should still be able to root mm, right? I dont see why not, the supersu zip can disable dm-verity in the kernel on unlocked BL.
Can you please confirm this?

Nandr0idC0nsumer said:
Oh, dm-verity. Or, damm-verity
Us with unlockable bootloaders should still be able to root mm, right? I dont see why not, the supersu zip can disable dm-verity in the kernel on unlocked BL.
Can you please confirm this?
Click to expand...
Click to collapse
Sorry, meant incorrect. The kernel cannot be modified on a locked BL device.

I've already emailed in regards to the kernel source for PD1.
Just playing the waiting game

Nandr0idC0nsumer said:
Then how does jrkruse's note5 port work on locked bootloaders and still allow root - while being 5.1.1? does it still use a 5.0 kernel?
Click to expand...
Click to collapse
I modify the boot.oat and boot.arm files to allow the rom to boot with 5.0 stock kernel

muniz_ri said:
Sorry, meant incorrect. The kernel cannot be modified on a locked BL device.
Click to expand...
Click to collapse
Yes - but unlocked bootloaders should be in luck, right?

Nandr0idC0nsumer said:
Yes - but unlocked bootloaders should be in luck, right?
Click to expand...
Click to collapse
Yes

Ok jrkruse and muniz_ri have rooted it. Unlocked bootloaders can go get root now.
I think this is my exit from the VZW S5 community. I've had enough constantly trying to battle all these locks.

How do I go about getting rooted/unlocked again if I set my phone back to stock to take the OTA. Do I flash PB1 firmware then downgrade to Lolli? I'm confused at this point, but am not horribly concerned if I managed to lose unlocked capability....

New Update - QI2

According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.

so its safe to say that the new modem ql2 is pretty much the same sa the previous update?

Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.

Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse

For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse

I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.

You will also have to re-flash TWRP via Odon.

kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.

I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.

I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!

purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.

bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??

purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:

Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers

Samsung A11 got android 12 and I want to flash it (help)

So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!

????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.

Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)

????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.

Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.

I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.

????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.