While I was at work, my buddy stopped over and started flashing over to 4.4. Something failed. I am running safestrap 3.72. How do I get this thing back to hyperdrive 14.0, or android 4.3.
edit: And I cant just wipe, and try to reflash because Im getting an E:/unable to mount error while trying it. This thing is shot.
Phone is currently creating a rom slot 1, because apparently my stock rom slot doesn't have an OS.
Thanks for the help in advance.
narc0tix said:
While I was at work, my buddy stopped over and started flashing over to 4.4. Something failed. I am running safestrap 3.72. How do I get this thing back to hyperdrive 14.0, or android 4.3.
edit: And I cant just wipe, and try to reflash because Im getting an E:/unable to mount error while trying it. This thing is shot.
Phone is currently creating a rom slot 1, because apparently my stock rom slot doesn't have an OS.
Thanks for the help in advance.
Click to expand...
Click to collapse
You can't create ROM slots in the (unsupported on Verizon) Safestrap 3.72, You can only flash over the stock slot.
If your stock slot is hosed, boot into downloader mode and use Odin to flash factory stock. Then you can root it and install HD.
Going back to 4.3 at this point is possible, but not recommended. Read one of the multiple 4.3->4.4 upgrade threads for details.
k1mu said:
You can't create ROM slots in the (unsupported on Verizon) Safestrap 3.72, You can only flash over the stock slot.
If your stock slot is hosed, boot into downloader mode and use Odin to flash factory stock. Then you can root it and install HD.
Going back to 4.3 at this point is possible, but not recommended. Read one of the multiple 4.3->4.4 upgrade threads for details.
Click to expand...
Click to collapse
Im having to go through a proxy to access this site at work. Are you able to maybe shoot me a link off hand? Searching on the forum is bad enough, but even worse while going through a proxy.
Thanks for your help thus far.
k1mu said:
You can't create ROM slots in the (unsupported on Verizon) Safestrap 3.72, You can only flash over the stock slot.
If your stock slot is hosed, boot into downloader mode and use Odin to flash factory stock. Then you can root it and install HD.
Going back to 4.3 at this point is possible, but not recommended. Read one of the multiple 4.3->4.4 upgrade threads for details.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=GL8XwuRYoWU&list=WL&index=21
This should work, no?
narc0tix said:
https://www.youtube.com/watch?v=GL8XwuRYoWU&list=WL&index=21
This should work, no?
Click to expand...
Click to collapse
odin is the way to go but download the files to a pc and check md5 checksums and make sure there is good communication between PC and the phone. ODIN is very sensitive to USB ports and the USB cable and this is a cause for many ODIN failures
do as much reading as possible and there are other youtube videos
decaturbob said:
odin is the way to go but download the files to a pc and check md5 checksums and make sure there is good communication between PC and the phone. ODIN is very sensitive to USB ports and the USB cable and this is a cause for many ODIN failures
do as much reading as possible and there are other youtube videos
Click to expand...
Click to collapse
Can you please help me out here? Ive read and read. Do I need to flash mk2? MJ7? Everything I try to download from androidfilehost doesnt work, and Im still stuck with a bricked device.
Any guidance would be greatly appreciated!
narc0tix said:
Can you please help me out here? Ive read and read. Do I need to flash mk2? MJ7? Everything I try to download from androidfilehost doesnt work, and Im still stuck with a bricked device.
Any guidance would be greatly appreciated!
Click to expand...
Click to collapse
you are downloading to a PC right? never download big files to the phone
narc0tix said:
Can you please help me out here? Ive read and read. Do I need to flash mk2? MJ7? Everything I try to download from androidfilehost doesnt work, and Im still stuck with a bricked device.
Click to expand...
Click to collapse
Your phone is running 4.4, so you need to flash NC5. Don't download to your phone, download it to your computer, like decaturbob said.
If you really can't download from Android File Host, get someone with a reliable network connection to download it for you.
Link to the NC5 Odin files: http://forum.xda-developers.com/showthread.php?t=2735172
As far as your question about the YouTube directions, that's the problem with You Tube videos - they're history, old, and unreliable. Nobody updates them. It's easy to find videos telling people how to flash CM on their S4 which NEVER say "oh, and this will brick your phone if you're not on the MDK build". Don't watch videos and follow them unless you understand the risks.
That's why we've created sticky threads here to try to keep people from going down the wrong path.
Related
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...
11
goofankle said:
I'm somewhat new to this, sorry you might have to spell it out to me like I'm stupid. I installed TWRP in an attempt to flash a rom. I selected "Factory Reset" and proceeded to reboot. Now I'm stuck in Download Mode and have no clue what to do. Also my sd card seemed to not be recognized by TWRP when in the Install menu. I'm using a Verizon GS4, MK2, Android 4.3
Click to expand...
Click to collapse
OK...lookup Odin...you should be able to find multiple threads on here with the download as well as detailed instructions on how to use it...you will also need to download a file which should also be readily available in 1 or more threads on here which is the Odin file for mk2 full wipe emergency .tar file...I could easily link you to all these files but if you had done your research before trying to install twrp you would know that you can't flash any recovery besides safestrap on mk2,mj7,mI1 or me7...learning to search the threads to fix your s4 will make you a more knowledgeable modder...after you fix your s4...PLEASE FOR THE LOVE OF TECHNOLOGY READ UP...Learn up on safe strap before using it as well because it can be kinda sketchy for inexperienced users...good luck!
11
goofankle said:
I get a "fail" over and over again with Odin.
After the first fail the screen has changed to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What am I doing wrong?
edit:
I had to use kies to go back to a working phone
Click to expand...
Click to collapse
Glad you got it figured out. Like jamesd said, do a lot of research before you try anything else with your phone. Those of us on MK2 are extremely limited as to what we can do.
Sent from my NCC 1701 using Tapatalk 4
goofankle said:
I'm somewhat new to this, sorry you might have to spell it out to me like I'm stupid. I installed TWRP in an attempt to flash a rom. I selected "Factory Reset" and proceeded to reboot. Now I'm stuck in Download Mode and have no clue what to do. Also my sd card seemed to not be recognized by TWRP when in the Install menu. I'm using a Verizon GS4, MK2, Android 4.3
Click to expand...
Click to collapse
first of all you can't install a recovery like twrp or CWM nor can you flash any ROMS using those recoveries. Its been made clear countless times with countless threads that any S4 since MDK build can not have a recovery as their bootloaders are locked. The ONLY avenue is safestrap and the handful of safestrap compatible ROMS.
A bricked phone is the end result.
In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
coltblue said:
In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
Click to expand...
Click to collapse
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
lacoursiere18 said:
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
Click to expand...
Click to collapse
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
those are the only readings that is see from odin. not sure aware of more output readings.
coltblue said:
those are the only readings that is see from odin. not sure aware of more output readings.
Click to expand...
Click to collapse
coltblue said:
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
Click to expand...
Click to collapse
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
lacoursiere18 said:
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
Click to expand...
Click to collapse
yes it was in downloading mode. tried deleting kies and usb drivers then download of new usb drivers after pc restart. now getting usb device not recognized.
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
coltblue said:
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
Click to expand...
Click to collapse
Sounds like a usb error. Try another
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
coltblue said:
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
Click to expand...
Click to collapse
Pit....
https://www.dropbox.com/s/ka9a0x6juscjwfc/sch-i605-16gb.pit
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
coltblue said:
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
Click to expand...
Click to collapse
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
i have tried i605vrufnd7 , and KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_ , but not the other 2. i coouldnt find a working link for the others. i shall try them and report back thank you.
success ! odin finally accepted stock 4.1.1 but showed a warning triangle saying not official software on the phone screen. ran 4.4.2 through odin and it worked first try. phone restarted , booted up and loaded 4.4.2 . never lost any settings contacts or data! the big thing i did different was using odin on my desktop with a new usb cable and using the usb 3.0 port. Thanks for all the help !
coltblue said:
success !....
Click to expand...
Click to collapse
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
mattnmag said:
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
Click to expand...
Click to collapse
stock is ok for now. just didnt like it to be a paperweight. ill watch for new rooting methods in the future too. Thanks.
Thanks!!!
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
These guys are really helpful!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
Cool. Glad you got it fixed. :thumbup:
I went to upgrade to the new hyperdrive since they sent me the ota. Phone has been acting weird so I was going to do a complete wipe. I took my sd card out which my son took and lost on me and OI can find anywhere. I had another card so d/l new hyperdrive onto other card. I went to wipe cache and install new rom. phone wiped data and now wouldnt install new rom. I dont remember all the build I was on on the phone but I had Hyperdrive 16 before I started this if that helps at all. I am stuck on samsung custom boot screen. I can get into odin recovery and tried recovery but keeps failing. can I get some help I need my phone i have to go to work soon. Thanks
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
FlipFlop425 said:
ive tried the rootjunky video with both no wipe and full wipe neither worked. odin failed.
Click to expand...
Click to collapse
What files are you trying to flash? Did you use Safestrap to install RLS16?
Sent from my NCC-1701 using Tapatalk.
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
FlipFlop425 said:
i had downloaded the new update for hyper drive. Right now my biggest probelm is I cannot get past the splash screen. I can get into download mode though so can we try to figure out how to unbrick me first. Download mode is the only thing I can seem to get into right now
Click to expand...
Click to collapse
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
riker147 said:
That's why I need to know if you used Safestrap as your recovery. It's very likely you're trying to flash the wrong file with Odin.
If you had Safestrap your build wasn't MDK. If you didn't need Safestrap then your build was MDK.
So I'll ask again, what file are you trying to flash, with Odin, that keeps failing?
Click to expand...
Click to collapse
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
FlipFlop425 said:
I used to have to use safestrap. I was trying to flash the mdk file from rootjunky's video on unbricking your phone
Click to expand...
Click to collapse
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
npjohnson said:
NO!!! You cannot flash the MDK file, you cannot downgrade the S4! Always ends badly, go to the general section and grab the NC5 full-wipe tar and flash with ODIN.
Click to expand...
Click to collapse
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
FlipFlop425 said:
I have tried that from SUrge1223. That did not work for me. I cannot get in to my phone to re root it. Is that the right file the one from him?
Click to expand...
Click to collapse
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
riker147 said:
From here http://forum.xda-developers.com/showthread.php?t=2735172. I would choose the "Full Wipe" version. Make sure you have a good download. Check MD5. Make sure you follow the directions for Odin. If you verify all of that, and it still doesn't work, I'm afraid I won't be any more help. Someone with more knowledge than I have will have to step in. Good luck.
Click to expand...
Click to collapse
I can vouch for the full Version. Saved my bacon.
You have to boot the phone into a special mode that will allow ODIN to funtion
Turn off the SGS4 and boot it into Download/Odin Mode: press and hold the Volume Down, Home and Power buttons simultaneously for a couple of seconds till you see a warning screen. Then press Volume Upkey to enter Download Mode.
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
FlipFlop425 said:
I got it!!! Found my Samsung cable and all went well. TY for ALL the help!
Click to expand...
Click to collapse
Yeah, it is a really good feeling when that ODIN starts to run like it means it. Nothing beats that first boot up!
"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.