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
Related
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
So i have Samsung Galaxy S4 that is stuck in the Firmware upgrade encountered error mode. I was attempted to root it with the Odin and Root_de_la_vega.
My phone is a Galaxy S4 SCH-I545 - VRUDMl1
I already attempted to do a Kies Recovery but it is telling me my S/N is not correct. I tried every word/letter underneath the battery.
I already saw the No-Wipe Factory Image Guide. I tried that but it fails everytime when it gets to the point that says ABoot. Don't really know whats left i can try.
Any help would be much appreciated.
thanks
Tuffguy721 said:
So i have Samsung Galaxy S4 that is stuck in the Firmware upgrade encountered error mode. I was attempted to root it with the Odin and Root_de_la_vega.
My phone is a Galaxy S4 SCH-I545 - VRUDMl1
I already attempted to do a Kies Recovery but it is telling me my S/N is not correct. I tried every word/letter underneath the battery.
I already saw the No-Wipe Factory Image Guide. I tried that but it fails everytime when it gets to the point that says ABoot. Don't really know whats left i can try.
Any help would be much appreciated.
thanks
Click to expand...
Click to collapse
Did you try to upgrade to mj7. If so that is the best option is to flash that odin image. Can't go backwards.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Did you try to upgrade to mj7. If so that is the best option is to flash that odin image. Can't go backwards.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I have not attempting to upgrade yet. I was doing everything that was for ME1.
Tuffguy721 said:
I have not attempting to upgrade yet. I was doing everything that was for ME1.
Click to expand...
Click to collapse
You sure you had the ml1 image when trying to flash a previous firmware it fails at aboot. Verifying the md5 is also good to make sure you didnt get a corrupted download.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
You sure you had the ml1 image when trying to flash a previous firmware it fails at aboot. Verifying the md5 is also good to make sure you didnt get a corrupted download.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I just downloaded and upgraded to MJ7 and to actually completed. Lost everything but got the phone back up and running at least. Now i will go read up but can this new MJ7 be rooted yet?
Thanks for the help
Tuffguy721 said:
I just downloaded and upgraded to MJ7 and to actually completed. Lost everything but got the phone back up and running at least. Now i will go read up but can this new MJ7 be rooted yet?
Thanks for the help
Click to expand...
Click to collapse
It can if you saved root from ml1. People are working on it right now tho theres a thread in the general section about it.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I can't figure out what to do. I accidentally wiped system when using safestrap and now my phone gets stuck at samsung boot. I tried to flash my MI1 with odin, and it says write failed, and now every time I start my device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried going into kies but it gets stuck at connecting even though all the drivers are installed. I really don't know what to do right now, and need to fix my phone. Can anyone help?
kcorj2244 said:
I can't figure out what to do. I accidentally wiped system when using safestrap and now my phone gets stuck at samsung boot. I tried to flash my MI1 with odin, and it says write failed, and now every time I start my device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried going into kies but it gets stuck at connecting even though all the drivers are installed. I really don't know what to do right now, and need to fix my phone. Can anyone help?
Click to expand...
Click to collapse
I tried firmware update via Kies, and it gets stuck at 69% and then fails... Need a fix for this guys, so I can have my phone for work.
kcorj2244 said:
I tried firmware update via Kies, and it gets stuck at 69% and then fails... Need a fix for this guys, so I can have my phone for work.
Click to expand...
Click to collapse
I've tried pretty much ever odin file. ME7, MJ7, MI1... All of them give me Complete(Write) Operation Failed.. Kies still hangs at 69%. I really really need a fix for this. Literally any help is wanted.
kcorj2244 said:
I've tried pretty much ever odin file. ME7, MJ7, MI1... All of them give me Complete(Write) Operation Failed.. Kies still hangs at 69%. I really really need a fix for this. Literally any help is wanted.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2507253
riker147 said:
Have you tried this? http://forum.xda-developers.com/showthread.php?t=2507253
Click to expand...
Click to collapse
Yeah I did. Is there a Complete Device Wipe/Repartition and Emergency Recovery for VRUEMI1 Build
I'm almost positive my device was on MI1. I tried this MI1 tar earlier and it didn't work though; http://forum.xda-developers.com/showthread.php?t=2484726
kcorj2244 said:
Yeah I did. Is there a Complete Device Wipe/Repartition and Emergency Recovery for VRUEMI1 Build
I'm almost positive my device was on MI1. I tried this MI1 tar earlier and it didn't work though; http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Not sure. Have you tried the "No Wipe" image? http://forum.xda-developers.com/showthread.php?t=2301259
riker147 said:
Not sure. Have you tried the "No Wipe" image? http://forum.xda-developers.com/showthread.php?t=2301259
Click to expand...
Click to collapse
Yes... The whole reason my phone is soft-bricked is because I accidentely deleted system via safestrap... I have tried pretty much all the odin restores and none work. I just tried the one you linked and I got SW Rev. Check FAIL : Fused : 5, Binary : 4
kcorj2244 said:
Yes... The whole reason my phone is soft-bricked is because I accidentely deleted system via safestrap... I have tried pretty much all the odin restores and none work. I just tried the one you linked and I got SW Rev. Check FAIL : Fused : 5, Binary : 4
Click to expand...
Click to collapse
Check this thread out. The OP had a similar issue and was able to get it resolved. http://forum.xda-developers.com/showthread.php?t=2546372
Other than that, maybe you can try re downloading the Tar files. A lot of people have had issues with bad downloads.
riker147 said:
Check this thread out. The OP had a similar issue and was able to get it resolved. http://forum.xda-developers.com/showthread.php?t=2546372
Other than that, maybe you can try re downloading the Tar files. A lot of people have had issues with bad downloads.
Click to expand...
Click to collapse
I'm able to access the recovery menu, and I get stuck at a samsung boot logo now. I'm thinking accessing the recovery menu and manually installing update.zip will work. Do you have a link to the MI1 update.zip?
kcorj2244 said:
I'm able to access the recovery menu, and I get stuck at a samsung boot logo now. I'm thinking accessing the recovery menu and manually installing update.zip will work. Do you have a link to the MI1 update.zip?
Click to expand...
Click to collapse
If you bothered to read the thread that was just linked for you, you'd see that the OP of that thread was having the same issue with the same error. I already explained why this happens in that thread and how to solve it, flash the full-wipe MJ7 odin tar.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If you bothered to read the thread that was just linked for you, you'd see that the OP of that thread was having the same issue with the same error. I already explained why this happens in that thread and how to solve it, flash the full-wipe MJ7 odin tar.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did read the thread, and i tried it. And when I do that I get a fail flash write. I'm trying it on a different computer now, to see if I can get it to work.
kcorj2244 said:
I did read the thread, and i tried it. And when I do that I get a fail flash write. I'm trying it on a different computer now, to see if I can get it to work.
Click to expand...
Click to collapse
Make sure you've uninstalled kies, then reinstall the latest Samsung usb drivers and use odin 3.07 running as admin. What was your exact failure message?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Make sure you've uninstalled kies, then reinstall the latest Samsung usb drivers and use odin 3.07 running as admin. What was your exact failure message?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On odin it says FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone it says ODIN: Flash write failure
kcorj2244 said:
On odin it says FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone it says ODIN: Flash write failure
Click to expand...
Click to collapse
Thats not good news...first make sure the md5 of the odin tar is valid. If its not then from my experience that error message correlates with the emmc starting to go corrupt. If the md5 us not the issue then I would suggest you make yourself a debrick image immediately because the only remaining solution you have left to try is to rewrite the partition map using a pit, and flashing the bootchain along with the stock odin tar...if you dont find another solution then ill give you more indepth instructions and a link to the proper pit file. I do encourage you to seek other solutions though as I havent encountered this error in some time and someone may have found a solution im not aware of. Consider my suggestion a final resort.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not good news...first make sure the md5 of the odin tar is valid. If its not then from my experience that error message correlates with the emmc starting to go corrupt. If the md5 us not the issue then I would suggest you make yourself a debrick image immediately because the only remaining solution you have left to try is to rewrite the partition map using a pit, and flashing the bootchain along with the stock odin tar...if you dont find another solution then ill give you more indepth instructions and a link to the proper pit file. I do encourage you to seek other solutions though as I havent encountered this error in some time and someone may have found a solution im not aware of. Consider my suggestion a final resort.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried pretty much every solution. I think I want to go with this.
Okay do you know how to do what I was suggesting? If not ill give you more directions when I get home
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Okay do you know how to do what I was suggesting? If not ill give you more directions when I get home
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, not really. and I don't want to mess it up.
kcorj2244 said:
No, not really. and I don't want to mess it up.
Click to expand...
Click to collapse
Im not saying it will for sure work. Im just suggesting an idea that ive seen work before. You suggested flashing ota in recovery earlier..id try that first just make sure its the MJ7 ota. Also you used the adb commands to remove safestrap right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Im not saying it will for sure work. Im just suggesting an idea that ive seen work before. You suggested flashing ota in recovery earlier..id try that first just make sure its the MJ7 ota. Also you used the adb commands to remove safestrap right?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh no I didn't use adb to remove safestrap. How do you do that?
kcorj2244 said:
Oh no I didn't use adb to remove safestrap. How do you do that?
Click to expand...
Click to collapse
The directions for that are in the Safestrap thread.
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
Ive looked all over and tryed a couple different things to fix this. I tryed doing a clockworkmod recovery and it did not work. Then i tryed to use loki and it bricked the phone. Now it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try agian". I have tryed using odin to go back to the stock rom/firmware and it fails half way through on two different pc's. then i tryed kies and it wont read my device on either pc. i have reinstalled samsung drivers on both pc's and still nothing. If anybody has any ideas it would be appreciated. I have a good knowledge of PC's but this is the first time messing with a phone.
Shafty6 said:
Ive looked all over and tryed a couple different things to fix this. I tryed doing a clockworkmod recovery and it did not work. Then i tryed to use loki and it bricked the phone. Now it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try agian". I have tryed using odin to go back to the stock rom/firmware and it fails half way through on two different pc's. then i tryed kies and it wont read my device on either pc. i have reinstalled samsung drivers on both pc's and still nothing. If anybody has any ideas it would be appreciated. I have a good knowledge of PC's but this is the first time messing with a phone.
Click to expand...
Click to collapse
Going to need more info. Build #? How did you root? How did you try to install custom recovery? What firmware did you try to install with Odin? Can you get back into Odin mode?
You should have started with this thread before you did anything to your phone. http://forum.xda-developers.com/showthread.php?t=2606501
riker147 said:
Going to need more info. Build #? How did you root? How did you try to install custom recovery? What firmware did you try to install with Odin? Can you get back into Odin mode?
You should have started with this thread before you did anything to your phone. http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
Build number ME7 I rooted with This Guide. I did the recovery with the ClockWorkMod app and that did not work so i then tryed GooManager for the loki recovery. The Odin Firmware was 6.0.4.4. I only get these screens to work with and both say ODIN MODE at the top, It also says "WRITE PROTECTION: Enabled
Shafty6 said:
Build number ME7 I rooted with This Guide. I did the recovery with the ClockWorkMod app and that did not work so i then tryed GooManager for the loki recovery. The Odin Firmware was 6.0.4.4. I only get these screens to work with and both say ODIN MODE at the top, It also says "WRITE PROTECTION: Enabled
Click to expand...
Click to collapse
Wow. You didn't do any research at all did you? You're going to have to find a ME7 (or later build) .tar file and use Odin to flash back to stock and start all over.
Just know you CAN'T install a custom recovery with ME7 (or any build after that) and you can't revert to an older build. Your ONLY option is Safestrap. Read that thread I linked you to and do your research.
riker147 said:
Wow. You didn't do any research at all did you? You're going to have to find a ME7 (or later build) .tar file and use Odin to flash back to stock and start all over.
Just know you CAN'T install a custom recovery with ME7 (or any build after that) and you can't revert to an older build. Your ONLY option is Safestrap. Read that thread I linked you to and do your research.
Click to expand...
Click to collapse
Thank you for the help the the build recovery i have is not a ME7. Yea I just kinda of went for it, not a good idea. On the other hand it is a backup phone so i have plenty of time to find what I need.
I am using ODIN3 v185 on my PC is that ok?
Shafty6 said:
Thank you for the help the the build recovery i have is not a ME7. Yea I just kinda of went for it, not a good idea. On the other hand it is a backup phone so i have plenty of time to find what I need.
I am using ODIN3 v185 on my PC is that ok?
Click to expand...
Click to collapse
Pretty sure 3.07 is the newest Odin build.
I don't understand what you mean by "build recovery".
riker147 said:
Pretty sure 3.07 is the newest Odin build.
I don't understand what you mean by "build recovery".
Click to expand...
Click to collapse
I dont have the ME7 .tar i had a different one I am downloading the ME7 and when its done Im going to give it a go.
Shafty6 said:
I dont have the ME7 .tar i had a different one I am downloading the ME7 and when its done Im going to give it a go.
Click to expand...
Click to collapse
Ok. Good luck.
riker147 said:
Ok. Good luck.
Click to expand...
Click to collapse
you are kind...
Well I successfully restored my s4 to working order. Thank you riker147 for all your help.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hit that thanks button!
Sent from my SCH-I545 using XDA Premium 4 mobile app