I rooted my verizon Samsung Galaxy S4 when I first got it with no problem.
A week ago I was misled by Verizon's sucky PC software to "repair" my phone. I inadvertently wiped the whole thing and it was returned to factory preset status, so the root was gone.
Now I'm trying to re-root the phone, but with no luck. I boot my phone into download mode fine. But everytime I try to get Odin to flash the "SCH-I545_MD2_423399_Kernel.tar.md5" rom, it fails at the first step! It just says "Fail", and that's the end of it.
I'm clueless about what to do. I've tried different USB cables, restarted both devices multiple times. I even tried unpacking the tar file before opening Odin.
Can anyone advise? I'm out of ideas.
Kevin
kevlut said:
I rooted my verizon Samsung Galaxy S4 when I first got it with no problem.
A week ago I was misled by Verizon's sucky PC software to "repair" my phone. I inadvertently wiped the whole thing and it was returned to factory preset status, so the root was gone.
Now I'm trying to re-root the phone, but with no luck. I boot my phone into download mode fine. But everytime I try to get Odin to flash the "SCH-I545_MD2_423399_Kernel.tar.md5" rom, it fails at the first step! It just says "Fail", and that's the end of it.
I'm clueless about what to do. I've tried different USB cables, restarted both devices multiple times. I even tried unpacking the tar file before opening Odin.
Can anyone advise? I'm out of ideas.
Kevin
Click to expand...
Click to collapse
Unfortunately, it seems as if you took the OTA Update, at this time I don't know if we have root abilities, or Loki/unlocked bootloader hack...
Many people have done this, you're not alone. Have patience, the great team of dev that are in this community are working on it.
Best of kick
Sent from my SCH-I545 using Tapatalk 2
Try downloading the file from internet explorer if u havent already
Sent from my SCH-I545 using Tapatalk 4 Beta
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
zomsoc said:
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
Click to expand...
Click to collapse
Find out what odin is. Then..
Google "odin emergency tar (your build number here)" or something to that effect.
If you don't know your build number then you have some more research to do. Good luck.
I'd recommend using the Verizon update assistant. Much easier, but takes about half an hour to do:
1) Connect phone to PC using USB cord
2) When prompted for what action to take when this device is connected, select Verizon update assistant. Installation will take a few minutes.
3) Start the update assistant and confirm that you want to update the phone. The update will take a few minutes.
When the update is complete, you should have the most current update (MK2), and no root access. Should you need root again, try Saferoot - it's quick and easy:
http://forum.xda-developers.com/showthread.php?t=2565758
Thanks for pointing me in the right direction guys, I'll do some more research into both and report back soon.
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
zomsoc said:
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
Click to expand...
Click to collapse
You need to flash the same stock image as what was previously on your phone.
If you don't know what version you were on previously, flash MJ7 or MK2.
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.....
So earlier today I had some time on my hands and decided to try and root my Rogers Note Edge phone. I failed miserably and now my phone does not seem to have an operating system and continuously restarts. I tried to restore it back to its factory settings, via Odin and Factory but with no success. Can anyone help me?
Not without more details.
What build number of the software were you on?
Which method to root did you use?
What else did you do to it (just rooting should not remove the operating system)?
What build number of the software did you try to reload with Odin?
Did the Odin flash work or did it fail with an error of some type?
i used everything in this guide http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
-Odin3 v3.07
-twrp v2.8.6
odin failed and then passed twrp, on reboot my phone died. once charged it kept rebooting over and over. I can still get into download and recovery mode again but now twrp says i have no os and I also noticed while it charges it says "kernel is not seandroid enforcing", "set warranty bit:kernel"
You said that you used everything in that guide, but you made no mention of trying to load a rom. That's the next step... If you have no OS, you've got 2 choices. A rom or reload stock firmware via Odin.
Thanks for the support. I made it back to my stock os through smart switch, finally! But Im no longer rooted and Knox is still 0x1. I plan on trying again, should i use the same guide? Just wondering because it seems more based for American carriers , and I'm in Canada.
That guide is for Tmobile version, not yours. That's why it wasn't working right. I'm not aware of a method to reset the Knox counter. You can just install TWRP and use that to install SuperSU from Chainfire for root access.
Well if I can get root tonight I'll let ya know if triangleaway works for Knox reset. Had it recommended from a friend, guess you can get it off the play store.