LOKI'd jfltexx TWRP for ATT/VZW S4 - AT&T Samsung Galaxy S 4 General

All credit goes to @Dees_Troy and TeamWin for their work on the TWRP recovery, and @djrbliss for his developing of the loki tools. As I'm not developing anything, just sharing the patched image, I didn't feel that this should be in the development forum, but rather general.
This is a loki-patched version of TWRP so that the ATT S4 and VZW S4 users can flash newer ROMs that require the latest TWRP for compatibility. I chose to use the latest stable JFLTEXX TWRP, instead of the carrier variants, as JFLTEXX is compatible with both JFLTEATT and JFLTEVZW devices. I tried JFLTE TWRP, but I couldn't get it to boot to recovery after patching and flashing.
Most ROMs for JFLTE devices will have the following disclaimer:
AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL bootloader.
VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK bootloader.
Do 'getprop ro.bootloader' in Terminal Emulator or through ADB shell to find out which bootloader you have.
Click to expand...
Click to collapse
If that pertains to you, and you want to give the recent pie ROMs being developed by devs like @side and @Buff99 a shot, this TWRP version is needed.
If your S4 DOESN'T have one of those listed bootloaders, but it IS either JFLTEATT or JFLTEVZW, read below, as you are on a bootloader that has been patched to block the Loki exploit:
Read @Hashcode's post HERE for info on SafeStrap, and what you'll be able to flash. I'm almost positive (iirc) safestrap means you can only flash stock-based ROMs.
Downloads:
IMG (using ATT aboot) (AFH)
IMG (using VZW aboot) (AFH) (thanks @grantd!)
ZIP (AFH)
work's for both carrier variants, as it check's against device bootloader to install proper recovery
ONLY ATT recovery is 3.3.1-0. VZW is still 3.2.3-0 as I don't have a VZW aboot.img to work with
TWRP variant: JFLTEXX
TWRP version: 3.3.1-0
IMG Steps:
1. Download to phone
2. Boot to recovery
5. Tap Install
4. Tap Install Image
5. Navigate to folder you saved the patched img to and select it
6. /** IMPORTANT!!! */ SELECT RECOVERY for which partition to flash image to.
7. Swipe to flash
8. Go back to TWRP main screen and reboot to recovery.
9. You should be good to go on 3.2.3-0!
ZIP Steps:
1. Download to phone
2. Boot to recovery
5. Tap Install
4. Navigate to folder you saved the patched zip to, and select it
5. Swipe to flash
6. Go back to TWRP main screen and reboot to recovery.
7. You should be good to go on 3.2.3-0!
Re-read instructions and realize I skipped 3 (just making sure you read the instructions )
King Arthur: "1, 2, 5."
Sir Bedevere: "3, sir...."
King Arthur: "3."
Old versions:
3.2.3-0 - ATT IMG
3.2.3-0 v2.1 ZIP

Peeeerfect

Good job someone's on the ball.
Cheers @mattgyver

Buff99 said:
Good job someone's on the ball.
Cheers @mattgyver
Click to expand...
Click to collapse
You guys are doing the hard part. I just wanted to be able to partake in it all
It may not be much of a contribution, but this should help the people on those wonky bootloaders at least try out the ROMs.

My AT&T s4 is on MDL with clockwork mod while my Verizon variant that I got from a friend is on a bootloader that has patched the Loki exploit (sadly). Does this need to be flashed with ODIN or from my current custom recovery?

StoneyJSG said:
My AT&T s4 is on MDL with clockwork mod while my Verizon variant that I got from a friend is on a bootloader that has patched the Loki exploit (sadly). Does this need to be flashed with ODIN or from my current custom recovery?
Click to expand...
Click to collapse
You should be able to use the Official TWRP Manager app to flash the downloaded img file.
1. Download Official TWRP Manager app
2. Run it (obviously)
3. Tap Backup existing recovery, choose a folder to back it up to, and tap Backup Recovery - not required, but seriously, backups are lifesavers when things go wonky.
4. Go back to the main screen and tap TWRP Flash
5. It should see your device as jflteatt, if not, tap Select Device, and find jflteatt in the list. It may prompt about downloading the latest twrp from them. safely ignore it.
6. Tap Select a File to Flash and navigate to, and choose the patched twrp img. Tap Select (1).
7. Tap Flash to Recovery.
That SHOULD work. I don't see why it wouldn't, since the recovery partition is the same partition, regardless of WHAT recovery resides on it. I'll make a flashable zip file up. It may be easier, and faster

StoneyJSG said:
My AT&T s4 is on MDL with clockwork mod while my Verizon variant that I got from a friend is on a bootloader that has patched the Loki exploit (sadly). Does this need to be flashed with ODIN or from my current custom recovery?
Click to expand...
Click to collapse
TWRP/CWM Flashable ZIP added to the OP.

How to flash this recovery through pc? As i am on stock rom and recovery

imrananis said:
How to flash this recovery through pc? As i am on stock rom and recovery
Click to expand...
Click to collapse
I guess first thing first:
are you rooted?
are you on one of the aforementioned bootloaders (check the OP to see how to find out)?
which carrier variant S4 do you have (ATT, VZW, or other)?
Have you EVER taken an OTA from your carrier?

My bootloader is I337UCUFNB1. My phone's rooted . Can I still install this and flash optimised lineage 16.0?

neilpatel99 said:
My bootloader is I337UCUFNB1. My phone's rooted . Can I still install this and flash optimised lineage 16.0?
Click to expand...
Click to collapse
Nope (to this recovery, at least). If you aren't on one of the bootloaders I mentioned in the OP, you're SafeStrapped and there are limitations to what you can flash.
Read HERE for info on SafeStrap, and what you'll be able to flash. I'm almost positive (iirc) safestrap means you can only flash stock-based ROMs.
I'll add the link to the OP. I figured someone on a different bootloader would ask eventually..

Hi, I have an S4 SGH-I337Z. I am rooted with skyfall OS and TWRP 2.8.4.0 and my boot loader is I337ZTUUBND3. I tried to install TWRP 3.2.3.0(via the ZIP method and the IMG method) so that I could install AOSP Extended Pie ROM but it put me into download mode. I, then, had to use ODIN to put the old TWRP 2.8.4.0 back in place so I could get back into TWRP recovery. Can someone please help me out and point me in the right direction?
Thanks!

raydantheman said:
Hi, I have an S4 SGH-I337Z. I am rooted with skyfall OS and TWRP 2.8.4.0 and my boot loader is I337ZTUUBND3. I tried to install TWRP 3.2.3.0(via the ZIP method and the IMG method) so that I could install AOSP Extended Pie ROM but it put me into download mode. I, then, had to use ODIN to put the old TWRP 2.8.4.0 back in place so I could get back into TWRP recovery. Can someone please help me out and point me in the right direction?
Thanks!
Click to expand...
Click to collapse
You can't use the Pie ROMs. Unfortunately, you're on a safestrapped bootloader, so you're limited to touchwiz-based ROMs. Look at my post directly before yours so that you can get all the information you need.

mattgyver said:
You can't use the Pie ROMs. Unfortunately, you're on a safestrapped bootloader, so you're limited to touchwiz-based ROMs. Look at my post directly before yours so that you can get all the information you need.
Click to expand...
Click to collapse
Are you sure I'm on a safestrapped bootloader? The reason I ask is that I am on a Cricket device and not AT&T...Not sure if that makes any difference.

raydantheman said:
Are you sure I'm on a safestrapped bootloader? The reason I ask is that I am on a Cricket device and not AT&T...Not sure if that makes any difference.
Click to expand...
Click to collapse
Yes.
The I337Z (AIO / CRICKET GALAXY S4 / jflteaio) is a variant of the I337. Cricket is owned by AT&T. The I337M (Canadian) doesn't have similar limitations from what I've seen over the last few years..
Have a look at this thread: https://forum.xda-developers.com/showthread.php?t=2634367. I can't find any evidence to the contrary that you are safestrapped.

Okay here's an update on my progress. I finally found the TWRP 3.2.3-0 that works with the Cricket/AIO variant! To be clear and forewarned, I have only tested this process on the SGH-I337Z.
My bootloader version is I337ZTUUBND3.
Here are the steps:
1. First, go to the TWRP website and click on "Samsung Galaxy S4 (Qualcomm) (jflte)"
2. On that page, scroll down to "International, Americas & China:" and under that choose the "Primary (Americas)"
3. Download the .img file and then follow steps from the OP to properly update TWRP.
4. Done!
Note: I was able to flash a Pie ROM by installing this latest version of TWRP! Thanks to the OP and all the Devs here at XDA for all the hard work put into these custom ROMs and recoveries! :good:
Cheers!

raydantheman said:
Okay here's an update on my progress. I finally found the TWRP 3.2.3-0 that works with the Cricket/AIO variant! To be clear and forewarned, I have only tested this process on the SGH-I337Z.
My bootloader version is I337ZTUUBND3.
Here are the steps:
1. First, go to the TWRP website and click on "Samsung Galaxy S4 (Qualcomm) (jflte)"
2. On that page, scroll down to "International, Americas & China:" and under that choose the "Primary (Americas)"
3. Download the .img file and then follow steps from the OP to properly update TWRP.
4. Done!
Note: I was able to flash a Pie ROM by installing this latest version of TWRP! Thanks to the OP and all the Devs here at XDA for all the hard work put into these custom ROMs and recoveries! :good:
Cheers!
Click to expand...
Click to collapse
Awesome! I'm glad you were able to find a twrp variant that worked for you! The S4 has so many variant, it's eye-crossing confusing!:silly:

You sir, are a hero.

OK att i337
Do I just but use Odin to flash custom recovery or do I need to root it first
I know att is a locked boot loader
Thanks

timj3371 said:
OK att i337
Do I just but use Odin to flash custom recovery or do I need to root it first
I know att is a locked boot loader
Thanks
Click to expand...
Click to collapse
You need to unlock the bootloader first. Go to Settings > About Phone. Somewhere in there will be software version. If you're on lollipop (5.x) you most likely are already limited to safestrap ROMs. There are steps in the OP to check your bootloader version..
Have you ever updated your s4 i337 via the OTA system updates pushed by ATT?

Related

Want to unlock my bootloader + installing TWRP

Hello all,
I am receiving tomorrow my new Samsung S6 and i want to know some things.
- Unlocking bootloader (how to and link?) - have searched a bit and you need ODIN. but what is the best version etc
- Installing TWRP3.0 (how-to) - where to find the latest TWRP for samsung s6
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
forumber2 said:
3- Boot up to TWRP and backup your unmodified stock ROM before do anything on TWRP;
4- flash this ZIP
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Also, here are the threads for TWRP and SuperSU for the S6 on XDA:
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
http://forum.xda-developers.com/galaxy-s6/orig-development/cf-auto-root-t3056630
djbosanac said:
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Click to expand...
Click to collapse
No, and there probably won't be any for a long time, but there are lots of TouchWiz-based custom ROMs.
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
djbosanac said:
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
Click to expand...
Click to collapse
Correct. The only custom ROMs availability now and the foreseeable future are based on TouchWiz, not AOSP Android or CyanogenMod.
CafeKampuchia said:
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Click to expand...
Click to collapse
He need dm-verity disabled boot image for working TWRP backups. That's why I suggest him to install this ZIP.
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
djbosanac said:
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
Click to expand...
Click to collapse
As I said before, there's no bootloader unlock because bootloader is factory-unlocked on Samsung devices.
If you want root, you should to use TWRP for install the latest SuperSU.
Yes, there's no CM ROM for Exynos 7420 right now. Maybe in future? Who knows...
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
djbosanac said:
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
Click to expand...
Click to collapse
It is not an issue, it is just a warning. I wrote what you need to do at first reply;
forumber2 said:
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
i tried to install it, used the AP method in Odin.
But when i want to go in TWRP recovery i get the stock recovery! How to solve this issue
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
SuddenGun007 said:
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
Click to expand...
Click to collapse
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
piotrus22 said:
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
Click to expand...
Click to collapse
I did figure this out, check this post for how I did it.

[GUIDE][SGH-I337] TWRP 3.0.2-0 Recovery & ROOT for AT&T Samsung Galaxy S4

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.

[GUIDE] Root, Bootloader Unlocks, and More!

Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!​
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.
i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.
The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021​
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
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...
forum.xda-developers.com
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
its uploading sorry it failed at 99 percent
jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded
jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!
tested on one of the spares I had kicking around
does what it says on the tin
!kickass
The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps
The OP has been updated to reflect @jrkruse 's new instructions
AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help
["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]

[DEV-ABOOT-ONLY/PF4/PD1/PG2/PJ2/PL1/QA1] Safestrap Recovery v4.05 B01 [2017-03-23]

VERIZON SAMSUNG GALAXY S5 (KLTEVZW)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.05-B01 (DEV-ABOOT-ONLY/PF4/PD1/PG2/PJ2/PL1/QA1/6.0.1)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S5 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root (systemless SuperSU)
[v4.03 Safestrap zip file]: Flash via TWRP/FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
KNOWN ISSUES:
- Not WORKING NON ROOTED DEVICES (DEV-ABOOT)
- NOT WORKING ON ANDROID 4.4.X
- NOT WORKING ON ANDROID 5.0
- NOT WORKING ON SYSTEM ROOT
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY S5 (kltevzw) (DEV-ABOOT-ONLY/PF4/PD1/PG2/PJ2/PL1/QA1/6.0.1)
LATEST FILE: Safestrap-4.05-B01-KLTEVZW-6.0.1.zip
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
@jrkruse for zip template
CHANGES:
4.05-B01 [2017-03-32]
- Update to latest TWRP 3.1.0.
- Major safestrap specific updates (https://github.com/mohammad92/recovery-safestrap/commits/safe3.1.0)
4.03-B01 [2017-02-26]
- Initial support.
This will work on android stock 6.0.1 only, maybe on cutom AOSP roms that included MM kernel headers.
APK version coming soon when it ready
stock 5.0 not tested since I'm on 6.0.1 QA1 but will try to compile it soon.
Nice job as always!
Really cool tool to use
Safestrap 4.05-B01 is up
Can I use safestrap to install lineage OS?
bereket said:
Can I use safestrap to install lineage OS?
Click to expand...
Click to collapse
No.
Why would this get used instead of twrp flashed to recovery?
mattnin said:
Why would this get used instead of twrp flashed to recovery?
Click to expand...
Click to collapse
kltevzw is locked! But some devices with CID start with 15 can be unlocked and flash twrp.
And they still need safestrap for upgarde bootloader and unlock their devices.
This version of safestrap does not need kitkat kernel to show up the boot menu, so you can use it with MM kernel.
mohammad.afaneh said:
kltevzw is locked! But some devices with CID start with 15 can be unlocked and flash twrp.
And they still need safestrap for upgarde bootloader and unlock their devices.
This version of safestrap does not need kitkat kernel to show up the boot menu, so you can use it with MM kernel.
Click to expand...
Click to collapse
Oh yeah! I forgot about that. I just have four CID 15 phones and just used to flashing TWRP into recovery. Thanks!
Hi Guys,
My phone is cid11 and when I flashed freedom ROM, I lost safestrap. It says that it's installed buy when I boot into recovery, the phone just restarts. What do I need to do to get it back?
I was referred to this thread through another.
d8n0g said:
Hi Guys,
My phone is cid11 and when I flashed freedom ROM, I lost safestrap. It says that it's installed buy when I boot into recovery, the phone just restarts. What do I need to do to get it back?
I was referred to this thread through another.
Click to expand...
Click to collapse
you are on 5.0 ROM and safestrap not support your kernel
use this https://forum.xda-developers.com/ve.../ncg-ne9-nha-ni2-nk2-4-4-x-safestrap-t3577599
flash kitkat kernel to boot safestrap and restore your 5.0 kernel after that
or simply use this https://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800
Much appreciated!!

[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?

Categories

Resources