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.....
Related
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....
Hi,
I recently J Tagged my galaxy S4 Verizon and it came back to me with these specs:
ME7 stock Rooted Rom
Android 4.2.2
Base band
I545VRUAME7
Safe Strap 3.64 TWPR v 2.6.3.1
Hyperdrive ROM ver 10
I tried to use ODIN to re-flash to stock ROM VRUAMDK_Nowipe_tar_md5. So that I may be able to update to the new Hyperdriver ROM and it didn't turn out as planned.
HERE IS WHAT I DID:
I just turned off the phone.
Installed Samsung drivers on PC
Down loaded the TAR file loaded it in to ODIN and hit PDA and let it do its thing.
I've tried this several times and every times it ends in a FAIL.
I can put the phone into download mode but that it nothing past that.
Some times I get the message to connect it to KIES as it need missing files. I did that too and KIES takes forever to search for the S4 and cannot find it.
The drivers are installed the PC recognizes the phone. But KIES does not.
The guy who J tagged it said that he froze the system apk SDM 1.0 to stop OTA.
Does any one know how to help me get out of this predicament? I would really appreciate the help and guidance.
Thanks in advance!
radiskull1973 said:
Hi,
I recently J Tagged my galaxy S4 Verizon and it came back to me with these specs:
ME7 stock Rooted Rom
Android 4.2.2
Base band
I545VRUAME7
Safe Strap 3.64 TWPR v 2.6.3.1
Hyperdrive ROM ver 10
I tried to use ODIN to re-flash to stock ROM VRUAMDK_Nowipe_tar_md5. So that I may be able to update to the new Hyperdriver ROM and it didn't turn out as planned.
HERE IS WHAT I DID:
I just turned off the phone.
Installed Samsung drivers on PC
Down loaded the TAR file loaded it in to ODIN and hit PDA and let it do its thing.
I've tried this several times and every times it ends in a FAIL.
I can put the phone into download mode but that it nothing past that.
Some times I get the message to connect it to KIES as it need missing files. I did that too and KIES takes forever to search for the S4 and cannot find it.
The drivers are installed the PC recognizes the phone. But KIES does not.
The guy who J tagged it said that he froze the system apk SDM 1.0 to stop OTA.
Does any one know how to help me get out of this predicament? I would really appreciate the help and guidance.
Thanks in advance!
Click to expand...
Click to collapse
You can't revert to older firmware. It's been posted over and over. If you were on ME7 then you have to get a ME7 Tar file and use Odin to flash that. After that, if you want Hyperdrive RLS 12, you would have to update to MJ7 (or MK2), then install Safestrap 3.70.
You have a lot of reading to do. I suggest you take your time and do your research.
Sent from my NCC 1701 Using Tapatalk 4
ME7 TAR
riker147 said:
You can't revert to older firmware. It's been posted over and over. If you were on ME7 then you have to get a ME7 Tar file and use Odin to flash that. After that, if you want Hyperdrive RLS 12, you would have to update to MJ7 (or MK2), then install Safestrap 3.70.
You have a lot of reading to do. I suggest you take your time and do your research.
Sent from my NCC 1701 Using Tapatalk 4
Click to expand...
Click to collapse
Hey thanks for the reply, you're right I should have done some more reading. I managed to start the phone but it's running real sluggish. I've done several searches for a ME7 TAR file to use with ODIN but I can't fine any thing. You happen to know of a link that could help me out. Appreciate it.
Sorry for the bother!
radiskull1973 said:
Hey thanks for the reply, you're right I should have done some more reading. I managed to start the phone but it's running real sluggish. I've done several searches for a ME7 TAR file to use with ODIN but I can't fine any thing. You happen to know of a link that could help me out. Appreciate it.
Sorry for the bother!
Click to expand...
Click to collapse
Quick search found this http://forum.xda-developers.com/showthread.php?t=2301259. Take your time and read everything before you jump in. Good luck.
Should I OTA now??
riker147 said:
Quick search found this http://forum.xda-developers.com/showthread.php?t=2301259. Take your time and read everything before you jump in. Good luck.
Click to expand...
Click to collapse
Thanks so much for the help and the links they really saved the day. I managed to follow instruction closely and installed stock ME7 through ODIN and rooted the phone.
Should I go ahead and do a OTA update or will lock me down and keep me from installing custom ROM?
radiskull1973 said:
Thanks so much for the help and the links they really saved the day. I managed to follow instruction closely and installed stock ME7 through ODIN and rooted the phone.
Should I go ahead and do a OTA update or will lock me down and keep me from installing custom ROM?
Click to expand...
Click to collapse
You can currently root any of the I545 versions, so updating is not prohibited. You'll need to decide if it's worthwhile.
None of the versions later than MDK will allow you to install a custom recovery. Also, Custom ROMs are limited and installed using Safestrap, only Touchwiz compatible. No AOSP or CM.
What exactly does j-tag do on an S4?
J Tag
Schoat333 said:
What exactly does j-tag do on an S4?
Click to expand...
Click to collapse
I just going to repeat things like a parrot because I'm new to all of this. I flashed the wrong ROM, meaning ROM meant for another model other than my phone which is a SCH-I545. That ruins the EMMC chip that has all the booting up information. At this point the phone is HARD BRICKED. In J TAG they use a certain device after disassembling the phone and re install necessary software to bring it back to life and save the phone, so you don't have to throw it away. Man folks of Ebay offer this service for around $30 not a bad deal. Made my phone run pretty good as new.
After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
decaturbob said:
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
apefist said:
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
Click to expand...
Click to collapse
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
riker147 said:
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
Click to expand...
Click to collapse
OK, well then my current problem is even though I have the safestrap app installed, and the program reports safestrap recovery as being installed, I can't access it. There is no safe strap screen while booting or button options, and even if I do the forced boot into recovery (press power+vol up+home at the same time and hold until you see the "Recovery Booting" message) it just boots to the normal phone every time.
Also worth noting is for every boot, no matter how i start it, it says "Recovery booting" at the top, but never boots into recovery. I have tried uninstalling safe strap recovery through the safe strap app and re-installing but it is the same thing.
apefist said:
After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Click to expand...
Click to collapse
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
k1mu said:
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
Click to expand...
Click to collapse
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
apefist said:
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
Click to expand...
Click to collapse
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
decaturbob said:
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
apefist said:
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
Click to expand...
Click to collapse
ok buddy you want to upgrade i take it?
click on the thread in my signature and download the 1st file listed called the COMPLETE PACKAGE it has everything you need.
you'll start tho by reflashing MK2 system through Odin then rerooting via Saferoot then reinstall Safestrap. Then the 4.4.2 ROM you want to use then reboot to Odin/Download mode and flash any of my NC2/NC5 1 File Upgrade packages. This is the easiest and most simplistic way to help you get to where you want to go. This will also keep your bootloaders at MK2 and your KNOX intact at 0x0! THE COMPLETE PACKAGE has all the modules, safestrap, supersu ect then if you have any questions the guys or me in the thread will help u. altho if you really do have CM running on your phone take screenshots I've tried porting to work with 4.3 and altho i can get two AOSP roms working I've never gotten close with CM it needs a custom kernel which is something we cannot use with our locked bootloader. only AOSP/GE Roms that will work for 4.4.2 or 4.3 are ones that are compatible with the stock 4.3 or 4.4.2 kernels theres a thread in the development section for that subject as well.
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.
Warning: VRUGOC1 is impervious to previous bootloader bypass methods, and cannot be downgraded. Proceed with caution.
I managed to hose my phone while rooting it somehow, so I had to track down the factory image for I545VRUGOC1 / I545VZWGOC1. To actually flash it, I had to use Odin 3.10.6 rather than 3.09 for some reason, which is available in the links below. I also replaced Odin's SS_DL.dll with the one from the zip that contains the tar file, but I'm not sure if that was necessary.
Hope this helps anyone else from who's stuck
TAR
https://mega.nz/#!T0tTDZKA!tIw4ebWEWhsTJWTbyWVx9e07aSBSc_1_Xm2mWWkdu8I
Mirror: http://upple.it/4b1331ec4f4dd04e/VZW-I545VRUGOC1-20150502144520.zip
Slower / crappier mirrors I found in case the above doesn't work:
http://rapidgator.net/file/6f4fd8106796c1bba92dd20a7b5a5c51
http://uploaded.net/file/zcbqwyz5
Odin
http://odindownload.com/download/Odin3_v3.10.6.zip
Mirror: https://mega.nz/#!qh9UTJ6Q!gLDkj2xwXRb8Wa2YTbPODpdrhqowK-s6eZjXI_bTrhQ
kd- said:
Warning: VRUGOC1 is impervious to previous bootloader bypass methods. Proceed with caution.
Click to expand...
Click to collapse
Thanks! I found the file here too:
http://d-h.st/LNQV
My question is, I have a Kitkat Verizon phone here, I assume upgrading it restricts custom ROMs that can be loaded to it?
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
kd- said:
Thanks for another mirror - the more the better
Yes, I don't think any current custom ROMs work with the VRUGOC1 bootloader, etc. FlashFire has worked for a couple experiments I've run (flashing wireless hotspot fix, for example), but I'm hesitant to flash anything more substantial. I have not tried SafeStrap but I have not seen anything about it working yet.
Click to expand...
Click to collapse
muniz_ri has posted a stock, de-odexed (and odexed, too of course) that should work with OC1 bootloader (it doesn't have a bootloader in it, so the current bootloader should stay)
http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
I haven't installed flashfire yet, but i am on OC1 and already went through the rooting process.
Does this boot if I flash it and the NK4 bootloader?
Oishikatta said:
Does this boot if I flash it and the NK4 bootloader?
Click to expand...
Click to collapse
muniz_ri has a tar with the oc1 build and the nk4 bootloader, look in either general or Android development
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
XxD34THxX said:
^^
It's in android development. Only two or three ROMs work on OC1(at most). I only know of one confirmed.
Click to expand...
Click to collapse
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
skepticmisfit said:
muniz has a stock rooted ROM for the oc1 people, which makes sense if you're going from stock. you can flash deodexed ROM and be able to use xposed framework
Click to expand...
Click to collapse
Yep, it works just fine, flashed with FlashFire.
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api&pli=1 I found it here two
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
bayron_olaff said:
Can somebody please help me? First, my phone is locked and I was in NK1, so I decided to flash OC1 by the flashfire method (I don't remember who's the author of the topic), everything went fine and I started to use lollipop, but then I was about to sell my phone and I went to settings, then factory reset and the phone restarted, wiped data and cache by itself and then turned on, I thought everything was ok, but then it just stayed in the samsung's wizard screen, it never passed from that screen. So, I decided to manually enter recovery and do a factory reset again, but the result was the same. In order to unbrick the phone I had to use odin and install the NC5 original firmware .
So, my question is, If I want to install lollipop and I don't care to stay with an unlockable bootloader I justt need to use this Firmware and install it through odin? Or do I need to have an specific firmware (e.g nc5, nk1) and unlocked bootloader?
Click to expand...
Click to collapse
Yes, that sounds correct. Personally, I wouldn't flash the OC1 factory image unless you have to - I'd flash the NK1 image, which should reset everything, then upgrade to Lollipop using a method that doesn't upgrade the bootloader so whoever gets the phone next can downgrade if they want to.
Can anyone confirm the mega link is a no-wipe oc1 package?
persdata.img doesnt appear in it just making sure.
Edit : been tested it appears to be a no wipe Odin package