Hi folks,
I'm trying to unroot my phone, and have attempted to use the latest version of Odin (3.12), and the latest Stock Firmware that I could find. At this point, I've also tried other versions of Odin (3.11, and various versions of 3.12 -- including the PrinceComsy version and other modified versions), and several versions of the ATT Firmware (G935AUCS2APF2, G935AATT4API2, etc.), and I continue to get the same error message "Complete(Write) operation failed." Once, I got the Dismatch error, but that was likely when I used an older version of Odin.
I don't know what to do at the point. The phone is now soft-bricked, and the only way to get it back on is to flash the old root file that I originally used. That file works just fine, but only for a few days before it starts tripping the updates, etc. Now, the phone won't boot past the AT&T logo.
I've googled and read and looked at every forum I could find to see if there is any info on troubleshooting the issue, but I've come up empty. Other people have had the issue, and have fixed their phones. Mine, not so much.
Can anyone help? Please? BIG please?
Related
hello forum,
im new here so sorry if this is in the wrong section!
So my problem starts here, i previously Flashed a custom OS onto my phone, Cyanogen Mod 11, when i got bored of it i decided to download the Stock touchwiz android for my Samsung Galaxy S4 i9505, i proceeded to download Odin307, once i had the OS and Odin i opened Odin in Administrator, i choose my file which was extracted and i used the PDA option to choose it, all was fine until it encountered this error (<ID:0/006> Complete(Write) operation failed.)
once that failed i tried to boot the phone where it says "Firmware upgrade encountered an issue. please select recovery mode ion Kies and try again" SO basically i can still get into the Download mode and can get to the Firmware upgrade error screen, that is all, is there a way to fix it? ive tried countless times to flash the stock touchwiz but get the same error message on odin! Please help!
What is the stock version you tied to flash?
Is the drivers installed and phone get recognised in the ODIN and device manager when in download mode?
Have you mistakenly or intentionally ticked re-partition in ODIN?
Did KIES run in background?
there is lot of threads here on XDA on same problem, try one of those our users have suggested like without closing ODIN and reflashing again.
try with another firmware file or ODIN version. here are some links I thought useful. google would help on searching "complete(write) operation failed".
http://forum.xda-developers.com/showthread.php?t=2516513
Flashing
- I tried to flash the vesion 4.3 for samsung galaxy s4 i9505 telstra.
- yes they get recognised and so odes the phone
- after various tries i tried the re-paritition btu initially i did not, only the auto boot.
- didnt have kies installed at the time of flashing
Thanks for the help, ill try tonight to get it sorted.
Mttogo said:
- I tried to flash the vesion 4.3 for samsung galaxy s4 i9505 telstra.
- yes they get recognised and so odes the phone
- after various tries i tried the re-paritition btu initially i did not, only the auto boot.
- didnt have kies installed at the time of flashing
Thanks for the help, ill try tonight to get it sorted.
Click to expand...
Click to collapse
okay, let us know update. repartitioning with pit file is last resort. its better not to play with it. bt if anything doesn't solve this, repartitioning with PIT file would be the last option to try. bt I would rather go for warranty if you have binary counter reseted.
and if you are trying to flash a rom without knox bootloader on a device that had been on knox this error is occurs mostly.
EDIT: Solution for anyone having the same issues I saw below: Step 3, here:
http://forum.xda-developers.com/showthread.php?t=2281949
I'm not deleting the post since someone else may find this useful unless the mods think this post is noise. I do have one questions for the community: I would like to get to 4.4 and ideally, rooted. Does anyone with one of the first Verizon Note 2's have an experience similar to mine or advice on which route to take? Or should I just stick with OTA and forget root?
I need help getting my phone working. My original goal was to get a modified stock 4.4 ROM + root on my phone. My phone was 4.1.1 until I began this process. I tried to root via exynox, that failed, but using CF-Auto-Root (CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar) worked. I added CWM, wiped data/cache, and tried to install this kernel: http://forum.xda-developers.com/showthread.php?t=2607652 and this ROM: http://forum.xda-developers.com/showthread.php?t=2765021. Similar to some of the messages in the ROM thread, I was stuck at the red screen. I followed krowley3's strategy here: http://forum.xda-developers.com/showpost.php?p=52982544&postcount=41, I Odin'd back to 4.1, unlocked the phone again, got to 4.3, ran saferoot, tried to flash to 4.4, that failed updating the firmware - failed to write sboot.bin.
I tried the suggestion in this thread: http://forum.xda-developers.com/showthread.php?p=39299305 using the VRALJB update to Odin a new PDA. I did get this within the first month of release and didn't take any OTA, so per the warning, I used that version. No luck. Per advice in a thread I'm trying to find again, I Odin'd this PIT: http://www.mediafire.com/download.php?05cj895zu3tls7z, which worked, tried to Odin the bootloader, but that fails at sboot.bin and says: Complete(Write) operation failed.
The status of my phone: it boots into recovery and I can install 4.1.1 stock. It still fails at the sboot when I try a bootloader. When I try to load the firmware, its stuck at the black screen that says "samsung galaxy note 2" and doesn't continue.
In trying to debug, I opened CASUAL-SuckItVerizon-Injection9 while it was loading (to see if it would spit out any logs) and it did something odd: it when I'm on the black screen, it keeps saying 'connected' and 'disconnected' and the adb server connects and disconnects. I'm not familiar enough with debugging these things to dig further. I can't abb to the phone via command line on Windows 7. When I go to Odin mode on the phone, it says:
Product Name: SCH-I605
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
KNOX WARRANY VOID: 0
AP SWREV: A2
Click to expand...
Click to collapse
I'm reading up on this one: http://forum.xda-developers.com/showthread.php?t=2690033, but I'd REALLY appreciate any advice you can give me. At this point, I want a working phone, rooted and at 4.4 (or 4.3) are nice-to-haves.
Sorry if I'm missing something obvious in the stickies - I'm getting stressed right now.
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
BCityModz said:
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
Click to expand...
Click to collapse
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
mattnmag said:
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
Click to expand...
Click to collapse
Ive tried that one as well and almost all the files in that thread. When he flashed the 4.4.2 firmware the phone wouldnt boot all it did was flash the Note 2 screen. Ive used the pit file as well with no luck. Using the top file on the link fails almost instantly, VRAMC3 writes and passes but will not boot, shows the unauthorized firmware screen.
I'm wondering if he flashed a firmware onto the phone that was from a different carrier like ATT or something. If so, he may have messed up the phone so bad that it might need jtag to repair it.
You've probably already tried all the normal Odin tips like using a different usb cable, different ports on the computer (usb 2.0 port is recommended), etc... so I won't go over all those.
I've never tried it and don't know if I'd recommend it, but I recall reading some threads a while back where someone discussed trying the Nand Erase function in Odin.... (again.... I'm not saying to do that... but you may want to research it to see if it might be an option if nothing else works).
I've also read where people say that they've used Cygwin to create custom tar files... then they ODIN installed each of the separate partition files (e.g. recovery, boot, modem, system, etc...), onto their Samsung device.
I'm not knowledgeable enough to offer guidance with Cygwin and I'm not sure if either of these ideas would work, but I just thought I'd throw them out there for the sake of brainstorming for ideas. Maybe someone will respond to your request who has more knowledge and ideas.
I wish you luck with getting it fixed.
PROBLEM SOLVED: Downloaded newer version of Firmware and that worked. I feel super super dumb for not thinking of that sooner. I was following an older guide to unroot/restore to stock and the newest available link was VREUMJ9 and apparently that was too old.
I'm trying to send my Galaxy Note 2 in for warranty. It had accepted 4.3 OTA but I had rooted it afterward. So I went to restore to stock and unroot so I could send it in. I had just recently done another Note 2 (My dads) back to stock without a hitch so I figured it would be no big deal. Except I forgot one minor detail that his phone didn't take 4.3 OTA and still had unlocked bootloader. So I opened up Odin 3.07 and put PIT file in PIT and VRAMC3 firmware in PDA and hit start and the flash failed. Took me a few seconds to realize that I flashed the wrong firmware and should've been VRUEMJ9. I was panicing and downloaded VRUEMJ9 and attempted to flash that and it wouldn't even start the flash just failed right away. Now ODIN isn't even recognizing the phone anymore. Am I totally screwed here? I've been googling furiously and it sounds like maybe cause I selected a .PIT file it may have hard bricked my device? I just instinctively did that because it was required to make it work correctly on the last phone I did just a few weeks ago.
I can still access download mode but ODIN doesn't show anything in COM window. Trying to boot phone normally shows "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again" I've tried repeatedly restarting phone and rebooting PC and reinstalling USB drivers. Is "Software Repair Assistant" something I should try? It sounds like Verizon's version of ODIN? http://www.verizonwireless.com/support/knowledge-base-80201/
Any help GREATLY appreciated. I really really really don't have the money to pay full price for this bricked phone Assuming I can't get this fixed and I just send them the phone as-is what are the chances they even notice? Do they test them?
I managed to get ODIN to recognize the phone using a different computer. Upon attempting to flash VRUEMJ9 in PDA of ODIN this happens: http://imgur.com/2msfTEQ
Firmware update start..
sboot.bin
NAND write start!!
FAIL!
All threads completed. (Succeed 0 / Failed 1)
This happens whether I do just the firmware or firmware + PIT. Flashing PIT by itself will succeed and the phone changes to a message saying something about unsupported software and to turn my phone off and take it to Verizon. But it doesn't seem to change anything cause flashing FW still doesn't work. Almost identical error message using ODIN 3.09 figured I would try a newer version of ODIN.
Edit: After reading some more. It sounds like I might have a corrupted NAND which from what I read is only fixable by replacing MB. Is this true? If so how much would it cost to get repaired if I went to a samsung service center?
I have a SCH-1545 model galaxy s4. I posted about this already on a year old thread so I thought I'd try a new thread entirely. I also see that many people have this issue with my particular model. Odin fails at aboot.mbn. It just says failed. I'm using the .tar (SCH-I545_MDK_562219_Stock_Restore.tar.md5) file to flash to. Is this the latest build? I was using Odin3 v.1.85, is that the latest version? I assumed as much when following the youtube tutorial video. I'm a newbie at all this and would appreciate all the help i can get. I got tired of all the failed update messages I'd get when I had the custom rom and now the phone won't boot normally or in recovery mode.