Database Users

[Q] Issues Using Odin3+1.61

Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?

It sounds like you have done a lot of research and educated yourself prior to attempting your first flash. Major props to you for that as most people don't.
My $0.02 about your issues...I had something similar happen once when I forgot to uncheck "F. Reset Time" before starting the flash. If that's not the problem then I'd try a different cable. Next step would be to try a different version of Odin, there are plenty floating around these forums.
Good luck!

hongseong said:
Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<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> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
Click to expand...
Click to collapse
put it in the phone slot not the pda slot to bypass the pda bug

Oooh, thanks for the replies! I don't think I can get a micro USB cable right at this moment, but...
I did try the Phone method, and at first it seemed to actually start flashing, but it got stuck at factoryfs.rfs for quite a while, so I restarted the process and now it will just fail like it did before in about three seconds. Not sure what's gong on here, but it was nice to see it exhibiting some semblance of working up until it began hanging at factoryfs.rfs!
More helpful tips would be greatly appreciated!

Are you exiting Odin, disconnecting the phone, rebooting the phone into DL mode BEFORE trying to flash again? Odin will fail forever if you simply try to restart the process without the steps above.

I sure am!
I also think it has to do something with the param.lfs file since Odin always seems to fail once it encounters it (and it does so early on!).
Thanks again ^^

Ok have you tried to redownload the tar file it could be corrupted.You should be putting the whole tar file unopened in PDA leaving all the other slots empty and using the correct pit file that comes with odin.It is ok to leave the reset time option set it will not hurt anything.

Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]

hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App

hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Was Re-Partition checked during any of your attempts?

For the longest time no, but then I talked to noobnl and he asked me to try to put it into both re-partition mode and phone bootloader update mode. It just hung at "DO NOT TURN OF TARGET" and that was it. He warned me that it could brick it, but I guess I got lucky and it didn't.
So yes, I did check re-partition mode, but not until I tried all aforementioned tips in every combination possible.

bubby323 said:
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh, I was trying to flash DI18 the entire time (I gave up trying to flash DK17 last night, haha ^^ But I'll try your DK05 extended tip right now! Sorry I missed this ><

Okay, so using artemis' DK05 extended package and older Odin, I get a different readout
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
But it just stalls at boot.bin forever, and I've tried this several times, so...
I think the moral of the story here is that I'm unlucky
But yeah, that's what's happened so far. Thanks for the continued help, everyone!

Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck

marsknight said:
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
Click to expand...
Click to collapse
I tried to do it on another laptop in the house, but I ran into the same errors, but I'll try the microSD card trick soon
Thanks for the words of encouragement! I'm continuing to work on this problem, though I am a bit anxious to see how I can live without a cell phone...

im stuck with the same problem... and the messed up thing is i used odin before on this phone with win7 64bit... now i wish i never try updating to the new modem...

spent sooo much time on this and nothing im just gonna put it away b4 i smash it with a hammer... back to win mo...

Eeek, well, I think I'm going to scale back my attempts at fixing this for the moment. I'd be flat out lying if I said this wasn't a little bit frustrating, so I'm going to just relax before I make this fiasco ruin my Thanksgiving break for me. I'm most likely going to just purchase a cheap used flip phone and see through the rest of my contract with Sprint after changing my plan accordingly (no need for a data plan with a cheapo flip phone, and CERTAINLY no need for the 10USD WiMax surcharge, ^^; ).
That isn't to say that I'm not very thankful for all y'alls help, because I am, and this forum is awesome (along with the IRC chat!). Plus, not everything is *that* bleak; I mean, now I have a device that can charge batteries AND a 16GB microSD card freed up for other uses. So, thank you for all the help, and I hope y'all have a nice day!

Odin always seems to work for me windows 7 64bit and I have the 32bit drivers for the phone maybe try to deletethe old ones and install the 32bit drivers
Sent from my SPH-D700 using XDA App

Couple of questions and suggestions. Have you tried flashing just the modem in the proper slot(phone) with the proper pit file. I WOULD SUGGEST YOU TRY IT WITH THE OLDER ODIN(not 1.6) and the older pit. Then I would suggest you try to flash the full tar for DI18 with the older odin and no pit file. I have flashed my phone dozens of times with no pit as long as its the full tar. I could be wrong but I believe the pit is for partial system flashing. The only option I have checked on the left hand side of odin is reboot fwiw. Lastly, others have hinted at it too, odin is very finicky, try and try again. Always close down odin and restart it between attempts, and rebooting the computer seems to help others, and pull the phone battery and re-enter download mode each time too. Good luck, don't give up, if you can get into download mode all is not lost.
sent from an Epic4g through the cosmos

Massive problems with new cyanogenmod 10.2

Hey guys just looking for any help if at all possible.
My install has been anything but smooth. I had many issues actually getting cyanogenmod on to the phone in the first place ( seems the help out there doesn't really cover the international i9505 very well, where it does you often just hit a brick wall)
In anycase i finally got it onto the phone and was looking for an explanation as to why the phone is not detecting my carrier. I mean its just not detecting it at all. I have made some strange findings when looking through the phone. It doesn't know what baseband i'm on for example.
Now for the real problem. After all the hassle of getting CM onto the phone i decided to reboot it to see if that would pick up my carrier. Now the phone takes AGES (2-5 mins) to boot up, some times it hangs. The phone functions fine when it boots.
I used CWM recovery to install CM because TWRP just would not work, infact CWM recovery was a pain in the arse too, the only way i could get it to boot into recovery mode was to download the rom manager app and use its widget to boot into recovery because manually trying it just resulted in multiple hangs.
This is the first time i have rooted/flashed an android device so i may be making some rookie errors here but this is bordering on stupid now.

Cwm and which version?
Sent from my GT-I9505 using xda app-developers app

mkhattat said:
Cwm and which version?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
i9505-cwm-recovery-6.0.3.2-4. Its the 28th's nightly also. Im trying to get it to see my o2 version of the s4. I installed gapps from zip straight after CM but i havn't used it. might the problem be there?

i have reinstalled CWM and flashed a new CM nightly from here.
http://forum.xda-developers.com/showthread.php?t=2317040
I still cant get access to my mobile network (UK o2). When i flash cyanogen it says please insert sim yadayada. Any help on this would still be very much appreciated :crying:

Possibly a corrupt EFS partition? If you flash stock ROM can you get signal and baseband back?
Sent from my GT-I9505 using XDA Premium HD app

TouchWiz king of ROMs ..... dont careeee CM bla bla bla

This is really bad im still in need of help sadly. I am trying to flash stock firmware from sammobile.com. It has the o2 uk one i need. I am using odin to do it following this guide youtube dot com/watch?v=hZTTTk7vbVM
The problem now is that it fails to flash (using odin 3.06) . Kies doesnt even recognise my device....this is a disaster so far
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505O2UBMG1_I9505XXUBMF8_HOME.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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now

Try this sir. Post #9 http://forum.xda-developers.com/showthread.php?p=46143562
Sent from my GT-I9505 using xda app-developers app

phrazersco said:
So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now
Click to expand...
Click to collapse
User Odin version 1.85

Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?

donalgodon said:
Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?
Click to expand...
Click to collapse
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!

phrazersco said:
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!
Click to expand...
Click to collapse
Look no further, because the full wipe is the fix, like it or not.

My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?

phrazersco said:
My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing

jd1639 said:
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing
Click to expand...
Click to collapse
Thanks guys im back into my phone and its all working normal again!
Did i do something wrong by rooting then installing cyanogen mod the way i did? i mean it worked i just didnt have my phone network. kept saying insert SIM. was i supposed to unlock the carrier or something? i though cyanogen did all that.

Still looking for that last bit of advice people. Is there something i should have done before rooting/flashing to unlock my phone from o2uk or was i correct in thinking CM10.2 unlocked the phone also? if i was incorrect is there any help i can be given with respects to this? Thanks again.

[Q] My Note 3 is stuck after trying Odin

thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-

I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...

I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:

K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...

amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.

You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers

Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?

In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.

One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed

Are you trying to Root ur phone or Flash Stock ROM?

Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.

Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?

Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?

Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.

amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.

OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!

Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.

OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...

Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?

Cannot mount '/data' in twrp. Is there anything left for me to try?

I am afraid i have turned my galaxy tab 4 7" (sm-t230) into an expensive coaster at this point.
It doesn't do much of anything anymore. When it's booted it does nothing but show the samsung logo sparkling and when i start it into twrp just about anything i do ends with "cannot mount '/data' and not much else.
the local storage shows 0 and through the filemanager i see there are the folders but no files inside the folders.
Ofcourse i am well aware that i must've done goofed somewhere in my enthousiastic attempt to install a custom rom and the increasingly frantic attempts after that somehow resulted in the tab not booting past the samsung logo to fix it (from trying other roms to using odo in different configs to get anything on it that worked, including kernels and such) probably only added to the result which i described above. I know that, if this is irreversably killed the tablet i have only myself to blame.
But somehow i still have a sparkle of hope there is a way to fix the damage my stupidity has caused. It's still trying to boot and when i try to install for example the stockrom rom zipfile the progress bar dutyfully progresses until its end and the message "successfull" even shows in blue. When i put the tablet into download mode Odin still gives the all clear like it should but it seems like its teasing me with those things. When i boot it stops at the logo and when i go into twrp and do anything it fails to mount '/data' and some actions result in other failures to mount folders.
So.... IS there anything i can still do? (flashing the stock samsung rom wont work at all by the way, from twrp)
any help in getting any rom doing anything similar to working would be an improvement and appreciated.

So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?

thisisapoorusernamechoice said:
So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?
Click to expand...
Click to collapse
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]

deuZige said:
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]
Click to expand...
Click to collapse
It's a good thing there's no audio recording of what i shouted here the last 30 seconds to a minute. Everything seemed to go perfectly in Odo. I started the tablet in download mode, started Odo, and connected the usb cable. then clicked ap and selected the tar file and removed the tick at f.reset time. then i clicked start. heres the messages odo gave me... errr i mean odin:
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0AOD2_T230PHN0AOD3_T230XXU0AOD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> timh.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> obm.bin
<ID:0/004> loke_1st.bin
<ID:0/004> loke_2nd.bin
<ID:0/004> DTim.Primary
<ID:0/004> DTim.Recovery
<ID:0/004> DTim.CP
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Odin showed the green square with pass and the tablet rebooted.
and didn't go further than the samsung logo.
which it show still.... i have exhausted my most vile, evil and offensive curseword vocabulary shouting (which my neighbours will probably not appreciate as it's 01:35 am right now) before starting to write this reply....
i guess i am, truely inescabably, F worded now ain't i??
i am so depressed right now i can't even tell ya.
anyway, any suggestions?
(thanks for taking the time to read my sorrows and replying by the way. it IS really appreciated.)

just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....

deuZige said:
just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....
Click to expand...
Click to collapse
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!

deuZige said:
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!
Click to expand...
Click to collapse
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
honestly, i have tested taking pictures, uploading them to google and i have added all new accounts where i could. That worked without error, and the picture worked, and uploaded. I am doing nothing else until i get back home tomorrow from the park where i'll be taking pictures of my son.
When those are safe, i'll do whatever you want!!!
again, i cannot express the greatness of my gratitude for this!!
[supplemental]
i must sleep now. gnight!!!
[/consciousness]

Seems like everything is working fine! No need for wiping and formatting data if you have no more issues. I guess your good to go!
Sent from my ZTE_N9511 using Tapatalk

Hey I'm sorry I never got back to you, and I feel like a total moron for forgetting to tell you to factory reset, glad @DUHAsianSKILLZ took care of things for @deuZige, I hope everything's OK going forward and I'll be happy to help if I can if it isn't.

Stuck on recovery mode after NCG Kernel flash on S5 SM-G900V

I have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU

You are on the latest OTA of BOG5. The bootloader is completely locked down and you cannot root, downgrade, or flash anything. You are stuck with the phone as is. You will have to find the BOG5 full stock firmware .tar file and flash that through ODIN to get your phone back.

Damn!!!!
do you know any links from where i can download the BOG5 firmware from?

I am having the exact same issue. Any help is appreciated!

I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?

You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.

So I managed to get mine back working by using the VZW-G900VVRU2BOG5-20150813111348.zip firmware downloaded from Sammobile.com and flashing using Odin3.
Used the first firmware on Sammobile firmware page for model SM-G900V
Unzipped the file and flashed the .md5
Back up and running.
Hope this helps someone.

wgafsck said:
I am having the exact same issue. Any help is appreciated!
Click to expand...
Click to collapse
jac1985 said:
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
Click to expand...
Click to collapse
smn216 said:
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
Click to expand...
Click to collapse
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!

landshark68 said:
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
Click to expand...
Click to collapse
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.

Seriously, do none of you have even the basic, simple ability to look through these forums at all?
Click to expand...
Click to collapse
Same here, in fact it was my first time posting and I was also kind of lost. In any case, thanks for the lesson and the links.

wgafsck said:
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Click to expand...
Click to collapse
Understood. It just gets very old and frustrating answering the same questions over and over again, and questions for which the answer is already readily available. Glad you got it straightened out, and that you realized more research before embarking on your adventure would have helped. When it comes to messing around with an expensive piece of hardware like these smart phones, it's best to think of the carpentry line - measure twice, cut once. Read, read, read, and make sure you know what you are doing before you do it when it comes to rooting and modding your phone.

Thanks a million! I thought my phone is toasted.