Database Info

[GUIDE] Dirty update: stay stock, rooted, unencrypted and RETAIN ALL YOUR DATA

I've wrote it in many thread and I report here for users that want:
stay stock and updated
root (with Magisk)
unencrypted
never lose data and configuration
Here's my procedure, I'm using it since since I bought my S8 exynos (jun 2017), never had a problem, never lost a single bit of my data. And I don't know any alternative until now.
G950FXXU4DSDA (pie) tested​
I assume you have:
unencrypted device
oem unlock option checked (never uncheck it)
stock rom: any system mod is ok, but you'll lose it
What you need:
last odin (download here)
last stock rom for your country (download here)
last twrp on your exynos device (download here)
last Magisk zip on your device (download here)
Here's the steps:
if you haven't did before, create a magisk config file executing this two command on a shell (this file remain until you clean /data partition):
Code:
echo KEEPVERITY=false>>/data/.magisk;
echo KEEPFORCEENCRYPT=false>>/data/.magisk;
extract the rom and delete CSC_OXM_G950Fxxx (you don't need it, this file do the factory reset we don't want)
reboot you phone in download mode (boot with voldown+power+bixby)
connect your phone (you already have the driver, right?)
select all files in odin
uncheck auto-reboot option
press start
at the end manually restart the phone with voldown+power
the phone will boot in stock recovery and complete the installation ("Installing system update..." and "Erasing...")
keep attention because when rebooting you have to put your finger on voldown+power+bixby to return in download mode (if system boot your data partition will be encrypted)
in odin select TWRP file in AP slot
check auto-reboot option
put your finger on volup+power+bixby and keep there
press start
after a while you'll be in TWRP and you can relase the finger
flash Magisk
reboot in system
Then you can do any other mod you wan't, my favourites here.
I wrote this thread because all the guides I found skip the important (and tricky) 9-10 step and my tests results in:
interrupted csc install (twrp tried to execute a script producing "Error installing zip file 'CACHE:recovery/sec_omc.zip'")
empty CSC (Phone Info app) and no /system/omc folder
phone works well, but i'm not sure I was using VoLTE because I didn't see the icon
dial codes aren't working
korean operator "KT" voice in settings

Anyone else tried this method? Hoping to give it a try later this week when I have some time should something go wrong

so on s8 works too. nice. I've been doing this on my S7 edge every FW update. dirty flash, then root then xposed. So I hope this trick works in my S8 too.
are you on Nougat or Oreo?

Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.

t12icky0 said:
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
Click to expand...
Click to collapse
this way works like an ota for my experience, not a single issue in one year of updates

Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk

zelenko said:
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
if you've never modify the phone, you're encrypted
if you,re encrypted, you need to format your data partition to get root permission (for what I know is not possible / not safe to stay encrypted)
you can follow my guide adding a format data step before flashing supersu, but the phone will be factory reset

so after doing this i'll still get ota updates and i can install them fine plus having the root privileges ?

No, I've never tried ti install otas (I expect it will fail).
To stay updated you have to repeat the procedure whit the new stock image, usually released before the ota.

pie tested ​:good:

Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk

can you help me please???

silverik1 said:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
Click to expand...
Click to collapse
Confirming, it's working perfectly
@c3k ,
Thanhs for this great solution !!
m.

I still have the stock rom and rooted with magisk. But in twrp I can not mount the data partition. Is it because it's still encrypted ?

... that's what I assume but it`s strange because you should be decrypted already after formatting data installing twrp, magisc etc. ...
m.

Yeah..I know...any suggestions ?

... it sounds like a data format is needed then ... Or does this method from c3k work for you ... ?
You `ve the latest TWRP installed?
m.

How do I install the latest one if I have an older version ? Can I use flashify for it ?

Or with twrp itself ?

I install new twrp via the installed one as an img file.
m.

[TWRP + ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0) (Boost Mobile)

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737p) (Oreo 8.0)​
DISCLAIMER: THIS IS NOT AN ODIN FLASHABLE TWRP. THIS IS NOT AN OFFICIAL TWRP. THIS IS A TWRP PORT THAT HAS BEEN MADE POSSIBLE BY BOTH @Dark98 & MYSELF. IT WAS BUILT USING FILES FROM R16NW.J737PVPU1ARG3. IT MAY OR MAY NOT WORK ON DEVICES WITH A DIFFERENT BOOTLOADER VERSION
You must have root access. I am currently working on making an Odin-flashable .tar for TWRP devs. Hopefully it will be available soon. Until then, root your device with Magisk. SuperSU is dead..
There is a downside & an upside to porting TWRP. The downside is that after you flash TWRP, you will lose root. The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip. It's a very delicate process & you will need to pay attention or else you will bootloop & start over.
In order to flash, you need an app that will do so without booting into recovery. Flashify is the ideal choice for this procedure. View attachment flashify.apk Flash TWRP in Flashify but do not reboot from the app. Power off your device & boot into TWRP manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Boot into TWRP for the first time
- Swipe to allow modifications
- Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once wipe is completed, go to TWRP home screen & Reboot > Power Off
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to restart.​First boot is to clear out the /Data partition to make room for your new recovery. Second boot is to secure it.​
Now that you have secured TWRP, go ahead & make a backup of your Boot + System + Data partitions. Keep in mind that you've lost root access so the backup will be "stock" firmware with TWRP.
------------------------------------------------------------------------------------------------------------------------------
Now to get root back
(In TWRP)
You will now flash Magisk-v18.1. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks. YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
In this order, flash:
- View attachment Magisk-v18.1(18100).zip
- View attachment no-verity-opt-encrypt-6.0.zip
- View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Now reboot device normally. If you do not flash the verity & RMM zip files in order, you will fυck your sh¡t up & have to start over.
PROOF OF TWRP:
View attachment 4730415
View attachment 4730414
View attachment 4730413
View attachment 4730412
When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager. Allow Magisk to install the update, not TWRP.
Extract the .tar from the .zip > extract the twrp.img from the .tar View attachment J737P.zip
This is for the Galaxy J7 Refine (SM-J737P) (RUNNING OREO 8.0) (J737PVPU1ARG3)
Special thanks to @topjohnwu for Magisk
Special thanks to @Dark98 for working with me on this project. Probably could've done it without you bro but it would've taken longer

work for j737t and j737t1?

juniorgerman said:
work for j737t and j737t1?
Click to expand...
Click to collapse
The root method should, provided you substitute in your own patched_boot.img from your stock firmware.
TWRP however, will not. Those variants are GSM Carriers (T-Mobile network). This is for Boost, a CDMA Carrier (exynos7885)

Thank you
Thank you for this as I will give it a go.

Kireej said:
Thank you for this as I will give it a go.
Click to expand...
Click to collapse
This thread should've been deleted already as it's not the main one. I've moved it to here. Please direct any further comments or inquires here as well.

Is there a rootable method for the J737P 9.0 Android update?

LeThAiL JoKeR said:
Is there a rootable method for the J737P 9.0 Android update?
Click to expand...
Click to collapse
Hello, I have a Galaxy J7 Refine from Boost. Recently I decided to root it. There are only a few places that have ANY info on rooting SM-J737P.
Not realizing that this was an OLD thread, I basically just went along with this and a little info from somewhere else and some knowledge of rooting from back when I basically HAD to have my phone rooted.
Good news is, first try it worked for me. But I had this issue that I figured would be easy to remedy.
There is a notification when I boot the phone saying Unauthorized actions have been detected. Restart your device to undo any unauthorized changes.
Without doing any research on the notification I immediatly lept into action and caused the phone not only to boot loop, but also not be able to boot into recovery, where I had made my backup.
I tried flashing several roms/files and trying to figure out the issue, I realized that this was an old thread and the Binary Update number on my phone was 7, and here i was trying to flash 1's, 2's, 4's, 6's. Like no wonder they didnt do anything to help.
Immediately trying to search for U7, I was hitting road blocks, because it seems as though everyone's list stopped at U6.
Fortunatly for you, I would not take no for an answer and spents HOURS trying to figure out what file I needed and then locating it. Not being able to boot into OS or Recovery, figuring out what version my phone was on was a bit tricky. Cross referanced this info with that info, yada yada yada.
I found the most up to date file in case you brick your phone, but also if your still interested, I can help supply the info and files I used to accomplish this.
But as I type this, I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
I'll get back to you on those results. For now, im done typing. I haven't typed this much in a LONG time.

I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
(Disable the app called securitylogagent do no th delete will cause bootloop) I am looking to see is there new firmware u7. i have binary 6 rooted and would like to find u7 to try root?

Disable image
......fix that notification

I found out using lucky patcher to get rid of notification. Which that was the first app I was going to install anyways. So it worked out great.
As far as the u7 binary, I found it. I'll upload it to drive and share a link here shortly.
Currently uploading file to folder, but when its done you should be able to access it here.
https://drive.google.com/drive/folders/1MD3owVbiAjgSyz0-f4Q_eSATV1zcXZeZ?usp=sharing

hello i'm on the u7 binary i'm having trouble rooting can someone share a link for the patched boot for the u7 or a flashable twrp if there is one? any help is appreciated and thank u

never mind i got it thanks anyway

How do you root a Samsung Galaxy SM-J737P Version 9

PlsHelpMeRootingImBegging said:
How do you root a Samsung Galaxy SM-J737P Version 9
Click to expand...
Click to collapse
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above

weric43 said:
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
Click to expand...
Click to collapse
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible

PlsHelpMeRootingImBegging said:
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
Click to expand...
Click to collapse
I have the twrp flash file give me a few mins I'll get it to u

weric43 said:
I have the twrp flash file give me a few mins I'll get it to u
Click to expand...
Click to collapse
download files unzip files inside u will find flashable twrp

okey

PlsHelpMeRootingImBegging said:
okey
Click to expand...
Click to collapse
Did u get it?

weric43 said:
Did u get it?
Click to expand...
Click to collapse
so i installed magiska and tapped install to the tar file idk it never flashed so i tried again and it said their was no recovery.img found

Root SM-J410G - J4 Core

Is it possible to route a samsung galaxy j4 core?
I could not install twrp and no other custom recovery.
Any suggestion?

izCaio said:
Is it possible to route a samsung galaxy j4 core?
I could not install twrp and no other custom recovery.
Any suggestion?
Click to expand...
Click to collapse
See the Magisk thread.

ashyx said:
See the Magisk thread.
Click to expand...
Click to collapse
Link, please.

izCaio said:
Is it possible to route a samsung galaxy j4 core?
I could not install twrp and no other custom recovery.
Any suggestion?
Click to expand...
Click to collapse
It is possible! You're kindly invited to visit my thread! ?
https://forum.xda-developers.com/android/general/thread-t4017391

Might I add something. After doing all the steps of thimprfct , enable developer option again and see if oem unlocking is there and tick on or else if you reboot the phone you will be stuck on ONLY SAMSUNG OFFICIAL DISPLAY. So don't reboot until you see the oem unlocking ticked on in developer option. It will appear after a day you flash the patched boot file.

@Star Dust,
[good that you mentioned! I will add that issue in my thread. thank you!
I've added the issue to the guide, to make it complete.]
I'm happy that you were able to root your device through my guide!
afaik & spoken from my own experience, oem unlock button should be enabled automatically after flashing the patched boot.img.
this is what magisk generally does.
a wait time of 1 day or more is NOT what happens
if you already unlocked the bootloader before root.
this is a WRONG information.
and also a wrong information is, that everyone is stuck at the samsung boot logo when oem unlocking is off/the bootloader is locked again while rooted.
normally, what happens is, that your device becomes unrooted and/or does a factory reset.
there must have been another issue! ---
are you sure that you have enabled oem unlocking before root, as in the guide?
make sure to disable system auto update in developer options after root!
rule of thumb:
[the steps you made before root on your phone- think about them also after root. what I mean is, your device was reset, so some settings have to be re-applied (eg looking if oem unlocking is on).]
there's smth more to look at, after root.
I'll post a thread with more guidelines, soon.
what else have you done in/with your phone?
please tell me & let's see if we can reproduce what has happened!
always best wishes for you!

Root in J4 Core SM-J410G
izCaio said:
Is it possible to route a samsung galaxy j4 core?
I could not install twrp and no other custom recovery.
Any suggestion?
Click to expand...
Click to collapse
Try Magisk. Thread here XDA.

Hi y'all really interested in this device & rooting it, flashing, get a twrp one day for it...
Here's my new thread for the Samsung Galaxy J4 Core with ROOT GUIDE!
Feel free to join!
https://forum.xda-developers.com/android/general/thread-t4017391
?

And here is: THE MAGISK THREAD:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
cause I'm nice & I am awesome! ?

@thimprfct
It happens to me a couple of times. I already rooted my j4 core even before you posted your tutorial.
Everytime I flash the patched boot.img or even doing a factory reset while rooted, the oem unlock switch disappear briefly in the developer option. If I restarted the phone before the switch appears, boom the phone always got stuck in ONLY SAMSUNG OFFICIAL message and then I rebooted to bootloader and it states the KG STATUS : PRENORMAL when it should be just CHECKING if your rooted and the oem unlock switch is tick on. I reproduce the issue many times. I flash the patched boot.img then reboot to recovery then factory reset then set up the phone then install magisk app then activate developer option and oem unlock switch is not there. It always appear to my phone after a day or atleast more than 12 hours.

kapmino269 said:
wait twrp ....... @SebaUbuntu is working on it ...
I don't have pc to build it ..
Click to expand...
Click to collapse
Oh man!!! That's a good news then.

Star Dust said:
@thimprfct
It happens to me a couple of times. I already rooted my j4 core even before you posted your tutorial.
Everytime I flash the patched boot.img or even doing a factory reset while rooted, the oem unlock switch disappear briefly in the developer option. If I restarted the phone before the switch appears, boom the phone always got stuck in ONLY SAMSUNG OFFICIAL message and then I rebooted to bootloader and it states the KG STATUS : PRENORMAL when it should be just CHECKING if your rooted and the oem unlock switch is tick on. I reproduce the issue many times. I flash the patched boot.img then reboot to recovery then factory reset then set up the phone then install magisk app then activate developer option and oem unlock switch is not there. It always appear to my phone after a day or atleast more than 12 hours.
Click to expand...
Click to collapse
btw @Star Dust, thx for your honesty! (that u rooted before my tutorial & didn't have your problems because of my tutorial) I appreciate that very much!
1.)while rooted, you can update magisk (patched boot.img) through magisk manager app. this way you avoid yourself much trouble.
in magisk manager settings you can tick the option: 'magisk hide-hide magisk from various forms of detection', this could help with your phone.
in magisk manager app main screen where you can update magisk/magisk manager, open the advanced settings & untick: preserve force encryption, preserve AVB 2.0/dm-verity, recovery mode. take care that these 3 are always unticked.
when you have twrp you can tick recovery mode to use it through magisk, but you will need a special module before you can use it.
2.)try flashing magisk patched boot.img without factory resetting your phone.
the phone will wether factory reset by itself after flashing (you only have to press one button during the boot process), or it boots straight to the home screen.
If you really want to start clean, I recommend to reflash your firmware with odin & re-root instead.
at least before we hopefully have a twrp!
best regards

@thimprfct do you know some custom ROM for the J410G? It is possible to change the Android Go to regular version?

Levi Stark said:
@thimprfct do you know some custom ROM for the J410G? It is possible to change the Android Go to regular version?
Click to expand...
Click to collapse
I'm myself searching... will let you know if I found smth.

Hola amigo. Puedo ayudarte.
izCaio said:
Is it possible to route a samsung galaxy j4 core?
I could not install twrp and no other custom recovery.
Any suggestion?
Click to expand...
Click to collapse
escríbeme al +57 3007817319

[Guide] Update and Retain Root

*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse

If you do it this way you'll be using the patched boot image from the previous update and not the current one.

airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.

For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.

pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.

So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!

DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

This work for the Verizon Pixel 4 XL???

SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.

Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.

Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?

Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img

When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it

Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.

mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC

eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol

2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover

This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom .​
Downloads
S5_Root_Tools_2023.7z
EMMC_15_Rom.zip -- Stock QL1 6.0
Directions For Unlocking Stock Phone
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. Once process is done reboot too twrp and flash rom of choice or use provide one and flash root zip of choice
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Old Method And Old Downloads
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip -- Rom Zip
EMMC_11_S5_Root_Tools_2022_V7.7z
-- Files Needed To Root Phone
Instructions To Root And Install Safestrap
**If you already have safestrap installed you can skip to Instructions To Unlock Bootloader
**If you are already rooted but do not have safestrap installed download View attachment S5_Safestrap.apk install then skip to Instructions To Unlock Bootloader**
Directions
1. Download both files and unzip EMMC_15_And_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1Click bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox must be installed ifirst if you used towelroot method too root
Instructions To Unlock Bootloader
11. Enter safestrap now in safetrap it will ask you to swipe to allow modding system make sure to do this now . If you have not copied the EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip from the EMMC_15_Bootloader_Unlock_Zip folder do so now Click install tab and choose EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip and install.
12. When done phone will power off.
13. Reboot phone to recovery you should now have TWRP recovery installed and the choose wipe the advanced wipe and wipe data only then reboot
14. Phone will reboot and stick on red Verizon screen for probably 15 to 20 min be patient. When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with EFTSU with root hide and safetynet pass module
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with unlocking bootloader step 11 you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Credits
beaups Sourcecode and tool
ryanbg
haggertk For his CID
autonomousperson For compiling the source to a app
magic_man185 For compiling the source
GeTex
klabit87 - Basically Everything
@GSMCHEN Lots of stuff
elliwigy Lots of stuff
afaneh92 -Safestrap and too much too mention
Sourcecode
https://github.com/beaups/SamsungCID

Instructions for downgrading or updating bootloaders can be found here
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
​

jrkruse said:
mine
Click to expand...
Click to collapse
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms

stang5litre said:
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
Click to expand...
Click to collapse
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days

@jrkruse awesome job...!! :good:You definitely must be bored... Lol. May try that on an old one for craps and giggles... Lol. Again, awesome to bring a lil history back to life... :good:

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
Nice job man, much appreciated.
If you ever get bored try to make a pre-rooted rom/safestrap recovery (course no bootloader unlock) for the G930U/G935U with the latest firmware UUESACSI1 (Aug 27 2019), since it looks like Samsung has stopped updating this phone, or better yet a root-patcher for a stock sytem.img like you did for the G950/N950. I have uploaded the latest eng-boot vA/10 here: https://forum.xda-developers.com/sho...postcount=1826

jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.

googlephoneFKLenAsh said:
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ent/vzwemmc15chipset-dev-bl-unlocked-t4010757
Sent from some device I modified

the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?

bigstack said:
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
Click to expand...
Click to collapse
What are you extracting it with?
Sent from some device I modified

First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?

Remedy1230 said:
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Click to expand...
Click to collapse
Its really no easy process to flash an international rom if you are using Verizon then data will probably not work with out some editing. You can always try it but Verizon will probably need Verizon csc stuff to work and build.prop edits.
Sent from some device I modified

Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?

SaltedSand said:
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
Click to expand...
Click to collapse
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified

jrkruse said:
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
Click to expand...
Click to collapse
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but needs device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified

al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Yeah that's what I have in mind.
jrkruse said:
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
Click to expand...
Click to collapse
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.

SaltedSand said:
Yeah that's what I have in mind.
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
Click to expand...
Click to collapse
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified

jrkruse said:
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
Click to expand...
Click to collapse
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.

SaltedSand said:
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
Click to expand...
Click to collapse
If you stop at 12 you will just have king root and some apps work with kingroot but some do not
Sent from some device I modified