Related
I need some assistance.
First off, I AM rooted, with TWRP recovery.
I had some apps frozen/disabled, but have defrosted/enabled all of them.
I have flashed some mods (remove ongoing wifi notif, different boot animation, volume hack).
Other than that, I am completely stock.
I currently have the VRUAMDK build, but want to update to the newest October firmware (and either retain root, or re-root with the new methods).
I'm not able to get the OTA update to load. Every time I try, it fails (and also mentions that no MD5 is found). Is this just because I'm rooted, or is something else causing this? I was under the impression I could take the OTA (and probably lose root) and it would flash.
Would flashing the update via Odin fix this issue? I currently don't have a working Windows machine, so I'm stuck with my Mac right now.
Any help is greatly appreciated. As you can tell, I'm somewhat inexperienced with specifics, but I am pretty comfortable with rooting (my third rooted device now).
Dont get the ota update you dont want it, it locks bootloader so you cant put roms or anything id be more willing to trade you my phone that has it for your mdk yours is better.
Wait for a rom to come out with the updates or you can get the modem to flash for it its floating around here its had mixed reviews as far as helping.
Sent from my SCH-I545 using xda app-developers app
fghtffyrdmns said:
I need some assistance.
First off, I AM rooted, with TWRP recovery.
I had some apps frozen/disabled, but have defrosted/enabled all of them.
I have flashed some mods (remove ongoing wifi notif, different boot animation, volume hack).
Other than that, I am completely stock.
I currently have the VRUAMDK build, but want to update to the newest October firmware (and either retain root, or re-root with the new methods).
I'm not able to get the OTA update to load. Every time I try, it fails (and also mentions that no MD5 is found). Is this just because I'm rooted, or is something else causing this? I was under the impression I could take the OTA (and probably lose root) and it would flash.
Would flashing the update via Odin fix this issue? I currently don't have a working Windows machine, so I'm stuck with my Mac right now.
Any help is greatly appreciated. As you can tell, I'm somewhat inexperienced with specifics, but I am pretty comfortable with rooting (my third rooted device now).
Click to expand...
Click to collapse
You could use odin to flash either the newest firmware or reflash mdk and then take the update.
Edit:
Just noticed your on a mac. Heimdall is like odin and its mac compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
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
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
madtomatoes said:
Hi All,
I picked up an MI1 GS4 a month ago and after a few nights of scrolling through the forums I was able to get HD 10.2 loaded onto my phone via Safestrap. During the root process, I got a little bit a head of myself and flashed a custom recovery. After some research (and a presumed brick scare) I found that there is no way to get CWM recovery on the phone. While it's a major disappointment, it is what it is. So I have two questions:
So right now, my phone doesnt have a recovery and if I try to boot into it, it will go into Odin mode and give me some sort of an error. I assume I need to flash a new recovery through Odin, but am wondering if someone could point me in the direction of the correct file.
Is MJ7 the latest OTA from VZW? Should I wipe my device completely, go back to stock, and take the latest OTA? From what I am gathering, safestap is now working on MJ7, but I want to be sure that is what I will get to if I take the OTA. If I do want to take the OTA, how would I go about doing this and is the problem listed above an issue?
Thanks!
Click to expand...
Click to collapse
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Your only recourse is odin the full wipe stock image back and start over.
I suggest a thorough reading of the forum threads here first so you know better what to do.
I have a guide in the general forum here that lists steps to go from ME7 to MJ7 and root, install safestrap 3.65 and HD11....I'm not sure how it would play with your MI1 base phone so proceed at your own risk
decaturbob said:
safestrap is a recovery of sorts, so what you are saying, you rooted, installed safestrap, installed HD10.2 than installed a recovery on top of that like CWM? So you soft bricked your phone?
Click to expand...
Click to collapse
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
madtomatoes said:
The other way around. I first rooted and attempted to install CWM. After that failed, I read further and discoved that only MDK roms are truly unlocked. From that point, I installed safestrap and HD. My phone is functional right now, I just have no way of getting into the stock recovery.
It's my understanding that I will need to use Odin to flash the stock MI1 image. I just want to confirm what happens from there. After flashing the stock image, I will be stock MI1, unrooted, with the opportunity to OTA to MJ7 (?). From that point, I'll take the OTA, re-root, reinstall safestrap, and finally HD11/12. Is all of this correct?
Thanks
Click to expand...
Click to collapse
that sounds about right. When you do HD12, be sure you have the safestrap version....
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.
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Sent from my SCH-I545
SnyderGuy said:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
Sent from my SCH-I545
Click to expand...
Click to collapse
I am using an MDK S4.
I can bit to room, but cannot reboot to recovery.
Corrupted recovery after update via TWRP app.
How exactly, do I re-image my device back to MDK?
Do I use this stock MDK ROM? http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
Do I put it in the BL or AP box in ODIN?
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
XxD34THxX said:
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
Click to expand...
Click to collapse
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
pizza_pablo said:
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
Click to expand...
Click to collapse
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
XxD34THxX said:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
Click to expand...
Click to collapse
That may have been the case, since my connection was weak.
I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.
Here I go....
Well....I tried these to .tar files with no luck:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
https://www.androidfilehost.com/?fid=22979706399752783
I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Now, I no longer have the option to cancel Download Mode and bot ROM.
I didn't want to do anything in Kies, for fear of taking an OTA.
Do I have any options?
Even just taking an OTA and selling a former MDK treasure?
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.
Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.
What do you think may have caused the bootloader to change?
At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.
Thanks, for your assistance, as I am at a loss, at this point!
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
I used the link file, from my last post.
After I unzip it, delete the " .gz "
Got it. Thanks, again!
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.
It was not zipped, either.
On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .
What could ODIN do with this?
The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .
Do you have any other suggestions,please?
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.
You're a champ!
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?
ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.
I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.
Giving up for the night.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....
The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.
I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.
What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.
This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.
I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.
Sorry if rambling, just trying to pass as many details and thoughts as possible.
Do I have any options, now?
I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"
I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?
Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
XxD34THxX said:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
Click to expand...
Click to collapse
No need to apologize! You have helped all you can. I appreciate it greatly!
I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.
I wonder if I'll get in hot water for starting a new thread.....