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
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
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
[Q&A] Super6 - v1.89 - all s4 safe - fast s6 everything, ur new favorite rom is here
Q&A for Super6 - v1.89 - all s4 safe - fast s6 everything, ur new favorite rom is here.
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Super6 - v1.89 - all s4 safe - fast s6 everything, ur new favorite rom is here.. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
gigilie said:
not much to the scripts it uses Dan's Loki scripts to determine if the phone on MDK then flashes the lokied kernel and modem otherwise flashes all in safestrap. no Odin is needed.
@XxD34THxX weird you lost root? and your having issues with the settings etc FC? not the case on my end. did you flash anything else with the ROM? theres a script in the installer that flashes SuperSu literally the exact same way as flashing Chain's SuperSu.zip after installing a ROM. I started infusing the 2 long ago back on 4.4.2 now every dev uses this technique. No reason why binaries shouldnt install and the only FC in Settings should come from trying to visit the Theme Store
Can some people please verify this to be true for all? definately not the way it works on my S4. what about MMS and Phone with VZW service that was one thing I wasn't able to test
Click to expand...
Click to collapse
I don't have any of the issues stated root and settings work fine the only force closes i have are when I tried to launch the theme store like you said. I love the rom I hope you guys can get the themes working tho incredibly smooth and fast good battery life used echoe v49 as my DD till this came out and I love this rom so much it's my new DD. No WiFi issues either which was surprising compared to other lollipop roms! Thanks for the hard work! I'm also interested in testing new builds before release so I can report bugs that may arise!
first off i love what youve done so far. i have tried to clean install this rom on my verizon I545 running NC5 several times today, everytime i lose root. MMS works if i change my text app to Google Messenger. i also can not get Google Chrome to work either. wifi and phone calls work in and out but i also lose data. my procedures consist of odin back to stock, root, install safestrap, reboot into safestrap and install. i do not install anything else during installation. hope to hear what others have done to make this work. thanks in advance...
Root Gone, No Data or Outgoing SMS
So I came from OC1 deodexed. Used FlashFire and wipped everything before install v1.89.
It is fast, but can't send SMS, and not getting 4g notification. I get bars, just no data.
And Root appears gone.
steepdgaf said:
first off i love what youve done so far. i have tried to clean install this rom on my verizon I545 running NC5 several times today, everytime i lose root. MMS works if i change my text app to Google Messenger. i also can not get Google Chrome to work either. wifi and phone calls work in and out but i also lose data. my procedures consist of odin back to stock, root, install safestrap, reboot into safestrap and install. i do not install anything else during installation. hope to hear what others have done to make this work. thanks in advance...
Click to expand...
Click to collapse
I would try flashing his rom echoe v49 that's what I was on then I installed safestrap 3.72 and used the nc2 flasher apk he makes to boot into safestrap on lollipop run a factory reset and flash the rom I didn't wipe system just factory reset and flashed with no problems at all everything works fine for me.
dabigbmc said:
I would try flashing his rom echoe v49 that's what I was on then I installed safestrap 3.72 and used the nc2 flasher apk he makes to boot into safestrap on lollipop run a factory reset and flash the rom I didn't wipe system just factory reset and flashed with no problems at all everything works fine for me.
Click to expand...
Click to collapse
thanks, i will give that a try when i get home from work and report back my progress.
gave it a try,everything went smooth but same thing i had before, no root or messaging. my CSC in phone info is TGY, is that correct?
steepdgaf said:
thanks, i will give that a try when i get home from work and report back my progress.
gave it a try,everything went smooth but same thing i had before, no root or messaging. my CSC in phone info is TGY, is that correct?
Click to expand...
Click to collapse
I'm not sure my root is gone to I don't use many root apps so I just assumed it worked but no go as far as texting goes try a third party app I use textra.
Nevermind this
How can we root the rom? Plzz help
Likkleskip said:
How can we root the rom? Plzz help
Click to expand...
Click to collapse
Yayyyyy I found a fix go into SuperSu after normal rom install don't install SuperSu in recovery for root it doesn't always fix the problem after the rom is flashed go into SuperSu and go to settings and go down to where it says install to system and it will go through and after a reboot my root worked
Just wanted to report that loosing root seems to be fixed by just telling SuperSU to grant by default and if you try to open them the SystemUI crashes and if you change the swipe effect to none the SystemUI constantly crashes.
I like this ROM. But I wish the font was better. Even using font changer, the font gets wacky.
Sent from my SCH-I545 using Tapatalk
Sigh....
Installed last night and have many issues:
Came from rooted NC5 with safestrap
now i have no root (it updated to OC1) and lost safestrap
wifi works but no mobile data (no connection except for calling)
I did a factory reset and still same issues.
Reegs said:
Installed last night and have many issues:
Came from rooted NC5 with safestrap
now i have no root (it updated to OC1) and lost safestrap
wifi works but no mobile data (no connection except for calling)
I did a factory reset and still same issues.
Click to expand...
Click to collapse
So, root you have. Just go to superuser app and instead of asking the app to prompt every time an app has to use root to grant. This will allow for root to work.
I'm still waiting for a fix for the mobile data.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
rp1226 said:
So, root you have. Just go to superuser app and instead of asking the app to prompt every time an app has to use root to grant. This will allow for root to work.
I'm still waiting for a fix for the mobile data.
Click to expand...
Click to collapse
I think a lot of people will like this rom! It's good to show some love to @gigilie for keeping the S4 up and running!
same problem with safestrap
champdr0id said:
I tried this a few days back and my wifi wouldn't work. Then I had trouble getting back into safestrap. Took a few days to get back in, and I got it working last night all proper. I can't wait to mess with it after work tonight. Everything I did play with was total butter though. I'm excited.
Click to expand...
Click to collapse
how did you get into safestrap? recovery wont boot... before updating busybox i couldn't even see the splash screen. i cant use data call or send messages and there isn't an APN option with your rom, at least not for me so i cant edit the values manually. i have Verizon service and want to try your fixes but im unable to boot into safestraps recovery. when i click recovery it just boots lolipop haha
Did you reinstall safestrap?
Install busybox and then install safe strap.
Run NC2 flasher and it will take you to safestrap.
Sent from my SCH-I545 using Tapatalk
rp1226 said:
Did you reinstall safestrap?
Install busybox and then install safe strap.
Run NC2 flasher and it will take you to safestrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yes i did all that just not the nc2 thing i was actually just reading up on it hahaha.... slight confusion, i was trying to find a video as not sure what kernel they are talking about dont want to do the wrong thing as im on oc1 with the super6 rom but its bootloader is nk4.... so what do i need exactly in order to keep things running smoothly as in the warning for the app it says you have to flash custom rom upgrade odin tar with odin. it also says it will flash nc1 then i have to flash either nc4 or oc1 when im done.... is this before rebooting to lolipop or is this after im done using safestrap to try the fixes that were uploaded for data messaging and phone?
So once you use the nc2flasher you will have the nc2 kernel installed and it will let you boot into safestrap. To go back to oc1 kernel, there is a flashable kernel in one of the topics about booting into safestrap in the general section.
Sent from my SCH-I545 using Tapatalk
rp1226 said:
So once you use the nc2flasher you will have the nc2 kernel installed and it will let you boot into safestrap. To go back to oc1 kernel, there is a flashable kernel in one of the topics about booting into safestrap in the general section.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
ok so just to be clear i am flashing the oc1 kernel after im finished with updates in safestrap. i use safestrap to flash oc1 kernel zip..... and when i do this i will not be able to use safestrap again unless i keep doing the nc2 work around correct? and thank you for your help it is much appreciated
DeathsAsylum said:
ok so just to be clear i am flashing the oc1 kernel after im finished with updates in safestrap. i use safestrap to flash oc1 kernel zip..... and when i do this i will not be able to use safestrap again unless i keep doing the nc2 work around correct? and thank you for your help it is much appreciated
Click to expand...
Click to collapse
Yup.
http://forum.xda-developers.com/showthread.php?t=3120483
[GUIDE] Safestrap access WITHOUT Odin
Sent from my SCH-I545 using Tapatalk
Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!