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.
Related
I have a Verizon Samsung Galaxy S4 (SCH-I545) which I previously rooted via the Open1Your1Eyes0 pwn script. Everything was great except I wanted to update to the latest version and my phone failed with each attempt. I tried to unroot it using Odin to flash the VRUAMDK_NoWipe.tar.md5 stock ROM image.
That failed and now it's stuck on the ODIN MODE "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message screen. The phone won't boot. If I hold Vol Down I can still go to the Downloading firmware screen, but I've tried flashing 3 other stock ROM's and nothing will work.
Any suggestions?
Not 100% sure as to whether this will work but I had this happen to me about 2 months ago and I THINK it was the "Full Wipe ( AKA Emeregency Repair)" file from this thread: http://forum.xda-developers.com/showthread.php?t=2735172 that fixed it. Also since it says Emergency Repair as Kies would if you could fix it using that I assume its for this purpose, may be wrong though but worth a shot. I'd probably be more help if i wasn't like brain dead atm but once it goes away i'll re-think this and if i decide I gave you incorrect advice i'll edit this or post again with the correct information.
Anyways just follow the instructions there on the Full wipe one and report back if it works. Quite confident it will but as with anyone I could be wrong. NO GUARANTEES
waffleking said:
I have a Verizon Samsung Galaxy S4 (SCH-I545) which I previously rooted via the Open1Your1Eyes0 pwn script. Everything was great except I wanted to update to the latest version and my phone failed with each attempt. I tried to unroot it using Odin to flash the VRUAMDK_NoWipe.tar.md5 stock ROM image.
That failed and now it's stuck on the ODIN MODE "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message screen. The phone won't boot. If I hold Vol Down I can still go to the Downloading firmware screen, but I've tried flashing 3 other stock ROM's and nothing will work.
Any suggestions?
Click to expand...
Click to collapse
Before you flash MDK, you first have to know what build and bootloader you're on. Apparently you're not running a MDK bootloader, and consequently can't flash MDK.
What baseband and bootloader did you start from? If you don't know, then why did you choose to flash MDK?
S1L3nTShaDoWz said:
Not 100% sure as to whether this will work but I had this happen to me about 2 months ago and I THINK it was the "Full Wipe ( AKA Emeregency Repair)" file from this thread: http://forum.xda-developers.com/showthread.php?t=2735172 that fixed it. Also since it says Emergency Repair as Kies would if you could fix it using that I assume its for this purpose, may be wrong though but worth a shot. I'd probably be more help if i wasn't like brain dead atm but once it goes away i'll re-think this and if i decide I gave you incorrect advice i'll edit this or post again with the correct information.
Anyways just follow the instructions there on the Full wipe one and report back if it works. Quite confident it will but as with anyone I could be wrong. NO GUARANTEES
Click to expand...
Click to collapse
I got it working using the Full Wipe instructions you linked to. THANK YOU SO MUCH!
Hi there. I am trying to flash a stock rom to my gs5 900a with heimdall on my mac. the device is detected but i cant seem to download the pitfile it says claimed interface error. I think its because i system wiped my phone with safestrap when i was trying to intall a custim rom. anyhow I am softbrick state now. i cant get passed samsung galaxy window with the lock. myphone was also unlocked to use metropcs and it was also rooted. any information out there could that would help would be appreacited. thank you very much.
Leandrozx said:
Hi there. I am trying to flash a stock rom to my gs5 900a with heimdall on my mac. the device is detected but i cant seem to download the pitfile it says claimed interface error. I think its because i system wiped my phone with safestrap when i was trying to intall a custim rom. anyhow I am softbrick state now. i cant get passed samsung galaxy window with the lock. myphone was also unlocked to use metropcs and it was also rooted. any information out there could that would help would be appreacited. thank you very much.
Click to expand...
Click to collapse
The pit file isn't the cause of that particular error. It's a problem with the drivers installed by Kies, which interfere with Heimdall. More info can be found here:
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
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?