Hi. I have S6 edge SM-G925F. I tried to flash custom rom,but i didn't backup EFS files. And now as you can guess, i don't have signal. I tried to flash stock firmware with odin but i got error. How can i make EFS work again? Download from somewhere and flash it? If yes,would you share it?
FakeSmile said:
Hi. I have S6 edge SM-G925F. I tried to flash custom rom,but i didn't backup EFS files. And now as you can guess, i don't have signal. I tried to flash stock firmware with odin but i got error. How can i make EFS work again? Download from somewhere and flash it? If yes,would you share it?
Click to expand...
Click to collapse
What error did you get flashing stock in odin?
I dont think anybody will share there efs backup.. as you will end up with there imei, which means cloned imei, also its illegal to do that in some countrys.
Best way is to flash the same stock you had before.
Sent from my SM-G925F using Tapatalk
callumbr1 said:
What error did you get flashing stock in odin?
I dont think anybody will share there efs backup.. as you will end up with there imei, which means cloned imei, also its illegal to do that in some countrys.
Best way is to flash the same stock you had before.
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Is this going to bring back my efs?
FakeSmile said:
Is this going to bring back my efs?
Click to expand...
Click to collapse
I did exactly the same a few weeks back. I flashed the stock i was on before and efs was restored.
Ok. Thanks a lot.
callumbr1 said:
I did exactly the same a few weeks back. I flashed the stock i was on before and efs was restored.
Click to expand...
Click to collapse
This is the error i got when trying to flash stock firmware from sammobile:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU4DPGW_G925FITV4DPH1_G925FXXU4DPGW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also how can i find out which firmware i was before i start flashing?
FakeSmile said:
Also how can i find out which firmware i was before i start flashing?
Click to expand...
Click to collapse
Which region are you? Is your phone unlocked or is it locked to a network? What android version was you on?
---------- Post added at 06:44 AM ---------- Previous post was at 06:30 AM ----------
FakeSmile said:
This is the error i got when trying to flash stock firmware from sammobile:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU4DPGW_G925FITV4DPH1_G925FXXU4DPGW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
https://mega.nz/#!rERH1LqK!QSYjirrXtPjKc1giOahnZI0BrWR2WXMg0GI3ZR3LLeY
Download the pit file from the link.
In odin click ap and insert the firmware again. The one you just used G925FXXU4DPGW.
click PIT and insert the pit file from the link. In options you need to check re partition and auto reboot.
Flash and that will fix the hidden.img
I was on android 6.0.1 August 1 st security patch. Im from Bulgaria so region should be Europe.
FakeSmile said:
I was on android 6.0.1 August 1 st security patch. Im from Bulgaria so region should be Europe.
Click to expand...
Click to collapse
Did you try to flash the firmware with the PIT?
Try this if pit didn't work ...
Extract the firmware , rename hidden.img to hidden.img.tar
Now flash hidden.img.tar in AP with Odin
BTW : it is possible you have to restart your phone in download mode after flashing the firmware to flash the hidden.img.tar after it
Good luck
Related
Hello,
I have a Samsung galaxy s4 (sgh-m919), I rooted it using odin3. about 2 months later I decided to revert back to a unroot state. I followed galaxys4root.com tutorial to unroot. I downloaded the usb driver and downloaded the firmware,
I ran odin in admin mode and pluged in phone in download mode. I clicked pda and added my .tar.md5 file and clicked start. this is what I got .
<ID:0/003> Added!!
<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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
don't know how to fix the problem!!!!!!!!!
Hello,
I have a Samsung galaxy s4 (sgh-m919), I rooted it using odin3. about 2 months later I decided to revert back to a unroot state. I followed galaxys4root.com tutorial to unroot. I downloaded the usb driver and downloaded the firmware,
I ran odin in admin mode and pluged in phone in download mode. I clicked pda and added my .tar.md5 file and clicked start. this is what I got .
<ID:0/003> Added!!
<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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
don't know how to fix the problem!!!!!!!!!
Sent from my SGH-M919 using xda app-developers app
Problem fixed
richardlg1 said:
Hello,
I have a Samsung galaxy s4 (sgh-m919), I rooted it using odin3. about 2 months later I decided to revert back to a unroot state. I followed galaxys4root.com tutorial to unroot. I downloaded the usb driver and downloaded the firmware,
I ran odin in admin mode and pluged in phone in download mode. I clicked pda and added my .tar.md5 file and clicked start. this is what I got .
<ID:0/003> Added!!
<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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
don't know how to fix the problem!!!!!!!!!
Sent from my SGH-M919 using xda app-developers app
Problem fixed
Click to expand...
Click to collapse
OMG YES IM HAVING THE SAME ISSUE i was able to get back into the os but i tried to root again and it didnt stick so im back in the soft brick SOMEONE PLEASE HELP
Bump! I would appreciate if someone would help with this issue, as I am also having the same problem.
Odin fails to flash even a stock rom.. please help.
skay301 said:
Bump! I would appreciate if someone would help with this issue, as I am also having the same problem.
Odin fails to flash even a stock rom.. please help.
Click to expand...
Click to collapse
bump. I am having the same issue. stuck in a soft brick with odin unable to successfully load stock or a custom rom. tried different PIT files. tried different roms, tried pushing via adb, tried on windows, osx, and Linux. im seriously gasping as straws here.
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
<ID:0/003> Removed!!
<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
toosweetnitemare said:
bump. I am having the same issue. stuck in a soft brick with odin unable to successfully load stock or a custom rom. tried different PIT files. tried different roms, tried pushing via adb, tried on windows, osx, and Linux. im seriously gasping as straws here.
Click to expand...
Click to collapse
You need to create your own thread and describe in detail :
Can you get to Download Mode?
Can you get into Recovery? If so, custom (version>) or stock?
What version of the software / firmware WERE you on?
What did you do to cause it to soft brick?
What versions of the software / firmware have you tried?
Why were you trying different PIT files??
What errors are you having?
es0tericcha0s said:
You need to create your own thread and describe in detail :
Click to expand...
Click to collapse
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.
What version of the software / firmware WERE you on?
I was on 4.4.2 from tmobile stock but it was rooted.
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. let my wife use my phone and she clicked approve for the update. The phone then rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods, all my errors seem to be directed to the PIT. I am currently downloading the Samsung firmware for 4.4.4 from the Samsung website to try sending over to the phone from odin.
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, about to try 4.4.4 when it finishes downloading.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT"
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)
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> 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/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> 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)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> 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/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> 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)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.
So I have this message on the screen "firmware upgrade encountered an issue. please select recovery mode in kies & try again".
I have tried installing alot of new firmware, but it doesn't help. Everytime I'm installing a new firmware it just goes to <ID:0/003> factoryfs.img
<ID:0/003> FAIL!
Someone please help me fix my phone?
LOG:
<ID:0/003> Added!!
<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..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> factoryfs.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Hi there,
Where are you downloading the firmware files from? Is it from a reliable source? Did your phone have enough power to complete the flash? What about a different computer?
Regards, gsstudios
gsstudios said:
Hi there,
Where are you downloading the firmware files from? Is it from a reliable source? Did your phone have enough power to complete the flash? What about a different computer?
Regards, gsstudios
Click to expand...
Click to collapse
Thanks for you reply, I am downloading the files from sammobile.com and I charged my phones battery before I did it.
mixtape45 said:
Thanks for you reply, I am downloading the files from sammobile.com and I charged my phones battery before I did it.
Click to expand...
Click to collapse
Try an Older Version of 'ODIN' and see, Sometimes the latest version do pose Issues for u
I always use ODIN ver 1.85 as it has never failed for me so far
Sun90 said:
Try an Older Version of 'ODIN' and see, Sometimes the latest version do pose Issues for u
I always use ODIN ver 1.85 as it has never failed for me so far
Click to expand...
Click to collapse
I have tried using that version, and I have tried using the latest version of odin.
mixtape45 said:
Thanks for you reply, I am downloading the files from sammobile.com and I charged my phones battery before I did it.
Click to expand...
Click to collapse
Have you followed this guide before posting on XDA: http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Regards, gsstudios
I did try that guide, and I got past the usual factoryfs.img but my phones battery discharged, and when I charged it, I still get FAIL at factoryfs.img
I am trying to fix a S6 edge. The problem is that when i boot it up it shows me "an error has occurred while updating the device software"
Odin, newest version, does not see the phone. I have searched around and downloaded the G9250ZTU2COKB_G9250ZZT2COKB_BRI firmware for my SM-G9250 and trying to flash it with Odin 3.10.7
It starts but soon after starting it shows me the following error. Any help please? I have searched and found a thread where it says that i need to remove the hidden image from the file but there is no hidden image in it after extracting the tar file.
TIA
<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..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<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> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try flashing the XEU or BTU firmware.
mikey_sk said:
try flashing the XEU or BTU firmware.
Click to expand...
Click to collapse
DON'T do this ^ - your 9250 is a different hardware variant to the 925F/I/T etc models and if you flash a non-9250 firmware you'll likely end up with a paperweight.
Anyone else with any ideas?
Guys I flashed my SM-G531H / DL whit this Fiemware (G531HVJU0APC2_G531HZTO0APC1_G531HUBU0APC1)
and now I have this problem,my Phone is brick can you tell me what Firmware can I use to Desbrick my phone?
thx in advance.
It say that After the flash with odin and this Rom
<ID:0/003> Added!!
<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..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> SPRDCP.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
pacoelo said:
Guys I flashed my SM-G531H / DL whit this Fiemware (G531HVJU0APC2_G531HZTO0APC1_G531HUBU0APC1)
and now I have this problem,my Phone is brick can you tell me what Firmware can I use to Desbrick my phone?
thx in advance.
Click to expand...
Click to collapse
Are you sure it is the correct firmware?
You can try this link i created a thread about fail after hidden.img but u can try the something instead of doing steps on hidden.img do for SPRDCP.img. if u dont understand ask me
https://forum.xda-developers.com/grand-prime/help/guide-odin-failed-flashing-stock-t3514810
Becareful
Maybe is baseband G531HUBUAOJ2