Disclaimer: You own the responsibility for choosing to take this route versus the Factory OTA. If it breaks, you own both pieces.
This process uses an unsupported Safestrap. Issues with that program should NOT be reported to Hashcode.
If something goes wrong, you need to be sure that you have a way to recover. Back up first.
The SCH-I545L is a variant of the Verizon Galaxy S4 that's used for several carriers - for example, Bluegrass Cellular, Cellcom, Appalachian Wireless, and others. The "L" variant isn't compatible with kernels and bootloaders designed for the stock SCH-I545 so it needs different treatment.
This method allows you to upgrade from MK4 to the official NC5 root and retain root in the process. It's exactly the same process as the one introduced by @muniz_ri for the I545, found here.
Without his work, this would not have been possible.
Thanks also to @evilryry for his help with pulling the files together and with testing this upgrade.
This is a copy of the MK4-to-NC5 OTA hammered into shape to not flash the NC5 bootloader, and install SuperSU. When you're done, it's a stock, rooted NC5.
This will not upgrade the bootloader to NC5, which means that if anything goes wrong you can flash back to stock MK4 to recover.
However, back up your phone in Safestrap before you begin so you have something to revert to.
Steps to do this:
You must first ensure that your MK4 system is in factory stock condition, with no files modified, no Xposed framework, etc. You must have SuperSU and Safestrap 3.72 installed before starting. See post #2 in this thread for a script that you can run on your phone to ensure that it's pristine.
If your phone is not clean, flashing a no-wipe MK4 ROM image will repair it. Just make sure that you flash Safestrap 3.72 as well. ( Safestrap-JFLTE-3.72-kk-B01.apk)
Download Upgrade_I545L_MK4toNC5.zip from here,
MD5: c2e6673da0b235d9a3258c0ab46c8a65
Download I545L_Stock_Kernel_and_Modem.tar.md5 from here,
MD5: 693274326ad9d9209be0f0680bcb125e
Put the "Upgrade_I545L_MK4toNC5.zip" file onto the root of your external SDcard.
Reboot and open Recovery from the Safestrap screen. Do not wipe anything!
Flash the "Upgrade_I545L_MK4toNC5.zip" file into the stock slot.
When the flash is complete, Press "Home" and reboot into Downloader mode.
Using ODIN, flash " I545L_Stock_Kernel_and_Modem.tar.md5" by putting it into the PDA or AP slot.
The first boot will take a long time as the phone optimizes apps. Be patient.
Before trying this, there's a way to verify that your phone is "stock enough" for the flash to work.
Download the attached script file and push it to the root of your SDcard.
Then, open terminal emulator and type at the prompt:
su -c /storage/extSdCard/mk4-verify.sh
or
su
sh /storage/extSdCard/mk4-verify.sh
You MUST have busybox installed for this to work; otherwise, you'll get a bunch of "/system/bin/sh: cut: not found" errors.
If everything is right, you'll get no output. Otherwise, any tampered files will be listed.
If you choose to install a non-stock ROM image after your NC5 upgrade, you'll need a set of kernel modules to flash. @evilryry has built a ZIP containing those, available from here.
You flash these in recovery after flashing the ROM but before rebooting.
Also note that you should flash SuperSU at the same time
Reserved #3.
Rock on. Thanks k1mu. Hell of a help. I'll be happy to help if anyone has any issues, as I have the phone and have gone through your upgrade process.
Fellow 545L'ers, Just a note to addon if you choose to install a custom rom, on 3.72 safestrap, backup your stock slot, and install over stock slot. remember, flash rom, then flash modules, and very important flash supersu zip. or else you wont have root/safestrap on custom rom and you will have to odin back to 4.3 and start the upgrade process all over again!
@k1mu Nice job!
And please let me know if you have better luck than I have had trying to resolve the safestrap apk force close issue after the upgrade.
If we already have NC5 without root, is there a downgrade option so I can use this method? Sorry, I'm new....
Ampz55 said:
If we already have NC5 without root, is there a downgrade option so I can use this method? Sorry, I'm new....
Click to expand...
Click to collapse
Several threads discuss it...
sent by bajarom v2.2 kitkat
I've found threads on downgrading, including Surge's here: http://forum.xda-developers.com/showthread.php?t=2726868
but I figured downgrading using this method for the regular I545 would not work correctly.
Well first of all I'm not a developer but I consider myself decently knowledgeable. So, Not 100% sure but I believe that was to downgrade kitkat to jb with the jb bootloader intact in case you don't like kitkat or need to restart the whole process. I don't think you can get back to the jb bootloader once you upgrade it to kitkat. The way this process works is by updating the system and stuff but not the bootloader, leaving it at mk2 or mk4 in the 545L. So you can go back to the 4.3 and start again if you mess up. But the bootloader no, I think it's the same principle as not being able to Odin back to mdk because the bootloader updates. You can't downgrade it.
Have a screenshot showing my bootloader version (4.3) with kitkat baseband running hyperdrive 16.1
So forgive me if I'm wrong, but I believe if you take the ota or whatever to kitkat you're SOL for this posts process for root atm.
Edit, as with other phones, if anyone with this has upgraded via ota to kitkat you should be able to use @geohot "towelroot" method. Be sure to thank him too!
Sent from my SCH-I545L using XDA Free mobile app
Where can one find a No Wipe MK4 ROM?
Rom? No. Odin flash yes. It's a few pages back in the other 545L thread, also on sammobile site. You'll see me linking it to someone else and the other guy who caught the download. You download it and extract the file, put in odin ap slot and flash. You are better off though if you backup and factory reset beforehand. Also, you could just use kies 3 to update with then use towelroot then install supersu from play store.
Remember at some point on stock rom backup your apn using apn backup and restore.
If custom rom is desired: From then if you choose to use safestrap download "selinux mode changer" app in play store change to permissive. Then download the 3.72 safestrap linked in op, and flash supersu *zip* and then desired rom. Also you will find somewhere in other thread our modules I Dropboxed but if you can't find it (will be 2 or 3 pgs back) I will link again. Feel free to post here or pm if you need any help. FYI, 4.3 mk4 flash we have and kies are no wipe.
Sent from my SCH-I545 using XDA Free mobile app
---------- Post added at 03:11 AM ---------- Previous post was at 03:04 AM ----------
kmg90 said:
Where can one find a No Wipe MK4 ROM?
Click to expand...
Click to collapse
https://mega.co.nz/#!HYBVHRQY!AigKnk8oNokcStYZ6GR6l13t1oAa9bQsOHxjEMj1A2U +extract = 4.3 MK4 Odin flash. if you want root, easier option is to just use kies imo. or use this and do an ota. then use towelroot+supersu. you basically follow this http://forum.xda-developers.com/showthread.php?t=2784138 steps 5-7 use ss method heading.
Hello I was wondering do you know what the mms settings are ? I'm trying to use evolve app. And it won't automatically find the mms settings.
Sent from my SCH-I545L using XDA Premium 4 mobile app
blackbeard10 said:
Hello I was wondering do you know what the mms settings are ? I'm trying to use evolve app. And it won't automatically find the mms settings.
Sent from my SCH-I545L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try harvesting from this or the info Dallas posted in other 545L thread.
Sent from my SM-G900V using XDA Free mobile app
When I try to flash this update with Safestrap 3.72 I get an error. I've checked MD5 it's good, I can't flash the original upgrade either. Is there a permission's set wrong somewhere?
XRSTOY1 said:
When I try to flash this update with Safestrap 3.72 I get an error. I've checked MD5 it's good, I can't flash the original upgrade either. Is there a permission's set wrong somewhere?
Click to expand...
Click to collapse
Are you on 4.3? You probably have modified system files or something. For this to work you need stock minus supersu and safestrap. Though the easy way to do this now is just to upgrade with kies and use towelroot. Just plug phone up and use kies. or if you must do it the harder way..
download https://mega.co.nz/#!HYBVHRQY!AigKnk...bQsOHxjEMj1A2U Should be a zip so extract and flash(4.3 is only flash i know is publicly available, 4.4.2 nc5 might be too tho) then with odin and upgrade with ota or try this process again.
Sent from my Supercharged KT Powered S5
worked for me
decaturbob said:
Several threads discuss it...
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
Had good luck with this one.
GSM/CDMA Unlock for SCH-I545L
Hi,
I just bought a SCH-I545L over ebay and the seller said its Verizon but it turned out to be Other local carrier phone probably Cell Com. Verizon Phones are GSM Factory unlocked and hence I wanted to buy the same but this is not working with International GSM Service providers.
I basically want to use the phone outside of the USA on GSM and CDMA network.
I would like to know anyone here can guide me to a post or thread where there is a GSM/CDMA unlock available for SCH-I545L.
The other problem which I am facing is that I am not able to enable hidden menu. Dont know how to enable the hidden menu. Have already checked out various posts saying to take a backup followed by changing /efs/carrier/HiddenMenu. Change OFF to ON. Did the same but thats not working for me. *#06# doesn't work.
I was however able to root the phone through Towelroot. I am currently on 4.4.2 NC5.
Any guidance in the matter would be highly appreciated.
Thanks
Related
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 7 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
VRUFNC2 ("NC2")
VRUFNC5 ("NC5")
There's another release that was apparently a leak or limited release, MG7.
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on. The best way to tell what bootloader you have is to install an app - "Phone INFO *Samsung*" and "Phone info" will both tell you what build and bootloader you have.
The "Developer Edition" devices have "I545OYUA" build numbers versus the consumer versions, which start with I545VR.
Once you're on a particular build, it is not possible to downgrade to an earlier release. The single exception to this is that you can flash MJ7 over MK2, but that's it.
If you're past MDK, you can't bypass the bootloader until an exploit is found.
If you start flashing things without verifying that it's for the release on YOUR phone, you risk bricking it. There's dozens of youtube videos telling you how to flash custom recovery on your phone that WILL NOT WORK unless you're on the MDK bootloader. Be sure to comment in the youtube thread after they assist you with bricking your phone.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
For NC2 and NC5, you can't currrently root unless you downgrade the baseband to MK2.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recovery will not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
k1mu said:
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
Click to expand...
Click to collapse
this really needs to be a sticky as we all know how many aren't taking the time to more than a cursory check in these threads
---------- Post added at 06:16 AM ---------- Previous post was at 06:09 AM ----------
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is the original MDK baseband. Not checking first before flashing will often break your phone.
If you need to know what baseband you're on, use "Settings", "More", "About phone" and scroll down to the "Baseband Version".
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're on the MDK baseband. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
k1mu, I also created a step by step guide (with links) that walks you thru the entire process of going from ME7/MI1 to MJ7 by flashing the wipe tar image of MJ7, installing your saferoot, safestrap and HD11
http://forum.xda-developers.com/showthread.php?t=2579278
I was feeling pretty bad for all the people that were messing up their phone becasue od not understanding the entire process.
Props to you both ! The only thing I would emphasize for MDK users is to get yourself educated (plenty of threads) on the Loki process. The proper use of it when flashing unfamiliar recoveries or kernels can save alot of headaches (trust me I know !!)
Bumping
Sent from my SCH-I545 using XDA Premium 4 mobile app
MJ7
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
sixtythreechevy said:
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
Click to expand...
Click to collapse
nope updating modem changes what your baseband version says.
For those who are unsure if you can install the custom recovery:
The BUILD must be MDK not the MODEM. If you are running different build you can flash different modems. Just because you have the MDK modem does not mean you can flash a custom recovery.
Yeah you can flash any baseband at any time you like...that's your radio/modem. You can also flash a new build as long as your bootloader remains on MDK. For example, I'm running a stock MJ7 ROM but I'm still Loki'd on the MDK bootloader.
Sent from my SCH-I545 using Tapatalk
ok heres my issue
Delete
What really matters here is what Bootloader you're running. Since updating the modem changes the Baseband string, that can't be used to tell if a phone is locked. I've updated the OP to say Bootloader version and to explain how to get to the Bootloader version.
FordNate said:
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good.
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
tkacer said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
Click to expand...
Click to collapse
yes and got it running again with root
Happy 4 ya - nothing worse than a borked phone !!!!
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
dbinnc said:
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
Click to expand...
Click to collapse
Install the MK2 no-wipe from here.
I want to bump this thread so we can use the OP as a starting point for a stickie guide concerning verizon S4 and what you need to know for modding your phone.
Naddict will be assisting in getting the sticky set up. This will be a WIP and will NOT be a thread to post questions. Lets get all our smart people contributing with info and links as needed to help all those who wish to mod their phone from not repeating all the same errors and bricking.
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 5 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on.
If you start flashing things without verifying that it's for YOUR phone, you risk bricking it.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
Excellent! Thank you!
Developers edition bootlader
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
kerryh420 said:
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
Click to expand...
Click to collapse
I'm pretty sure you'll need to root first. Also I'm not sure standard twrp is what you need for the Dev edition. They are lokied and I don't believe you have a need for that. That being sailing not exactly sure what your process for rooting will be or which recovery you need.
Maybe this thread will give you some insight.
http://forum.xda-developers.com/showthread.php?t=2339849
Then research about flashing roms on the Dev. Edition. It will be different for you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hey All!
MODERATORS: Please change the name of this thread to "[ROOT] [RECOVERY] [ODIN] [APK] All-in-One Guide" and maybe sticky it?
Before Reading this guide, check your Bootloader version in Settings ==> about this phone, it looks like VRUFxxx, if on MDK, go here NOW http://forum.xda-developers.com/showthread.php?t=2292112, this guide uses CWM recovery, but there are others, just google either "PhilZ touch Recovery Galaxy S4 Verizon Loki" or "TWRP Recovery Galaxy S4 Verizon Loki" if you don't like CWM.
If on any other bootloader, Flash the MK2 Full-Wipe Tar (below in the ODIN section) if you want to run 4.3 Jellybean ROMS, or NC5 Full-Wipe Tar if you want to run 4.4.x Kitkat ROMs
MAJOR EDIT - SafeStrap can now boot (very few) Google Edition (AOSP) ROMs!!! After getting SafeStrap 3.72 installed, SELinux set to Permissive, and your bootloader on NC5, you can wipe /data /system and /cache (as well as dalvik-cache), the Google Edition ROM linked later in the thread under the SafeStrap Compatible ROMs Section, and of course flash either NC2 Modules or NC5 Modules depending on your bootloader version.
ROOT
To begin I didn't create this, Geohot (George Hotz) did, I am just sharing it with this forum and creating a discussion type post for it, as not to junk up the initial thread.
It exploits CVE-2014-315, which exists in all Kitkat 4.4.2 (and Nexus 4.4.3) devices. This will work on all 4.4.2 (and some 4.4.3) devices as long as they don't have /system write protection (Like newer Moto and HTC phones...)
This was originally thought to be a useless vulnerability due to the fact that when exploited it only gave access to a remote root shell for ~15 seconds before SELinux implementations kick on and kill it, or in most cases it causes the system to reboot upon exploitation (I still don't understand why this happened...?)
Geohot however, found a way to shape this vulnerability into the amazing exploit TowelRoot. It comes in the form of an installable APK
Prerequisites: Enabled Unknown sources in settings
1. Navigate to http://towelroot.com
2. Click the lambda (the greek letter) or download here https://www.dropbox.com/s/71a7e8wdscbdd0t/tr.apk
3. Open the APK file and click install
4. Follow on-screen prompts
Now you can either use SafeStrap which can flash mods/zips/ROMs:
SafeStrap Method
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
5. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
6. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/showthread.php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
7. Flash http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip, this step is NOT OPTIONAL, without this file, your SU Binaries will not update!!! (This is important!). Do this by rebooting your phone and clicking "recovery" when safestrap prompts you, then clicking "install" and selecting the /zip linked above, then swiping to flash, and rebooting.
Normal Method
5. Download http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip
6. Use ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop and unzip the file
7. Open the /common folder in the unzipped file, and copy the SuperUser.apk to the /system/app/ folder in the root of the phone, confirm any SuperUser Access requests at this point
8. Reboot
9. Open SuperSU and under the settings tab, update your SU Binary
10. Profit
TWEAKS
(Optional)
10. Flash http://www.androidfilehost.com/?fid=23487008491962487 in SafeStrap to enable wifi tethering
11. Use https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete to update to the newest version of BusyBox (The more popular BusyBox apps wouldn't work for me/ didn't have the newest version)
SAFESTRAP NOTES/HOW TO
- Have Wifi/Data/Bluetooth issues? Flash NC5 Modules and wifi fix:http://www.androidfilehost.com/?fid=23487008491963692
- Still have Wifi/Data/Bluetooth issues after NC5 Modules? Wipe clean and ref lash your ROM and this time try the NC2 Modules and wifi fix:http://www.androidfilehost.com/?fid=23487008491963696
- We CANNOT just flash a custom recovery, our bootloader is locked, and won't be unlock in the foreseeable future, we have to use SafeStrap instead
- To flash a ROM, reboot the phone, and click the menu button during boot up to get to SafeStrap, go to "Mount" ==> Check /System, leave the others checked
Then go back to the menu, go to "Wipe" ==> /System and swipe to wipe, you do not have to wipe /data, but it is strongly recommended (But this WILL wipe your data!!!)
The go back to menu, click "Install" select you ROM's .zip file AND SuperSU 1.99v4.zip to be safe
- You cannot use ROM Slots because this version of SafeStrap is made for the ATT S4, because of that we have some incompatibilities, you can only install to the "Stock" Slot
- BEWARE of flashing a Custom ROM and wiping /system, because if wipe /system, YOU ARE ERASING SAFESTRAP, if you flash a ROM that doesn't boot/is incompatible, you will have to ODIN back to stock!!!
- On a similar note, don't just flash a new ROM over your current ROM without wiping /system, as "dirty" flashing never ends well
- Most ATT SafeStrap 4.4.2/3 ROM work on the Verizon version, just a matter of testing them!!!
ROMS THAT ARE CURRENTLY COMPATIBLE WITH SAFESTRAP 3.72
Pre-Rooted 4.4.2 - Removes BloatWare stuff and implements the features from the International version that Verizon removed http://www.androidfilehost.com/?fid=23329332407590564
Google Edition ROM (TW Kernel) Option 1 - Google Edition ROM that IS compatible with SafeStrap, although not everything works... I know it says ATT, but I have tested and it works on verizon[/B]http://forum.xda-developers.com/showthread.php?t=2767026
Google Edition AOSP (TW Kernel) Option 2 - Madre de Dios.... Google Edition for Safestrap, who'd of thunk. It is the latest 4.4.4 and everything except for MTP Mode (file transfer), and Wifi is touchy... but who cares, AOSP!!! http://www.livewinter.com/mirror/get_file.php?id=30
BlackBox - An AOSP themed ROM that keeps many Samsung features, just google "BlackBox ROM S4 for a list of features/screenshots http://www.androidfilehost.com/?fid=23501681358541454
HyperDrive RLS 16.1 - TouchWiz S5/Note 3 with many awesome baked in features http://forum.xda-developers.com/showthread.php?t=2301724
Purified ROM - AOSP Themed with custom toggles http://forum.xda-developers.com/showthread.php?t=2759811
gDux - Highly Customized TouchWiz/AOSP, hard to explain, but really cool!!! http://forum.xda-developers.com/showthread.php?t=2759786
Blue Chrome Edition - Googlie made this.... I don't know anything about it, wanna describe it @googlie? http://www.androidfilehost.com/?fid=23329332407588272
PhoeniX ROM V8.0.1 - Strongly tweaked ROM based on TouchWiz, again just google "PhoeniX ROM S4" for description/screenies http://www.androidfilehost.com/?fid=23501681358541455
FoxHound ROM - One of the best ports I've found around, there are so many options that no 2 installs of Foxhound are the same, you could live with just raflashing different options of this ROM and be happy for a long time...http://www.androidfilehost.com/?fid=23487008491966537
Baja ROM - AOSP/TouchWiz Hybrid http://forum.xda-developers.com/showthread.php?t=2696872
Echoe ROM - First 4.4.2 TouchWiz ROM made for out phone, very stable/stock-ish with some added features http://forum.xda-developers.com/showthread.php?t=2702592
Eclipse - My personal favorite!!! My daily runner. Best Google themed TW ROM that exists in my opinionhttp://forum.xda-developers.com/showthread.php?t=2351840
This is a link to @googlies downloads folder in case anybody wants it, there are some work in progress ROMs and ROM backups (.rar files,) you can check out in there, to use those just unRAR them into you SafeStrap folder on you SD Card, and then restore the backup in SafeStrap
HOW TO BOOT TO RECOVERY/DOWNLOAD MODE
Stock Recovery Mode = Hold Volume Up + Home Button + Power until it buzzes, then release the power button
Download/ODIN Mode = Hold Volume Down until it buzzes and when prompted push volume up to accept
SafeStrap Recovery = "Reboot to Recovery" buttoning the SafeStrap app does not work, instead turn the phone off and turn it back on, then push the menu button after the Samsung Screen goes away
Note - If you see a "Samsung Custom" screen with an unlocked padlock, it doesn't mean you have an unlocked bootloader!!! Don't get your hopes up, it just means that the phone is customized software wize.
ODIN GUIDE
ODIN is a program used to return Samsung phones to stock, it provides many ways to restore the different partitions of the phone;
F. Reset Time - Doesn't ever hurt anything, usually recommended/necessary, but I am not completely sure what it does?
Auto Reboot - Check unless you plan on flashing multiple files before reboot (not recommended)
PIT File - Necessary when completely repartitioning the phone, in most cases will wipe the whole phone clean (excluding @googlies/@Surge1223s guide to downgrade from NC5), it is a partition table template. Comes in the form of a .PIT file.
BL (Called Bootloader in older versions of ODIN) - Restores Bootloader, don't jack with this unless you know what you are doing, you cannot flash any bootloader lower than the on you are currently on! Ex. NC5 ==> MDK won't work, there are some small exceptions like @googlies NC5 ==> MK2 Downgrade, this was only possible due to the NC2 leak that allows downgrades. These files must be signed by Samsung. Comes in the form of a .tar file
AP (Called PDA in older versions of ODIN) - Restores to /System, doesn't Wipe it, just overwrites if necessary. Comes in the form of a .tar file
CP - (Called Phone/Modem in older versions of ODIN) - Restores Modem, wipes it and overwrites with new version. Comes in the form of a .tar file
CSC - (Called Cache in older versions of ODIN) - Restores to /Cache, wipes it and overwrites with new version. Comes in the form of a .tar file
UMS - I am unsure... Anyone? Possibly custom file flashing for Developer editions...?
ODIN 3.09 - Stock ODIN program, used in ALL cases except downgradeshttps://www.dropbox.com/s/b1kjainbic4iloo/Odin_v3.09.zip
ODIN 3.10 - made by @googlie I believe? Used in his guide for downgrading http://www.androidfilehost.com/?fid=23329332407587822
NC5 No-Wipe and Full-Wipe Tars - No-Wipe (Use in most cases) will leave your data in tact but restore /system to stock, Full-Wipe restores everything to stockhttp://forum.xda-developers.com/showthread.php?t=2735172
MK2 No-Wipe and Full-Wipe Tars - http://forum.xda-developers.com/showthread.php?t=2578209
MDK Full-Wipe Tar (If anyone has a link to a No-Wipe, please post it) - http://forum.xda-developers.com/showthread.php?t=2289325
HOW TO RUN 4.3 ROMS IF ON NC5/NC2
This is made for NC5 phones, but will also work on NC2 and allow you to retain the NC2 Bootloader. If you don't know if you are on NC2, THEN YOU ARE NOT, very few people are on NC2, and those that are are there because they know what they are doing (hopefully).
If you want to run 4.3 ROMS in SafeStrap unRAR this file and place it in the AP slot of ODIN (credits to @googlie) http://www.androidfilehost.com/?fid=23501681358537591, then reboot to stock recovery and wipe data and cache, then reboot and use SafeRoot to Root http://forum.xda-developers.com/showthread.php?t=2565758 and install SafeStrap 3.71 from here http://forum.xda-developers.com/showthread.php?t=2441441 and finally flash your 4.3 ROM found here: http://forum.xda-developers.com/show....php?t=2630040
If you have issues, flash the different fixes (Wifi, Voice, Data, etc.) from this thread http://forum.xda-developers.com/showpost.php?p=51955929 in SafeStrap, READ WHAT THEY ARE BEFORE FLASHING
SAMSUNG KNOX
To disable/remove KNOX from stock ROMs:
Download: To Disable: Titanium Backup https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
To remove completely use RootAppDelete https://play.google.com/store/apps/details?id=zsj.android.uninstall, use Pro mode within the app when it asks
Open the app that you downloaded above (either one depending on your choice) Tap the search button and type ‘Knox’ and you’ll get the list of all the files named as knox.
Freeze/Remove (Pro-Mode) the following using titanium backup/RootAppDelete, to find them just search "KNOX"
Delete/Freeze
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
I will be updating this thread as more comes out.
Please refrain from asking stupid questions like "It wonnnnn't boot?" and "Why it no work?", give a good question, and we will give a good answer.
Have Fun!!!
Edit: Added Dropbox Mirror (because some people are having issues with the TowelRoot site... maybe overloaded? XD )
Edit 2: I added a WHOLE lot to this thread and converted it to an All-in-One type guide, hope you enjoy
I may try this on my wife's stock s4 as long as no one tells her.
sent by bajarom v2.2 kitkat
I did this at 1 o'clock today when he release it. Works great! However be sure to download the latest SuperSU here:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
The one in the play store refused to update binaries for some reason.
After you download, open/extract the Zip file. In it is a folder called 'common'. In that folder you will find the updated apk. Just install that and you are good to go!
Sent from my SCH-I545 using XDA Premium 4 mobile app
So if I'm on rooted MK2 (stock, no special recovery or anything, just rooted) should I just unfreeze the updater, full unroot in supersu, get the ota, then run this?
Just curious if anyone currently on stock/rooted mk2 has ota'd up without having to factory reset and lose all their data or not.
esheesle said:
So if I'm on rooted MK2 (stock, no special recovery or anything, just rooted) should I just unfreeze the updater, full unroot in supersu, get the ota, then run this?
Just curious if anyone currently on stock/rooted mk2 has ota'd up without having to factory reset and lose all their data or not.
Click to expand...
Click to collapse
If you update OTA, you shouldn't have to factory reset. Worse comes to worse, I use the no-wipe files in Odin to clean everything out and maintain data.
Do exactly as you said above... Unfreeze updater, unroot, make sure all stock files are there though. Meaning if you uninstalled a system app (VZW stuff for example) reinstall it. Then take the update OTA. Once there , install towel root and push button and whala! Root on 4.4.2!
If you run into trouble updating (if it won't OTA for some reason). Use the no-wipe file found here
http://forum.xda-developers.com/showthread.php?t=2578209
This will protect your data, and do everything stated above in one instance. If you need help with this, just google how to use Odin and read that thread. (File goes in PDA/AP slot. Click start)
Forgot to mention, after you Odin, you take the OTA, and proceed.
Those are MK2 files....
Sent from my SCH-I545 using XDA Premium 4 mobile app
Just used this method myself, works great, easiest and quickest root I have ever done.
this doesn't trip the know counter right? also, does this mean we can install SS and install custom roms now? sorry if it's dumb question.
vzwnexus said:
this doesn't trip the know counter right? also, does this mean we can install SS and install custom roms now? sorry if it's dumb question.
Click to expand...
Click to collapse
Knox is still 0x0
You could install SS before with the downgrade/upgrade root methods. I did not re-install SS recover but you should be able to use the ATT version just like with the downgrade/upgrade methods
I want to try this, but first I must ask will the mobile hotspot hack that was put out for Jelly Bean work for this also, or is there something similar?
just rooted mine as well.
Since having to get a warranty replacement and losing the ability to flash stock roms, i have not had the need for root, but why not? lol
will4958 said:
I want to try this, but first I must ask will the mobile hotspot hack that was put out for Jelly Bean work for this also, or is there something similar?
Click to expand...
Click to collapse
I'm unsure if tethering will work on the NC5 build... Will look into it though
Sent from my SCH-I545 using XDA Premium 4 mobile app
I did this and tried to install safestrap and all it did was reboot. Don't know what I left out.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Nicklag said:
I did this and tried to install safestrap and all it did was reboot. Don't know what I left out.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you open the app and tell it to install recovery?
Yes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Having the same issues myself. I have no clue in how to install safestrap at all after using towelroot. Got my rom ready to flash but cant get a recovery going to be able to do so.
Nicklag said:
Yes
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What version of SS? Did you try the 3.72 for ATT?
I rooted my wife's s4 with towelroot then tried to install SuperSU but when it tries to update binaries it says this device has Knox would you like to try to disable Knox continue or cancel if I hit cancel it just doesn't install but I haven't hit continue because I don't know what will happen
Sent from my SCH-I605 using Tapatalk
timmyd463229 said:
I rooted my wife's s4 with towelroot then tried to install SuperSU but when it tries to update binaries it says this device has Knox would you like to try to disable Knox continue or cancel if I hit cancel it just doesn't install but I haven't hit continue because I don't know what will happen
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
It will turn off the knox notification, there is no harm in doing so.
---------- Post added at 08:58 PM ---------- Previous post was at 08:56 PM ----------
djsbad said:
Having the same issues myself. I have no clue in how to install safestrap at all after using towelroot. Got my rom ready to flash but cant get a recovery going to be able to do so.
Click to expand...
Click to collapse
You need to run Selinux mode Changer and change mode to permissive to allow the safestrap apk to work after upgrading to NC5 using the OTA: https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
timmyd463229 said:
I rooted my wife's s4 with towelroot then tried to install SuperSU but when it tries to update binaries it says this device has Knox would you like to try to disable Knox continue or cancel if I hit cancel it just doesn't install but I haven't hit continue because I don't know what will happen
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I was scared to disable mine but I ended up doing it anyway. It froze up the first time but I restarted my phone and went back to update the binaries. The second time worked. My know counter in ODIN mode still shows 0x0.
vzwnexus said:
I was scared to disable mine but I ended up doing it anyway. It froze up the first time but I restarted my phone and went back to update the binaries. The second time worked. My know counter in ODIN mode still shows 0x0.
Click to expand...
Click to collapse
OK cool I'm doing it now thanks
Sent from my SCH-I605 using Tapatalk
---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------
Should I try to install safestrap before I install xposed
Sent from my SCH-I605 using Tapatalk
4.4.4 Google Play Edition running on Verizon S4 i545 NC5 with a locked bootloader and safestrap. Here is how to do it.
**Note** I am not a developer nor did I create anything I linked in this post. I just put together the pieces to make this work on my phone. Read the AT&T ROM thread as there is a lot of good information there. Likely will answer a lot of questions you may have. Good luck
I have added an additional method that I found to be easier than my original. I kept the original instructions below and put the new method up top.
***Warnings***
Softbricking and screwing up APN settings is a very real possibility that will make your phone unusable. Always make backups and know how to use ODIN to restore factory image before attempting.
Do NOT mess with any APN/Cell network settings if everything is working.
The 4.4.3 from JMSQ will attempt to download an OTA. The 4.4.4 ROMS may attempt to download the Lollipop OTA...DO NOT TAKE THESE UPDATES.
Known Issues (See ROM threads for more details about the known issues and fixes. Or lack thereof.)AT&T thread Pure Nexus GPE thread
Play Store paid apps wont install(set SElinux to permissive)
Chrome Force close(set SElinux to permissive)
Wi-Fi won't turn on(Soft restart will fix when this happens until next full reboot. Then you will have to soft restart again to bring it back. **Or** turn off Wi-Fi before full reboot and it will turn on automatically after boot.)
MTP(Does not work...at all. So you cannot transfer files to computer VIA USB. I use ES File explorer to transfer files VIA WiFi
MMS may not be working.(In hangouts go to settings, SMS, Access point names. Enter Verizon for the name and for the MMSC enter "http://mms.vtext.com/servlets/mms" without the quotes. Leave rest default. Reboot and MMS should be working.) Other messaging apps may be different but the same basic idea applies I assume.
Software update OTA notification Not really a bug/issue. But it is annoying and you DO NOT want to take this OTA. Press and hold on the notification. Open app properties and un-check notifications. This will stop it until your next reboot.
Install Instructions
Method #1
1. I started with stock factory tar.md5 of NC5. The no-wipe link found here and installed with odin. If your already stock on NC5 probably not necessary but its good to have handy if you need it. I then rooted with towelroot. Then I installed supersu, busybox from playstore(both required for Safestrap) and then Safestrap.
2. Download either Pure Nexus Edition or Google Play Edition from this thread to a computer. Both are 4.4.4
3. Download this ROM Zip to a computer.***This is not a Safestrap compatible ROM DO NOT FLASH THIS ZIP EVER!!!!!!****. Extract ZIP and copy build.prop from /system folder to your computer. Then copy apns-conf.xml from /system/etc folder to computer.
4. Now that you pulled out build.prop and apns files delete that ROM zip from step 3 so there is no confusion.
5. Using 7-zip replace the build.prop and apns-conf.xml in the Pure Nexus or GPE zip you downloaded in step 2 with the files you pulled in step 3. This way you have Verizon compatible files in the ROM you are flashing. This allows the phone to connect to VZW network.
5. Get the wifi modules appropriate for you phone and the latest flashable supersu zip
6. Copy the ROM, modules and supersu files to your phone
7. Reboot your phone into safestrap, wipe everything and flash ROM then modules then supersu.
8. Reboot and boot into the new ROM. Once it loads up let it sit a bit and reboot again. Then do a hot reboot if your wifi wont turn on.
9. Make sure you have root and get SELinux to permissive.
Method #2 the OG
1. I started with stock factory tar.md5 of NC5. The no-wipe link found here and installed with odin. If your already stock on NC5 probably not necessary but its good to have handy if you need it. I then rooted with towelroot. Then I installed supersu, busybox from playstore(both required for Safestrap) and then Safestrap.
2. I copied apns-conf.xml from the /etc directory on my phone to my download folder on my phone(this file contains all the settings needed to connect to Verizon's network and is vital for this to work for Verizon phones).
3. Plugged phone into computer and copied apns-conf.xml from the download folder on my phone to my computer.
4. Downloaded 4.4.3 zip from here on to your computer. MAKE SURE YOU GET THE 4.4.3 one.
5. Download and install 7-zip on computer
6. On computer create a new folder on your desktop and name it “etc”(without quotes). Move apns-conf.xml copied from phone to your computer in step 3 into this new etc folder
7. Right click on the 4.4.3 zip downloaded in step 4 and choose to open archive with 7-zip
8. Once open in 7-zip, open system folder. Open etc folder. Delete apns-conf.xml.
9. Back up one directory so the system folder is open again in 7-zip. Drag and drop the etc folder(from step 6 which contains the apns-conf from factory) from your desktop into the system folder in 7-zip. This will add the apns-conf to the etc folder in the flashable zip. See this for more details about altering flashable zip files.
10. Copy this zip with the new apns-conf.xml to your external SD card on your phone. Download NC5 module zip from here and put this on your external SD card as well(The NC5 module zip is important for WiFi to function).
11. Reboot phone into safestrap. I used stock slot because the rom slots are not working. !!!WIPE!!! and flash zip copied to phone in step 10. Also be sure to flash NC5 module for Wi-Fi after flashing the ROM.
12. Reboot from safestrap and continue to boot into the newly flashed ROM.
13. Then install and run towelroot.apk found at towelroot.com to attain root. Install SELinuxModeChanger from playstore and set to permissive (without this chrome force closes and play store has issues with paid apps)
14. Data connected but showed 3g. After a reboot this cleared up on its own and showed LTE. Guessing it pulled the needed information from the APN file on reboot.
Update to 4.4.4 Instructions
1. Download 4.4.4 zip from here. Make sure you get the 4.4.4 link.
2. Again I replaced the apns-conf file with the one I pulled from my stock ROM. Follow steps 6 through 9 above but with the 4.4.4 zip downloaded(unsure if this is necessary but i did it anyway)
3. Make sure your NC5 module zip is still handy and Download SuperSu 2.01.zip here(Make sure to use the flashable zip link. This zip is key to attaining root after flashing this update. Without this SElinux mode changer will not run and set to SElinux to permissive and you will have a bad time
4. Transfer all three of these to external card on phone
5. Reboot to safestrap no need to wipe
6. Choose install and flash the 4.4.4 update zip. Then flash the SuperSu zip. Flash NC5 module again.
7. Reboot and let apps update
8. Verify SuperSu installed and that you still have root
Enjoy 4.4.4 GPE on Verizon S4.
HUGE Thanks to
Hashcode
Surge1223
Chainfire
jmsq
jamal2367
You all get all the credit here. I just put it all together in one post for my fellow Verizon folks.
DOWNLOADS
NC5 tar.md5 http://forum.xda-developers.com/showthread.php?t=2735172
Safestrap 3.72 http://forum.xda-developers.com/devdb/project/?id=680#downloads
Safestrap 3.75 http://forum.xda-developers.com/showthread.php?t=2793891
JMSQ AT&T 4.4.3 ROM and 4.4.4 update http://forum.xda-developers.com/showthread.php?t=2767026
Pure Nexus & Google Play Edition
NC5 Module http://www.androidfilehost.com/?fid=23486521113837640
SuperSU flashable ZIP http://forum.xda-developers.com/showthread.php?t=1538053
Great great write up, good job man.
May just give this a whirl over the weekend. Hate this locked up crap.
Sent from my GT-I9505 using xda premium
Guess our bootloaders need to be NC5 for this to work and not MK2?
Rick, if you stop at the 4.4.3 point, do the 'Known Issues" apply? GPE 4.4.3 is still way better than NC5.
Could you maybe provide a link to modules?
Sent from my SCH-I545 using XDA Premium 4 mobile app
I'm a bit confused. I read all over the Safestrap ROM community that ROMs had to be based upon the same kernel, since the Samsung bootloader checked some codes in the kernel. How does this work with the GPE Google kernel?
JeeperDon said:
I'm a bit confused. I read all over the Safestrap ROM community that ROMs had to be based upon the same kernel, since the Samsung bootloader checked some codes in the kernel. How does this work with the GPE Google kernel?
Click to expand...
Click to collapse
Normally, the AOSP kernel is very similar to our kernel. The developer of this rom modified the kernel so it is compatible with our phones and wont trip knox unless you take an OTA.
Sent from my SCH-I545 using XDA Premium 4 mobile app
aknotts415 said:
Guess our bootloaders need to be NC5 for this to work and not MK2?
Click to expand...
Click to collapse
Correct me if I am wrong but MK2 is 4.3. AFAIK 4.4 ROM's will not work on MK2. I could be wrong but I would think you would need to be on NC5 for this to work.
Awesome write up! I'm downloading the files now to try it out
If you don't mind, can you tell me your average screen on time in regards to battery life?
And just to verify, that mms fix only needs to be done and then it's perfect right?
Thanks!
Sent from my SCH-I545 using XDA Free mobile app
xXsquirr3lsXx said:
Could you maybe provide a link to modules?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the link in step 10 in the first section for installing 4.4.3. I labeled the link "here". Not the most obvious. Maybe i'll add a section for download links.
But here you go
http://forum.xda-developers.com/showthread.php?t=2487298
RickGrimes411 said:
Correct me if I am wrong but MK2 is 4.3. AFAIK 4.4 ROM's will not work on MK2. I could be wrong but I would think you would need to be on NC5 for this to work.
Click to expand...
Click to collapse
If you upgrade to kitkat via surges method before towelroot came out you kept your mk2 bookloader and had a 4.4.2 NC5 rom rooted running SS 3.72. So I am on 4.4.2. Most people around here are using MK2 bootloaders. The ones with towelroot are NC5. Some even have NC2 from the OTA leak. lol sooo yeah.
What does AFAIK mean? never heard that term before? :silly:
aknotts415 said:
If you upgrade to kitkat via surges method before towelroot came out you kept your mk2 bookloader and had a 4.4.2 NC5 rom rooted running SS 3.72. So I am on 4.4.2. Most people around here are using MK2 bootloaders. The ones with towelroot are NC5. Some even have NC2 from the OTA leak. lol sooo yeah.
What does AFAIK mean? never heard that term before? :silly:
Click to expand...
Click to collapse
means "as far as i know" haha
have you done this method to get the GE rom with the 3.72 safestrap? or did you update to 3.75 first, because im currently running eclipse rom on 3.72
JeeperDon said:
Rick, if you stop at the 4.4.3 point, do the 'Known Issues" apply? GPE 4.4.3 is still way better than NC5.
Click to expand...
Click to collapse
Hard to fully answer your question as I did not stay on 4.4.3 for very long before I updated. For me the WiFi seemed to work fine and I did not have to soft reset. I still had to set SElinux to permissive to allow Chrome and Play store to function correctly. I did not test MMS in 4.4.3 so I am unsure if that worked or not(probably didn't). I also didn't fully test file transfers/MTP in 4.4.3 but I would assume they would not work as well reading the At&T thread. I'd say if 4.4.3 is working fine for you there is no real difference between that and 4.4.4 other than some security patches. Stick with it unless you like to live on the edge like me
aknotts415 said:
What does AFAIK mean? never heard that term before? :silly:
Click to expand...
Click to collapse
As Far As I Know
pfizzle said:
means "as far as i know" haha
have you done this method to get the GE rom with the 3.72 safestrap? or did you update to 3.75 first, because im currently running eclipse rom on 3.72
Click to expand...
Click to collapse
I think you and me are in the same boat. Our bootloaders arent NC5. Ur MJ7 and im MK2. Wonder how this would work for us. Never heard of SS3.75
aknotts415 said:
I think you and me are in the same boat. Our bootloaders arent NC5. Ur MJ7 and im MK2. Wonder how this would work for us. Never heard of SS3.75
Click to expand...
Click to collapse
I think i'll try out, I just downloaded the rom files. I'm going to try it with just staying on SS3.72 . I'll let you guys know what happens
pfizzle said:
I think i'll try out, I just downloaded the rom files. I'm going to try it with just staying on SS3.72 . I'll let you guys know what happens
Click to expand...
Click to collapse
Goodluck!
pfizzle said:
Awesome write up! I'm downloading the files now to try it out
If you don't mind, can you tell me your average screen on time in regards to battery life?
And just to verify, that mms fix only needs to be done and then it's perfect right?
Thanks!
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
I have not been using it long so hard to get an average screentime. I looked after the first full discharge and it was not quite 5 hours. Which is about what I was getting on stock. This may improve with time. I am not using any battery mods so with some tweaking you might be able to get more.
As far as the MMS fix that was the only thing I had to do as far as APN stuff.
But there are WiFi issues that get fixed with a soft reset. Also you need root to set SElinux to permissive. File transfers are not working right now for me either. Check http://forum.xda-developers.com/showthread.php?t=2767026&highlight=mk2 for details on the known issues that are not APN related. That's the actual ROM thread. All I did was tweak some stuff to work on verizon. No clue on the ultimate fix for the other issues.
For me these issues are fairly minor. I'm digging this ROM.
aknotts415 said:
Goodluck!
Click to expand...
Click to collapse
My phone booted!
I'm not sure if i still have root yet, im at the welcome screen right now, waiting a few minutes for it to settle before i start playing with 4.4.3.
I modified the procedure a little bit.. I started off on eclipse rom and SS3.72. I copied over the zip of the modified 4.4.3 rom with my apn file. I also had supersu2.01 already on my sd card, and teh wifi modules.
I booted safestrap, wiped the data,cache,dalvic,and system in the stock slot. then i installed the 4.4.3 rom, then without rebooting, i flashed the modules, and then flashed the supersu zip. then i hit reboot. my phone started up fine !
now i'm just waiting a few minutes before setting the 4.4.3 rom and then going to update to 4.4.4. I'll report back if i still have root or not
---------- Post added at 12:33 PM ---------- Previous post was at 12:18 PM ----------
UPDATE
I have root! my method worked without any problems
SAFE UP/DOWN GRADING THE EZ WAY
this is a continuation of my SAFE UP/DOWN GRADING TO 4.4.2 thread where I developed a few safe ways to upgrade/update/downgrade to various versions of 4.4. This thread will be aimed at Lollipop. I apologize for the wait I had this ready on the 29th but muniz beat me to the punch while I was still uploading by releasing his odex'd stock OC1 which apparently had broken wifi but is now fixed. however our methods are different and my method will allow you to very quickly upgrade to a Custom ROM 5.0 or fully downgrade back to 4.4.2 NK1-NC2.
Please Note for now I recommend not using Flashfire but if all else fails when attempting this method keep in mind you can use it as an alternative until you can get Safestrap installed again. Flashfire will let you use only your Android to upgrade nothing more is required which can be nice/necessary for those without PC available or a broken USB port.
Pre-Installation Requirements:
You'll need a PC with Windows, OSX or Linux unless opting to upgrade using Flashfire in which case just a phone and the app is required.
Download my UP/DOWN Grading Packa .rar which you unpack includes 4 tars for flashing in Odin
Download Odin 3.10.6 for Windows or dl JOdin if your using OSX or Linux
A Custom ROM or a Prerooted Stock ROM (I'm uploading a Deodex'd debloated stock ROM shortly otherwise you can use muniz's stock release too)
Newest Safestrap 3.75 A03, Towelroot v3+, SuperSU and Busybox apk files are handy to have available on SD CARD I've uploaded a zip containing these here.
If downgrading you'll need a custom ROM (like Echoe v49 VZW for 5.0) for that firmware or an Odin Stock image.
We'll basically be using the same workaround for safestrap that I had used pre 4.4.2 safestrap only in 5.0 and this time were going down to 4.4.2 instead of 4.3. That is in condensed form: were downgrading to 4.4.2 boot.img in order to use Safestrap then modifying ROM or installing a new ROM on Stock Slot then reupgrading boot.img to 5.0!
Steps to Upgrade from 4.4.2 Rooted with Safestrap:
1. Connect phone to PC. Open Odin on PC and boot phone into Safestrap.
2. Load CustomROM_Upgrade_Lollipop_VZW_wNK4-NoSys-gogolie.tar into Odin AP slot on PC. On your Phone in Safestrap install 5.01 TW ROM.
3. Restart Phone to Download Mode when installation of ROM is finished.
4. Now On PC press flash and flash the tar to phone.
5. Your Done. Odin will restart the phone and you'll have to skip through 3-4 Boot Screens for Safestrap before ROM will load. To avoid having to skip these screens after 1st boot install Safestrap and Busybox on phone. Open SS and Uninstall Recovery. Then the phone will boot into ROM without hesitation. However I wouldn't recommend this personally as you'll need SS installed and ready in order to modify the ROM in Safestrap.
From 5.0: Modify ROM / Install different ROM / Downgrading back to 4.4.2
1. Connect phone to PC. Open Odin on PC and in Safestrap's App press Reboot to Recovery only hold down Vol Down. This will bring phone into Download Mode 1st.
2. Load Custom_ROM_Downgrade_Lollipop_VZW_wNK4_Boot-only-gogolie.tar into Odin AP slot on PC and Press Flash.
3. Phone will restart to Safestrap if it doesn't it will display boot option for Safestrap which you should enter the recovery.
4. Now in Safestrap you're able to modify the currently installed 5.01 ROM or install a new ROM for either 5.0 or 4.4.2.
5. After install / modification you'll need to reupgrade if intending on running a 5.0 ROM or finish downgrading if youre reverting to a 4.4.2 ROM. Which means restart phone to Download Mode!
6. Back on your PC load Custom_ROM_Re-Upgrade_Lollipop_VZW_wNK4_Boot-only-gogolie.tar into AP Slot to reupgrade to 5.0 or load Custom_ROM_Re-Upgrade_Lollipop_VZW_wNK4_no-BL-gogolie.tar if you think you possibly need to rewrite the recovery-kernel-modem-etc to 5.0 otherwise VZW-I545VRUFNC2_FULL4.42-ODIN_UPGRADE-NO-PARTITIONS_989434_REV06_user_low_noship_MULTI_CERT.tar.tar.md5 or I545VRUFNK1_ALL_UPGRADES_W_NO_SYSTEM-CACHE-USER-PARTITIONS.taror similar modified Odin package can be flashed in Odin to finish Downgrading to any 4.4.2 Firmware.
7. There is no step 7, you were done at 6!
Good day!
- gogolie
v1-4-29-15
Please thank the OP if you're inclined.
Ask questions in thread those not answered can be assumed have been before and your just too lazy to search before asking which mean's I'll be to lazy to answer / search for you!
special thanks: dgutierrez04 for capture OTAs
2nd
as always,
enjoy
So @gigilie, I've already installed using @muniz_ri 's method and used FlashFire. Can I now install Safestrap and use it to install your rom for testing? (Omega v41 VZW)
Thanks gigilie, your method worked for me. I installed OC1 to my stock rom slot in Safestrap, and to be clear... Safestrap does not function after updating the rom. I expected that. Maybe soon we will have Safestrap back, or something like it.
However, I'm noticing after install that I have only 2 GB free out of 16 GB device memory. So I suspect that my former Slot 1 rom is still present and eating up lots of space. Any suggestions on how to reclaim the rom slot storage?
PMac10000 said:
Thanks gigilie, your method worked for me. I installed OC1 to my stock rom slot in Safestrap, and to be clear... Safestrap does not function after updating the rom. I expected that. Maybe soon we will have Safestrap back, or something like it.
However, I'm noticing after install that I have only 2 GB free out of 16 GB device memory. So I suspect that my former Slot 1 rom is still present and eating up lots of space. Any suggestions on how to reclaim the rom slot storage?
Click to expand...
Click to collapse
your former Slotted ROM is probably still intact and accessible. if you flash my downgrade pack in odin and restart you'll be able to access Safestrap. There you can either try and boot into the slot rom, delete the ROM or Modify any ROM you have installed on the Stock slot. Yes even 5.0 ROMs
rp1226 said:
So @gigilie, I've already installed using @muniz_ri 's method and used FlashFire. Can I now install Safestrap and use it to install your rom for testing? (Omega v41 VZW)
Click to expand...
Click to collapse
if your on stock u should be able to install su, busybox and then safestrap. reboot to safestrap but while the phone is restarting hold vol down and boot into download mode. flash the downgrade pack in the OP of my Safe UP and Down thread for 5.0 then install ROM.... I'd try Echoe v49 VZW posted in the Development section first as I know the ROM works flawlessly with this method then explore other custom ROM options after that!
Can I use this method from 4.2.2
Sent from my H7 using XDA Free mobile app
iansamz said:
Can I use this method from 4.2.2
Sent from my H7 using XDA Free mobile app
Click to expand...
Click to collapse
no sorry. what BL are you currently on i'll give you proper instructions
I don't know what BL means ...sorry am a newbie
Sent from my H7 using XDA Free mobile app
iansamz said:
I don't know what BL means ...sorry am a newbie
Sent from my H7 using XDA Free mobile app
Click to expand...
Click to collapse
BL is your bootloader
I've got Echoe Rom v49 installed via this method. Very nice so far... one exception: all outgoing SMS fails. Tried pulling battery/SIM/SD, many restarts, and safe mode. None of these fixed outgoing SMS.
First outgoing SMS after a restart takes about a minute to try... then fails. Subsequent outgoing SMS messages fail immediately. I can make calls and receive SMS, however. Any ideas?
Also, tried your suggestion to access Safestrap by downgrading with Odin using "Custom_ROM_Downgrade_NC5Lollipop_VZW_wNK4_Boot-only-gogolie.tar" in AP. This resulted in a bootloop. I got back up again by flashing "Custom_ROM_Re-Upgrade_Lollipop_VZW_wNK4_Boot-only-gogolie.tar"
Thanks
My outgoing sms is not working either. Able to receive sms and mms.
I can get into safestrap no problem.
So if I took the new OTA update to lollipop, can I use this to downgrade then root and update again with the root?
thank you!
For SMS, change the "SecMMs_Candy" and "SecTelephonyProvider_Candy" in /system/priv-app with correct permission.
Copy these 2 files from any known good VZW ROM.
For me, any international ROMI used had this issue and that's how I got the SMS and MMS to work.
meazz1 said:
For SMS, change the "SecMMs_Candy" and "SecTelephonyProvider_Candy" in /system/priv-app with correct permission.
Copy these 2 files from any known good VZW ROM.
For me, any international ROMI used had this issue and that's how I got the SMS and MMS to work.
Click to expand...
Click to collapse
Thanks for the feedback.
Couldn't find them in hyperdrive or kitpop. Muniz_ri's stock rooted oc1 didn't have a system folder to explore when I unzipped it. Grabbed them from a lollipop ROM in the s5 forum, replaced the respective files, and set permissions. After, messaging app wouldn't open.
If you took the OTA, then no way to do it. Sorry. Don't take the OTA.
notonmdk said:
Thanks for the feedback.
Couldn't find them in hyperdrive or kitpop. Muniz_ri's stock rooted oc1 didn't have a system folder to explore when I unzipped it. Grabbed them from a lollipop ROM in the s5 forum, replaced the respective files, and set permissions. After, messaging app wouldn't open.
Click to expand...
Click to collapse
Try wiping the cache for message in application manager and reboot.
Should I uninstall my Xposed Framework and all the modules before updating? And why should I not use the FlashFire method?
meazz1 said:
Try wiping the cache for message in application manager and reboot.
Click to expand...
Click to collapse
Didn't change anything for me.
In addition to the outgoing SMS problem, I'm noticing my phone running hot with Echoe rom v49... battery life is about half what it was before. Exchange service seems to be a big culprit.
So from what I am reading, this is aimed at those who took the 5.0 OTA correct?
Just bought a refurbished Galaxy S4 as my other phone was stolen. I am on Verizon. My S4 looks brand new and it's running 4.4.2! I would love to root and then probably flash to cm12. How would I root right now? The s4 has been out for some time and maybe the threads are old. Do I root before activating?
Build kot49h.i545vrufnc5
Please help. I have been without root on another phone for over a year. You can imagine my pain.
NO CM12. Nc5 does not have an unlocked bootloader.
As far as rootz towelroot still works. 1 click apk by geohot.
nc5
Tried the towelroot apk and it does not root, work. i get this message
"Only the Galaxy S4 active is currently supported. If you see this error and you think you have the right phone, email geohot at... i know i have an S4 but cant tell if it is an s4 Active. i just left verizon with an activated phone and it is already trying to push an update. I dont know if i should or what to do.
bbiigg said:
Tried the towelroot apk and it does not root, work. i get this message
"Only the Galaxy S4 active is currently supported. If you see this error and you think you have the right phone, email geohot at... i know i have an S4 but cant tell if it is an s4 Active. i just left verizon with an activated phone and it is already trying to push an update. I dont know if i should or what to do.
Click to expand...
Click to collapse
Make sure you are on nc5. Screenshot your settings if you want.
Next, make sure you got it from the real site... That doesn't sound like the right one.
If you have physical menu and back buttons, that's the s4 active. It's ATT only, in which case, this is the wrong device.
NC5
I just gave it a go again after rebooting and it worked. I have root. Now I need to figure out how to remove all this bloated crap. Any ideas. Wish I could flash a custom though. I'm still getting this annoying update window.
bbiigg said:
I just gave it a go again after rebooting and it worked. I have root. Now I need to figure out how to remove all this bloated crap. Any ideas. Wish I could flash a custom though. I'm still getting this annoying update window.
Click to expand...
Click to collapse
There are some debloater scripts on general forum, but I think the best choise to debloat is installing some file explorer (E.G. MiXplorer) and go to /system/app and /system/priv-app and delete everything you don't want. If you don't know what apps to delete This guide it's great
Btw, if you want a rom you can choose any 4.4.2 or newer, don't try any lower android version rom. To install custom roms on this device you can use Flashfire or Safestrap(only for kitkat or lower), I suggest you to use safestrap if you're on kitkat (keep in mind that rom slots doesn't work, you have to flash in stock slot any rom).
oops
I had a rom Hyperdrive installed and it was running well for a minute but I just had to try another rom "Galaxy S6 Port by Albe95"! Now i can make calls and recieve texts but not send them. i have no internet unless its wifi. Im not rooted and Towelroot wont work. No recovery available now and my Android Version is 5.0.2. Im really stuck and nervous. I need my phone for work. Any ideas?
bbiigg said:
I had a rom Hyperdrive installed and it was running well for a minute but I just had to try another rom "Galaxy S6 Port by Albe95"! Now i can make calls and recieve texts but not send them. i have no internet unless its wifi. Im not rooted and Towelroot wont work. No recovery available now and my Android Version is 5.0.2. Im really stuck and nervous. I need my phone for work. Any ideas?
Click to expand...
Click to collapse
No worries. I think you have to flash the OC1 modems for lollipop roms to work when coming from kk. Check your bootloader version, if it is a NC[place number here] you can odin back to the right update and use the flashfire or safestrap to use the installation instructions in the second post of the ROM forum. Your other option is to stay and flash modems. This is how to do it:
If you lost your recovery:
1)Get root (NOTE: you don't need to do the kernel flashing part because you are already on of1
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
http://forum.xda-developers.com/galaxy-s4-verizon/general/samsung-s4-i545-verizon-of1-root-t3254434
2)Get Flashfire
3)Flash this (fist link) if it fails to solve the problem this
If this doesn't solve your problem and you can't go back to kitkat, you should odin OC1 and root. All credit goes to their respective contributors. Hope I helped
S4 flashing
whowatchlist said:
No worries. I think you have to flash the OC1 modems for lollipop roms to work when coming from kk. Check your bootloader version, if it is a NC[place number here] you can odin back to the right update and use the flashfire or safestrap to use the installation instructions in the second post of the ROM forum. Your other option is to stay and flash modems. This is how to do it:
If you lost your recovery:
1)Get root (NOTE: you don't need to do the kernel flashing part because you are already on of1
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
http://forum.xda-developers.com/galaxy-s4-verizon/general/samsung-s4-i545-verizon-of1-root-t3254434
2)Get Flashfire
3)Flash this (fist link) if it fails to solve the problem this
If this doesn't solve your problem and you can't go back to kitkat, you should odin OC1 and root. All credit goes to their respective contributors. Hope I helped
Click to expand...
Click to collapse
I tried the 2nd option of rooting and it didn't work. I'm still on oc1. How would I Odin back or what files would I use? It's getting confusing.