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
Related
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
KizzleKat said:
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.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> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
Click to expand...
Click to collapse
Get the official firmware needed on Sammobile.com, you need an account on there. Don't worry it's free. Flash it as PDA on Odin. Make sure your phone is in download mode (volume up+volume down+power). If it boots, the boot animation might start looping. From theres you can access recovery (volume up+power+home). In recovery you wipe data and wipe cache and select reboot. It should work.
Sent from my GT-I8190N using Tapatalk
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Galaxy_Ace_Love said:
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Click to expand...
Click to collapse
Odin 3.07 supports one file package
Humm...
iamareebjamal said:
Odin 3.07 supports one file package
Click to expand...
Click to collapse
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
KizzleKat said:
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
Click to expand...
Click to collapse
Format the data
Put the pit file and tick Repartition. And then flash with Odin.
And you have to use Cooperve pit, not Totoro, it's for SGY
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
KizzleKat said:
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
Click to expand...
Click to collapse
Follow these Guidehttp://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
Yo Guys! I think my bootloader was already updated, and I tried to flash back to original 4.3 or 4.1.2, but nothing of it worked.
When I try to flash f.e. the
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMR2_I9300VFREMA3_I9300BUEMA1_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me I was on CM 10.2/CM11 and wanted to restore factory images, because my Audio Plug-In didnt work properly anymore and my screen had some pixel errors.
I tried to flash a CWM touch recovery, but that did work only once - then flashed the bootloader downgrade Restore_Bootloader_XXBLFB.zip, but
I still couldnt flash any factory firmware
I also tried this here:
http://forum.xda-developers.com/showthread.php?t=2083860
Tried method 2 of that one, didnt get me in position to install the stock firmware.
Does anyone have any advice?
I still can enter CWM (or install it) and can enter Download Mode
I tried 4.3, 4.1.2 and 4.0.4 , nothing worked
Update #1 I could reflash cyangenmod over cwm again and my cell works too. *phew*
How do I get back to stock rom? Meanwhile I'll try mobile odin
update #2
mobile odin worked, got back to stock. just letting u know.
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
froycard said:
Have you tried another version of ODIN? I used to have some issue with version 3.0 and above. So it seems that version 1.8.5 is more stable that the new ones... try redownload your ROM, maybe it has some issues too.
Finally, use SAMSUNG SG3 TOOLKIT, I have used that too and without any issue.
Good Luck
:cyclops:
Click to expand...
Click to collapse
Read post above you
I tried Version 1.85 and 3.09, both didn't work. But thanks to Chainfire for developing this awesome tool :laugh::good:
mobile odin got my phone finally flashed
I tried to do a cyanogenmod update, but something went wrong and now I can't boot into android. I've tried going back into the recovery mode to reflash the rom, but it freezes there. I've also tried flashing clockworkmod recovery through ODIN and download mode, but the download back never moves at all, so I'm not sure if I can't use download mode or if it's just that ODIN isn't doing anything. I'm not sure what to do anymore, does anyone have any idea how to get me out of this?
Clothbox said:
I tried to do a cyanogenmod update, but something went wrong and now I can't boot into android. I've tried going back into the recovery mode to reflash the rom, but it freezes there. I've also tried flashing clockworkmod recovery through ODIN and download mode, but the download back never moves at all, so I'm not sure if I can't use download mode or if it's just that ODIN isn't doing anything. I'm not sure what to do anymore, does anyone have any idea how to get me out of this?
Click to expand...
Click to collapse
you could try heimdall.
it seems like you got a corrupted download or the boot.img is jacked up.
it wont help to flash the same rom.
grab stock files (need pit file) and flash with heimdall or odin.(preferably not using windows 8/8.1)
http://forum.xda-developers.com/showthread.php?t=2363213 does this link help?
Lgrootnoob said:
you could try heimdall.
it seems like you got a corrupted download or the boot.img is jacked up.
it wont help to flash the same rom.
grab stock files (need pit file) and flash with heimdall or odin.(preferably not using windows 8/8.1)
http://forum.xda-developers.com/showthread.php?t=2363213 does this link help?
Click to expand...
Click to collapse
Yeah, I'll try this approach. Where do I get the pit file?
Clothbox said:
Yeah, I'll try this approach. Where do I get the pit file?
Click to expand...
Click to collapse
should just be a part of the odin packages they provide.
dont worry about it.
just follow the instructions.
Lgrootnoob said:
should just be a part of the odin packages they provide.
dont worry about it.
just follow the instructions.
Click to expand...
Click to collapse
I tried it, and the phone is stuck in download mode with the progress bar never moving past a little dot. Is it hopeless?
Clothbox said:
I tried it, and the phone is stuck in download mode with the progress bar never moving past a little dot. Is it hopeless?
Click to expand...
Click to collapse
screenshot odin,
try different usb port, and different cable, and use the latest odin for sure, use kies to install drivers and different pc
Lgrootnoob said:
screenshot odin,
try different usb port, and different cable, and use the latest odin for sure, use kies to install drivers and different pc
Click to expand...
Click to collapse
Wow, thanks! I got it to work. I don't think I can boot into android but I can definitely boot into recovery. But it's just the standard recovery, I'm not sure if I can flash a rom through it. Where do I go from here?
Clothbox said:
Wow, thanks! I got it to work. I don't think I can boot into android but I can definitely boot into recovery. But it's just the standard recovery, I'm not sure if I can flash a rom through it. Where do I go from here?
Click to expand...
Click to collapse
what happened in odin? I can't really tell if something happened when it flashed system.img
.....
---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------
just copy and paste the output of the message box here from odin.
Lgrootnoob said:
what happened in odin? I can't really tell if something happened when it flashed system.img
.....
Click to expand...
Click to collapse
Not sure if this will help, but here:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Clothbox said:
Not sure if this will help, but here:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
wtf....
how can you not boot into android?
did you do the repartition check thing?
Lgrootnoob said:
wtf....
how can you not boot into android?
did you do the repartition check thing?
Click to expand...
Click to collapse
No, the only thing I checked was "Auto Reboot" and "F. Reset Time". Should I do it one more time or should I find a way to flash cyanogenmod again?
Clothbox said:
No, the only thing I checked was "Auto Reboot" and "F. Reset Time". Should I do it one more time or should I find a way to flash cyanogenmod again?
Click to expand...
Click to collapse
dont check auto reboot, manually reboot with power + volume up this time.
Lgrootnoob said:
dont check auto reboot, manually reboot with power + volume up this time.
Click to expand...
Click to collapse
Yeah, it still won't let me boot. Is there a way I can flash a rom or put in a different recovery mode from here?
Clothbox said:
Yeah, it still won't let me boot. Is there a way I can flash a rom or put in a different recovery mode from here?
Click to expand...
Click to collapse
yea, just install a different odin recovery img.
you can also take any recovery.img you want and format it as odin file with md5 igning etc
Lgrootnoob said:
yea, just install a different odin recovery img.
you can also take any recovery.img you want and format it as odin file with md5 igning etc
Click to expand...
Click to collapse
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Clothbox said:
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Click to expand...
Click to collapse
yes, take a cynagoen mod flashable zip, put it into an ext4 system.img if it isnt already one, then make an odin tar.md5 out of it.(if your already lost then your screwed)
It's not uncommon to need to reboot to recovery to factory reset after flashing the firmware through Odin or Heimdall as many of the packages do not wipe data as they are meant to be update versions.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Clothbox said:
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Click to expand...
Click to collapse
^ he made a good point
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