i have galaxy s3 the international model
right now it stucks on the logo. i can get into download mod, but not into recovery.
i've tried to flash stock version. i used first the one file method . didn't work, then i tried the 4 files method
with bootloader etc... but it failed again.
i changed cables, usb ports, nothing!
here's the odin log.
___________________
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMG4_I9300ITVEML2_I9300XXEMG4_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
could it be an hardware issue. or theres still chance
thanks..
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead
Dinkec27 said:
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead[/Q
in download mode it says:
custom binary download: no
currnet binary: samsung official
system status: official
so maybe its not??
Click to expand...
Click to collapse
I think your device is dead
tyler6389 said:
I think your device is dead
Click to expand...
Click to collapse
i think too, but is there any last options i could try.. like flash it with pit files???
Related
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.
I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
falconflyer82 said:
I've been using OmniROM and TWRP for quite some time now.
I put the phone on charge and a few minutes later it was stuck on Samsung initial Screen with the usual red triangle. (Showing SAMSUNG Galaxy SIII GT-I9300)
I removed the charger and battery and restarted, it was still stuck on Samsung Boot Screen.
Any ideas how to recover the phone?
I have tried going through some of the other forum threads but most of them can't go to download mode. I can go into TWRP and download mode both. I tried recovering the phone using Kies "Firmware Initialization" but it generates "your phone cannot be upgraded to the latest version" and stops.
Click to expand...
Click to collapse
Download stock rom from Sammobile and flash in Odin..
tallman43 said:
Download stock rom from Sammobile and flash in Odin..
Click to expand...
Click to collapse
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
falconflyer82 said:
Downloaded latest stock rom ML4 and this is what I get in Odin 3.09:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XWUGML4_I9300ODDGML4_I9300DDUGMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/038> Added!!
<ID:0/038> Odin v.3 engine (ID:38)..
<ID:0/038> File analysis..
<ID:0/038> SetupConnection..
<ID:0/038> Initialzation..
<ID:0/038> Get PIT for mapping..
<ID:0/038> Firmware update start..
<ID:0/038> SingleDownload.
<ID:0/038> sboot.bin
<ID:0/038> NAND Write Start!!
<ID:0/038> FAIL!
<ID:0/038>
<ID:0/038> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
tallman43 said:
Nand write fail usually means dead emmc chip. You can try rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but I think you need to send it fto service for repair.
Click to expand...
Click to collapse
I tried the rescue firmware, similar result:
Code:
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
P. S. I read somewhere in case of dead emmc I shouldn't be able to see the device version in download mode. But I can..
bricked device i9300..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
falconflyer82 said:
Did you try Odin 3.09? I too get the same result as you with Odin 3.07. With 3.09 I get the write fail error.
Click to expand...
Click to collapse
I used the 3.09 still same problem am stuked up really
If the rescue firmware and pit didn't flash then your emmc chip is damaged, either new motherboard or phone.
Sent from my GT-I9300 using Tapatalk
falconflyer82 said:
I finally took to a repair shop, they say it is my fault since I rooted it (they can see the red exclamation mark), and will charge extra for "software change".
Any idea how to reset the counter in download mode, revert to stock recovery and remove the red exclamation mark in bootloader?
Click to expand...
Click to collapse
There must be a way to reset the download count by installing stock recovery. Maybe @Chainfire can help here.
Sent from my XT1033 using Tapatalk
dupri11 said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CheckROM_V4_LG8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
it gets stuck for hours without any response ... can any one help please
Click to expand...
Click to collapse
what @boomboomer said is what you should consider.
If you keep on insisting, you will just damage the phone more ( i am talking from experience ) .
change motherboard or in some places, people can replace the emmc Chip for you.
Salam
Hi XDA.
I've been trying to search for solutions to my problem, but I really can't seem to find any. If a thread similar to mine exists already, I am sorry.
Today i tried flashing a LiquidSmooth 4.4.4 ROM to my device, but the install of the ROM gives an error (Status 7). Now the phone is stuck in a bootloop.
Now I am trying to flash stock ROM with Odin 3.07 but none of the .tar-files I've been trying will work. I have also tried to install TWRP Recovery through ODIN just now, but it fails every time. I can't seem to figure out what to do now.
Hope you guys can help me. Thanks in advance!
This is what ODIN writes when trying to flash the stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_L710VPUCMK3_L710SPRCMK3_2034598_REV03_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: When I try to boot up the device just with the power button it now shows white static noise all over the screen. I am in a panic right now, as I don't have the money to buy a new phone. I am afraid I have stupidly installed some kind of bootchain made for a Verizon S3 instead of the International version like mine.
EmilBakke said:
This is what ODIN writes when trying to flash the stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_L710VPUCMK3_L710SPRCMK3_2034598_REV03_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That's the Galaxy S3 L710 not S3 I9300. Either you are flashing the wrong firmware or your in the wrong forum >> http://forum.xda-developers.com/galaxy-s3-sprint <<
tallman43 said:
That's the Galaxy S3 L710 not S3 I9300. Either you are flashing the wrong firmware or your in the wrong forum >> http://forum.xda-developers.com/galaxy-s3-sprint <<
Click to expand...
Click to collapse
Well I surely am an idiot. Thank you so much, it works fine now! Have a nice day.
So pretty much no matter what I try flashing I get the following immediately: Any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRAMC3_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of stock, 4.4, clockwork mod, odin 3.07, 3.09, I've uninstalled and re-installed Kies. right now my phone can't do anything but be in download mode.
ODIN MODE
Product Name: GT-N7100
Current Binary: Samsung Official
System Status: Custom
KNOX Warranty VOID: 0
AP SWREV: A2
BrianAnim said:
So pretty much no matter what I try flashing I get the following immediately: Any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRAMC3_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of stock, 4.4, clockwork mod, odin 3.07, 3.09, I've uninstalled and re-installed Kies. right now my phone can't do anything but be in download mode.
ODIN MODE
Product Name: GT-N7100
Current Binary: Samsung Official
System Status: Custom
KNOX Warranty VOID: 0
AP SWREV: A2
Click to expand...
Click to collapse
Me too. Does misery like company?
I called verizon and told them it failed during an OTA update. They are shipping me out a new phone under warranty.
BrianAnim said:
So pretty much no matter what I try flashing I get the following immediately: Any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRAMC3_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of stock, 4.4, clockwork mod, odin 3.07, 3.09, I've uninstalled and re-installed Kies. right now my phone can't do anything but be in download mode.
ODIN MODE
Product Name: GT-N7100
Current Binary: Samsung Official
System Status: Custom
KNOX Warranty VOID: 0
AP SWREV: A2
Click to expand...
Click to collapse
If you have a Verizon Note 2 which is SCH-i605 then I can tell you why Odin isn't working. You flashed a bootloader for the GT-N7100.
These are what I've tried flashing:
N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_HOME.tar.md5
N7100XXUFNE1_N7100BTUFNE1_N7100XXUFND3_HOME.tar.md5
N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
I605_VRALJB_Restore.tar.md5
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
KS_MULTI_CSC_N7100XXUEMK4.tar.md5
BrianAnim said:
These are what I've tried flashing:
N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_HOME.tar.md5
N7100XXUFNE1_N7100BTUFNE1_N7100XXUFND3_HOME.tar.md5
N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
I605_VRALJB_Restore.tar.md5
KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5
KS_MULTI_CSC_N7100XXUEMK4.tar.md5
Click to expand...
Click to collapse
You see all those files that say N7100. That is for a different phone. Not the i605. That is why your phone isn't working. There are a couple of ways to fix the problem in the general section of this forum for the Verizon note 2. I just don't have the time to find them. Also there is mobiltechvideos which I believe can fix this problem for a fee.
BluGuy said:
You see all those files that say N7100. That is for a different phone. Not the i605. That is why your phone isn't working. There are a couple of ways to fix the problem in the general section of this forum for the Verizon note 2. I just don't have the time to find them. Also there is mobiltechvideos which I believe can fix this problem for a fee.
Click to expand...
Click to collapse
Ah, my phone starts up and said n7100 so that's where the confusion lay. I already have my replacement phone and all is well.
I was having serious restarting randomly problems with the old phone and it needed to be RMA'd anyway so no biggy. Thanks for all your help.
An admin can lock this thread.
Hi there,
it's matteios1984 first of all i'd like to say hello to the comunity and thank you all for interesting post about Android!
I'm here to asking help about a tricky case. I've a Samsung Galaxy S3 (i9300) bricked. In other words the phone behaves as follow:
- If i try to turn on the device it remains stuck on Samsung S3 logo
- No possible to boot in recovery mode
- When I connect it to the charger it's stucked showing the battery image and not showing any progress about charging status
- The device is still able to boot in download mode both with buttons combo and with resistor trick, but Odin is not able to flash anything on the device (my idea is to flash a Customer Recovery, perform a full wipe of the device and after restore original italian firmware)
Here following a log taken from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If i try to flash a file containing PIT informations here following the log from Odin:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've heard about the possibility to boot the device by a MicroSD card that allows me to flash the device... Do you think this will fix my issue? Or do I need a box? If so, any suggestion about the model is appreciated.
Thanks in advance for your support
Try downgrading the bootloader to BLFB before flashing firmware or pit.