I have recently rooted my phone and using MIUI and Siyah-s2-v6.0b4 Kernel. I followed steps from a tutorial. It was working fine until yesterday. I was on Instagram when the phone froze on that screen. I left it as it is. It stayed like that for some time and then it rebooted automatically. The phone shows initial Samsung Galaxy S2 screen and after that it goes blank. The boot animation doesn't load. If the press the Home Key 4 times, it shows a bright white screen continuously and stays like that. And the screen turns off when I press the home screen 4 times. Nothing else happens. When I try to get into recovery mode it gives me error Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The phone worked perfectly and suddenly this happened. I had tried updating when I got the MIUI update notification. It downloaded the update, rebooted the phone automatically and phone started normally and I got the update notification again. Please help me fix my phone. I need it as soon as possible. And sorry if I posted in the wrong section.
Download stock rom for country/carrier from Samfirmware, boot into download mode, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware', problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Once you've done that, re-root your phone & restore nandroid backup or re-flash custom rom/kernel & start again.
But frankly, you should already know this stuff if you're modding your phone. Not knowing how to recover when things go wrong (and they do for everyone sooner or later) potentially leaves you without a working phone for hours (at least), especially given S2 Q&A doesn't get as many posters or people answering other people's questions as it used to.
MistahBungle said:
Download stock rom for country/carrier from Samfirmware, boot into download mode, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware', problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Once you've done that, re-root your phone & restore nandroid backup or re-flash custom rom/kernel & start again.
But frankly, you should already know this stuff if you're modding your phone. Not knowing how to recover when things go wrong (and they do for everyone sooner or later) potentially leaves you without a working phone for hours (at least), especially given S2 Q&A doesn't get as many posters or people answering other people's questions as it used to.
Click to expand...
Click to collapse
Have downloaded the stock ROM, tried flashing it but it got stuck on
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
No progress after this point.
ansariaamir_leo said:
Have downloaded the stock ROM, tried flashing it but it got stuck on
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> NAND Write Start!!
No progress after this point.
Click to expand...
Click to collapse
Did you even read what my thread said? Or what MistahBungle wrote?
MistahBungle said:
problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash.
Click to expand...
Click to collapse
The whole purpose of my thread is to troubleshoot Odin flashing errors. Time to read it and do what it says. As MistahBungle says, there's nothing missed out in that thread. If, after trying everything in that thread multiple times, you don't get it to 'take' a flash, then time for a service centre/new motherboard.
OK...
You're obviously not someone who pays attention to the help they're given, so I'm going to repeat what I said in my last post once, and then I'm not posting to this thread again...
'Problems with flash = find Hopper8's 'Odin troubleshooting' thread stickied in General, it has all the info you need to get a successful flash'.
If you want your phone fixed, you go through as many of the troubleshooting steps in Hopper's thread as many times as you need to.
You are the only person who can fix it. We can't fix it for you. I've given you the tools to fix it, go fix it. Or not. I don't care. But I can guarantee you one thing, if all you do is post 'But it won't work !' to this thread when I've given you the tools to get it fixed, your phone will probably still be busted this time tomorrow.
Related
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dmonger11b said:
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2280680
Sent from my SCH-I605 using XDA Premium HD app
dmonger11b said:
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Click to expand...
Click to collapse
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
larry_thagr81 said:
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
Click to expand...
Click to collapse
Awesome thank you. Worked perfectly. I feel kinda embarrassed I didn't look in Adam's thread. But the issue was caused by something a little different than what he warned against. Either way phone booted back up. Definitely irritated I didn't look better,
Glad I could point you in the right direction.
So my unrooted, Jellybean SG2 decided to crap out on me. It's stuck in the dread boot loop! OH NOES! I got a new SG2, so I don't care if my SG2 what software is put on it. I just want my precious data (music, photos, videos). Some said it couldn't be done, but I found this thread on here that said otherwise.
Making use of SiyahKernal, it should be possible to mount my SG2 to my laptop. I decided to Odin this puppy up. I wanted to go by the tutorial the other thread posted, so I tried using the Jellybean T-Mobile rom (which my SG2 was using). I used the ROM, for my device, from Samsung Updates. I made sure to restart my PC, shut down any processes by Kies, etc, etc before starting Odin. When I went to flash the ROM, Odin froze for a good 15 minutes. I decided that nothing was going to happen and unplugged my S2.
So, here I am, stuck with the message, "firmware upgrade encountered an issue in Samsung Galaxy S2." I, somehow, made the problem worse. I just want my data. As you can see, I'm a total noob with this stuff. Please help!
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
MistahBungle said:
Get a stock rom from Samfirmware, AndroidFirmwares.net or Samsung-Updates.com, flash it with Odin following instructions in thread stickied near top of Q&A titled 'Flash stock firmware...'. Clean slate. You shouldn't lose your stuff, but there are never guarantees with this or even that this will definitely fix your phone & enable it to boot normally (it shouldn't & it should though).
Click to expand...
Click to collapse
Thanks. I'll give it a try and post my results.
Ricequakes said:
Thanks. I'll give it a try and post my results.
Click to expand...
Click to collapse
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
thuva06 said:
well loosing data is something that i've experienced alot of times (my case i9100g)
i guess flashing the clean stock rom will help out.. but recently when my friend messed up his s2 i9100 i flashed the stock through odin which made him all the data its uncertain whether you loose your data or not.. fingers crossed flash the stock you may or may not loose data
Click to expand...
Click to collapse
Let's hope. If only it would even flash. Just tried and this is what I got on Odin:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVMC6_T989TMB_T989UVMC6_HOME.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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> amss.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what it said on my SG2:
nand_write: flash write fail
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
theunderling said:
http://forum.xda-developers.com/galaxy-s2-tmobile
Post in correct forum
S4 victim
Click to expand...
Click to collapse
I'm a bigger noob than I thought. Sorry, guys.
Mod Edit
Thread closed
[OP] found correct forum
malybru
Forum Moderator
XDA, I need your help. I have an international S3. I accidentally clicked an XDA link, linking to Verizon S3 and installed a pit file from a Verizon thread. I really need help.
The phone will boot up and won't let me continue past the first screen because my phone doesn't have a Verizon SIM, it has a Venezuelan (Movistar) SIM.
I checked many many places and the only place that has anything similar to what I need is this thread:
http://forum.xda-developers.com/galaxy-s3/general/odinfirmware-sgsiii-i9300-prerooted-t1825272
I tried what was there and could not manage anything.
I am desperate. I don't know what to do. I really need your help.
Please.
Also, I've been using this phone for around a year now in Venezuela. Which, I assumed, meant it international.
When I go to "Download Mode" it reads as follows:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (14 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Unsupport dev_type
Follow the guide in stickies, general forum to flash back to full stock rom, then factory reset.
Once you have your phone booting again then read up on where you went wrong, before you try flashing anything else.
boomboomer said:
Follow the guide in stickies, general forum to flash back to full stock rom, then factory reset.
Once you have your phone booting again then read up on where you went wrong, before you try flashing anything else.
Click to expand...
Click to collapse
I tried and ODIN FAILS.
It says (auth)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is serious. Your remaining options are the rescue firmware (search) or a new motherboard. I can only guess you flashed a recovery meant for another model, which usually blows the digitiser or corrupts the emmc chip.
boomboomer said:
That is serious. Your remaining options are the rescue firmware (search) or a new motherboard. I can only guess you flashed a recovery meant for another model, which usually blows the digitiser or corrupts the emmc chip.
Click to expand...
Click to collapse
pleasae help me. please.
boomboomer said:
That is serious. Your remaining options are the rescue firmware (search) or a new motherboard. I can only guess you flashed a recovery meant for another model, which usually blows the digitiser or corrupts the emmc chip.
Click to expand...
Click to collapse
Good call, he flashed Verizon files and probably messed up his emmc chip.
Sent from my SCH-I535 using Tapatalk 2
What can I do? I need to fix this.
I don't have the money to send it to a repair shop or buy a new one for my dad. I really need your help. Please and thanks.
I need help. I am very desperate.
Thank you.
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!
Hi, need some advice on restoring my S3 back to stock.
What I've done so far...
Used this guide http://forum.xda-developers.com/galaxy-s3/general/galaxy-s3-i9300-basics-best-performance-t3111802 to install CyanogenMod V11.0(Android 4.4.4)
I have had battery issues and also changed to a new phone, so now would like to restore the S3 back to its original state.
I have followed this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
But so far had no success.
The ROM that thread links to doesn't work for me so have tried to download 2 others
I9300OXAEMG4
I9300OXAGMK6
Having run Odin it gives the following messages:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
Normally just seems to hang at this point, or eventually display failed message.
This is first time I have ever used a Custom ROM on a phone so I am very much a novice at this.
Apologies if this seems a stupid question or if I'm asking the wrong place, just have no idea what I'm doing wrong!
athunder said:
Hi, need some advice on restoring my S3 back to stock.
What I've done so far...
Used this guide http://forum.xda-developers.com/galaxy-s3/general/galaxy-s3-i9300-basics-best-performance-t3111802 to install CyanogenMod V11.0(Android 4.4.4)
I have had battery issues and also changed to a new phone, so now would like to restore the S3 back to its original state.
I have followed this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
But so far had no success.
The ROM that thread links to doesn't work for me so have tried to download 2 others
I9300OXAEMG4
I9300OXAGMK6
Having run Odin it gives the following messages:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
Normally just seems to hang at this point, or eventually display failed message.
This is first time I have ever used a Custom ROM on a phone so I am very much a novice at this.
Apologies if this seems a stupid question or if I'm asking the wrong place, just have no idea what I'm doing wrong!
Click to expand...
Click to collapse
For a start,try diffrent cable and other usb ports on pc.
Sent from my Q10101 using Tapatalk
Sorted!
Seems it may have been drivers?
Had Kies installed but when i loaded it up and tried to connect my phone, i got some files/setup appear that didn't happen before, tried with Odin again and worked.
Thanks for the suggestion Stevica