Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Squerl101 said:
Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Click to expand...
Click to collapse
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
gnubian said:
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
Click to expand...
Click to collapse
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Squerl101 said:
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Click to expand...
Click to collapse
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
decaturbob said:
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
That's your problem. You can't revert to an older build. You have to flash the build you were originally on.
Sent from my NCC 1701 using Tapatalk 4
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
There's a guide telling you to flash down from mj7??
I don't think so..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
Can't flash backwards...bootloader changes from 1 version to the next makes impossible
safestrap enabled, Hyperdrive driven
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Squerl101 said:
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Click to expand...
Click to collapse
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
decaturbob said:
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Squerl101 said:
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Click to expand...
Click to collapse
Correct.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
Correct.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Squerl101 said:
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Click to expand...
Click to collapse
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
tech_head said:
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
Click to expand...
Click to collapse
I would, but I have been downloading MJ7 for about an hour (slow internet ) so it's probably not worth starting over. Hopefully everything works out!
Cool, the problem no longer exists. It took about 5 minutes to flash, and after that, it started working perfectly again. Thank you everyone for your help!
Sent from my SCH-I545 using Tapatalk
Have you tried using Kies to fix your phone?
Sent from my SCH-I545 using Tapatalk
Related
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
HerdOn said:
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
Click to expand...
Click to collapse
Have you tried a different USB cable and/or running odin as an administrator?
BladeRunner said:
Have you tried a different USB cable and/or running odin as an administrator?
Click to expand...
Click to collapse
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
HerdOn said:
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
Click to expand...
Click to collapse
which Verizon release are you on VRUAMDK or VRUAME7?
BladeRunner said:
which Verizon release are you on VRUAMDK or ?
Click to expand...
Click to collapse
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
HerdOn said:
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
Click to expand...
Click to collapse
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? http://www.androidfilehost.com/?fid=23032113221600748? Also did you try doing a data wipe/factory reset in stock android recovery?
BladeRunner said:
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? Also did you try doing a data wipe/factory reset in stock android recovery?
Click to expand...
Click to collapse
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
HerdOn said:
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
Click to expand...
Click to collapse
sorry, here is the link to the Odin files thread: http://forum.xda-developers.com/showthread.php?t=2301259 Download the VRAUME7 factory image. I'm not sure but I think you may have the MDK image from RWILCO and there's no going back to that once you've updated to ME7.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
Checkm8 said:
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Don't know where that extra "?" came from
Alright I'm downloading that version now. Its capping my connection so it should be done in 25 mins and we'll try again! Thanks for your help so far bladerunner. Seems like we're getting somewhere...
Bladerunner, you were right my friend! The image is finally going to the phone. After nearly pulling all of my hair out, we're making extreme progress!
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
HerdOn said:
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
Click to expand...
Click to collapse
Excellent! No problem
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
This did not belong in development section. This had been said 1000 times in all these threads the last couple of days. Problem is no one reads before they risk bricking their device.
jogawa said:
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
Click to expand...
Click to collapse
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Travisdroidx2 said:
This did not belong in development section. This had been said 1000 times in all these threads the last couple of days. Problem is no one reads before they risk bricking their device.
Click to expand...
Click to collapse
You're right about which forum. I had READ most of the discussion about going to MJ7 in the Development forum. But it does belong here.
tech_head said:
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Click to expand...
Click to collapse
Thanks!
I can't seem to get into recovery using the Up+Power+Home method. I keep getting the "Firmware upgrade encountered ..." screen. Any tips?
Is that after a battery pull?
jogawa said:
Thanks!
I can't seem to get into recovery using the Up+Power+Home method. I keep getting the "Firmware upgrade encountered ..." screen. Any tips?
Click to expand...
Click to collapse
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
-Lawless said:
Is that after a battery pull?
Click to expand...
Click to collapse
Yep. Pulled battery. Tried for download mode. Still stuck in the "Firmware upgrade encountered ..." mode.
mmuzzy said:
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
Click to expand...
Click to collapse
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
jogawa said:
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
Click to expand...
Click to collapse
Good to hear
tech_head said:
There is an update.zip available and some people in your situation have had look booting into recovery and applying the update.zip manually.
Won't get you closer to root, but you do get a working phone.
Click to expand...
Click to collapse
My son is on ME7, and his phone kept trying to update. He gave it to me and I pulled the update.zip and I have it on my computer. Is this the update.zip you are talking about?
mmuzzy said:
I did the same thing and ended up with the failed firmware error. I flashed the file in the second post of this thread in Odin and my phone booted up again: http://forum.xda-developers.com/showthread.php?t=2502591
Click to expand...
Click to collapse
Muzzy! Are you on an s4 now?! I'm a devotee of your rom from my Toro days.
Probably not if he was on ME7. That is probably the MI1. The OTA updates require you take all of them in sequence.
Sent from my SCH-I545 using Tapatalk
tech_head said:
Probably not if he was on ME7. That is probably the MI1. The OTA updates require you take all of them in sequence.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
How long does it normally take to get root on new updates from Verizon?
Depends. It's getting harder each time. It could be tomorrow or next month.
Sent from my SCH-I545 using Tapatalk
ntb81 said:
Muzzy! Are you on an s4 now?! I'm a devotee of your rom from my Toro days.
Click to expand...
Click to collapse
Thanks. I do have an S4 now. I'm settling in as a user these days now that Nexus on VZW is becoming a distant memory. :\
jogawa said:
Yep. Pulled battery. Tried for download mode. Still stuck in the "Firmware upgrade encountered ..." mode.
Click to expand...
Click to collapse
jogawa said:
YAY!
Thank you!
Worked like a charm.
Un-soft-bricked.
Now I wait for a root procedure for MJ7.
AND, I don't feel quite as dumb if YOU did it too.
Thanks again.
Click to expand...
Click to collapse
Out of curiosity, how did you get into Odin mode while every time you tried to enter DL mode you got the same error?
Jsyme222 said:
Out of curiosity, how did you get into Odin mode while every time you tried to enter DL mode you got the same error?
Click to expand...
Click to collapse
When it's displaying that error, it's in download mode - you can plug it in and run ODIN to re-flash.
I found that kind of surprising, but it's understandable since all you can do at that point is to redo the failed flash.
k1mu said:
When it's displaying that error, it's in download mode - you can plug it in and run ODIN to re-flash.
I found that kind of surprising, but it's understandable since all you can do at that point is to redo the failed flash.
Click to expand...
Click to collapse
That's exactly right. It was in download mode all the time, even though it was showing the error. Odin always showed the COM in blue, which suggested to me that it was flashable. No big insight on my part.
jogawa said:
I'm a newbie on the forum, so I can't post this in the right thread in the Development forum, so here it is.
As several people have mentioned elsewhere, you can't go back to anything before MJ7 via Odin. I speak from sad experience. Here's my story.
I was on ME7, rooted, using SafeStrap (SS) to use the Hyper ROM. Everything was good.
I decided to get MJ7.
So I got VoodooOTAKeeper and saved my SU.
Then tried to get the OTA update and couldn't.
I uninstalled SS, re-installed the stock Verizon/Samsung stuff (bloatware) that I had removed, unrooted with VoodooOTA, and tried again.
Still no OTA (error).
I read more on the forums and decided that I had to Odin back to stock ME7. I got Odin and the stock ME7 ROM and went back in time.
NOW the OTA worked. BUT it put me on MI1.
Here's where I made my big mistake.
I hadn't read enough and didn't know that I needed to re-root on MI1 and do all the other stuff in the "Upgrade to MJ7 and keep your root" post in the Dev forum. In my defense, it wasn't up yet.
So, I then took the MJ7 OTA.
Now I was on MJ7 OK. I tried to re-root with VoodooOTA. No dice.
I decided to try to go back to ME7 via Odin. BIG MISTAKE.
It failed (won't go back), and then left me in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." mode, which I cannot get out of.
So now I have to either send the phone to Samsung and have it reflashed, or wait till the Odin MJ7 ROM is out and try that, I think.
So, DON'T DO WHAT I DID!
Click to expand...
Click to collapse
Youll need to completely wipe your phone with the emergency recovery file found here. Flash that with Odin in Download Mode.
Doing this will remove root, but one of these should give it back.
I was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
Fused 5 means you need to flash either mj7 or mk2 .
I'd do the full wipe at this point. If one doesn't work right at first... Try the other. Do you recall which your phone was on prior to this?
Sent From My Verizon S4
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Yea I don't know either.. I just saw that Odin error then I saw me7. Figured op tried flashing the wrong one. It is a bit confusing though with no actual info to go on.
Sent From My Verizon S4
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
af_nm said:
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
Click to expand...
Click to collapse
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
With the new knox security trying to flash a prior firmware will trip the flag so it's advised to be careful when flashing images via Odin. Flash an earlier version that doesn't take and you'll lose the warranty on your phone.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
would reinstalling the pit files work?
odin mdk
Mistertac said:
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
Click to expand...
Click to collapse
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
af_nm said:
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
Click to expand...
Click to collapse
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
same here, I'm not sure what he has or what he has done........
decaturbob said:
same here, I'm not sure what he has or what he has done........
Click to expand...
Click to collapse
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Mistertac said:
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Click to expand...
Click to collapse
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
k1mu said:
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
Click to expand...
Click to collapse
Yea good call I think I was actually confusing posts when I was responding earlier. Forgot about the fused 5. Thanks .
Sent From My Verizon S4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 and used this http://forum.xda-developers.com/showthread.php?t=2507253. when I ran it in odin it ran until it stopped at system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440]
af_nm said:
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 as well but I can't find one that will work
Click to expand...
Click to collapse
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
af_nm said:
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
Click to expand...
Click to collapse
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Surge1223 said:
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Click to expand...
Click to collapse
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
af_nm said:
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
Click to expand...
Click to collapse
Driver issue 99% of the time make sure you've uninstalled all Samsung drivers. Use windows' control panel option to uninstall programs and make sure all kies, samsung, and verizon related stuff is uninstalled. Then reboot the pc, let your phone install the drivers for your pc, and try using a different usb port with the stock oem cable. Also make sure adb isn't running in the background
Sent from my SCH-I545 using XDA Premium 4 mobile app
"Firmware Upgrade Encountered an Issue" "Device not responding" Samsung Kies
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Bumping for others to hopefully see... I've still made no progress and am in the same situation and simply can't find what I need to do.
What build were you on before you started? What file are you trying to flash with Odin?
Jmick363 said:
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Hightower24 said:
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Click to expand...
Click to collapse
Crap. You're right. I completely forgot about that last night. I was getting frustrated with Hyperdrive because when I was trying to install version 20, the WiFi would never work no matter which modules.zip I flashed.
I got fed up and just wanted to flash something else and I did this without even thinking about it... I can get the phone into download mode, but when I try to flash this in odin, it fails.
I saw someone with the same screen as me with a Note 2 and someone said something about flashing a PIT file or something like that? I think I'm going to look into that next, hopefully I can find some useful links.
riker147 said:
What build were you on before you started? What file are you trying to flash with Odin?
Click to expand...
Click to collapse
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Jmick363 said:
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Click to expand...
Click to collapse
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Hightower24 said:
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Click to expand...
Click to collapse
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Jmick363 said:
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Click to expand...
Click to collapse
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Hightower24 said:
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Jmick363 said:
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Click to expand...
Click to collapse
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
So right now things aren't going as smoothly as I would've hoped.... The first time I flashed Hyperdrive and then that modules zip you linked, and the phone got stuck on the Samsung custom screen in some sort of loop. I reset it with odin and just the PDA from the link from before, and I then installed towelroot and safestrap again then flashed hyperdrive and modules and now I'm stuck on the hyperdrive red screen... It's just the boot animation and nothing else. When I take out the battery, the power button does nothing if the phone is not plugged in. When I plug the phone in and hold down the power button, it just shows an empty battery with a loading icon in the middle. I can't do anything else.... I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Jmick363 said:
I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Click to expand...
Click to collapse
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Jmick363 said:
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Click to expand...
Click to collapse
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Hightower24 said:
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Click to expand...
Click to collapse
No need to apologize!! Your job isn't to monitor me, and I can't thank you enough for all the help. I'm going to give this a shot at some point today, hopefully it'll work. I'll comment back in the thread whatever happens... As you can probably tell, I typically have horrible luck with these things.
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
madhavok09 said:
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
Click to expand...
Click to collapse
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
Well the OP said he did the wipe with that link I listed, and I would assume it's a good link. I am flashing the full wipe with the PIT file, using the cable that came with the phone, and I have tried using a different USB port. I have tried 3 different MD5 files as well and still have had no luck.
Edit (2:13 PM Eastern): Had the wrong file after some digging, and got the NC5 instead of the MK2. Phone is booting normally. Thanks for the help.