Database Info

Managed to flash MM 6.0.1 T-mobile firmware on Verizon S5 with CID 11

Not responsible for anything that goes wrong.
Follow the steps Here EXACTLY then install Super-Su Me
(You need Super SU to continue)
Once you're done download Here and
Put 'G900TUVU1GPE1_G900TTMB1GPE1_G900TUVU1GPE1_HOME.tar.md5' in your sd card or phone storage (doesn't matter)
Install Flash fire (allow root) and touch the plus on the bottom right. Select "flash firmware package" and select the file you put in your storage.
Once it is finished you're gonna see it reboot and show a screen telling you it failed. Take out the battery and reboot into Download Mode.
Launch Odin, press AP and flash both the recovery and the boot files.
once done, remove you're battery and reboot into recovery, wipe data and cache.
you're all done!
Boot may take a while (2.40GB Firmware) so make sure it stays in a cool place. It will get hot.
Screenshots coming soon

Can we get a link to the T-mobile firmware? Great find!!! I can't wait to see some nice 6.0.1 roms.

This should have hardbricked your device, you got very lucky.

Lightn1ng said:
This should have hardbricked your device, you got very lucky.
Click to expand...
Click to collapse
No hardbrick just a softbrick. Remember flashfire only flashes the bootloader partition when a checkbox is checked.

Hariiiii said:
No hardbrick just a softbrick. Remember flashfire only flashes the bootloader partition when a checkbox is checked.
Click to expand...
Click to collapse
I believe the bootloader checkbox is checked by default. I use TWRP so I don't quite remember.

Lightn1ng said:
I believe the bootloader checkbox is checked by default. I use TWRP so I don't quite remember.
Click to expand...
Click to collapse
Nah you have to go all the way in to settings to change it and you get a warning confirmation message AND the setting gets reset to not flashing bootloaders every time the app loads.

Hariiiii said:
Nah you have to go all the way in to settings to change it and you get a warning confirmation message AND the setting gets reset to not flashing bootloaders every time the app loads.
Click to expand...
Click to collapse
I wish fastboot did this too *looks at my hardbricked Kindle Fire HD*

Lightn1ng said:
I wish fastboot did this too *looks at my hardbricked Kindle Fire HD*
Click to expand...
Click to collapse
Just flash a debrick image.
============
Nice find OP!
Finally we can enjoy MM with root!
Do all VZ services still work like VZ Messages? Does MMS work properly?

smokerbond said:
Just flash a debrick image.
============
Nice find OP!
Finally we can enjoy MM with root!
Do all VZ services still work like VZ Messages? Does MMS work properly?
Click to expand...
Click to collapse
Ahhh....What!? I see the words MM, Root, And CID 11......This can't be the case. I don't believe it. Need more verification.

Gxzn said:
Not responsible for anything that goes wrong.
Follow the steps Here EXACTLY then install Super-Su Me
(You need Super SU to continue)
Once you're done download (Still Uploading) and
Put 'G900TUVU1GPE1_G900TTMB1GPE1_G900TUVU1GPE1_HOME.tar.md5' in your sd card or phone storage (doesn't matter)
Install Flash fire (allow root) and touch the plus on the bottom right. Select "flash firmware package" and select the file you put in your storage.
Once it is finished you're gonna see it reboot and show a screen telling you it failed. Take out the battery and reboot into Download Mode.
Launch Odin, press AP and flash both the recovery and the boot files.
once done, remove you're battery and reboot into recovery, wipe data and cache.
you're all done!
Boot may take a while (2.40GB Firmware) so make sure it stays in a cool place. It will get hot.
Screenshots coming soon
Click to expand...
Click to collapse
If this is true , then you the men off the year ! Lets wait and see

@Gxzn
Can you verify you are Rooted on a MM ROM with a CID 11 chip please.... Talking about screenshots here.
I only ask because I think some people are misunderstanding what you accomplished. I don't believe you are actually rooted on a MM ROM with CID 11 chip.

Stupifier said:
@Gxzn
Can you verify you are Rooted on a MM ROM with a CID 11 chip please.... Talking about screenshots here.
I only ask because I think some people are misunderstanding what you accomplished. I don't believe you are actually rooted on a MM ROM with CID 11 chip.
Click to expand...
Click to collapse
I have to agree... There's a lot of brilliant minds that put a lot of thought into unlocing the 11 chips bootloader. Which is necessary to run 6.0 rooted roms. To my knowledge u would be the first to actually do it. I just don't imagine it being accomplished in such a sloopy and simple manner.

verification needed, probably unrooted.

Alright, so i recently got stuck on the tmobile screen and won't continue again, tried reflashing and doing everything over and it did not work, this time i tried it with Lolipop (tmobile version) and this one worked this time, not sure what went wrong or what i did to get it, but with MM it boots up to t-mobile screen now

So you can boot a stock Lollipop T-Mobile rom on a Verizon S5? I have to see the proof. Pure stock. Unrooted. Screenshots.

Mattix724 said:
So you can boot a stock Lollipop T-Mobile rom on a Verizon S5? I have to see the proof. Pure stock. Unrooted. Screenshots.
Click to expand...
Click to collapse
Here you go

UPDATE: So I tried MM again and everything boots up to "starting apps" then it restarts and then gets stuck on the tmobile screen

https://mega.nz/#!xFUiDTZZ need a key

Gxzn said:
Alright, so i recently got stuck on the tmobile screen and won't continue again, tried reflashing and doing everything over and it did not work, this time i tried it with Lolipop (tmobile version) and this one worked this time, not sure what went wrong or what i did to get it, but with MM it boots up to t-mobile screen now
Click to expand...
Click to collapse
the base has to be the same if you are on lollipop you can flash a lollipop g900t firmware it has to do with fact that you on a lollipop kernel that's why mm t mobile firmware didn't work
to do this the easy way flash only the system img in flashfire then you can be on g900t firmware on your s5 verizon
you have to use the closest lollipop g900t firmware you might have to try a few until you don't have cell connection problems
for me to have g900f firmware on g900v ok3 and boi3 firmware didn't have cell connection problems

I didn't get it to boot either maybe some one more experienced can get of to boot

TWRP Error "No Command" when i choose Recovery.

Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks

Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?

Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/

Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?

wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.

Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good

wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.

[08.01.19][Guide] ROOT S9+(Exynos)Magisk + OEM fix + EFS Backup Tool

Here is script for Root + OEM Fix for S9+
READ THIS BEFORE ROOTING DEVICE
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, but for that there are some workaround like Magisk Hide or SU hide, google it.
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
What is OEM fix?
Since Note8 samsung have introduced OEM unlock control remotely and flashing any custom binary removes OEM unlock option and rebooting in this state it ends with custom binary error and have to flash stock firmware. OEM patch will retain OEM unlock option in spite of having custom recovery. If you are not sure your device have OEM issue then there is nothing wrong to use 'OEM patch' option.
If you don't have OEM unlock option out of box then it may appear after 7 days, before this nothing can be done. Also this suggest, you have OEM affected device.
Click to expand...
Click to collapse
How to Root device
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy G96*_Root_for_OEM_issue_devices_V*.zip to Ext SD card (There is different files for Oreo & Pie according device)
4.Download TWRP for S9+
5.Switch Off device
6.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14A (If you are ion Pie).
Now select Install and navigate path to Ext SD card - N965F_root_OEM_issue_devices.zip, you have copied earlier, select desired root method and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
OR
14B (If you are on Q)
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
15.Once flash successfully finish, Reboot to System
Important Note for Pie OS -
1.You may find OEM option disabled after root by above method, Even if you enable and reboot, again it will be disabled. This is because of kernel is patched while rooting device to prevent binary errors. So ignore this OEM status as it is.
2.Magisk app may not be there in drawer. Simply Download Magisk app for Pie attached here and Install as regular apk.
Root device with Q
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
Credits and Thanks goes to BlackMesa123 for this post for OEM patch script. tkkg1994 for pre patched dm-variety stock kernel
Click to expand...
Click to collapse
IMPORTANT :
1.Magisk may appear after one reboot
2.When you select OEM Patch + Root method in aroma, YOU DON'T NEED TO FLASH ANY EXTRA ZIP like dm-verity or RMM fix etc This tool have evrything in one go.
Update (8Jan19)
- Added support for S9+ Pie with Kernel patching for OEM Fix
Update (25Oct18)
Separate fies for S9 & S9+
Kernel level patch for OEM Issue
No more flashing kernel
Update (05Aug18) :
Script updated to V5
Added support to root with magisk ,
Update 24Sept18
Fixed possible issue with RMM
Magisk updated to 17.2
Removed SuperSu support
Universal with Note9
EFS Backup
Here Note 8 EFS backup tool is fully compatible with S9+

Reserved

dr.ketan said:
Reserved
Click to expand...
Click to collapse
Nice.. you bringing a custom rom to S9+?

PG101 said:
Nice.. you bringing a custom rom to S9+?
Click to expand...
Click to collapse
Not decided yet. Never bought S series device since Note1. If I will buy S9+ then surely start development

dr.ketan said:
Not decided yet. Never bought S series device since Note1. If I will buy S9+ then surely start development
Click to expand...
Click to collapse
Great.. I've setup the whole device but it still feels incomplete with proper root and a custom ROM

thanks for this tuto
You know if this manipulation increment knox to Ox1 ?
Thanks

dr.ketan said:
Not decided yet. Never bought S series device since Note1. If I will buy S9+ then surely start development
Click to expand...
Click to collapse
What do you think about flashing treble aosp

does it works for S9+ (965F/DS)?

EDIT: sorry, just realized i posted in the wrong thread.

FRoZeN ACiD said:
so i tried the method above and got the RED "only official released binaries are allowed to be flashed"
phone wont boot up... any support is appreciated.
I also tried to resinstall TWRP through ODIN and it keeps failing.
Click to expand...
Click to collapse
Have you selected oem patch option in aroma?
Tell what exact steps you followed

dr.ketan said:
Have you selected oem patch option in aroma?
Tell what exact steps you followed
Click to expand...
Click to collapse
apologies, i just realised i posted in the wrong thread, this was supposed to be a response in the official TWRP root thread.

Am waiting for magisk to be fixed and then I'm all Root
Does one needs to format data during the process?

PG101 said:
Am waiting for magisk to be fixed and then I'm all Root
Does one needs to format data during the process?
Click to expand...
Click to collapse
Without full format device storage won't be usable bcoz of encryption.

dr.ketan said:
Without full format device storage won't be usable bcoz of encryption.
Click to expand...
Click to collapse
Thanks

PG101 said:
Am waiting for magisk to be fixed and then I'm all Root
Click to expand...
Click to collapse
Same here. Magisk seems to work very well. I tried using supersu and suhide, but it wasn't passing. I need to be able to hide root, and Magisk does a great job at it.

dr.ketan said:
Not decided yet. Never bought S series device since Note1. If I will buy S9+ then surely start development
Click to expand...
Click to collapse
Oh wow i haven't seen you since the note 2 days as I skipped upgrading Note series as well as S series. Good to have you here

Has anyone tried this root method? Does it work perfectly without boot loop or bricking the phone?

This works fine here with supersu on G965f/D.

Tried this method. Was able to flash recovery successfully and install the zip but after clicking reboot to system, it won't boot the phone

codekaran said:
Tried this method. Was able to flash recovery successfully and install the zip but after clicking reboot to system, it won't boot the phone
Click to expand...
Click to collapse
Have you selected supersu and oem patch option both?

[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

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