Database Info

[Q] Odin: what is that?

Hello, guys!
I've been using Odin for some time, I messed up my phone once, but then restored it...
Now what I'd like is to know exactly how it works, which files it writes (csc, pit, etc). I.e., I want to understand the internals.
After 10 minutes of googling, I didn't find absolutely anything about who makes this software and what's the official site and where can I find the docs.
Is there any chance that someone could point me to the right direction? At least the docs?
Thanks in advance!
Igor

I only know that's Samsung made. Google explains me that it was made by Jeong-Hwan Min Seung-Bum Kang.
http://www.faqs.org/patents/app/20080209201

it's a closed samsung software that no one fully understands

Thanks for the information.

c4manceph said:
Thanks for the information.
Click to expand...
Click to collapse
Well, no, I actually appreciate it
You see, I didn't even know that it was made by Samsung
It seemed to me that they used it to update apple devices as well, but obviously I was wrong.
Anyhow, my next question is: what every control in this program means? What are the files that you choose before the upload? PIT, Bootloader (is it like lilo or grub in linux?), PDA, Phone and CSC (heard that it is used for file allocation, but not sure). I guess, these should be more or less the same for every Android, not just a Samsung, right?
There are also the checkboxes: Re-partition (I kinda have a vague notion of what it does, but it's... vague), F. reset time, Phone EFS Clear?
Thanks in advance!
Igor

I would say you should hit up Benjamin Dobell, the creator of Heimdall. Since Heimdall is reverse-engineered from Odin, I would say he's a knowledgeable person concerning Odin.

Odin is a developer tool made by samsung that was leaked to the community to allow for flashing the modem and operating system with partitions to the compatible samsung phone.
It in conjunction with the drivers for your android device it will create a virtual serial com port , usually COM4 or COM5.
There are many posts on Odin on the forums, use search and you might be surprised what else you may pick up.
Hope this helps.

Thanks, guys!

It can be what you put back on your device after you bricked it. Or if you are rooting you can flash that on there to get root with a rom and Clockworkmod

tyvallely said:
It can be what you put back on your device after you bricked it. Or if you are rooting you can flash that on there to get root with a rom and Clockworkmod
Click to expand...
Click to collapse
Thanks, but it's a little... superficial. I know that you use it to upload some firmware stuff (new os, modded os, etc), I need more concrete info...

One down: csc
Just searched for "What is csc?"
http://forum.xda-developers.com/showthread.php?t=772201
Mithent said:
CSC is the Country/Carrier Specific Code (not sure exactly which it is, both kinda make sense). It contains the files for customisation for specific networks, so will have the APN settings, maybe custom ringtones or backgrounds, and can have programs too. Some CSC files contain a lot more than others, hence the file size differences.
Mixing different PDA/PHONE/CSC files is certainly possible, although it might be best not to stray too far on the PDA and PHONE side. The CSC isn't really very important in most cases - at worst you'll probably just have to set up the APN manually.
Click to expand...
Click to collapse

Found another one (.PIT files) here:
http://forum.xda-developers.com/showthread.php?t=771426
Richthofen said:
As far as I know .pit files are only used to tell Odin which file names to program to which "partition".
Even if separate images are used, Odin will treat them as a single image.
For example .pit file tells Odin to program modem.bin file to MODEM "partition", zImage to KERNEL "partition", etc.
If you use separate images (3-pack, CODE, MODEM, CSC), you can for example put CSC to CODE, MODEM to CSC and vice versa. Nothing odd will happen as long as you don´t tamper with the file names inside the tarballs.
Click to expand...
Click to collapse

Heimdall
A nice article on Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265

i would suggest hemdall ... much better way to go about things

[Q] Am I bricked? :(

My infuse when turned on goes to a screen that looks like phone ! pc with the message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So this happens even when I try and go to download mode or recovery mode. Basically as soon as I hit the power button. I'm really freaking out. It was rooted and I was doing following this link: http://forum.xda-developers.com/showthread.php?t=1613523
Then the problems started when my computer didn't recognize the phone in download mode. and then it was recognized so I started the Odin flash. Then it froze at cache.rts (I believe that's what Odin said, I can't get to it anymore)...So I uninstalled and reinstalled the drivers and did it again and it got to factoryfs.rfs before it froze there for a really long time. So I unplugged it and tried to do GTG Ultimate Unbrick...but I can't get the .zip file to open. My computer keeps telling me "Can Not Open ____ as archive". I re-downloaded it and same result. Is there anything I can do to save my phone? I'm a real idiot and this kind of stuff always happens to me no matter how much I read up on something and make sure I'm doing it right. I would really appreciate a little help though, thanks!

I actually got it downloaded and followed Rammstein874's video on youtube on how to do it and I am once again stuck on factoryfs.rfs :-(
What can I do at this point? It is still stuck at the Phone-!-PC screen when I try to go to download mode. Please help, I'm starting to get pretty worried about this...

When your screen is phone!computer, that's an alternative version of download mode. You can either use ODIN or heimdall back to stock. Just plug it in via usb, allow odin/heimdall to recognize it and start flashing.

This is correct....if you see those pic on your phone that is a form of download...i would run the one click method...

sfgiants2010 said:
Rammstein874's video on youtube
Click to expand...
Click to collapse
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

jscott30 said:
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Lemma know if that's the one..pm sent...

Sorry I was at work all day.
This is the video link I used: http://www.youtube.com/watch?v=y1HgcZrYR_4
I am also looking at the following one-click method posts:
- http://forum.xda-developers.com/showthread.php?t=1331381
- http://forum.xda-developers.com/showthread.php?t=1524081
* I used the above link (or tried) and it didn't seem to work either. I downloaded Heimdall Suite for Windows 64bit and then installed the drivers and plugged in my phone in download mode. But then I was unable to get it started...I used the "Stock_SGH_I997_UCLB3_Repartition-One-Click.jar" file I found on mediafire (because all of these posts link to mediaupload which is no longer working). Anyway, so I tried to run Heimdall-frontend.exe on windows and once it opened up I connected my phone (nothing turns green like the post says) and hit browse. I chose the jar file aforementioned and it said "tar header contained invalid file size."
So if someone could point me toward a more up to date thread if I'm using the wrong one and kind of explain to me how to get around the other problem I'm having with the jar file then I would be forever appreciative

Not sure what you did...not saying you did something wrong but here is what I do, below are how i perform using qkster's method...
The USB + Volume Down + Volume Up Method: Download mode (Noticeable by an Android robot digging with a shovel) is reached by taking everything out (Battery, SIM, MicroSD). plug in the USB cable to your computer and phone then putting in battery at the same time Holding the volume buttons both up and down, (Don't press the power button at all in this method).
How to INSTALL:
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
download this file for your one click to stock...and using above directions...
once that is done and you want to put CWM mod on for flashing a custom ROM, same directions to get in to download mod...
download this file to use the one click to put CWM mod on your phone
here is the link where i took all this...
http://forum.xda-developers.com/showthread.php?t=1524081

Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).

sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
why are you using these other programs...idk,
I just click on the one click file it an executable design to open and run itself...you say attach the jar file...why the suite version of heimdall...?
did you download the links i provided and just use those...?

sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
Is your phone still stuck on the phone-!-pc ?

did you read the last post he had regarding the actual heimdall program suite...
not sure what he had going on...I believe he has download mode capability...
thx ''Goshujin-sama'' qkster

Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.

qkster said:
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
Click to expand...
Click to collapse
that's when I started to question him on these other programs...due to the one clicker is self sustained as a exe...idk...but believe he log off...i will monitor and holler at you if required thank you...

Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?

It should of rebooted it self the phone...
Btw you are not wasting my time...wife is watching cup cake wars...so ....rather help you...lol

sfgiants2010 said:
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
Click to expand...
Click to collapse
Once the connected bar is on, you click flash. It should complete it's routine. the phone reboots. you should click on the boot loader box. you disconnect. let it finish. set it back into donwload mode and flash again.
you can try different usb port or data cord or different pc

Plus you have my master...qkster here...cuz you lost me on the programs you were using...so i called in the jedia master!

As long as your screen has that Phone! Computer sign, it's not bricked yet. I recommend you to search some how to videos online so you can see the exact instructions on how to use heimdall because it's that easy. If possible maybe one of our awesome contributors can make a how to video for heimdall.

I believe he is tracking now qkster is providing....thx

4.3 help!!!

I have an N8013 and I have been trying to go to 4.3 for a while. Like illusion rom... i've tried cwm a few versions even the latest, twrp, and even philz recovery as recommended and I even deleted the updater scripts as recommended. I for the life of me can not get past the zip file failing to flash. I've downloaded the rom multiple times, used odin to go back to completely stock, factory reset.... just about everything. There is one other dude tellin me to do this....
"I have a N8013, and deleting the assert and getprops works for me 100% of the time. However, it is important to note, two things. One you have to have the N8013 version of the ROM, which is labeled N80xx, and 2, when you go to install it after you have modified the file, you will get a validation error because the zip file will no longer match the MD5 validation, you have to install anyways. Other than that it works fine on my N8013, using CWM 6.0.3.1, running official CM 10.2."
But I dont know exactly what file he is talkin about. If ANYONE can help me out with this id be forever grateful.

First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.

Niscandia said:
First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.
Click to expand...
Click to collapse
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.

Thought:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..

RussellEstridge25 said:
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.
Click to expand...
Click to collapse
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
RussellEstridge25 said:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..
Click to expand...
Click to collapse
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.

Niscandia said:
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.
Click to expand...
Click to collapse
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.

RussellEstridge25 said:
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.
Click to expand...
Click to collapse
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0

Niscandia said:
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0
Click to expand...
Click to collapse
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:

RussellEstridge25 said:
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:
Click to expand...
Click to collapse
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.

Niscandia said:
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.
Click to expand...
Click to collapse
I completely agree. And I plan to. Didnt know it would be that easy. Again thanks man. But you completely helped me understand. I love learning about this when there is someone willing to teach.

I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?

RussellEstridge25 said:
I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?
Click to expand...
Click to collapse
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.

Niscandia said:
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.
Click to expand...
Click to collapse
Great ideas! I can try the sd one tomorrow. Day 3 lol. Wish Me luck

I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.

spycedtx said:
I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.
Click to expand...
Click to collapse
Already got cm10.3 up and running. The developer gave me a nightly build that had all the files taken out already. Had to download it twice but got it after putting it on my internal memory. Thank you for your help. The note 10.1 has a good community of people.

[Q] Trying to reflash with stock firmware using JODIN3

After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file "HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5". It wants to get a pit file from the device. I let it do that and put the tablet back into download mode. Then I pressed "start". JODIN3 then complained that the firmware file was corrupt. I tried a few more times. The unzip program on my computer seemed satisfied that the zipfile was not corrupt. Tar seemed satisfied that the tar file within was not corrupt.
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, I tried again with the .tar.md5 file. That seemed to do something. The spew in the xterm in which I
started JODIN3 flashed the names of the six file contained within. The spew then kept printing stuff about "heimdall detect" confirming that a
device was attached. Nothing new was printed to the JODIN3 GUI. I let it sit there for 30 minutes. Nothing -- not even a complaint of
something being corrupt. Scrolling back in the xterm, I saw this:
Exception in thread "Thread-103" java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:619)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:53)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:570)
at java.lang.Thread.run(Thread.java:744)
[DEBUG]Run Heimdall from
DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows and I can't make it work with Virtualbox. I hear there are problems inherent to emulation that prevent Odin from working correctly there. Trying to run the plain jar file doesn't work because it complains that it needs a newer version of Java. I'm running OpenJDK7 and that seems to be what the Linux64 package uses. Someone, please help me out here.

dgriffi said:
After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file "HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5". It wants to get a pit file from the device. I let it do that and put the tablet back into download mode. Then I pressed "start". JODIN3 then complained that the firmware file was corrupt. I tried a few more times. The unzip program on my computer seemed satisfied that the zipfile was not corrupt. Tar seemed satisfied that the tar file within was not corrupt.
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, I tried again with the .tar.md5 file. That seemed to do something. The spew in the xterm in which I
started JODIN3 flashed the names of the six file contained within. The spew then kept printing stuff about "heimdall detect" confirming that a
device was attached. Nothing new was printed to the JODIN3 GUI. I let it sit there for 30 minutes. Nothing -- not even a complaint of
something being corrupt. Scrolling back in the xterm, I saw this:
Exception in thread "Thread-103" java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:619)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:53)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:570)
at java.lang.Thread.run(Thread.java:744)
[DEBUG]Run Heimdall from
DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows and I can't make it work with Virtualbox. I hear there are problems inherent to emulation that prevent Odin from working correctly there. Trying to run the plain jar file doesn't work because it complains that it needs a newer version of Java. I'm running OpenJDK7 and that seems to be what the Linux64 package uses. Someone, please help me out here.
Click to expand...
Click to collapse
Apparently Jodin3 does not support Stock Firmware flashing at this time...

spidergrafxxx said:
Apparently Jodin3 does not support Stock Firmware flashing at this time...
Click to expand...
Click to collapse
You are correct. I always use Heimdall Frontend to flash Samsung on Linux. OP, do you need a pit file?
Sent from my SGH-T989

cant flash a .tar.gz file
dgriffi said:
After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file...
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, ...
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows ...
Click to expand...
Click to collapse
So, the last reply to this thread branch was nearly a year ago. I'm having identical difficulties. Every time I download the pit file from my Galaxy S3 and hit the start button I get the corrupt pit file error message. Additionally, I have an impossible time getting jOdin3 to pick up my phone after the reboot to pull the pit file. If this is a Heimdall shortcoming it makes the an impossibly useless utility for me, at least for the time being.
I'm running Ubuntu 15.04 (Vivid vervet? friends don't let friends use Windows...) with all the latest updates. I've downloaded and built Heimdall and Heimdall-frontend. The binaries are in my shell's PATH variable, as is that of the platform-tools folder for the android sdk. I have the latest java update from the oracle site, both x64 and i386 libraries.
Anyway, I guess I'm not really expecting a fix or help in this regard. This is more just sort of a status ping with regards to the issue. I'm going to go back to using Heimdall-frontend directly. I had to package the firmware I wanted to flash so I could use jOdin3 anyway. I just wanted to avoid the desmadre that happens sometimes when flashing firmware from Heimdall (seems to hang after trying to flash a modem partition, sometimes, and I'm not at all sure I can characterize the conditions of the failure). I'm trying to take my UCUFNE4 I747 firmware back to a T-Mobile T999UCALJ2 setup which purportedly enables the AWS/LTE 1700/2100 band AND unlocks the unit to T-Mobile (I'm a feeling a bit incredulous at this point....). And, yes, I've pulled the aboot.img file out of the package I'm installing. God forbid I step on the Samsung/Qualcomm/ATT locked primary bootloader and brick my second GS3 (8}
Hasn't seemed to be an issue doing this before, I took it back to DLK3 to see if I could get the hidden service menus back, unfortunately to no avail. At this point I just want to cut to the chase. I've spent a month of more than full time effort getting to the point I'm comfortable with what I'm about to do, although I still have nagging doubts and a feeling of uncertainty, lol. At this point I'm about ready to offer myself back to the development gods and take on some real work. I vowed I'd NEVER go back to being a software developer after the stock market crash of 2001 cost me my house et al and left me homeless (another long saga for another time and place)...
'nuf said, off to the races. See you on the other side of Heimdall
BTW, good work Adam, I am impressed! just chagrined that this won't serve my current purposes. peace out
one last thing, if anyone knows how I can change the ro.anyprop properties in the build props file so they stick (they didn't from a terminal emulator via the setprop command), please inform me. I want my phone to tell the world it's a(n aboriginal) TMO unit even though it's really a red-headed step child. Quality goes in before the label goes on....

riches2rags said:
So, the last reply to this thread branch was nearly a year ago. I'm having identical difficulties. Every time I download the pit file from my Galaxy S3 and hit the start button I get the corrupt pit file error message. Additionally, I have an impossible time getting jOdin3 to pick up my phone after the reboot to pull the pit file. If this is a Heimdall shortcoming it makes the an impossibly useless utility for me, at least for the time being.
I'm running Ubuntu 15.04 (Vivid vervet? friends don't let friends use Windows...) with all the latest updates. I've downloaded and built Heimdall and Heimdall-frontend. The binaries are in my shell's PATH variable, as is that of the platform-tools folder for the android sdk. I have the latest java update from the oracle site, both x64 and i386 libraries.
Anyway, I guess I'm not really expecting a fix or help in this regard. This is more just sort of a status ping with regards to the issue. I'm going to go back to using Heimdall-frontend directly. I had to package the firmware I wanted to flash so I could use jOdin3 anyway. I just wanted to avoid the desmadre that happens sometimes when flashing firmware from Heimdall (seems to hang after trying to flash a modem partition, sometimes, and I'm not at all sure I can characterize the conditions of the failure). I'm trying to take my UCUFNE4 I747 firmware back to a T-Mobile T999UCALJ2 setup which purportedly enables the AWS/LTE 1700/2100 band AND unlocks the unit to T-Mobile (I'm a feeling a bit incredulous at this point....). And, yes, I've pulled the aboot.img file out of the package I'm installing. God forbid I step on the Samsung/Qualcomm/ATT locked primary bootloader and brick my second GS3 (8}
Hasn't seemed to be an issue doing this before, I took it back to DLK3 to see if I could get the hidden service menus back, unfortunately to no avail. At this point I just want to cut to the chase. I've spent a month of more than full time effort getting to the point I'm comfortable with what I'm about to do, although I still have nagging doubts and a feeling of uncertainty, lol. At this point I'm about ready to offer myself back to the development gods and take on some real work. I vowed I'd NEVER go back to being a software developer after the stock market crash of 2001 cost me my house et al and left me homeless (another long saga for another time and place)...
'nuf said, off to the races. See you on the other side of Heimdall
BTW, good work Adam, I am impressed! just chagrined that this won't serve my current purposes. peace out
one last thing, if anyone knows how I can change the ro.anyprop properties in the build props file so they stick (they didn't from a terminal emulator via the setprop command), please inform me. I want my phone to tell the world it's a(n aboriginal) TMO unit even though it's really a red-headed step child. Quality goes in before the label goes on....
Click to expand...
Click to collapse
This thread is for the Tab 2, not S3. Please post in the correct forum for your device.
jrc2

jrc2 said:
You are correct. I always use Heimdall Frontend to flash Samsung on Linux. OP, do you need a pit file?
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, sorry if i resume the threat, I am trying to flash the origin firmware. If I have understand well it could not bi done with jodin3 on Mac ? I have to use another program ? Could you tell me more please ?

[Q] All links down, need T839UVKJ2 SK4G stock rom

so after looking for 3-4 hours i'm convinced that almost all the links for files related to the SK4G are expired/down/DL limit reached. i had to wipe my HDD and can't find my backup anywhere!?!? if anyone has the stock firmwares (any and all) could you pretty pretty please send them to me? i'm stuck in a buggy version of glorious overdose and just need my phone to work right again. respond for e-mail or just post ***NEW*** link in this thread.
P.S. so when the mods say "wrong thread" or "duplicate" i looked i searched and found nothing newer than 2013 so i started a fresh one......... that and i just signed up and it keep telling me "NO" in what seemed like the correct forum.
P.S.S i'm assuming there's legal reasons but whats up with a file repository on or at least paired with XDA to hold all the files posted here. shooting in the dark but maybe Kimdotcom will provide a mega account to serve as a repo?!?!?!?

I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
If you brick your phone, well you're lucky because it can't get any easier to fix. This is pretty much a one-click version of ODIN that is OPERABLE AND EXECUTABLE on ANY operating system that has Java installed. Self-explanatory, but if you don't have Java installed yet, you probably should go get it installed now.
(Credits go to Ayoteddy for the following post) :
To get into download mode (if you can't) pull the battery out of your phone, the USB cord (if connected), the SIM card, and the SDCard. Now...in a position where your one hand is able to access the Trackball and - volume key, hold them both at the same time and with your other free hand, insert the battery, after a second or two, you should see an Android on screen with a logo saying DOWNLOADING..you're ready to advance.
After you install Java, double-click the .jar file in this folder.
Hit "flash" and if all is well, it'll work without any hassles and you'll be back to the stock ROM like the day you got your Sidekick (factory reset).
If it says driver was not found, a window will popup with an administrative prompt if you are running Windows 7, allow it to run.
On the new Zadig window, go to Options>List all devices.
You should now see SAMSUNG COMPOSITE DRIVER, make sure the box to the immediate right says WinUSB and then hit the install button.
You should be on stock after performing these steps...if not and YOUR MODEM fails to upload, check "Flash Bootloaders" and the modem should flash just fine and you'll be back on stock ROM soon enough.
Thanks to AdamOutler for Heimdall!
His thread is here if you want to thank him properly!
http://forum.xda-developers.com/showthread.php?t=1350060
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.

marathonjon said:
I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.
Click to expand...
Click to collapse
Please re-upload these to sammobile.com, samsung-firmware.org, MEGA, Android File Host, or similar where the files can live on longer.

Sorry, I got rid of my SK a couple years ago and all the files that went with it.

marathonjon said:
Sorry, I got rid of my SK a couple years ago and all the files that went with it.
Click to expand...
Click to collapse
Is there anyone out there that still has this? Please re-upload.