[Q] Unbrick Samsung Galaxy S4 - Verizon Samsung Galaxy S 4

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.

Related

[Q] Sch-i545 Soft Bricked (Semi-Noob)

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

[Q] cannot factory reset

I accidentally tried to install a custom recovery on my galaxy s4. Its running me7 and it got bricked. I can reboot it and everything works fine but if I try to factory reset the phone in the settings it gets stuck in download mode. Is there anyway around this?
Kwc0055 said:
I accidentally tried to install a custom recovery on my galaxy s4. Its running me7 and it got bricked. I can reboot it and everything works fine but if I try to factory reset the phone in the settings it gets stuck in download mode. Is there anyway around this?
Click to expand...
Click to collapse
First off your phone isnt bricked, its not even soft bricked. Your phone cant boot to stock recovery because you attempted to overwrite it with a custom version. Youll have to flash the stock me7 image via odin to get back your stock recovery. All the stock images can be found in the dev section. There is also a no wipe version if you apps/data you dont want to be wiped during the process.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
First off your phone isnt bricked, its not even soft bricked. Your phone cant boot to stock recovery because you attempted to overwrite it with a custom version. Youll have to flash the stock me7 image via odin to get back your stock recovery. All the stock images can be found in the dev section. There is also a no wipe version if you apps/data you dont want to be wiped during the process.
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 did try to odin it over after the fact thinking I did brick it i found a youtube guide on how to unbrick it via odin, sadly odin kept giving me failure messages. I think the me7 update blocks any kind of flashing.
Kwc0055 said:
I did try to odin it over after the fact thinking I did brick it i found a youtube guide on how to unbrick it via odin, sadly odin kept giving me failure messages. I think the me7 update blocks any kind of flashing.
Click to expand...
Click to collapse
If it failed after flashing aboot you were trying to flash mdk which you cant do. Prior firmwares are blocked. Me7 doesnt block odin flashing you just have to flash the me7 stock file.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
If it failed after flashing aboot you were trying to flash mdk which you cant do. Prior firmwares are blocked. Me7 doesnt block odin flashing you just have to flash the me7 stock file.
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 think I tried both honestly but I'm redownloading the me7 as we speak and I'll try it out again. I'll post again after and let u know if it works. I appreciate you taking the time to help me.
Kwc0055 said:
I think I tried both honestly but I'm redownloading the me7 as we speak and I'll try it out again. I'll post again after and let u know if it works. I appreciate you taking the time to help me.
Click to expand...
Click to collapse
Not a problem, yeah just make sure its the me7 image or it wont flash. Also when flashing me7 if youre still getting errors it could be a corrupted download so verifying the md5 after the download is suggested.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
it worked! thank you so much! many thanks
Kwc0055 said:
it worked! thank you so much! many thanks
Click to expand...
Click to collapse
No problem, glad you got it sorted out.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

HELP - Cannot Flash Stock Firmware, Bricked?

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

[Q] Bricked Note 2 i605

So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
mzaric said:
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
Click to expand...
Click to collapse
UPDATE: Since i posted this, i tried to flash a stock firmware on Odin (4.1.2 i believe) and it failed halfway through the procedure. with nothing more to be done, i reset my phone, and where before it was just bootlooping, it now shows me an entirely different screen reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Since then i have tried a different firmware file, still 4.1.2, Odin get's to the very end of the procedure, and crashes at what i assume is the reboot portion. Desperately need assistance!
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
akellar said:
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
Click to expand...
Click to collapse
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
mzaric said:
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
Click to expand...
Click to collapse
I cant seem to find the file anywhere. Only on terafile via SamMobile, but the download link doesn't seem to work.
What are my options as far as this bootloader go?
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I did a bunch of searches on the site as i was f****ing my phone up, systematically. Im really sorry if this thread doesn't go here, i just didn't know who else to ask
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
mzaric said:
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
Click to expand...
Click to collapse
Currently the only way to root your OTA 4.3 Note 2 is to use saferoot, read this thread carefully
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
Sent from my SCH-I605 using Tapatalk
I found myself in the same situation. Where might I find the PIT file? I can't reboot the phone to get the PIT file because it's soft bricked like mzaric's phone was. I'm using Mac OS X so I'm having to use JOdin3 to flash the stock 4.3 firmware back, but without the PIT file I can't continue and I've searched endlessly to find the PIT file. Also a somewhat related question, I heard JOdin isn't good for flashing big files, but I have no alternative, is the stock firmware which is 1.1gb too big to flash?
EDIT: I sadly didn't search hard enough thank you droidstyle for the guide. But my next question is I'm unsure of what version the phone is because when I originally tried to do the CASUAL unlock I believe it was on 4.1.2, but I think it softbricked to begin with because it was 4.3. Should I just try doing the 4.1.2 and if it doesn't take, retry with the 4.3?
If you flashed n7100 firmware you are screwed. If not just Odin back to stock. You were on 4.1.2 if you were unlocked using casual. Don't go to 4.3
Sent from my SCH-I605 using Tapatalk

[Q] Soft Brick

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

Categories

Resources