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
Related
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
John90uk said:
Hi, currently having problems with S3 GT-I9300. I am stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.' Cannot do anything with phone atm. I have tried kies to carry it emergency recovery but that fails everytime it gets to 4%. I have also tried to flash a stock rom using Odin but that again says FAIL in red. Any help would be great! thanks
ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMF1_I9300TMUEMF1_I9300BVEMF1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
haiderijaz said:
Try to enter download mode and again flash the rom. You said "I also tried flashing STOCK rom", what were you flashing before? I just encountered this error today and flashed again after entering download mode and the error went away.
Click to expand...
Click to collapse
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
JJEgan said:
You do not say what you where doing/ flashing in the first instance .
Kies must be off if using Odin .
STICKYS
http://forum.xda-developers.com/showthread.php?t=2344125
Click to expand...
Click to collapse
The problem started when i plugged my phone on charge, when i unplugged it the phone turned off and continued to restart after samsung logo screen. I then tried kies to upgrade and initiliase but when that reached 4% it would say an error occured. This happens constantly. I then closed kies and tried flashing a Stock rom with ODIN but it keeps saying FAIL in red.
Also afrer kies recovery it now says firmware upgrade encountered an error.
John90uk said:
i have tried this on many occasions but i still receive the same errors in odin and kies. have also tried different ports ad pc's. how do i find the correct firmware for my phone?
Click to expand...
Click to collapse
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
haiderijaz said:
I am unable to understand how you are using Kies and Odin at the same time. You need to go to sammobile.com and find your country there.
Click to expand...
Click to collapse
I am not using both softwares at the same time. Its a GT-I9300.
John90uk said:
I am not using both softwares at the same time. Its a GT-I9300.
Click to expand...
Click to collapse
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
haiderijaz said:
First of all, Please try and make sure you can enter recovery mode. From what I understand, your phone is soft bricked. Also you mentioned the model. To download the appropriate firmware you need the country.
IF you can enter recovery mode, things are okay. We can then try rooting your phone with and flashing a custom rom. If that works, stock rom can be flashed back later. But first of all please try entering recovering mode by pressing Volume Up, Home and Power Button. When you see the samsung boot logo, let go and if you get some options that means you are in recovery.
Click to expand...
Click to collapse
I can only get into download mode. When i try entering recovery mode i get a screen which says firmware upgrade encountered an error an issue. Where do i go from here?
Product code in download mode if blank its SDS .
JJEgan said:
Product code in download mode if blank its SDS .
Click to expand...
Click to collapse
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
John90uk said:
Odin mode
product name: GT-I9300
Custom Binary download: No
current binary: samsung official
System status: custom
Click to expand...
Click to collapse
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
haiderijaz said:
First of all pls find out which country your samsung is bought from. Europe? usa? Which firmware did you flash with ODIN? Where did you get it from?
May be we can try and root your phone.
Click to expand...
Click to collapse
It was from the UK. And i have tried to flash a T-mobile Uk firmware as it was on t-mobile. Thanks guys
Recovery mode and rooting are irrelevant to your issue. Try flashing the rescue firmware from the general forum, if that fails then you'll probably need a new motherboard.
Sent from my GT-I9300 using Tapatalk
Hi to everyone,
i had a problem with my galaxy S2 i9100 with stock ROM 4.1.2 with root executed by philz temporary recovery, i hope someone may help me.
Yesterday i was taking a picture and suddenly my phone showed Galaxy S2 logo, I think started bootlooping. I tried entering in recovery mode, sometimes showed "Applying csc etc." but never entering in recovery menu, other times blank screen.
So I decided to flash stock JB ROM with odin, my phone can enter in download mode correctly and stated original samsung binary and counter 0.
I used latest branded H3G stock ROM downloaded from sammobile: I9100XWLSD_I9100HUILS4_HUI Odin recognized phone but stucks on
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100HUILS4_I9100NELS1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> SingleDownload.
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
I followed this troubleshoot trying with multiple odin version, more cables but nothing worked. So i tried flashing philz custom kernel PhilZ-cwm6-XWLSD-OXX-4.87, odin started writing NAND but received write failed, i checked download mode and now i have custom binaries and increased counter with yellow triangle during power on.
After i tried to flash an old bootloader, and this flash was succesfully completed, but not resolved any problem.
Finally i tried to flash wipe JB leaked ROM linked in troubleshoot thread linked above with three separete files for PDA, CSC and MODEM but no luck. now when i power on, phone shows "Firmware Upgrade encountered an issue" message.
What can i do? Any suggestion will be appreciated
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
shionv plain
knuckles1978 said:
Try an older stock ROM with Odin (GB), and use a PIT file to repartition at the same time as flashing the ROM.
Then once you've got GB working, upgrade incrementally.
Click to expand...
Click to collapse
Do you mean selecting PDA from sammobile and pit file? Where can i get the stock one for pit?
I read about repartitioning with pit files that's a risky procedure that can brick phone definitively are there other safer procedures?
EDIT: Tried to flash stock ICS without pit and still not working
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.
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