I think I may have fired my phone.. late last night I was using http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-safestrap-access-odin-t3120483 and I never installed safestarp and flashed the kernel so now my phone only boots to a yellow triangle and says "this is old binary, please update" and under it in red caps says secure fail: Kernel... I feel like I messed up..... this is my only phone and I just and stumped.. Is it just a paper weight now? I was on 5.0.1 and I was rooted...
lucask1018 said:
I think I may have fired my phone.. late last night I was using http://forum.xda-developers.com/galaxy-s4-verizon/general/guide-safestrap-access-odin-t3120483 and I never installed safestarp and flashed the kernel so now my phone only boots to a yellow triangle and says "this is old binary, please update" and under it in red caps says secure fail: Kernel... I feel like I messed up..... this is my only phone and I just and stumped.. Is it just a paper weight now? I was on 5.0.1 and I was rooted...
Click to expand...
Click to collapse
I545VRUGOC1_Neutered_Full_Odin.tar.md5 I ALSO TRIED TO ODIN THIS AND IT JUST FAILS. <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUGOC1_Neutered_Full_Odin.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> 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)
and my phone reads
sv rev check fail fused 7 binary 8.... can anybody help me?/..
If you are on OC1 you should have read the disclaimer on the page to which you linked. The file you flashed is not for OC1
Before I can help I have to ask questions. Are you on a keeproot version of 5.0? (NOT OTA). Did you take the OTA for lollipop?
Matthew M. said:
If you are on OC1 you should have read the disclaimer on the page to which you linked. The file you flashed is not for OC1
Before I can help I have to ask questions. Are you on a keeproot version of 5.0? (NOT OTA). Did you take the OTA for lollipop?
Click to expand...
Click to collapse
no I the ota 5.0.1 youre right I should have read it...... im downloading the oct 5.0.1 firmware off samsmobile right now do u think ill be able to odin that, or do u think my phone is screwd? im lost honestly..
lucask1018 said:
no I the ota 5.0.1 youre right I should have read it...... im downloading the oct 5.0.1 firmware off samsmobile right now do u think ill be able to odin that, or do u think my phone is screwd? im lost honestly..
Click to expand...
Click to collapse
The only reason the file you attempted to flash in odin earlier was because it wasn't the right file for your installed firmware. If you can find an SCH-I545 OTA 5.0.1 file to flash then that is your best bet.
Matthew M. said:
The only reason the file you attempted to flash in odin earlier was because it wasn't the right file for your installed firmware. If you can find an SCH-I545 OTA 5.0.1 file to flash then that is your best bet.
Click to expand...
Click to collapse
im downloading the 5.0.1 from sammobile do u think this will work? and why didn't the other one work? I was trying to flash this md5 file called I545VRUGOC1_Neutered_Full_Odin.tar.md5... shouldn't that work?
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Matthew M. said:
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Click to expand...
Click to collapse
im going to work right now but I will try to odin the files from sammobile wheni get home and ill let u know wassup im praying
Matthew M. said:
There is a difference between the Ota and the non Ota 5.0.1, the qfuse counter and some other stuff which prevents you from downgrading. I would only think that it didn't work because of the difference. I can't guarantee anything will work but it's worth a shot since you can't even use the phone atm
Click to expand...
Click to collapse
the update from samsmobile didn't work so I think im ****ed . my fault but it sucks
acutally I got it to work and it is downloading as we speak. hope it goes through half way as we speak
Related
I was on MI1 rooted, I flashed the factory MI1 back to my phone via odin so I could download the update OTA.
The downloaded the update, it installed and my phone rebooted. On the reboot, I got a message saying the "UIDs on the system are inconsistent" but that was covered by non-stop failed processes. Every time I clicked okay, more processes would fail, leaving the phone unusable. I plugged it into my computer and using Verizon Repair assistant I try to do a factory restore. The restore stopped at 83% and said "device unexpectedly unplugged" and would not go any further.
I have tried several times to do a restore but without any luck. The phone will only boot to a "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE" then it tells me to connect to kies. It will not boot into recovery and KIES will not allow me to access the "firmware upgrade and initialization" because i cannot find a serial number. I spoke to a verizon rep, they gave me a serial number, it didn't work.
Any ideas? I have tried to ODIN the MI1 again, but it fails:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The phone's screen says: CHECK FAIL FUSED 5 BINARY 4
anyone have any thoughts?
Is there a .tar out for the new MJ7 update? maybe i could flash that?
You Sure you grabbed the ml1 image? When trying to flash a previous firmware (which you cant do) it fails at aboot like yours did.
Edit:
Nevermind I now see you did after re reading your post. Havent seen an mj7 download mode image but someone posted the update.zip for stock recovery.
villainous said:
Is there a .tar out for the new MJ7 update? maybe i could flash that?
Click to expand...
Click to collapse
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I've checked the MD5 and it matches, I've tried several different versions of MI1.
When I connect to the Verizon Repair Wizard, it shows my version as MI1, however I did install the OTA update today, shouldn't it say MJ7?
Also, since I installed the update, when I try to ODIN MI1 it should fail, is there any way to do a recovery any other way?
Ideally i would like a flashable MJ7 tar file
It is frightening how upsetting it is to be without a phone.
Verizon is sending me a replacement, but any help in recovering this phone so that I can retrieve my files would be greatly appreciated.
villainous said:
Verizon is sending me a replacement, but any help in recovering this phone so that I can retrieve my files would be greatly appreciated.
Click to expand...
Click to collapse
I think you'll need to wait for a mj7 tar file. Your Odin output shows "fused 5" which I think means mj7 loaded far enough to blow a qfuse.
jd1639 said:
I think you'll need to wait for a mj7 tar file. Your Odin output shows "fused 5" which I think means mj7 loaded far enough to blow a qfuse.
Click to expand...
Click to collapse
What is the usual wait time for these files to become available after it is released from Verizon?
i have a galaxy s 4 verizon i have mdk and i have tried unrooting it because my friend tried rooting it while i was gone and messed up the process but im using odin3.07 and im getting this.
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
my phone says start [224,1440]
sw rev. check fail : fused 5, binary 1
and ive tried 2 other stock files and i still get the same thing i even tried a Me7 to please help
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_u ser_low_ship_MULTI_CERT.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> 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/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> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im using Odin v1.85
this what i get from trying mdk and me7
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
he said he followed this youtube video https://www.youtube.com/watch?v=uii_mYm8IGE
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
A1C_Malone said:
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
Click to expand...
Click to collapse
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
scryan said:
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
Click to expand...
Click to collapse
where can i download mj7 or mk2 stock i have a verizon s4
Sounds like you may want to follow this... If a newer firmware was attempted to be flashed..http://forum.xda-developers.com/showthread.php?t=2579278. IF NO LONGER MDK AVAILABLE FOLLOW THOSE STEPS.
A1C_Malone said:
where can i download mj7 or mk2 stock i have a verizon s4
Click to expand...
Click to collapse
use Kies and get a factory clean install
Hello.
I usually don't post on forums but, I'm having a heck of a time trying to get this resolved. I don't know if this has already been addressed in a thread but I am having a hard time getting my phone to root with Odin.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I attempted following the root steps provided here: http://forum.xda-developers.com/showthread.php?t=2143479 and have run into a roadblock. The code I get when I run the PDA file through Odin is this:
<OSM> CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried doing a factory data reset, clearing the cache partition/wipe, and am still getting a fail. I have not rooted this device previously and notice while I had the device in Downloader mode that the system status says 'custom'. I tried downloading and installing the PIT file for my device and also attempted running No triangle (which will not start up properly).
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
jaycue said:
Hello.
My device is running Android Version 4.3 and firmware version VRUEMJ9
I have previously rooted devices successfully. But for some reason, I cannot get my Note 2 to cooperate. Any ideas?
Click to expand...
Click to collapse
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Thanks for the response
It's 4.3 OTA. I'll try that other program and see what happens.
Thank you
Another way than Kingo
jcollier said:
When you say 4.3, do you mean the OTA update from Verizon or one of the ROMs from the forum? If it is the OTA, Kingo is the only way currently to root.
Click to expand...
Click to collapse
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
TX_Jax said:
I disagree -- but I am not an expert.
Please read my problem at http://forum.xda-developers.com/showthread.php?t=2601903
If it sounds like you, then the answer link is posted in that same thread.
Click to expand...
Click to collapse
I hadn't seen your previous response before I responded on this thread. That said, it sounds like your thread might help the OP.
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.