Database Info

Hosed - could not leave well enough alone

Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.

bshpmark said:
Okay, folks. I need some help. I was not able to flash new Cyanogen ROM's so I tried updating my TF300T to the latest US firmware. Here are the results and where I stand now.
1. TWRP 2.5 is loaded in recovery.
2. Latest ASUS firmware is installed.
3. Lost root.
4. Tried to re-root and cannot. SuperSU fails every time I try to update the binary.
5. I wipe everything and can boot into recovery.
6. I tell TWRP to flash the latest ASUS firmware zip file.
7. Firmware flashes but then when I go to reboot in TWRP it says that no OS is available!!
8. I can swipe the lock and reboot into 4.2.1 but obviously no root.
9. I have tried flashing the signed superuser file and it flashes and says successful.
10. When I use root checker pro to see if I have root it tells me that I do not have root.
What in the hell is going on????????? Any help or outline of steps would be appreciated.
Click to expand...
Click to collapse
Bootloader info plz. Unless you were using the experimental CM10.1 build (or a select few others), it sounds like you tried to flash a ROM compatible only with an older bootloader onto the "latest" build (from your description).

[ROOT GUIDE] KNOX 0x0 NOTE 3 LTE (SM-N9005) LOLLIPOP DB 5.0 KNOX 0x0 [ROOT GUIDE]

Hello Everybody.
I have finally successfully rooted Note 3 N9005 on Android 5.0 Dev Base (DB) only, without tripping knox. The Dev base (DB) is made or compiled by Alexander on OB6 (the latest firmware). It has Multi-CSC feature and hence you will not have to worry about the CSC feature being a reason for holding you back from Rooting Note 3 N9005.
Disclaimer: I am not responsible if you mess up any of the steps and neither am I responsible for anyone bricking their phone. I have personally tested this step 3 times over to confirm its validity.
UPDATE: We have finally been able to root all LOLLIPOP without dev base. The new guide is on its way. All your data can remain, you will be able to root without having to worry about losing your DATA.
UPDATE: Here is the link to my ROM, you can replace this rom with Alexander's Dev Base in the Instruction Steps and all will be fine.
:: MEGA DOWNLOAD ::
:: DROPBOX DOWNLOAD ::
UPDATE: Added updated Links for Alexander DevBase, Bootloader and CP File.
NOTE: KNOX apps have been disabled by default by Alexander himself. Thank you Alexander.
NOTE: Moderators please move this thread to the right section. Also, please note, I will be giving credits to the original Devs for the rom and the root methods which I used common sense and made them work. All these changes will be released in the final Guide. In a few hours the whole guide with the complete step-by-step procedure will be uploaded here.
NOTE: I have written this guide on my own and have not copied anything from anywhere except the rooting process provided by W0lfDroid. If required, I will remove it and replace it with the link to the page to make it easier. But, in my opinion my steps are simpler
Things you will need.
Precautionary step: Make a backup of your PIT File just in case. You might need it though I had no need for it and its simply taking up a few KBs of Space on my PC
1). Official Stock 4.4.2 Firmware. (Grab it via Sammobile).
2). N9005XXUGBOEA_DevBase_alexndr.zip (Grab it HERE).
3). ODin v3.09. (Grab it HERE).
4). Mobile ODin Pro. (Buy it and support Chainfire).
5). SuperSU 2.46 APK. (Grab it from Google Playstore).
6). Towel Root APK v3 Offline. (Grab it HERE)
6). Device drivers. (My suggestion would be to just install Kies 2 and Kies 3).
7). ADB should be set up and accessible via CMD.
8). Root Kernel
9). Stock Kernel: NF4, NG1, NG2, NH1, NI4, NJ1, NJ2, ZTFUNJ1, NK1
10). Bootloader File (OEA – Latest as of now).
11). CP File (OD3 – Latest as of now).
Credits:
The Root Kernel and Stock Kernels are all credited to W0lfDroid.
SuperSU, Mobile ODIN Pro 4.20 are credited to Chainfire.
DevBase Rom, Bootloader File, CP File are credited to Alexander.
Towel Root is credited to Geohot.
Instructions:
Part 1: Downgrade 5.0 >> 4.4.2 (Skip this if you have 4.4.2 and move over to Part 2).
Procedure:
1). Run ODin v3.09 as Administrator.
2). Unzip the stock rom zip package that you downloaded for 4.4.2 and you will get a ".TAR.MD5" file. That is the one that you require.
3). Attach your phone in “Download Mode”. To enter this mode, turn off your phone. Press and hold POWER + MENU (Home Button) + Volume Down keys. Then a confirmation dialogue will pop up and ask you to continue to enter the mode by pressing the Volume UP key.
4). Click on AP and select the “.TAR.MD5” file extracted.
5). Make sure only "Autoreboot" and "F.Reset Time" are "checked".
6). Flash the Firmware by clicking "Start".
7). Once flashed, let your phone reboot. Should take about 10-15 mins.
NOTE: If your phone doesn't boot up after a considerable amount of time. Turn it off. Pull out the battery. Re-insert the battery and boot your phone into “Recovery Mode” by holding the Power + Menu (Home Button) + Volume UP keys. Wipe your data and cache partitions.
8). Setup your phone but better not connect it to Google/Samsung/Dropbox or any other accounts because you are going to get those wiped again.
Part 2: Rooting Note 3 on 4.4.2 (Skip this is you have a Rooted 4.4.2 phone and move over to Part 3).
Procedure:
Before starting this find your kernel version and build number, the last 3 letters/digits matter such as NG1 or NH1, etc.
Install SUPERSU 2.46 APK
1). Run Odin v3.09 and connect your phone in “Download Mode”
2). Click AP on the ODin screen and navigate and select the file Root Kernel.
3). “Auto-reboot” and “F.Reset Time” are selected and click “Start”.
4). Let it flash and reboot.
5). Install Towel Root v3 Offline APK.
6). Open the Towel Root APK now and tap “Make it rain”.
7). Install SuperSU from Playstore.
8). Update the SU Binary and Disable KNOX.
9). Reboot your phone.
10). Now flash the Stock Kernel, Follow the same steps 1 – 4 but just replace the Root Kernel with the Stock Kernel to allow you to have full functionality as Wi-Fi gets disabled with the root Kernel.
Part 3: Upgrading to Android 5.0 Lollipop Dev Base Alexander OEA.
Procedure:
1). Install Mobile ODIN Pro 4.20
2). Move the N9005XXUGBOEA_DevBase_alexndr.zip to your Internal SD Card.
3). Run Mobile ODIN Pro and choose the option OTA/Zip Update.
4). Select the N9005XXUGBOEA_DevBase_alexndr.zip file.
5). Uncheck (untick) the “Everroot” Option.
6). Flash Firmware. If it asks to verify the checksum let it, if it does not then don’t worry.
7). Let Mobile ODIN Pro do it’s thing.
8). The Aroma Installer will pop up. Leave every option as-is. The only extra options we have to select are “Wipe Data” and “Update Stock Recovery”.
9). Let it install.
10). Uncheck (untick) the “Reboot Device” option.
11). If your phone reboots, then let it start up and then DO NOT set up your phone, just hold the power button and turn it off.
12). Enter “Download Mode”.
13). Run ODin v3.09 and click on BL and select the OEA Bootloader File and click on CP and select the OD3 CP File.
14). Make sure Auto-reboot is not checked.
15). Now, hold down the power key and turn off your phone.
16). Boot into “Recovery Mode” by holding the POWER + MENU (HOME BUTTON) + VOLUME UP keys. You will see a msg at the bottom Applying Multi-csc which is essential to prevent your phone from entering boot-loop or crashing after the Samsung LOGO.
17). “Wipe Data/Factory Reset” and “Wipe Cache Partition”.
18). Reboot your phone and set it up. But DO NOT install any app, my opinion or suggestion is not to connect your google account just yet.
19). After the phone has booted, open play store and connect your GMAIL Account and install Root Checker from Playstore.
20). Do not open any app and do not install anything.
21). Turn off your phone and wait for 2 – 5 mins.
22). Turn it back on and open Root Checker and grant it SU permission.
23). Then open SuperSU, update the binary if asked and set it up as you like.
24). Have fun, you now have a Rooted Lollipop 5.0 Phone on the latest Build Number OEAwithout Tripping KNOX
Updated and Maintained as of 19th June 2015.
Consider buying me a couple of beers for my contribution
​

Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot

I think my team has been able to come up with the solution.

patate331 said:
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
Click to expand...
Click to collapse
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out

XxXKINGMAKXxX said:
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
Click to expand...
Click to collapse
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?

patate331 said:
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
Click to expand...
Click to collapse
Well yes. Flashing a stock rom with pre-root seems like the only case right now.

Sounds good enough for me! Awesome what you guys did, keep up the good work!

UPDATE
All variants (possibly) root knox 0x0

Thanks. worked like a charm. Just 1 suggestion. After point (14). Make sure Auto-reboot is not checked.) you can add "start odin flash" to avoid confusion. IMHO.

Yes very true. I will add it.
Also please note that I have tripped my knox in the learning process and will not continue any new guides regarding knox 0x0.
I'm quite satisfied and will now move forward towards hardcore development of Custom ROMS or development of stock ROMS with addition to more development of apps.
Check for new updates regarding new development apps that I am working on. I hope these apps become a game changer

thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?

sword_fish89 said:
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
Click to expand...
Click to collapse
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK

XxXKINGMAKXxX said:
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
Click to expand...
Click to collapse
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..

sword_fish89 said:
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
Click to expand...
Click to collapse
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.

Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?

if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question

XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
erevoz said:
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
Click to expand...
Click to collapse
No. This is to preserve 0x0. It won't change 0x1 to 0x0.

arvin2212 said:
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
Click to expand...
Click to collapse
Flash the CP and Bootloader files. Then wipe your data and cache partitions am all should be fine.

Once the whole setup is complete and i wanted to debloat the rom, can i just install thru mop the dev base rom? Is it necessary to do the bl and cp again?

XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
Thnx for the reply KingMak. But i hav few mre doubts.
1. Suppose if i use stock rom bob6.tar.md5 in mobile odin, how do we get that Rom rooted?
Should i tick everroot option and add supersu zip file and then flash to do that?
2. Does dev base (by alexndr) zip package include root installer? Is everroot option unticked for this reason?
3. Can we saferoot(knox 0x0) note 3 sm 9005 using the same method for s4 as posted by xda member Tyxerakias? Plz have a look>> forum.xda-developers.com/galaxy-s4/general/rooted-stock-lollipop-5-0-1-knox-0x0-t3061536

ROOT [n910C] Samsung Galaxy Note 4 Andoid 5.1.1 with Same Bootloader (5.1.1)

Hi Everyone, This is my first post. I am not a developer. Hope this will help you to Root your Note 4 N910C on 5.1.1, if you have any suggestions for me, you're most welcome
Note: I am not responsible for any damage of your phone, kindly read the steps carefully and follow one by one. I have done this with my Galaxy Note 4 N910C on Andoid 5.1.1. Its 100% working.​I have read many thread and websites, I only find Root Note 4 N910C with 5.0.1 bootloader, there was no any option without 5.0.1 bootloader one.
So, with this method you can stay with 5.1.1 Bootloader and can Root your phone. So, here is method I am going to explain you.
First Make sure that your phone's battery is charged above 60%
STEP-1
You need these Files to Root Your Note 4 N910C with Bootloader 5.1.1
Odin3_v3.10.7
SpaceX Kernel
TWRP Recovery
SuperSU
STEP-2
Connect your phone with your computer, You must have installed Samsung USB Drivers in your computer (if you don't have drivers, you can download Samsung USB Drivers Click here)
STEP-3
Copy SpaceX Kernel and SuperSU files in SD Card - Note: I have done this with SpaceX Kernel, if you want to use GoogyMax Kernel or any other Cutom Kernel you can try it. However, I highly recommend SpaceX Kernel.
STEP-4
Disconnect your phone and Switch off then put it into Download Mode (Press HOME+POWER+VOLUME DOWN) Buttons at same time until logo (GALAXY NOTE 4 Powered by Android LOGO) appears.
STEP-5
Open Odin3_v3.10.7 file in your computer (I will recommend open the file as an Administrator - right click on the file.)
STEP-6
Connect your phone with Computer - After Connecting, you will see in the first box [Blue Color] COM:6 or 8 or any other number.
---> if you will not see this please reinstall the Samsung USB Drivers and restart your computer and reconnect your phone.
STEP-6
Click on AP and select TWRP Recovery File from your computer, you have downloaded
Before Click on the Start, please make sure that your phone should not restart. Because it may orverwrite the stock recovery
You Can Do this:
When you see PASS on the window REMOVE The Battery or Press VOLUME UP+POWER+HOME buttons, it will show you the TWRP Recovery page
STEP-7
If you want your can Backup your Stock Kernel, if you want to update your Stock RoM, or install updates in future.
here are the steps:
1. select backup in TWRP Recovery
2. check Boot and uncheck all other options
3. swipe the backup option - and it will save in your internal storage - or you can also choose external storage option, its there
STEP-8
1. Now Install SpaceX Kernel - Click on the install and find SpaceX Kernel and install
2. Go Back and again Install SuperSU
STEP-9
Restart your phone
Your are Done Now!
If you want to check if you phone has been rooted or not,
1. Open SuperSU app in your phone go to setting -> Access (default) -> make it Grant.
2. Download Root Checker from Play Store and check if your ROM is Rooted.
Thank you!
I am new, please let me know if you have any suggests/advise for me.

Thanks, followed instructions to the letter and it's working for me

kazim said:
Thanks, followed instructions to the letter and it's working for me
Click to expand...
Click to collapse
You are welcome!

Titanium backup failed to find root access

Works!
Thanks man! followed the instructions to the letter, works great![

whats the difference between this version or flashing 5.0.1, rooting and flashing 5.1.1 bootloader afterwards?
like this
You can download the bootloader ► here or ► here and flash it via Odin adding the file in the "BL" box.
from here?
http://electron-team.com/dn5_note4_n910c.html

Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.

niceashwin79 said:
Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.
Click to expand...
Click to collapse
you can rebirth it also by flashing 5.1.1 fro scratch from sammobile...

annus9214 said:
Titanium backup failed to find root access
Click to expand...
Click to collapse
you may need busybox, install it from playstore

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8

Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!

Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.

Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?

Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.

annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?

hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?

Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:

Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.

How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol

Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)

Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?

GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...

annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.

annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.

GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse

I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing

Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

2023 EMMC_11 Exploit To Root And Flash Custom Boot And Recovery Images Allowing Custom Roms To Be Used

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 ryanbg​Summary 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.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
**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