Hello,
I borrowed my roommates Verizon S4 (SCH-I545) and I soft-bricked it. I had a different carrier and needed to root/unlock it, and after a day I was unable to send texts or use data, so I tried to install a recovery to flash a ROM.
However, once I tried to install a recovery, it would not longer boot and would say "Software Update Failed" and it tells me to use the Verizon Software Repair Assistant.
So, I tried using Odin to flash the stock, but I ran into trouble because this phone is on 5.0.1. On Odin, I would have the COM marker light up yellow, so I know the phone was at least recognized.
I also tried to find a Verizon Repair exe file (using windows), and I think I found one for Samsung, but it does not recognize the device being connected (even though Odin does)
Is there anything I can do to save this phone and return it to my roommate?
Fail Log:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
shivpaulchadha said:
Hello,
I borrowed my roommates Verizon S4 (SCH-I545) and I soft-bricked it. I had a different carrier and needed to root/unlock it, and after a day I was unable to send texts or use data, so I tried to install a recovery to flash a ROM.
However, once I tried to install a recovery, it would not longer boot and would say "Software Update Failed" and it tells me to use the Verizon Software Repair Assistant.
So, I tried using Odin to flash the stock, but I ran into trouble because this phone is on 5.0.1. On Odin, I would have the COM marker light up yellow, so I know the phone was at least recognized.
I also tried to find a Verizon Repair exe file (using windows), and I think I found one for Samsung, but it does not recognize the device being connected (even though Odin does)
Is there anything I can do to save this phone and return it to my roommate?
Click to expand...
Click to collapse
Do you know what baseband version is on the phone? When Odin initially failed for me it was because the phone was running 5.0.1 and I tried installing the earliest software. Then I downloaded the newest firmware (OF1) and flashed it successfully.
Snowby123 said:
Do you know what baseband version is on the phone? When Odin initially failed for me it was because the phone was running 5.0.1 and I tried installing the earliest software. Then I downloaded the newest firmware (OF1) and flashed it successfully.
Click to expand...
Click to collapse
can u give me the link Firmware OF1 pls :'(
AnggaKun said:
can u give me the link Firmware OF1 pls :'(
Click to expand...
Click to collapse
Turns out I could not find the firmware on here to download so I went too the site SamMobile and performed the painfully slow download from there
Snowby123 said:
Turns out I could not find the firmware on here to download so I went too the site SamMobile and performed the painfully slow download from there
Click to expand...
Click to collapse
when im download at sammobile, the file when im wanna ekstract it always corrupt file
help me im got bootloop on of1, can if im try instal oc1 firmware?:good:
AnggaKun said:
when im download at sammobile, the file when im wanna ekstract it always corrupt file
help me im got bootloop on of1, can if im try instal oc1 firmware?:good:
Click to expand...
Click to collapse
Installing an older firmware likely will fail. Moreover, your download was likely incomplete. That is the most common cause of the file being labeled corrupt. There are other sites you could find the firmware , but the other sites have a weaker reputation
Snowby123 said:
Installing an older firmware likely will fail. Moreover, your download was likely incomplete. That is the most common cause of the file being labeled corrupt. There are other sites you could find the firmware , but the other sites have a weaker reputation
Click to expand...
Click to collapse
im trying to flash.. but stuck
log odin
[/COLOR]<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
stuck in there
Related
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Portisface said:
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Click to expand...
Click to collapse
Were you originally on MDK? If so, have you checked MD5?
riker147 said:
Were you originally on MDK? If so, have you checked MD5?
Click to expand...
Click to collapse
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Portisface said:
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Click to expand...
Click to collapse
No. What build were you on before your problems?
riker147 said:
No. What build were you on before your problems?
Click to expand...
Click to collapse
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Portisface said:
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Click to expand...
Click to collapse
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
riker147 said:
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
Click to expand...
Click to collapse
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Portisface said:
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Click to expand...
Click to collapse
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
riker147 said:
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
Click to expand...
Click to collapse
So the "no PIT partition" message isn't a problem?
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gotshot87 said:
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi guys,
1st thing thank you for the informations and knowledge i have learned here at XDA.
I have the same problem . I have done all i believe i can from all the research i have done and come acrossed. Hands up in the air and i surrender.
Need some help
If anybody could please fhank you so much...
It looks like you are trying to unlock the wrong baseband version.
The only Verizon Samsung Galaxy S4 (SCH-I545), aka jfltevzw, that has an unlockable bootloader is the one that has the baseband version "I545VRUAMDK".
And once the baseband is updated to a newer one, it cannot be downgraded.
Sent from my SCH-I535 using XDA Free mobile app
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
toosweetnitemare said:
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
es0tericcha0s said:
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
Click to expand...
Click to collapse
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
toosweetnitemare said:
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
Click to expand...
Click to collapse
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
es0tericcha0s said:
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
Click to expand...
Click to collapse
yes I just tried M919UVUFNH7_M919TMBFNH7_TMB. Attached is a screenshot of odin. below is the output from odin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
when turning on the phone without booting into recovery or download mode, I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have tried recovery mode in Kies and it does not detect my device.
the little text in the upper left hand corner of the screen says:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
Click to expand...
Click to collapse
entering download mode I get the same little text in the upper left corner of the screen as when just booting the device. The message in the middle of the screen has changed to "Downloading... Do not turn off target!!"
when I try to push the img for 4.4.4 while in download mode, I get the output from odin that I pasted above and the text in the upper left hand corner of the screen has been appended to state:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
start [224, 1448]
bar [240, 1440]
Click to expand...
Click to collapse
and the blue loading bar has stopped moving.
please let me know if there is anything else I can give you for information. Thank you for looking into this with me.
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
That's what I was afraid of. Thanks for the info.
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Interesting find. Can't imagine why that would be the trick. Every time I've ever used Odin (on many dozens of Samsungs), it's always been recommended to check that for a full update. Thanks for sharing in case I, or another member has the same thing happen.
Wait, .tar or like the system.img?
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Can you post the .IMG here please? im running through same issue.
es0tericcha0s said:
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
Click to expand...
Click to collapse
Just for info. the Model: SGH-M919 will not boot from the SD card, Even if you have the correct debrick.img that was made from the same device.
Hi guys. I have a galaxy s6 that I tried to flash with official firmware 5.1.1 via odin. I was rooted before that. The flash failed and now it says to use Verizon's software utility to restore the phone. That utility doesn't work and the reps at the store had never heard of it.I literally can't fix the thing. No amount of flashing in download mode helps. It always fails.
Anyway, I went to Verizon and they are sending me a replacement in two days. In download mode it still says that the firmware is official. However it also says samsung custom. (Assuming the root) I don't know if Verizon will backcharge me for this. Is there any way to get rid of the custom status? When I put it in the box to return it I'll leave it on the System Software Update Failed screen.
Remember I can't flash via odin, that just fails. Samsung smartswitch doesn't recognize the device. Recovery mode is a no go.
Thanks for the help!
What's the error message in Odin?
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
es0tericcha0s said:
What's the error message in Odin?
Click to expand...
Click to collapse
in seems to always fail. I can go back to download mode or be instructed to restore via Verizon's software assistant. Here is what odin has to say. It fails at the system.img Verizon G920V
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mrao said:
Official 5.1.1? It's possible you were trying to flash a lower build....on 5.1.1, you've got to try flashing the same build or higher, it's possible verizon added a downgrade lock
Click to expand...
Click to collapse
I was not on 5.1.1 at the time. I downloaded 5.1.1 from sammobile or one of the other firmware hosting sites. I also tried 5.0.2 but that gives me a nand error.
Would perhaps flashing a pit file work? The problem is the the one firmware I originally tried to flash (5.1.1) doesn't have a pit file. The other firmware 5.0.2 does have one but it's only 4kb. I'm not sure if that's right.
Just in case anyone finds this in the future. I figured out how to fix this. I had have a working phone to install verizon's upgrade assitant. It would not work from the exe I found on the internet. From there I had to install it in a virtual machine because it did not like Win 10. From there I simply plugged in my device and it restored it. Use this method if odin doesn't work. I WILL NEVER ROOT AGAIN!
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
es0tericcha0s said:
So because you had an issue with your computer, you won't root again? Not sure I understand that, but glad you got it fixed.
Click to expand...
Click to collapse
Odin failed a flash and I could not reflash with odin again. I don't ever want to have that happen again. It wasn't the firmware I triple verified it before I flashed it. It was the correct firmware.
Very simple and hard for me at the same time
Flashed twrp on my galaxy s6edge 925f and that was the only thing i did so far, after 1st reboot it started up, but on second time i tryed to restart phone and wiped system (think ) becouse it ways i dont have os installed, it stuck at samsung logo, smartswtich neither kies recognizes my phone (yes drivers are installed) have downloaded stock firmware and tryed to flash it via odin, but..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed
ok with odin 3.12 i have this error
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can please anyone help me out?
managed somehow make it to work, cloes please
if you have samsung kies also installed on your comp it wont work....
I have this problem , can you explain how you fixed it?
aryaazimi72 said:
I have this problem , can you explain how you fixed it?
Click to expand...
Click to collapse
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
callumbr1 said:
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
Click to expand...
Click to collapse
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
aryaazimi72 said:
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
Click to expand...
Click to collapse
Which rom are you on? And which BL are you flashing?
callumbr1 said:
Which rom are you on? And which BL are you flashing?
Click to expand...
Click to collapse
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
aryaazimi72 said:
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
Click to expand...
Click to collapse
Crisscross development has stopped. I recommend CarHD rom it is the best by far.
Make sure your flashing the roms through twrp
Hello,
I have a Galaxy S6 Edge with a few Problems.
Whenever it starts, I can only see the Bootlogo. I tried to get into the Recovery but it istn Possible. Only the Downloadmode is working. I tried to Flash the latest original Firmware but it doesnt work.
Then I tried to reset the Phone via Smart Switch but it failed and now I cant even use Odin because the downloadmode says "SW REV. CHECK FAIL DEVICE: 5, BINARY: 4.
I'm new to Flashing Samsung but I flased a few HTC and Oneplus Devices.
My Region Code is DBT and i tried to flash the "G925FXXS4DPJ5" Firmware.
I hope you can help me
XeNTaX said:
Hello,
I have a Galaxy S6 Edge with a few Problems.
Whenever it starts, I can only see the Bootlogo. I tried to get into the Recovery but it istn Possible. Only the Downloadmode is working. I tried to Flash the latest original Firmware but it doesnt work
Click to expand...
Click to collapse
same here pls help
XeNTaX said:
Hello,
I have a Galaxy S6 Edge with a few Problems.
Whenever it starts, I can only see the Bootlogo. I tried to get into the Recovery but it istn Possible. Only the Downloadmode is working. I tried to Flash the latest original Firmware but it doesnt work.
Then I tried to reset the Phone via Smart Switch but it failed and now I cant even use Odin because the downloadmode says "SW REV. CHECK FAIL DEVICE: 5, BINARY: 4.
I'm new to Flashing Samsung but I flased a few HTC and Oneplus Devices.
My Region Code is DBT and i tried to flash the "G925FXXS4DPJ5" Firmware.
I hope you can help me
Click to expand...
Click to collapse
What error did you get in Odin?
In Odin it fails at Flashing sboot.bin
It seems like i got a newer Bootloader because i tried to flash the DTM firmware. Is there any way to downgrade the bootloader ?
When I try to flash the DTM firmware it fails.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if its failing at sboot then you may need to flash the bootloader as well if you are flashing as separate files
try to flash firmware with pit file or flash hidden separately
I tried to flash the firmware again with the right PIT file.
Odin said everything is okay but i still cant boot the system oder into recovery :/
XeNTaX said:
I tried to flash the firmware again with the right PIT file.
Odin said everything is okay but i still cant boot the system oder into recovery :/
Click to expand...
Click to collapse
Extract the firmware, remove shoot.bin, repack and flash again