Looks like the rollout today came in 2 updates. I downloaded the first and installed with no problem but the 2nd which actually puts in lolipop can't install. It says error 402, google/the Verizon forums doesn't have any info on it.
I have the same issue. I have tried Wifi and the Verizon Software Assistant download, and neither works. I am on the hunt for any suggestions as to how to get past this. Since I have just Factory Reset my phone, I will try pretty much anything.
I had 402 error. I downloaded I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar from here:
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Extract the .tar file
Install with Odin v3.09+ (put the .tar file in AP slot) and put phone in download mode
It will keep all data.
After reboot install both updates again.
do_9999 said:
I had 402 error. I downloaded I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar from here:
http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613
Extract the .tar file
Install with Odin v3.09+ (put the .tar file in AP slot) and put phone in download mode
It will keep all data.
After reboot install both updates again.
Click to expand...
Click to collapse
were you able to root after the updates?
meazz1 said:
were you able to root after the updates?
Click to expand...
Click to collapse
Negative. But I knew that before.
If you're having trouble with the Odin portion of this, check to see if you're using USB 2.0 or USB 3.0 port. My issues seemed to be directly related to using 3.0. No idea why, or whether or not this is a known thing but I'm Odin-ing successfully right now. I'm leaving the "struggle" report in case it might help somebody who has gone through the same process unsuccessfully. Cheers
Followed the Odin instructions. Get a Fail. Using original cable. Here's the log:
<ID:0/003> Added!!
<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> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I made it to NK4 on the OTAs so maybe flashing NK1 won't work? Gonna try the NG6 and NK1 FULL WIPE Odin file. (found here: https://www.androidfilehost.com/?fid=95916177934540736)
The good news is that I can still get into download mode after a battery pull so I'm just going to try and find another Odin file.
Tried using a Pit file given there's no partition. Didn't work. Looks like I've got a morning of thread crawling to look forward to.
As crazy as this might sound, I found the answer for me on Verizon's actual forums from a Verizon customer service rep! That NEVER happens. I almost entirely dismissed it. He told someone asking about this problem, "If that doesn't work, the manufacturer has another way to install the update." I thought that sounding interesting. The link took me to Samsung Kies (an app for the PC) and there you have a choice to install either Kies or Kies3. For some reason it suggests we need Kies, but Kies3 is actually what we need as our S4's have been updated beyond when this site was created.
After installing that, the app TRIES to suggest that we're better off with Smart-something or other, but that's just for transferring contacts and such between two phones. Ignore that and just connect your phone via cable to the PC and Kies will see it and tell you there's an update. It then installed the update without a hitch!
What's amazing is that I also own a Samsung Galaxy Note Pro (the 12.2 inch tablet) that had some issues. However, it would never say there was any sort of update and I could never find one mentioned online. Kies said there was one and installed it. Now the tablet's snappier and better than ever. What a surprise find....
Agrajag27 - OMG, thank you very much! That worked, simple update, and I am on lollipop! Great find!
Related
Hello,
I have a problem unrooting/unbricking my Galaxy S4 for Verizon. I followed step-by-step processes and it seems to not work properly for me. I downloaded "Odin3 v.1.85" and the stock firmware, "GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip" and "SCH-I545_MDK_562219_Stock_Restore.tar.md5" for Verizon. I put my phone into the Download Mode and began the process of unrooting using Odin. I made sure that my device was connected. I clicked PDA and chose the stock firmware for my phone. I clicked Start and it begins. As soon is it begins, it says it is not responding, but I wait a few seconds and it responds. After that, it continues where it left off for the unrooting process. The process turned out to be a fail. Here's the message:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It has failed and when I attempt to reboot my phone, it gives me a message that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I attempted the Kies process, and it would not connect my device to Kies. Please help. I feel as if I were the only user with this problem. Thank you.
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Seems like it's tough luck for me. What do you suggest I do? Did you resolve any of your similar issues?
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
goosedaddy said:
yep. I only wanted to make sure you did install the update or otherwise some of the 32gb s4 come with it preinstalled.
just saying this because updating to me7 is irreversible you wont be able to flash roms right now only apply a root
download the me7 md5 this time and do all the same steps I followed this guide
http://forum.xda-developers.com/showthread.php?t=2301259
hope this helps
Click to expand...
Click to collapse
Alright. I'll follow these steps and I'll get back to here and let you know. Thank you.
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
MattLife said:
I'm in the process of downloading the ME7 you told me about, but isn't this rooting my phone? I want to reformat my phone and have everything wiped out.
Click to expand...
Click to collapse
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
goosedaddy said:
nope its a stock image so everything will be like when you first got it. not sure if some data will be there but you will not be rooted.
the root process is here http://forum.xda-developers.com/showthread.php?t=2381382
Click to expand...
Click to collapse
This really helped me! Thank you so much! It's been fixed.
MattLife said:
This really helped me! Thank you so much! It's been fixed.
Click to expand...
Click to collapse
Awesome! Glad it all worked out.
help
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
gregorykbrownjr said:
Trying to unroot and revert to stock and I have soft bricked my galaxy s4! The charging port is gone so I cannot use a computer to fix this...I have searched everywhere for help and am stuck! Anyone have any suggestions???
Click to expand...
Click to collapse
if you can't get the usb port (charging port) to work with communicating to your computer then there really isn't much you can do. Have you tried cleaning the contacts off inside the port? Are you sure its NOT the cable?
This has been talked about somewhere else here in this forum
Same problem
goosedaddy said:
sounds like you were already on v7 baseband try getting that stock image and go through odin.
because you cant go back to the original baseband (which is the md5 you listed) but I had similiar issues.
Click to expand...
Click to collapse
Hey I have the exact same issue but with the international LTE galaxy s4 do you have any idea what i can do i have put the GPE rom on this and i found that flashing TWRP when it gave me the kies error bought me back to my GPE rom i'm going to sell this phone and i need to return to stock firmware should i try a new computer or something else please help me i've been really scared, i would appreciate it if you can help me in any way.
Hello, I hope someone can help me out here, Samsung's online help sure wasn't a big help. Trying to get my hands on the stock image for the SGH-i857 a got a little over zealous trying to clear out some of the stock APKs and was hoping to roll it back to stock.
If you have a windows machine try downloading Samsung Kies with your DoubleTime connected. Try to update the firmware/software and it should revert it back to stock.
I do have an Odin flashable I can give you if that doesn't work, but I would compress it with 7zip in order to put it on the Forum.
Legojr said:
If you have a windows machine try downloading Samsung Kies with your DoubleTime connected. Try to update the firmware/software and it should revert it back to stock.
I do have an Odin flashable I can give you if that doesn't work, but I would compress it with 7zip in order to put it on the Forum.
Click to expand...
Click to collapse
I did try the kids method with no luck, I would love to try the Odin flash for the phone. If you don't feel like uploading it to the forums I'd be happpy to PM you my gmail.
Here is the link: https://www.dropbox.com/s/p3dj426vdav4nsp/I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5
I had to put it on Dropbox because it was so big.
It is recommend that you use Odin v1.85, this however is not tested. I might be testing it soon though.
To put a DoubleTime into download mode you need to hold the volume up and powerb button at the same time from a completely off state.
I wish you luck.
Has anyone found a way for fully flashing the double time to stock? I accidentally flashed an update.zip file from another phone and now wifi and bluetooth are not working. Hopes fast answers-
migui0401 said:
Has anyone found a way for fully flashing the double time to stock? I accidentally flashed an update.zip file from another phone and now wifi and bluetooth are not working. Hopes fast answers-
Click to expand...
Click to collapse
Really? The thread has 4 other posts and the one right above yours has the file you need.
es0tericcha0s said:
Really? The thread has 4 other posts and the one right above yours has the file you need.
Click to expand...
Click to collapse
Man, i don't if you're up to date, but the double time has a firmware problem which conflicts with download mode and it's almost impossible to flash it. That's why my question, have you been able to flash? Please, i need help.
PD: i have the stock firmware and have used almost all compatible odin versions with this device without success.
migui0401 said:
Man, i don't if you're up to date, but the double time has a firmware problem which conflicts with download mode and it's almost impossible to flash it. That's why my question, have you been able to flash? Please, i need help.
PD: i have the stock firmware and have used almost all compatible odin versions with this device without success.
Click to expand...
Click to collapse
They don't sell the Doubletime around here, so wouldn't have a way to be up to date with it. Why don't you describe what's happening via Odin when trying to flash instead of just saying it didn't work, which is not very helpful.
es0tericcha0s said:
They don't sell the Doubletime around here, so wouldn't have a way to be up to date with it. Why don't you describe what's happening via Odin when trying to flash instead of just saying it didn't work, which is not very helpful.
Click to expand...
Click to collapse
This all what happens in odin, it stays stuck on Setup Connection...
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
migui0401 said:
This all what happens in odin, it stays stuck on Setup Connection...
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I857UCKI1-I857UCKI1-I857UCKI1-HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
Click to expand...
Click to collapse
I didn't realize that the Doubletime was an ATT phone. Have never seen one or had one brought by my shop. *shrug* Is yours ATT branded or GoPhone? It's possible the firmwares aren't compatible between the different versions... Or that being of that vintage Samsung, maybe the program Heimdall might have more luck a la the Samsung Galaxy S 4g from T-Mobile.
Is the version you are trying to install as newer or newer than the current firmware found on the phone?
Tried different cords?
Different ports on the PC?
Does it show up once or twice in the COM boxes of Odin?
Are you running Odin as admin?
Edit: Found other posts on other forums where it gets stuck at the same step, so guess it's a thing. Found in both Chinese and Spanish phone forums.
es0tericcha0s said:
I didn't realize that the Doubletime was an ATT phone. Have never seen one or had one brought by my shop. *shrug* Is yours ATT branded or GoPhone? It's possible the firmwares aren't compatible between the different versions... Or that being of that vintage Samsung, maybe the program Heimdall might have more luck a la the Samsung Galaxy S 4g from T-Mobile.
Is the version you are trying to install as newer or newer than the current firmware found on the phone?
Tried different cords?
Different ports on the PC?
Does it show up once or twice in the COM boxes of Odin?
Are you running Odin as admin?
Edit: Found other posts on other forums where it gets stuck at the same step, so guess it's a thing. Found in both Chinese and Spanish phone forums.
Click to expand...
Click to collapse
-Odin always opens with admi rights.
-Yes, i've tried all ports on my pc.
-It's the same firmware.
-It shows just once in COM BOX.
Can you help?
Doesn't seem like there is a readily available solution, as your issue seems to be shared by others without any posted fix I could find here, or in the other phone forums. Sorry. Like I said earlier, you could try the Heimdall tool, but other than that, haven't the slightest. Older Samsungs suck because of issues like this - limited Odin support. Have you tried Kies too?
Hello to all the devs in the forum and thanks in advance for the help that you will give me. Please bear with me, trust me I have made sure that seeking for help was my last resort seeing as I don't want to be just another guy with a bricked phone problem. Fortunately the forum has been quite educational and I have all you guys to thank you for that.
Now then, last night I decided to root my phone because it was running a bit slow and decided it was time to do it.
Everything went fine, I managed to root it successfully, installed Clockwork Recovery and all that, although when it said that backing up the image I think was an error, I sort of just disregarded it. I booted up my phone and everything is fine, I installed Titanium Backup Pro and deleted some of the bloatware that was in my phone.
Now this probably where my phone got on its way to being bricked.
Along with the bloatware that was deemed safe on the website, I also mindlessly uninstalled the Samsung Home and probably the stock keyboard app.
I deemed them unnecessary because I was running Go Launcher EX app as my launcher and Swiftkey as my keyboard app.
What I didn't know is that all the custom roms are probably going to be using those stock apps as base. Did I assume this correctly?
So then I tried to flash the custom rom that I found appealing, followed the steps in the guide that accompanied it, and when rebooted it, it was stuck in the Samsung logo screen.
Fortunately I planned ahead a bit, although not as much as I'd hope for, I knew that I can restore through CWM but unfortunately, the restore point that it created presented with an error and I can't restore it.
So I resorted to flashing a stock rom through ODIN and followed the steps in unbricking the phone.
I encountered some difficulties with regard to the drivers and all that but I managed to have the correct ones installed.
Now comes the final problem
As I am trying to have ODIN flash the stock rom, it wouldn't continue as it does in the videos that I watched. It would always stop in about 10 seconds and say that it failed.
I tried another stock rom from a different location and it still wouldn't work.
I have also run ODIN as an administrator, and this presented:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iDXMC1_S5830iOLBLD1_S5830iDXMC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> BcmCP.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Again it only took about 10 seconds to stop.
I am running ODIN 3 v1.85
I have also uninstalled KIES.
Whenever I would cleared all the cache and mount everything sometimes it would bring me to the android setup at startup, but if I try to type there is no keyboard that would popup. And if I choose skip it, it's just black, but if I lock it, the blue stock lockscreen appears. Nothing else after that.
I decided to post as a last resort and knowing that I have done all in my ability to repair it.
So there it is, I tried to be as specific as possible to the things that I have done throughout the day,
A couple of solutions I found as I searched was to try to flash a stock rom through CWM, another suggested to use a different version of ODIN.
If someone could please point me to the right direction as to how to repair my device, it would be hugely appreciated.
Thank you very much for your time.
UPDATE: While I'm writing this I tried the latest version of ODIN and it still won't work. Same issue. Please help
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Hitesh2626 said:
See first of all Split the Firmware into 3 Parts PDA & MODEM & CSC then use pit file also ..
Ok now follow these
1.Go into recovery mod do wipe data/Cache
2.Get into CWM again do wipe data/cache
3.Now take down it into download mode and flash the Stock firmware .
Hope these works .
Click to expand...
Click to collapse
Hello Hitesh! Thank you so much for your correspondence. I've been seeing your consistent replies to people who have the same problem as I had.
As for my phone, I managed to unbrick it yesterday by flashing a different custom ROM through CWM. I am currently running Extremis 2.1 from destructo570
Again thank you very much for your help.
As an advice to anyone who will have the same problem in the future, make sure that before you install a custom ROM to clear the cache and all that. Good luck!
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Incaendium said:
I tried to flash SCH-I545_MD2_423399_Kernel.tar onto my Galaxy S4, and it said boot.img Fail. I have a SCH I545 and I have been looking everywhere for a fix but this is sort of a last resort. Does anyone know what do to? Thanks in advance.
Click to expand...
Click to collapse
Was your S4 on the MDK bootloader/release before you tried flashing the MD2 kernel with Odin?
If it was NOT on MDK, then you can't root using that method; you'll need to flash the MK2 Odin tar from here: http://forum.xda-developers.com/showthread.php?t=2578209
And then root using saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
You will not be able to install TWRP/CWM on a non-MDK S4.
bleh
I have already rooted, the problem is that I can't flash and custom ROM's, This is exactly what happens whenever I try to flash anything onto my device.
I will put it in PDA or its specified placement, and make sure everything that is needed to be checked is checked, then I will press start.
Odin will proceed to fail at boot.img, and I will then get frustrated.I can't send you a link to a screenshot yet, so if you want one I might be able to send you it in a private message, just let me know.
Along with the full message that Odin gives me <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.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>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I had to use a different MD5, but this is exactly what happens with everything.
When and where did you buy your S4?
I bought it at Verizon about a month or two ago
You can't flash a custom recovery on it at all then, only the first S4s bought around when it was released and then never updated can have custom recoveries.
If your phone won't boot (now or in the future), you'll need to flash the MK2 Odin tar from the thread I linked to restore it to stock.
Your only option for flashing roms will be safestrap, and only TouchWiz-based roms will work.
Safestrap: http://forum.xda-developers.com/showthread.php?t=2441441
Compatible roms: http://forum.xda-developers.com/showthread.php?t=2634408
Any reccomendations? I have never seen these.
Incaendium said:
Any reccomendations? I have never seen these.
Click to expand...
Click to collapse
If you want AOSP, Eclipse is probably the closest (themed) you can get to it: http://forum.xda-developers.com/showthread.php?t=2351840
Otherwise maybe try Bonestock, BajaROM, Hyperdrive... find whatever you like best.
Nevermind again, how do I install a rom using safestrap
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Incaendium said:
Alright so I did a data wipe atempting to open up a rom slot, but I couldent get enough storage open so I just rebooted. Now my phone is stuck on the samsung custom screen that you get after you try to reboot. Did I just brick my phone?
Click to expand...
Click to collapse
You may or may not have bricked it. To me though it sounds like you may just want to start fresh and Odin MK2 back on your phone.. Use Saferoot, then install SafeStrap.
I'd suggest saving anything you don't want to lose and use the full wipe Odin image.
A fresh start sometimes is just the way to go. You can of course fiddle with things and see if that's not needed... But that's what I would do
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
I'll cut to the chase, I own a Verizon Samsung Galexy S4.
It's rooted, and I used Eclipse rom, but I wanted to update to Lollipop.
So I flashed the stock SCH-I545NC5 4.4.2 and everything was fine.
Now, I used software update and it would download, restart, and give me the "failed to download/update" etc. error ( I have figured out later that this was due to me still being rooted.)
Anyway, I then tried to use Kies3 and everything was going great.
It restarted annnnd boom, I get the firmware failed to update screen with the exclamation point telling me to use emergency repair. So I did. Aaand that fails every time too... so I did some searching and finally found the SCH-I545NC5 factory rom tar.md5 file for Odin.
I have all of the drivers and everything, and I have used Odin3 before to update this phone without trouble.
But now whenever I try to flash stock it gives me this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.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
It prints all of that out in a second or less...
I then got the .pit and tried that, it will stay at getting pit for mapping for ~5 minutes or more.
And that's where I am now... I'm at my wits end, can anyone help?
Many people say that using a different USB port or a different cable might work.
GDReaper said:
Many people say that using a different USB port or a different cable might work.
Click to expand...
Click to collapse
Well, that didn't seem to work :/
Does anyone know if I would be able to take this into a Verizon store to get help? or if they would refuse due to root?
yeronix said:
Well, that didn't seem to work :/
Does anyone know if I would be able to take this into a Verizon store to get help? or if they would refuse due to root?
Click to expand...
Click to collapse
If you want your warranty rights, then they might refuse it.
GDReaper said:
If you want your warranty rights, then they might refuse it.
Click to expand...
Click to collapse
Well I don't have a warranty.. I have heard they can flash there to fix(?) stuff... would that work, would they even do that?
yeronix said:
Well I don't have a warranty.. I have heard they can flash there to fix(?) stuff... would that work, would they even do that?
Click to expand...
Click to collapse
Well, since you're paying, they will certainly try, I guess.
GDReaper said:
Well, since you're paying, they will certainly try, I guess.
Click to expand...
Click to collapse
Well alright then.
Do you know of anything else I could try? I've tried a different cable, other ports, and another computer at this point.
yeronix said:
Well alright then.
Do you know of anything else I could try? I've tried a different cable, other ports, and another computer at this point.
Click to expand...
Click to collapse
To be honest I am not very familiar with Odin problems. I just suggested what I saw on other threads.
I also stumbled upon a similar error when I tried to flash a stock rom.
Well good news is it's working! I had been flashing NC5/NK1 thinking that's what I needed. Not the case! I tried flashing the latest GOC1 and it worked!!!!
I also uninstalled Kies3 and disables my antivirus, I think that played a large part in it.
Yes, Kies messes with Odin if they both run at the same time.