Related
I have read a lot about rooting prior to the new firmware. But I just got a new Sprint S5 yesterday, and it comes with firmware NK4 (4.4.4) I tried to odin flash the firmware from NE5 (from June 2014), and that boot me into a boot loop. So i had to Flash back to the NK4 (Nov.2014). This phone has NEVER been rooted. there is NO recovery flashed either.
Are there any suggestions or walkthroughs?
Here are the firmwares available from Sprint.
2014 November = NK4
2014 June = NE5
2014 April = ND2
2014 April = NCB
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
m20120 said:
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
Click to expand...
Click to collapse
I also forgot to mention that cf autoroot just boots be up to the Sprint boot up, and then hangs!!! So cf root doesnt seem to be an option on 4.4.4 NK4.
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Towel root will work, here are the steps and the kernels you will need.
1. Download and install towel root, but do not run.
2. Use odin to install NE5 kernel below, remember to unzip it first.
3. Boot phone and just hit ok or close to all the errors that will pop up because you have the wrong kernel installed.
4. Run towel root.
5. Use odin to install the NK4 kernel below.
6. After reboot, download supersu from the play store, then udpate binaries, answer yes to the disable knox prompt.
7. Profit!!! Use Galaxy Tools to unlock hotspot, or xposed framework and Wanum to customize phone.
What's the difference between the firmware and kernels?
Stuck
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
My baseband is nk4
xSpaceGhost said:
What's the difference between the firmware and kernels?
Click to expand...
Click to collapse
Firmware is the modem, kernel, etc. Not what you need to use towel root. All you need is the kernel to get towel root to work. If you flash the whole firmware you won't get towel root to work and your phone may not even boot.
banccalif said:
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
Click to expand...
Click to collapse
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
First i put supersu as a zip on my sd card, thenI had to install custom recovery through odin and then installed supersu via recovery and this worked fine.
Can you post the super SU file. I did the same method but had to install supersu from the playstore.
http://forum.xda-developers.com/showthread.php?p=23427715
Here's the link to chainfires stable version. In the OP scroll done to the link for the zip file under the play store versions
I am on nk4 (4.4.4) firmware and baseband. I rooted using this method. 1. Went to download mode and unchceck auto reboot and time. 2. Odin flash 6.26.6 philz recovery. 3. Then unplugged and entered recovery (made a backup) 4. Copied superSU to phone. 5. Rooted and rebooted. 6. Rebooted and installed superSU and disabled Knox. Check with root checker. (Happy face)
glad it worked.
jpgranger said:
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Click to expand...
Click to collapse
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
travanx said:
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
Click to expand...
Click to collapse
You should be able to use the galaxy tools app to get tethering, not sure if it requires root or not. If that doesn't work and you don't care about trippin knox you can re-download ne5 and follow these steps below to get root & custom recovery
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Can't I just use auto chainfire to root and recovery from Nk4?
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.
Can't I just use auto chainfire to root and recovery from Nk4?<br />
<br />
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.<br/>
See post 14 above those steps work and then use galaxy tools for hot spot. Worked great for me. Chainfires c.f. root did not work
banccalif said:
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Click to expand...
Click to collapse
.
Ended up using the oneclick NE5 from here, http://forum.xda-developers.com/showthread.php?t=2787760, knox says 0x0. Made it rain, still 0x0. And then odin 3.09 for philz recovery, still 0x0. As soon as I went into recovery it triggered 0x1 but not before. In case anyone new to the phone, like myself, cares what step triggers knox.
Hi guys! Welcome back to another R&R guide and I've been tricking out the AT&T Galaxy S4 of one of my friends, Laguire, and decided to make this guide. So as usual here comes the requirements, followed by a detailed and noob-friendly guide and download links whatsoever. If you have any questions about the guide, you know what to do underneath. This guide is my riskiest guide EVER, so use it at your own risk. Don't blame me if it dies.
Requirements
A PC running Windows
Your AT&T S4
Samsung USB cable(not neccesary to be Samsung's, as long as it is the same type)
A stable Internet connection
How-To
1. Download files to the correct devices:
-Root ZIP -> S4
-Odin and Recovery -> PC\
2. Connect your device to the PC via USB cable
3. Boot into download mode (Power off > Power and Volume Down)
4. Run Odin
5. Uncheck the Auto Reboot box.
6. Click AP and locate the MD5 file you downloaded earlier
7. Click OK or Start(haven't been using Odin recently)
8. Wait for the first box above to say PASS
9. Power off your S4 and unplug the cable.
10.Boot into recovery mode(Power+Volume up)
11.Tap Install > Locate to the folder where you downloaded the Root zip earlier > Select
12.Swipe to flash
13.After finished reboot your S4 and download Root Checker to check root
Done! Your AT&T Samsung Galaxy S4 is now officially rooted!
Downloads
Odin(Don't download from any other sources): https://www.androidfilehost.com/?fid=24572369242686499
Root ZIP(by Chainfire): http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
TWRP 3.0.2-0 Recovery(RISK AVAILABLE): https://www.androidfilehost.com/?fid=24591023225176226
Special Thanks
Laguire Sien Tiamat
Brano Esmeer
Kohlner Freisch
Liam Francis
and Kamross Sorberg
In Memoriam: DAFFEN KURM-THIS ONE'S FOR YOU
this question seems pretty stupid, but its worth a shot. is this for devices without the loki exploit or no?
Sterben Pistole said:
this question seems pretty stupid, but its worth a shot. is this for devices without the loki exploit or no?
Click to expand...
Click to collapse
It is probably for SGH-i337 with exploitable old bootloaders (MDB, MDL). Odin and TWRP is a new one but superSU is 2 years old.
How It Will Works ? I Think Not Possible To Install TWRP ! .... Because AT&T i337 Locked Bootloader ... How I Will Install This ?
Sorry guys, I haven't noticed that Laguire's I337 is the old version. Sorry again for the convenience though.
I have a smart question >.< :/.
Does this work for the Galaxy S4 I337..OC4<-- kernel? lollipop*
Thank you!
Does this work with build ok2?
And why is this considered the riskiest???
This seems to be for phones with the MDB and MDL firmware as if you try to flash TWRP recovery on any other firmware, it won't install.
its not warking for me i get this problem : E: Failed to mount / system (Invalid argument) is there any Solution
bouba05f said:
its not warking for me i get this problem : E: Failed to mount / system (Invalid argument) is there any Solution
Click to expand...
Click to collapse
This guide is for the MDB and MDL bootloaders that can use the Loki doki patch. Once you've upgraded your firmware, there's no going back.
:good:
err on the side of kindness
I'm on oc4 rooted, I tried flashing twrp 3230 using flashify...
Big mistake tried to boot into recovery and it said I wasnt using official at&t software and had me stuck until I finally found if I set odin to autostart 1 after flashing the stock kernel it will boot up.... trying to find a recovery to use atm
I thought that the carriers locked the bootloader sometime before kitkat, I'm still using my AT&T sg4. I looped it installing superuser,had a difficult time getting fixed,found a group of F/W files at sammobile that had to be flashed 1 at a time all the way up to lollipop 5.0 then it took an OTA to 5.01. I need to Root so I can clean out all the useless apps at&t installs. I haven't been able to tether my tablet and forgot what files to use to root with.
Did you still have bootloader you use Recovery on,that would be great.
kmbbo said:
I'm on oc4 rooted, I tried flashing twrp 3230 using flashify...
Big mistake tried to boot into recovery and it said I wasnt using official at&t software and had me stuck until I finally found if I set odin to autostart 1 after flashing the stock kernel it will boot up.... trying to find a recovery to use atm
Click to expand...
Click to collapse
The only recovery you can use is the stock recovery given you are on OC4 which patched the bootloader exploit that allowed TWRP to be installed.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
vtails said:
I thought that the carriers locked the bootloader sometime before kitkat, I'm still using my AT&T sg4. I looped it installing superuser,had a difficult time getting fixed,found a group of F/W files at sammobile that had to be flashed 1 at a time all the way up to lollipop 5.0 then it took an OTA to 5.01. I need to Root so I can clean out all the useless apps at&t installs. I haven't been able to tether my tablet and forgot what files to use to root with.
Did you still have bootloader you use Recovery on,that would be great.
Click to expand...
Click to collapse
You are correct, AT&T locked the bootloader from day 1 of the S4 launch. However, there was an exploit for the MDL firmware that allowed TWRP to be installed. If you updated past MDL then there's no going back. MDL was Android 4.2.2 jellybean. The only thing you can do with later firmware is root and boot custom TW ROMs by using safe strap for kit kat and flash fire for lollipop.
Hi All,
I have a Canadian S4, SGH-I337M. It is essentially identical to the AT&T version except the Canadian one's bootloader is UNLOCKED. I have been running TWRP 3.1.1-0 to create nandroid backup for YEARS.
Unfortunately, all the sudden I'm getting this error message when I backup, "E: Another threaded action is already running -- not running 1 actions starting with 'nandroid'". It would try to do something and then quit after a minute without creating anything.
So where do I start to troubleshoot this issue? Again, it has always worked in the past! Thank you
luckysoul777 said:
Hi All,
I have a Canadian S4, SGH-I337M. It is essentially identical to the AT&T version except the Canadian one's bootloader is UNLOCKED. I have been running TWRP 3.1.1-0 to create nandroid backup for YEARS.
Unfortunately, all the sudden I'm getting this error message when I backup, "E: Another threaded action is already running -- not running 1 actions starting with 'nandroid'". It would try to do something and then quit after a minute without creating anything.
So where do I start to troubleshoot this issue? Again, it has always worked in the past! Thank you
Click to expand...
Click to collapse
Are you sure the Canadian version's boot loader is unlocked? When I go in download mode there is still this line "Write protect enabled" on...
so I do have an S4 on the MDL bootloader, and i've followed all the steps but I can't flash TWRP.
pretty much every link is dead for the i337 root now except for this which doesn't appear to work. if someone is able to provide the loki, motochopper, and other necessary files for this device so i can get this paperweight loki'd, that would be sweet.
Hi.
Just recently I rooted my Xperia z3 (D6603) and upgraded the KitKat 4.4.4 into 6.0.1 MM through AROMA (found a link on this website).
After trying to install Xposed Framework, I had to flash it through TWRP recovery, but it said that I had the wrong version (arm)
I then downloaded a different version, however now my TWRP won't launch manually or automatically ( through a reboot app).
It will just jump straight into android instead of coming up with the team win logo etc.
I am confused as to why this is happening, do I need to flash the .img of it into my phone again or is there another sure way of fixing my issue.
Any help would be very appreciated . At the moment I cannot install Xposed framework because I have to flash it via recovery and I can't get into it.
Thank you
P.S Everything else works fine, no bootloop or brick
P.S2 Rebooting to recovery through TWRP Manager didn't work either (straight into Android)
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Dobsgw said:
If you cant get into recovery by pressing volume down on reboot. ie when they phone turns on there will be a buzz and a green light, press vol down and it should turn purple and then go to TWRP.
If you didn't unlock the bootloader this should help you fix it.
If this doesn't happen ensure you have SuperSU and that it works ie. you're actually still rooted...
If still rooted:
Find RecRoot v4 by Wolfbreak here: http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357 and use it from your PC to reinstall recovery.
If this fails it means root is broken.
If root is gone you will need to downgrade again and root and update again. Make sure this time you use a pre-rooted zip or at least flash recroot (works in recovery also) straight after you flash the ROM to keep root. If you use a custom ROM they should always include root (just read the XDA page of that ROM and make sure).
If your bootloader is locked (which I'm assuming it is if you downgraded to root and upgraded after) don't mess around flashing any .img files you will likely mess things up. Recoveries on LB have to be installed carefully.
If anyone says they haven't had an issue like this with root they're probably lying. It's all part of the fun ;P
To flash xposed make sure you download the one for MM which is SDK 23. And for the architecture of the Z3 processor you need ARM. This should work fine for you.
(please correct me if I missed something or got something wrong)
Click to expand...
Click to collapse
Problem is that when I downloaded the SDK23 arm, it said wrong format : ARM in red and gave me an error. After that I couldn't go back to twrp no matter what I did.
- I am now back to 6.0.1 MM rooted, going to try installing Xposed again, hopefully this time nothing will go wrong
Ok so i have* searched high and low for a root driver or auto root so i can root my s5 sm-g900i but everything i come across doesnt have this build number MMB29.G900IDVS1CPK1 my version is 6.0.1 i have already tried rooting it once using oceania auto root but i bricked my phone (I managed to restore it) So does anyone know where i can find a root package with that build number android version and model much appreciated
Model sm-g900i
Build Number MMB29.G900IDVS1CPK1
Version 6.0.1
P.s i know how to use odin and all that i just need that file :crying:
Maddyrosexx said:
Ok so i have* searched high and low for a root driver or auto root so i can root my s5 sm-g900i but everything i come across doesnt have this build number MMB29.G900IDVS1CPK1 my version is 6.0.1 i have already tried rooting it once using oceania auto root but i bricked my phone (I managed to restore it) So does anyone know where i can find a root package with that build number android version and model much appreciated
Model sm-g900i
Build Number MMB29.G900IDVS1CPK1
Version 6.0.1
P.s i know how to use odin and all that i just need that file :crying:
Click to expand...
Click to collapse
Its much easier than that WI will explain you how to root your device using a custom recovery.
Download SuperSU and copy it to your phone's storage
Download TWRP (must be compatible with your device!) and flash it as "AP" using Odin. Make sure to uncheck "auto reboot" in Odin. and remove the battery when the flashing is done.
Put back in the battery and start phone in recovery mode ("Vol +" + "Home" + "Power")
On first start TWRP asks for system read/write -> yes
Use TWRP to install the "SuperSU.zip"
Reboot and you're rooted and you got also a working custom recovery - you will like it...
Few questions
heres what i got
download supersu
(dont know whether to extract or not)
place on phone storage
Start up odin select ap and choose TWRP then start?
once finished remove battery start phone in recovery mode TWRP asks for system read/write i select yes
(i dont understand how to use it to install it because havent i already installed from step one??)
Then reboot
I didnt quite understand it ad because my phone us unique i need to b careful already bricked it once
ALSO how do i know if the TWRP is compatible with my device??
This process will allow flashing custom boot and recovery images on EMMC11 S5
Yes this will allow the EMMC11 S5 to run custom roms like Lineage
Than You ryanbgSummary Of What This Does
You must be on G900VVRU2DPD1 bootloader for the exploit too work.
The exploit patches the header of the boot or recovery image which forces the phone to skip security check of them and allow them to be used. If on totally stock phone this process flashes combo firmware to your phone which is kitkat based and allows easy rooting. Then I inject safestrap into combo firmware which gives a system based hijack that gives you a custom TWRP like recovery. I then have safestrap recovery flash a minimal QL1 based rom with DPD1 bootloader that updates you back to Marshmallow firmware and a prepatched TWRP recovery. I have to use this method because this prepatched TWRP recovery cannot be flashed in odin because you need unlocked bootloaders to be able too do this. This minimal firmware is also rooted just for good measure but the only thing you will be using this firmware for is to access TWRP so you can flash an actual rom that can be rooted with a magisk root. I have provides some for you to use. If you mess up and loose recovery and dont have a rooted rom you can boot up to. The whole process will have to be done again so take care not too loose your TWRP recovery once using this process.
What You Can Do
Flash custom boot images that allows you to use magisk
Flash custom recovery
Flash custom roms like Lineage
What You Cannot Do
You can not unlock bootloaders on EMMC_11 so all flashing must be done on a device with custom recovery
You cannot flash custom binaries using odin
Downloads
S5_Root_Tools_2023.7z -- Use If Totally Stock
EMMC_11_Rom.zip -- Stock QL1 6.0 Use If Already On Safestrap
Patch_Boot_Recovery_Image.zip
Boot Images Stock EMMC_11 Or 15
boot_ql1_stock.img
Boot Images Custom EMMC_11 Or 15
PhoeniX.Kernel.V13.0.TW6.0.1.img -- Phoenix Kernel Permissive
PhoeniX.Reborn.Kernel.V1.0.TW6.0.1.img -- Close To Stock Permissive
PhoeniX.Kernel.V1.0.TW6.0.1.G900V.img -- VZW Stock Permissive
TWRP Recovery EMMC 11
recovery_twrp_emmc_11.img -- Pre Patched For EMMC_11
TWRP Features
Backup and flash system images
Green color to distinguish between regular twrp
EMMC_11 TWRP image is prepatched flashing patch zip not needed
EMMC_11 TWRP startup screen labeled to identify its patched
Regualr TWRP can be use if you choose on either model
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical Questions And Answers Here
Telegram Channel
Directions If Already Running Safestrap
1. If already running safestrap flash EMMC_11_Rom.zip in safestrap this will install very minimal QL1 rom with proper bootloaders and stuff. From here you can flash rom of your choice just make sure you dont update or change bootloaders.
2. Then root with root of choice.
3. Then flash Patch_Boot_Recovery_Image.zip then your done
4. Then from there on in future flashes follow the EMMC_11 Flashing Custom Roms Boot Images And Recovery Images section
5. I recommend you dont mess with recovery. If you accidently flash an unpatched recovery you may not be able to get it back without starting the whole process over. If a rom you are using flashes a recovery image I recommend you remove it or make sure you flash the patch zip
Directions If Totally Stock
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. EMMC 11 detection will install Twrp recovery where you can install custom stuff from there.
EMMC_11 Flashing Custom Roms Boot Images And Recovery Images
1. The above tool will give you TWRP Recovery and stock 6.0 rom
2. Flash your rom of choice in TWRP or stay on stock one provide. Do not flash a rom that updates bootloaders.
3. Then flash your root zip like magisk this will patch your boot.img
4. Once a boot.img is no longer stock you will need to flash the Patch_Boot_Recovery_Image.zip after the image is patched with magisk. This zip will be placed on your internal storage from the above tool
5. I recommend you dont change recoveries there is really no need too
6. Anytime you flash a new boot.img it will most likely require you to reflash root zip and then make sure you flash the Patch_Boot_Image.zip very last
Source For Kernel
Source Code For Expolit
Source For TWRP
Instructions For Flashing An AOSP Based Rom
1. Download rom that will work for this device.
2. In twrp wipe data
3. Install rom zip
4. Install gapps that match the rom you are flashing and they must be arm gapps.
5. Install Root zip such as magisk zip
6. Install Patch_Boot_Recovery_Image.zip
7. Reboot
8. Anytime you flash a new boot.img it will most likely require you to reflash root zip and then make sure you flash the Patch_Boot_Image.zip very last
9. If using lineage recovery you will also need to flash the Patch_Boot_Image.zip after you flash lineage recovery
Official Lineage Builds For S5
LineageOS Downloads
download.lineageos.org
Open Gapps
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
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
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 flashing of rom of choice or unlocking the bootloader if you have EMMC15 device. On this particular rom you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Old Root Methods And Downloads
EMMC_11_S5_Root_Tools_2022_V7.7zInstructions To Install Safestrap
**If you already have safestrap installed you can skip to Installing Roms Post 2
**If you already have rooted you can skip to Installing Safestrap
**This process uses Kingroot too root but removes all traces of it when done.
Directions
1. Download and unzip EMMC_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 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 1ckick root 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 will need to be installed first if you used towel root method to root
Old Safestrap Rom Zips
EMMC_11_NK2_KK_Rooted_Safestrap_Full_V2.zip KIT KAT ROM
EMMC_11_PB1_LL_Rooted_Safestrap_Full_V2.zip LOLLIPOP ROM
EMMC_11_QL1_MM_NonRooted_Safestrap_Full_V2.zip MARSHMALLOW ROM
Entering Safestrap
To Enter Roms From Kit Kat Or Rooted Combo Firmware
1. Reboot phone and click on Recovery Button on safestrap splash screen
To Enter Safestrap On Marshmallow Or Lollipop Roms
2. Reboot to recovery (VolUp+Pwr+Home Buttons) when the bottom navigation lights turn on hold the volume down and power buttons for about 10 seconds until phone boots too Maintenance Boot Mode
Click image for larger version
3. Now use the volume keys to navigate too Factory Reset. Now press the Home button. This will not reset your phone but this is how you enter safestrap. Phone will reboot too safestrap give it about a minute too boot into safestrap it will boot directly too safestrap. Every time you want to enter safestrap you need to follow these steps
4. To leave safestrap simply click reboot system
Installing Roms Using Safestrap
1. If coming from a kitkat rom or the root method above in post 1. You must reboot too stock recovery wipe data and reboot and enter safestrap then Copy Rom Zip To Phone. The data wipe in recovery while on kitkat rom is necessary to partition data correctly too move on too Marshmallow or Lollipop. If on Lollipop or Marshmallow rom skip wiping data in stock recovery because you cannot and copy your rom zip too phone while system is still booted and reboot too safestrap.
2 In safestrap click swipe bar too allow system too be modified
3. Click wipe and swipe to factory reset then click home button then click install and choose EMMC_11_ROM.zip.
4 This will take several minutes too install
5. Once installed click reboot system. If first time in safestrap it will ask you if you want too install TWRP which you cannot. Uncheck the boxes to install twrp and choose Do Not Install and phone will reboot. This is only on first time you enter safestrap after first time it wont ask you this again and simply click reboot system
6. Phone will take several minutes too boot
Features
Stock Deodexed Rom Slightly Debloated
Some Features Added
Safestrap Available On All Roms Root And NonRooted With Ability To Enter Safetrap Without A Computer
Root On Lollipop And KitKat Only
Bugs
1. Lollipop and Marshmallow recovery image is replaced with KitKat boot.img to give ability too boot too safetrap without using a computer. This may cause your sometime to reboot to recovery screen and get stuck when your phone is turned off and you plug in a charger. You can fix by pulling battery with phone unplugged then plug back in if not cycle through a startup then power off
2. There is no recovery image on Lollipop or Marshmallow so you have to wipe cache and data through safestrap
3. If you flash odin files or other roms that flash a recovery image you will loose safestrap ability. There is a safestrap recovery image in files in post 1 that you can flash in odin too get back safestrap abilty.
4. Flashing roms that dont contain safestrap may cause you too loose safestrap so I recommend flashing one of the safestrap zips to add it to roms. This is not necessary on above roms.
5. This is not supported by me anymore. I try and help but I don't check this threads regularly.
6. If you loose safestrap on Marshmallow roms the only way too get it back is to start over from post 1
7. If you find yourself on kitkit rom constantly booting too safestrap flash the KitKat safetrap zip in safestrap
SafeStrap Zips
View attachment Safestrap-4.11-B01-KLTEVZW_MM_LL.zip
View attachment Safestrap-4.11-B01-KLTEVZW-SS-FF-flashable-KK.zip
Bro, you are quite a crack, despite the time that the S5 already has, you keep releasing content to get more out of the s5, I'm still using it and personally I have installed all your roms. Thanks a hug.
Jose_cm001 said:
Bro, you are quite a crack, despite the time that the S5 already has, you keep releasing content to get more out of the s5, I'm still using it and personally I have installed all your roms. Thanks a hug.
Click to expand...
Click to collapse
I just organized stuff better. All this stuff has been around for awhile. I just had it in many different threads so I consolidated it into one thread. I have been cleaning and closing some threads. Im really surprised anyone still uses an s5 but hey im glad someone still gets some use out of this stuff. I made sure all links worked and reuploaded stuff with dead links so should be good now.
Sent from my iPad using Tapatalk
i'm following these instructions but i'm too gumpy to understand:
"7. Run the Install.cmd this should install some apks on your phone then reboot your phone"
i'm connected to a windows 7, i'm supposed to be running a program from the pc then?
chrisco78 said:
i'm following these instructions but i'm too gumpy to understand:
"7. Run the Install.cmd this should install some apks on your phone then reboot your phone"
i'm connected to a windows 7, i'm supposed to be running a program from the pc then?
Click to expand...
Click to collapse
Well yes you have to initially root the phone so you can install safestrap. You have too push the apps to your phone after you install the combination firmware as it has no apk installer so you have too install the apps needed for root and safestrap with adb using the computer. Once that’s done you don’t need computer anymore
Sent from my iPad using Tapatalk
jrkruse said:
Well yes you have to initially root the phone so you can install safestrap. You have too push the apps to your phone after you install the combination firmware as it has no apk installer so you have too install the apps needed for root and safestrap with adb using the computer. Once that’s done you don’t need computer anymore
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
thank you, i was actually able to figure it out eventually i just forgot to timestamp how long it took me (hours)
appreciate the condensed update, though! most s5ers are still holding on because battery swapability is more important than the app du jour
If I flash the Lollipop ROM will I be able to use the settings factory reset option? Or will that cause a brick without reflashing again?
I want to get the phone in a stock state but maintain safestrap otherwise. Remove all personal data, Disable Reactivation Lock etc (I can't turn it off on my current ROM for some reason). Or I guess getting completely stock even without safestrap is okay too since its still possible to re-get it if needed.
hypermetuljason said:
If I flash the Lollipop ROM will I be able to use the settings factory reset option? Or will that cause a brick without reflashing again?
I want to get the phone in a stock state but maintain safestrap otherwise. Remove all personal data, Disable Reactivation Lock etc (I can't turn it off on my current ROM for some reason). Or I guess getting completely stock even without safestrap is okay too since its still possible to re-get it if needed.
Click to expand...
Click to collapse
The factory reset option in settings will only work if you have stock recovery installed. Format data in safestrap will totally wipe internal storage. wiping just data in safestrap will remove all data except media files. You can flash stock and do it or the combination firmware. All will accomplish the same results.
Sent from my iPhone using Tapatalk
jrkruse said:
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5
Marshmallow QL1 Stock Rom NonRooted With Safestrap.
Lollipop PB1 Stock Rom Rooted With Safestrap.
KK Rom Rooted With Safestrap
What This Does
This gives you the ability to boot into safestrap without a computer like the old way was.
You can use safestrap to modify the rom delete apps flash mod zips and even run xposed. Many xposed modules will work without root
You can use safestrap to go back to earlier roms like lolipop or kitkat were you can have root
You can flash some custom Samsung Based Roms. I have a few in the forum
You cannot root Marshmallow roms with a locked bootloader
You cannot flash asop based roms like Lineage as these require a custom boot image
You cannot unlock your bootloader even though you have safestrap
Downloads
EMMC_11_S5_Root_Tools.7z
Instructions To Install Safestrap
**If you already have safestrap installed you can skip to Installing Roms Post 2
**If you already have rooted you can skip to Installing Safestrap
1. Download and unzip files
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.cmd this should install some apks on your phone then reboot your phone
8. When phone reboots choose the Apex launcher which will make it easier to find stuff
9. There are 3 different options installed to root your phone 2 different towel root methods and a KingRoot method
Towel Root Method
10. 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
11. 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
12. You will need to be connected to a network. Click on King root app then click try root
13. Once root is successful don't click on the optimize and close the king root app.
Installing Safestrap
14. Now that you have rooted from one of the above methods click on the BusyBox app and install busybox click allow in the root dialog box
15. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
Click to expand...
Click to collapse
Ok, I followed these steps and made it all the way through this time. HUZZAH!!! (Towelroot didn't work since it said it couldn't connect to the internet) King root worked.
Only problem is, how do I know it worked? There isn't a tool for checking if root worked and this version of ROM doesn't seem to have any apps like Google Play Store to grab more apps. How do I install more apps? Thanks!
OreganoPlanter said:
Ok, I followed these steps and made it all the way through this time. HUZZAH!!! (Towelroot didn't work since it said it couldn't connect to the internet) King root worked.
Only problem is, how do I know it worked? There isn't a tool for checking if root worked and this version of ROM doesn't seem to have any apps like Google Play Store to grab more apps. How do I install more apps? Thanks!
Click to expand...
Click to collapse
The whole point is too get safestrap installed if you can boot to safestrap then the process worked
Sent from my iPhone using Tapatalk
JRKRUSE. Thanks so much for this. I've been stuck for a few days with my dad's old S5 trying to get it back to working. I wiped it, and couldn't get past the Samsung Account Reactivation Lock. Tried flashing a few stock firmwares, but nothing worked. I used your method to install the bootloader successfully. Once installed it boated me into a stripped down version of Android, which displayed all sorts of system diagnostic info on the bottom half of the screen. (Not sure what this is called.) I couldn't get the .cmd file to copy the apk's over but it let me copy them over to the downloads folder and install them all one at a time on the phone. Successfully gained root and followed the rest of your steps. Was successfully installing KitKat and finally getting around the Activation Lock. Thank so much!!!
jmc15john said:
JRKRUSE. Thanks so much for this. I've been stuck for a few days with my dad's old S5 trying to get it back to working. I wiped it, and couldn't get past the Samsung Account Reactivation Lock. Tried flashing a few stock firmwares, but nothing worked. I used your method to install the bootloader successfully. Once installed it boated me into a stripped down version of Android, which displayed all sorts of system diagnostic info on the bottom half of the screen. (Not sure what this is called.) I couldn't get the .cmd file to copy the apk's over but it let me copy them over to the downloads folder and install them all one at a time on the phone. Successfully gained root and followed the rest of your steps. Was successfully installing KitKat and finally getting around the Activation Lock. Thank so much!!!
Click to expand...
Click to collapse
Sorry to reply to such an old post, but which KitKat ROM did you end up using? I have a few phones stuck asking me to log into the last used Samsung account and I need a ROM that will bypass that screen.
This thread saved my mysteriously soft bricked, unlocked & rooted S5 VZW device. Thank you jkrruse.
When I try to download EMMC_11_PB1_LL_Rooted_Safestrap_Full.zip I get no mirrors available. Am I SOL?
edit - now one mirror is available which is flaky slow and drops less than 10% into download.
2nd edit- went with Brave browser and used it's download manager to continuously resume dropped download. Hash looks good so here goes...
Final cut: All is well and once I got everything my way I wanted to backup and could not find Safestrap. On boot I get RECOVERY BOOTING..... and nothing else. Had to pull battery. So I'm at a loss. Finally I took the time to make a check list of every step which really doesn't take long and methodically performed each step until success. Have the device where I want it and including a backup. I have many devices and each is unique but this 900V is a workhorse. I think I task overloaded it before so lesson learned.
Updated files to be more compatible with newer computers
JKruse you are awesome man - I just tried to take an old S5 (cid 11) to try and work some magic to get around the YouTube app "not supporting" it, broke my S5 bad, and used your threads to fix myself back to PHX 15. (NOT the first time ive been totaled before) You been dope since I first bought it! Many thanks!
Well with dozens of phones and most far newer than my s5 I finally had to update it to use a certain mission critical app so I went for LL. Followed the above mostly and it's working although I haven't had the chance to wring out everything yet. Thanks jrkruse again for all your great work! Wondering if I'm the last person on the planet to upgrade 4.4.2 to 5
droidzer1 said:
Well with dozens of phones and most far newer than my s5 I finally had to update it to use a certain mission critical app so I went for LL. Followed the above mostly and it's working although I haven't had the chance to wring out everything yet. Thanks jrkruse again for all your great work! Wondering if I'm the last person on the planet to upgrade 4.4.2 to 5
Click to expand...
Click to collapse
I'm still using 4.4.2 but on a T-Mobile S5 instead of the Verizon one.
I wish to thank jrkruse for making this post two years ago, for a phone that is 9 years old.
I paid $45 for the Verizon version of the Galaxy S5. Obviously, I don’t know what I’m doing. Thanks to this post and all the work that went into researching the problems and packaging the solution into a concise solution, I have a working version of an unrooted Marshmallow.
When I got the phone, it started up from a factory reset but as soon as I connected to the internet I got the message
“Device owner policies aren't supported on this phone.”
The menu key, home key and camera were disabled. I was locked out.
I used the Verizon 6.01 upgrade package, hoping it would do a fresh install. It got worse, I got the Knox security violation. I was double locked out.
So I started reading. It was looking bad, there was an embedded kill switch that permanently bricks the phone. After a bit more reading, I discover that I had the Version with cid starting with 11 from a post that said any manufacture date after the year 2014 was a cid 11. I found this thread, so from a locked up phone. my situation worked out to a smoothly running unrooted version of Marshmallow.
I know I didn’t carefully follow the instructions but I’ll layout my journey, for anyone else who is in similar circumstances. I invite comments to tell me what I should’ve done.
Requirements, I used a Windows PC, cable connecting the PC to phone, a micro SD card and an SD adapter that connects to a PC.
The package EMMC_11_S5_Root_Tools_2022_V3.7z is the complete one stop shopping deal and I went to https://www.7-zip.org/download.html to be able to unzip it.
After you unzip it, everything is ready to go.
The procedures are done by scripts, so there is hardly any typing.
The first routine prepares the phone for rooting and safestrap.
The next instruction reads
‘7. Run the Install_One_Click.cmd this should install safestrap.”
When I first read this, it was confusing to me, because I didn’t see a One_Click program. But all you have to do is double click the file named “Install_One_Click”. This is a command file that does all of the typing, both on the PC and phone.
In my case, everything ran as planned and I could skip the instructions for contingency cases.
The script did more work than the instructions in the post required.
The script stops to ask to allow rooting to install safestrap. Tap allow.
The script ends up with the safestrap screen on the phone, asking to install a rooted TWRP. This second time you decline.
On the PC I copied the EMMC_11_QL1_MM_NonRooted_Safestrap_Full_V2.zip file onto a micro SD card, using a USB SD card adapter.
I inserted the card on the phone.
I tapped the install button in safestrap selecting the file on the SD card.
After the install, you end up with Marshmallow. All I did was a few clicks in Odlin, double click on “Install_One_Click” , one tap to allow rooting, one tap to prevent rooting of TWRP and one tap on the install button in safestrap. All in under 15 minutes.
I got a very sleek, clean Marshmallow.
I then got the pop screen “Unfortunately, Google Store has stopped.”
I followed instructions from
https://www.androidpolice.com/install-google-play-store-any-android-device/
I simply downloaded 4 files.
https://www.apkmirror.com/apk/googl...account-manager-6-0-1-2-android-apk-download/
https://www.apkmirror.com/apk/googl...ervices-framework-6-0-1-android-apk-download/
https://www.apkmirror.com/apk/googl...-42-12-040408-481949630-android-apk-download/
https://www.apkmirror.com/apk/googl...-18-21-0-pr-481699564-3-android-apk-download/
installed them and clicked done not open and then rebooted.
The Google Store message was gone, just like the Knox and owner policy messages.
I could download apps from Google Play.
Everyone’s work turned a broken phone into a fully operational one.
I thank everyone.
jrkruse said:
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5
Marshmallow QL1 Stock Rom NonRooted With Safestrap.
Lollipop PB1 Stock Rom Rooted With Safestrap.
KK Rom Rooted With Safestrap
What This Does
This gives you the ability to boot into safestrap without a computer like the old way was.
You can use safestrap to modify the rom delete apps flash mod zips and even run xposed. Many xposed modules will work without root
You can use safestrap to go back to earlier roms like lolipop or kitkat were you can have root
You can flash some custom Samsung Based Roms. I have a few in the forum
You cannot root Marshmallow roms with a locked bootloader
You cannot flash asop based roms like Lineage as these require a custom boot image
You cannot unlock your bootloader even though you have safestrap
Click to expand...
Click to collapse
JR - Not as experienced as I'd like to be in this area, but patient and willing to put the time in if I can get the results I'm preferable to - I like the S5 size (one-hand-operable), swappable-battery of course, and several other factors. I've got three Verizon S5 phones still in service and I was hoping to get a little more time with them (prefer to stick with Verizon's network if I can). Was excited to discover Lineage, but it looks like I may not be able to proceed with these specific phones in hand based on finally arriving at your post/thread.
After running your EMMC Check App, it appears they're all version 11 (bootlocked - hence my fail in the Odin steps of Lineage).
Given this, is there NO way to unlock the bootloader or force ANY kind or work-around to proceed with Lineage? Not even if downgrading to the original Lollipop?
From what I understand in your post - other non-Lineage approaches may be able deliver a newer Android OS...but I'd really like to achieve Lineage though if possible (bringing me up to at least Android 11. I even would consider seeking out phone(s) with the 15 EMMC CID if necessary (though I don't know how I'd practically inquire/identify such when asking sellers for that info [decipherable through IMEI/etc?]).
Thanks for all the info assembled here. Hope you might have some advice.
-Jonn