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.
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.
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> 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!
<OSM> All threads completed. (succeed 0 / failed 1)
ArcelasTheNoob said:
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I605_VRALJB_Restore.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
NAND Write Start!!
cache.img
hidden.img
modem.bin
FAIL!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hey bro, have you unlocked the bootloader? if so and you're trying to go back to stock try the alternative stock odin file from imnuts.
EDITuno: http://www.androidfilehost.com/?fid=9390225151984927096
theres the link to his alt restore odin package. idk if that'll help fix the modem.bin failure, but it should help someway. hope it does! if you need anymore help you can pm me if you need to.
I'm curious to what rom you flashed. Was it for a Verizon note 2? If you get no network, try flashing the modem in recovery. That should solve it
Link for modem download.
http://www.androidfilehost.com/?fid=22946563261203878
Follow droidstyle's guide. Read his thread.
http://forum.xda-developers.com/showthread.php?p=34891181
EDIT: Just realized you are making multiple threads for the same question. Sorry dude, that's my only rule. No more help. Also noticed that you flashed an international rom. Good job :thumbup: This is why you are supposed to READ before flashing
Sent From My Sticky Note, Too?
Not needed
I apoligze if it looks like I posted this question multiple times. I was told to post in a different forum, but figured more info=better.
I returned my phone to Best Buy, replacement in a few days. So thank you for all the help, next time I'll be more careful.
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Deleted cause by my noob. Sorry
Sent from my Nexus 7 using Tapatalk
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thought this was the Mega forum? And yes I know about knox I bricked an S3 because of it but I didn't think it was added until 4.3?
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
jk0l said:
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
Click to expand...
Click to collapse
I'm not using it as a phone anymore, just kinda as a tablet. So does it matter that it isnt the r960 firmware?
vBIGLEWISv said:
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try with samsung kies to revert back to stock..See it helps or not.
Carnage said:
Try with samsung kies to revert back to stock..See it helps or not.
Click to expand...
Click to collapse
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
I am also found ths problem. Kies also not working... Bad experience..
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
vBIGLEWISv said:
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
Click to expand...
Click to collapse
Are you really cannot boot into download mode?..vol down+power button..try power on the device,remove the battery,put it back again,and quickly press the download mode combination keys (vol down+power button) see it boots to download mode or not..if its boot, grab your latest firmware and flash it via odin. About the kies,try to uninstall and download the latest version of kies solve it..
EDIT:I have search your firmware and don't find any link.you have to wait until the firmware for your specific model number released by Samsung.
hopsin4444 said:
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
Click to expand...
Click to collapse
Thats the problem the stock firmware doesnt exist for my phone or at least I cant find it.
well then, thats unfortunate. im sorry.
so its certain that theres no way for you to go back to stock.
edit:
actually, try to wipe data and cache in recovery then reboot.
if it still bootloops, then I recommend you patiently wait until the stock firmware for your phone is released.
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 Guys, I'm new on this forum but I really need someone's help.
So, Last week I've bought Samsung s4 from the internet, it turned out to be SCH-I545 Verizone with 4.4.2 android. I didn't have menu in my language (Polish) so I decided to install 5.0.1 and that was my biggest mistake. Now my phone doesn't see my SIM card from T-mobile, I don't have Polish language at all, I have lots of useless Verizone apps, and I would like to get back 4.4.2 or install custom ROM where I could find Polish language. The problem is I have no idea how to do this, because I only know how to install softwares by ODIN. I've read a lot about this and the problem is I can't install custom recovery because it says FAIL at the end, I can't root my phone and I don't know why, i've tried towelroot, kingoroot and others but they all doesnt work. Can You please tell me what should I do or give my some links with instruction because I'm helpless and please I'm layman in this topic so it must be written like for someone who is 5 years old. . . Thank You in advance, I hope there is some solution for my problem. .
Go to network mode and select global...i535 are sim free. Just change what i said.
I did it and i can phone but internet doesn't work, I still prefer to change this software for some other. Can You help me with that ?
Go to sammobile download the room for your device. Flash via odin do factory reset bcoze you gona stuck in bootloop.root the phone install totalunistaller and remove bloatware
lummujaj said:
Go to sammobile download the room for your device. Flash via odin do factory reset bcoze you gona stuck in bootloop.root the phone install totalunistaller and remove bloatware
Click to expand...
Click to collapse
which ROM? I have 5.0.1. Flash it again ? I still wont be able won't be able to do ROOT like it is now.
Still waiting for some solution how to flash other soft ( I cant do root right now !)
Youve search button in samfirmware and search for i535 firmware.find the 4.4.2 firmware and download it. And search how to disable software update to remain in 4.4.2
lummujaj said:
Youve search button in samfirmware and search for i535 firmware.find the 4.4.2 firmware and download it. And search how to disable software update to remain in 4.4.2
Click to expand...
Click to collapse
i can't make downgrade.. this is what I get in ODIN:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
whats wrong ?