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
Related
I need that file to fix my phone and Adrynaly's web host went down. If someone could p2p or rehost this for me it would be greatly apperciated... Merry Christmas.
Try here
http://forum.xda-developers.com/archive/index.php/t-867648.html
Swyped from a black hole in a galaxy far far away, using the XDA app.
http://dl.dropbox.com/u/15289892/DI01package3.tar
justin94 said:
Try here
http://forum.xda-developers.com/archive/index.php/t-867648.html
Swyped from a black hole in a galaxy far far away, using the XDA app.
Click to expand...
Click to collapse
Yeah, that's what I need but it's down.
Im trying to get a mirror but so far its slow going.
DI01
I am trying to flash my phone back to stock and have downloaded this DI01 from other sites. when I try to use ODIN it gives me an "INVALID IMAGE TYPE" error message. my phone is on the yellow downloading screen. PLEASE HELP!
please do not be mad if I am posting this on the wrong thread. I am a noob and thus do not know better
I too am trying to flash back to stock.
Ive DL'd DI01package3.tar.md5...
Connected to Odin
But when I click start, I get the following messages
<ID:0/003> Check MD5.. Do not unplug the cable..
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ive tried it a number of times, but no luck
the phone is now dead
can anyone help
I had a similar problem to you, with the package3 file; try the files linked to here:
http://forum.xda-developers.com/showpost.php?p=10711126&postcount=315
Namely, try flashing the Stock-i500-VZW-System.tar.md5 file via ODIN's PDA.
Follow the instructions on the first page of that thread; it should get you to a stock (as far as I can tell, anyway) DI01.
rushfanx1 said:
I too am trying to flash back to stock.
Ive DL'd DI01package3.tar.md5...
Connected to Odin
But when I click start, I get the following messages
<ID:0/003> Check MD5.. Do not unplug the cable..
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ive tried it a number of times, but no luck
the phone is now dead
can anyone help
Click to expand...
Click to collapse
mine gets this far have you got your to work
<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> Sbl.bin
<ID:0/003> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> movinand.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
DI01package3.tar?????
Does anyone know if DI01package3.tar has been replaced with a newer file as I can not find a good link to download it.
Thank you
FrostBitten4x said:
Does anyone know if DI01package3.tar has been replaced with a newer file as I can not find a good link to download it.
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1526488
Hi everyone,
I'm having a great problem. Recently got rooted SIII with CF-CWM and ICS Rom. I tried to install recent update of official 4.3 announced for UK (BTU) downloaded from SamMobile.
I used ODIN 3.7 for this process. All went successfully. ODIN automatically did a factory reset but after reset phone is on Samsung logo. Logo and LED light are blinking but not going any further. And I'm unable to go into recovery as well.
Please someone help me out in this matter. I searched here but found nothing relevant. And by the way I'm in Pakistan.
Here is the log of ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<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)
Odin does not do factory reset, boot into recovery and do it again.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Odin does not do factory reset, boot into recovery and do it again.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
thanks a lot brother
my problem is resolved.
please tell me how can I close this thread now?
How to root?
one more things.
Please guide me will the CF-Auto Root for SIII v6.4 by ChainFire work with 4.3 stock rom or not?
Check out CF's thread, I'm sure it will.
CF's Thread?
boomboomer said:
Check out CF's thread, I'm sure it will.
Click to expand...
Click to collapse
Would you like to tell me which one is CF's thread? any link for that?
faakher said:
Would you like to tell me which one is CF's thread? any link for that?
Click to expand...
Click to collapse
In development or found via the faqs and guides .
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.
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
my s3(i9305) is stuck in download mode with stock recovery on it and ive got odin, but i cant get any stock roms booted on it, cant get onto the phone, and it dont have any working firmware on it...i just want to put it back to stock asap and get the dam thing working again.
any help would be great!!
What output are you getting in odin?
Beamed in by telepathy.
shivadow said:
What output are you getting in odin?
Beamed in by telepathy.
Click to expand...
Click to collapse
the bar is blue
No, there is a 'window' on the bottom left of the app with text in it. What does that text say when you've attempted to flash the phone?. Need all of it, not just the result at the end.
The blue bar means the flash completed successfully but doesn't give any more info than that.
Beamed in by telepathy.
shivadow said:
No, there is a 'window' on the bottom left of the app with text in it. What does that text say when you've attempted to flash the phone?. Need all of it, not just the result at the end.
Beamed in by telepathy.
Click to expand...
Click to collapse
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGPE1_I9300AMNGPF1_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sboot.bin is the bootloader so I presume that it is either locked or corrupt. I'm not sure if that is a pit error or not. You could try to find another file and hope it works but if you're absolutely sure the one you have is good then there's no point. You could try finding a stock rom that doesn't include the bootloader. Also flashing a pit file (only as a very last step) is an option but make sure it is the correct one for your specific model and region etc.
I hate recommending pit file flashing but in this case it could be viable from other reports around the site. Flashing a pit file is a last resort only, I cannot stress this enough.
Beamed in by telepathy.
shivadow said:
Sboot.bin is the bootloader so I presume that it is either locked or corrupt. I'm not sure if that is a pit error or not. You could try to find another file and hope it works but if you're absolutely sure the one you have is good then there's no point. You could try finding a stock rom that doesn't include the bootloader. Also flashing a pit file (only as a very last step) is an option but make sure it is the correct one for your specific model and region etc.
I hate recommending pit file flashing but in this case it could be viable from other reports around the site. Flashing a pit file is a last resort only, I cannot stress this enough.
Beamed in by telepathy.
Click to expand...
Click to collapse
where might i find a stock rom without a bootloader? dont fancy the pit file tbh!!
Try using different USB cables and USB 2.0 ports.
audit13 said:
Try using different USB cables and USB 2.0 ports.
Click to expand...
Click to collapse
ive only got the 1 usb port on my tablet
The sboot.bin is not flashing because the bootloader on the phone is newer than the bootloader in the ROM you are flashing, the ROM is not for your phone, and/or you need to try another computer.
It's unlikely that the bootloader is locked as AT&T and Verizon are the only two carriers I know of who lock down the bootloader.
i'm totally out of my knowledge zone here....i did do thison 1 of my old phones a few years back and some one wrote on a comment exactly how to make it stock again....but i'm buggered if i can find that post again....or thats even if the site still has that thread...can anyone point me in the right direction here please?
Ok this is what i get when i try and flash this:I9300XXUGNB5_I9300EVRGML2_EVR
which i got from sam pass and selected my exact model of phone from my country(uk) and the network i'm using....with odin v3.10
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB5_I9300EVRGML2_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone please tell me what i'm doing wrong??
so this is what i'm getting when i'm using odin v3.10 trying to install the correct firmware for my phone from sam pas and selecting the country/network
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNB5_I9300EVRGML2_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone please point me in the right direction??
Your original post says the phone is a 9305 and you are flashing a 9300 ROM?
yea i'm trying to download I9305XXUFOC1 now but every site i go to its giving me a 5 hour wait time.....is there a faster way i can get it downloaded?
audit13 said:
Your original post says the phone is a 9305 and you are flashing a 9300 ROM?
Click to expand...
Click to collapse
Well spotted, didn't even occur to me..
Beamed in by telepathy.
In use sammobile.com. The download speed for free accounts is not great but I usually start the download and do something else for a while.