Related
Hi unfortunately I'm on a mac and have been unable to use odin for obvious reasons. I came across a program called Heimdall, which you all know of. Well the program recently has been updated to 1.3.0 and in turn has introduced Heimdall Firmware Package format. See here: http://www.glassechidna.com.au/2011/devblogs/heimdall-suite-1-3-0-and-anti-squish-graphical-update/
My issue is whenever I go to load a package file, I've tried to use odin roms, it look like its about to work and then after it loads up you get a error saying "Firmware.xml Is Missing From The Package" obviously this package was not made to be used with Heimdall 1.3.0.
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Thank you so much people
Not having a windows computer at my disposal really keeps me behind on all these updates lol
Run vmware and try odin
Sent from my SGH-T959V using XDA Premium App
dualkiller said:
Hi unfortunately I'm on a mac and have been unable to use odin for obvious reasons. I came across a program called Heimdall, which you all know of. Well the program recently has been updated to 1.3.0 and in turn has introduced Heimdall Firmware Package format. See here: http://www.glassechidna.com.au/2011/devblogs/heimdall-suite-1-3-0-and-anti-squish-graphical-update/
My issue is whenever I go to load a package file, I've tried to use odin roms, it look like its about to work and then after it loads up you get a error saying "Firmware.xml Is Missing From The Package" obviously this package was not made to be used with Heimdall 1.3.0.
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Thank you so much people
Not having a windows computer at my disposal really keeps me behind on all these updates lol
Click to expand...
Click to collapse
If you can find a good, working heimdall package I can take a look at the firmware.xml file and figure out how it works for you.
FBis251 said:
If you can find a good, working heimdall package I can take a look at the firmware.xml file and figure out how it works for you.
Click to expand...
Click to collapse
The Heimdall Firmware Package format (and subsequently firmware.xml) is detailed in Heimdall's README. Refer to the Appendices.
dualkiller said:
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Click to expand...
Click to collapse
The README contains instructions that explain how to build a Heimdall Firmware Package. You just need to fill out the "Flash" tab as if you were performing a custom flash (see the README). Then instead of pressing the "Start" button go to the "Create Package" tab and fill out the details there.
If you're not sure how the partitions and file names match you can go to the Utilities tab and run the "Print Pit" action. This will output the PIT information in a human readable format so that you can match partition names to their "default" filename. I say "default", because unlike Odin, Heimdall places no restriction on what filenames can be used.
jager555 said:
Run vmware and try odin
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
that is quiet bad idea.
sharljimhtsin said:
that is quiet bad idea.
Click to expand...
Click to collapse
:what: Dead thread resurrection
Sent from my Maybach s 4g
Help
Benjamin Dobell said:
The Heimdall Firmware Package format (and subsequently firmware.xml) is detailed in Heimdall's README. Refer to the Appendices.
The README contains instructions that explain how to build a Heimdall Firmware Package. You just need to fill out the "Flash" tab as if you were performing a custom flash (see the README). Then instead of pressing the "Start" button go to the "Create Package" tab and fill out the details there.
If you're not sure how the partitions and file names match you can go to the Utilities tab and run the "Print Pit" action. This will output the PIT information in a human readable format so that you can match partition names to their "default" filename. I say "default", because unlike Odin, Heimdall places no restriction on what filenames can be used.
Click to expand...
Click to collapse
Hi, guys. I'm a simple guy. I just want to update my phone.
As you can imagine, I want to click on something and hit next a few times and wait patiently while a progress bar tires to lower my anxiety level.
So far I have installed Odin on my windows virtual machine with no luck and now this Heimdall program so kindly made by the open source comunity.
I have not the brains, time, aptitude or inclination to read a README file nor the IQ to create an XML file, however well explained the tutorial might be.
Any chance anybody can help me hit "next" a few times and get my phone to upgrade without having to learn, understand or figureout anything?
I have a Galaxy Note (the old one)
Much obliged.
Oh jeeze...
Let me save you some pain. I won't comment on the "I don't have the time..." statement and, with luck, nobody else here will either.
You should post in the Galaxy Note forums -- they are probably in much better position to save you from your rush.
Before you do leave, you might want to read the "Before you flash anything..." sticky.
never mind
alessioaguirre said:
Hi, guys. I'm a simple guy. I just want to update my phone.
As you can imagine, I want to click on something and hit next a few times and wait patiently while a progress bar tires to lower my anxiety level.
So far I have installed Odin on my windows virtual machine with no luck and now this Heimdall program so kindly made by the open source comunity.
I have not the brains, time, aptitude or inclination to read a README file nor the IQ to create an XML file, however well explained the tutorial might be.
Any chance anybody can help me hit "next" a few times and get my phone to upgrade without having to learn, understand or figureout anything?
I have a Galaxy Note (the old one)
Much obliged.
Click to expand...
Click to collapse
I installed windows. Never mind. Thanks
[whoops - tried to update and blew away my original. Sorry!]
I've run into some problems using Unbrickabe Resurrector with my (modded but currently bricked sgs4g.
If I do the following, I can get my Unbrickabe-modded sgs4g into download mode from a hard brick
install / startup Unbrickabe Resurrector (ubuntu box)
then at the phone
unplug USB
remove battery
replace battery
plug USB in
back at the PC, click 'Resurrect' the moment Unbrickabe Resurrector shows that it's detected a S5PC110 (be quick!)
My current issue is that, if I unplug the USB, even with a battery in, the phone drops out of download mode, goes back to being hard bricked (lsusb shows nothing if I plug it back in)
...and I can't find a for-Heimdall ROM for this phone. There are some one-click, but these fail, due to the downloaded PIT being different and re-partition not being specified.
So, got a pointer to a for-Heimdall ROM (2.3.x preferred), or a way to get one-click to repartition?
Thanks!
bobkoure said:
I've run into some problems using Unbrickabe Resurrector with my (modded but currently bricked sgs4g.
So, on to Heimdall - only there don't seem to be any Heimdall 2.3.x ROMs.
Click to expand...
Click to collapse
It's my understanding that Heimdall is an open source alternative to ODIN, which means you should be able to flash ROMs with it fine. I've not used it, though, but I'm sure there's something in the forums about it.
So, a bit more reluctantly, on to Odin. Got a copy of sgs4g-OfficalGB2.3.6-NOCIQ-Edition.zip from this forum (Raver's work if I remember correctly).
I put the phone in dl mode (adb reboot download) and on a windows xp box, ran Odin, specified PDA and this ROM. It reported FAIL.
Click to expand...
Click to collapse
That is a CWM-flashable ROM. You shouldn't have done that from ODIN. That's why it failed.
Sigh
Re-tried a couple of times. No luck.
The phone had the 'shoveling andy' and 'do not turn off' warning
Well, eventually, I had to shut it off (what do you do?) - and it hard bricked.
I then moved the phone to a linux box with Unbrickable Resurrector installed.
The phone is detected as a S5PC110 - which is good - for about five seconds. Not long enough to enter my password, so I ran this logged in as root (I'm also enough of a Linux noob to not know how to sudo a .JAR file).
And... so long as I have a cursor over the 'Perform Resurrection' button, I could plug in the USB, get detected as a S5PC110, click the button and get a 'success' dialog box - and the graphic in Unbrickable Resurrector turns into 'shovelling andy'. If I run lsusb, the device now reports as a Samsung phone. Good!
I then tried installing / running a 'one click' from bhundven to get back to stock.
It failed - and the phone stopped showing up in lsusb.
OK, back to Unbrickable Resurrector, do the same routine - only now it shows a success dialog box, but NO 'andy shovelling', and lsusb shows nothing at all.
From the name of the library being loaded, I guessed that Unbrickable Resurrector might have been picking up the one-click library (both were \tmp).
So I rebooted, let Linux clear \tmp, and tried again.
Still the same issue with Unbrickable Resurrector (says it succeeded but no download mode).
And here I'm stuck.
Any suggestions?
Thanks!
PS: sorry for being so wordy, but I'm not sure which parts of this are important for the problem I've got and which are not. And I still may have missed something important. I'd be glad to add whatever's needed, just ask.
Click to expand...
Click to collapse
Being wordy is a good thing Help me understand the current state of the phone, though. Can you get it into download mode? If so we can probably ODIN a ROM onto it and get you going again.
My current state is I'm in download mode but can't disconnect from the Ubuntu box, so it's Heimdall (which I'd like to use if I can, anyway).
The one-click stuff http://forum.xda-developers.com/showthread.php?t=1358498
looks to be using Heimdall one-click - and so does the Unbrickable Resurrector (just from looking at what gets left in /tmp).
When I try to run the one-click (after running rm -r /tmp/rootH* BTW, as the two apps seemed to getting crossed up - but maybe not) I get
Local and device PIT files don't match and repartition wasn't specified!
And my phone drops out of download mode and I then need to re-run Unbrickable Resurrector as above.
I'm appending the output from the one-click, if that's of any help.
Thanks!
%%%%%%%%%%%%%%%%%%%%%
Operating System: Debian Based i686
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
SMS-KJ6 (v0.0.2d) Stock-Rom with Bootloaders UVKJ6 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS DATAFS CACHE MODEM
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Re-attaching kernel driver...
Device not connected.
%%%%%%%%%%%%%%%%%
BTW, yes, I see
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
...but the 'flash bootloader' option is greyed out.
I hear ya on staying with Heimdall. I'm just not really knowledgeable of it. I guess I need to learn
I'm downloading the one-click you're trying to use so I can see what it looks like, does, etc. It might take me a few (downloading, gotta reboot into Linux, mount Windows, etc.) but I'll get back to you as soon as I can.
---------- Post added at 01:06 PM ---------- Previous post was at 12:13 PM ----------
Yeah, I'm not totally sure man. We need someone that's Heimdall smart to help us out here.
I read through some of the one-click docs, the one-click page by Adam (the creator of the one-click Heimdall), but I don't want to throw something at you that might not work or make it worse.
When you run the .jar, the files are extracted to a directory in /tmp that is prefixed with your Linux user name+HeimdallOneClick+a random suffix. So all of the files you would need to manually try to flash with Heimdall are there if you can get the right command from someone to flash from the command line.
Sorry I wasn't able to help, though.
I made this for heimdall a while back. Try it it might work:
http://sourceforge.net/projects/tea..._kh2_with_kg4_kernel_heimdall.tar.gz/download
Extract the 7zip file and load the tar with heimdall. I'm not sure if the command line version can load heimdall firmware packages, but I know the frontend does so consider using that.
It should get you on KH2, and it comes with bootloaders, from there you can just get into download mode and flash KJ6. I'll get around to making a heimdall version of stock KJ6 eventually though.
Thanks! I'll give it a shot as soon as I get home (had to run off to a client who's having probs with a win 2k8 server).
At this point, I'm not too worried about trying something that might mess me up. I've been hard bricked three or four times now, and, now that I have a notion of what's needed, I can get back to d/l mode.
I was looking at the Heimdall doc pack earlier today; building the xml file it needs (looks like it's basically a manifest) looks fairly straightforward.
I'll report back...
bobkoure said:
Thanks! I'll give it a shot as soon as I get home (had to run off to a client who's having probs with a win 2k8 server).
At this point, I'm not too worried about trying something that might mess me up. I've been hard bricked three or four times now, and, now that I have a notion of what's needed, I can get back to d/l mode.
I was looking at the Heimdall doc pack earlier today; building the xml file it needs (looks like it's basically a manifest) looks fairly straightforward.
I'll report back...
Click to expand...
Click to collapse
Yeah kind of annoying to do it by hand. I was looking into it also, but the frontend builds it for you. The file I linked you to comes with the xml file it built.
I saw that option in the frontend. You just point it at an Odin ROM and tell it to build the XML? Doesn't sound totally right as I'm pretty sure Heimdall expects everything in a single file (no hierarchy) and Odin's the other way.
Have to look at it later...
As a side issue, why do folks stick with Odin? Is there some functionality it has that Heimdall doesn't?
bobkoure said:
I saw that option in the frontend. You just point it at an Odin ROM and tell it to build the XML? Doesn't sound totally right as I'm pretty sure Heimdall expects everything in a single file (no hierarchy) and Odin's the other way.
Have to look at it later...
As a side issue, why do folks stick with Odin? Is there some functionality it has that Heimdall doesn't?
Click to expand...
Click to collapse
My only reason is because it was the first program I found when trying to flash my first ROM. I've stuck with it as I've not had a reason to not use it, you know? I need to get Heimdall smart though as I've read it has more/better/easier functionality.
Fortunately dorking around with my phone has renewed my interest in Linux again. I'm getting back up to speed there & wanting to dig into Android a bit. Now if I could just get the kids to take care of themselves.....LOL
Yeah, I just recently got back to Linux. Was a unix guy in the '70's, got hooked on PCs (all assembler at the time) and have only been back sporadically.
I installed Ubuntu 11.10 to do this - that UI seems a bit... not ready for prime time. Ah, well.
BTW, if you're in the Boston area, I have a client who's getting rid of six or seven p4 boxes. They'd make IMO fine linux boxes. Want one, or several?
You should try ubuntu 10.04. The UI's been going downhill since.
Not in that part of the country, but thanks I only used with Ubuntu here and there. I'm currently running Fedora and it's not bad. The UI on this is a bit different. Given that you're from the UNIX world you probably are like me and appreciate the command line better, anyway. Then again, maybe I just like doing things the hard way. LOL
It gets annoying when the UI makes it hard to use the command line. Switching apps in the latest ubuntu has been like that for me. I only use it in a virtual machine but it's nice to have it there when I need to work with tar files. Never liked using the windows commandline, even with cygwin. It feels so old.
No Joy.
I have had the phone repeatedly in download mode:
'andy shovelling' on screen
lsusb shows a samsung phone
From Heimdall, I can download my PIT file, but whether I use this file or the one with the ROM (with repartition enabled) I get communications errors.
Either PIT failed no EOF (sorry, didn't write this one down) or ERROR: failed to receive response.
Beats me what's going on in there. This behavior makes me wonder if I have a bad uart. Hoping it's a software issue...
BTW, should I be able to read a PIT as a text file? I tried with the two I downloaded from the phone, and they're not readable. Or maybe these don't have EOFs - does that matter in linux?
Thanks for all the help so far!
You should be able to see filenames as plain text inside a pit file, followed by binary data. For example, the first few bytes of my PIT say IBL+PBL and boot.bin followed by more ascii characters with null bytes.
Most of it is filled with null bytes though.
Do you have a different USB cable you can try to flash with? You should try it.
I've tried a few USB cables with the same results.
Sounds like the PIT files I have in my phone are bad - or aren't downloading, in spite of what Heimdall thinks.
[edit]
not just different usb cables, but all the different usb ports on the linux box
[/edit]
I'm wondering if I should re-ask this question, but with a title something like "unrecoverable SGS4g with unbrickable mod", and the current state of things - or should I just change the title of this one (if that's even do-able)? Or is either of those things considered 'rude' here at xda?
The more I look at this the more I think, for whatever reason, Adam's Unbrickable Resurrector isn't getting the entire HIBL.bin loaded, or something like that's going on. His app shows 'success' one time in five or six tries, and a large proportion of these are white-screen bricks. In either case, it's a download mode that doesn't download. On a semi-positive note, it's got me grovelling through the code to hibl.bin, with an ARM reference manual. It's a pretty cool architecture, actually. I used to write assembler for both the 8086 and the 6502, so I can sort of stumble through it.
bobkoure said:
I'm wondering if I should re-ask this question, but with a title something like "unrecoverable SGS4g with unbrickable mod", and the current state of things - or should I just change the title of this one (if that's even do-able)? Or is either of those things considered 'rude' here at xda?
The more I look at this the more I think, for whatever reason, Adam's Unbrickable Resurrector isn't getting the entire HIBL.bin loaded, or something like that's going on. His app shows 'success' one time in five or six tries, and a large proportion of these are white-screen bricks. In either case, it's a download mode that doesn't download. On a semi-positive note, it's got me grovelling through the code to hibl.bin, with an ARM reference manual. It's a pretty cool architecture, actually. I used to write assembler for both the 8086 and the 6502, so I can sort of stumble through it.
Click to expand...
Click to collapse
I just had to comment on that...6502 assembler. I was teaching myself that on my Commodore many moons ago.
Many moons indeed...
Here's exactly what I've done so far, and I've re-downloaded everything so I have fresh files and filenames/extensions just to clear any mucking up I did:
I downloaded this file from this thread as I understand this is the stock firmware necessary to use here.
I unzipped the file, and used 7-zip to extract the tar.md5 which also extracted a .dll.
The tar.md5 file is named: M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME_.tar.md5
I have installed Heimdall version 1.3.1 as the download site claims that version 1.3.2 broke compatability with many devices.
I downloaded the two .jar files which make up the one-click.
If all of this is correct so far, I'm understanding that I need to now feed a tar.gz file to heimdall one-click, however, I don't have any files that end in .gz. Just the tar.md5, which the one-click does not accept.
The button on the one-click literally says, "Select a Heimdall tar.gz for one-click" - So I'm lost there.
I'm reading that the front-end GUI is what would be used to create a tar.gz, but it seems to require downloading the PIT file from your phone, and this is failing now, possibly due to me having installed Kies and now having different kernel extensions that apparently need to be unloaded (no idea how to do that lol).
This is so complicated! Makes me want to go buy a cheap netbook lol
Anyone see the solution here? Please don't say buy a netbook.
I rooted using the method on this thread just yesterday, and it works great so far.
The short version (read the full instructions on that thread and it's linked posts before you try this, I'm not responsible for anything):
I used Odin and CWM
I flashed the ROOT_M919UVUAMDL.zip that the linked post provides
I also flashed the custom kernel linked in that post
Now it works great (including wifi, PC connection, etc.) I even flashed the Wicked ROM
Just Another User said:
I rooted using the method on this thread just yesterday, and it works great so far.
The short version (read the full instructions on that thread and it's linked posts before you try this, I'm not responsible for anything):
I used Odin and CWM
I flashed the ROOT_M919UVUAMDL.zip that the linked post provides
I also flashed the custom kernel linked in that post
Now it works great (including wifi, PC connection, etc.) I even flashed the Wicked ROM
Click to expand...
Click to collapse
I'm sorry, I should have been more clear. I'm using Heimdall instead of Odin because I need to do this on a Mac.
Heimdall issues
caffeineighted said:
Here's exactly what I've done so far, and I've re-downloaded everything so I have fresh files and filenames/extensions just to clear any mucking up I did:
I downloaded this file from this thread as I understand this is the stock firmware necessary to use here.
I unzipped the file, and used 7-zip to extract the tar.md5 which also extracted a .dll.
The tar.md5 file is named: M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME_.tar.md5
I have installed Heimdall version 1.3.1 as the download site claims that version 1.3.2 broke compatability with many devices.
I downloaded the two .jar files which make up the one-click.
If all of this is correct so far, I'm understanding that I need to now feed a tar.gz file to heimdall one-click, however, I don't have any files that end in .gz. Just the tar.md5, which the one-click does not accept.
The button on the one-click literally says, "Select a Heimdall tar.gz for one-click" - So I'm lost there.
I'm reading that the front-end GUI is what would be used to create a tar.gz, but it seems to require downloading the PIT file from your phone, and this is failing now, possibly due to me having installed Kies and now having different kernel extensions that apparently need to be unloaded (no idea how to do that lol).
This is so complicated! Makes me want to go buy a cheap netbook lol
Anyone see the solution here? Please don't say buy a netbook.
Click to expand...
Click to collapse
I'm having a b**** of a time too, and all I f'ing want is market enabler, tasker and titanium backup.
I've downloaded the CF-Auto-Root for the S4 LTE international (i9505) and am using Heimdall 1.3.1.
Originally using heimdall, whenever I place the commands in terminal, it always fails on :
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
So realized there wasn't a .pit file, thought that was the issue, and tried to download the .pit in the gui version; what does it tell me?
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
This is after trying the motochopper method repeatedly and receiving a failure because of the OTA update (which apparently didn't only affect Sprint S4 users in the US).
Any idea what I'm doing wrong?
Up...
Can anyone help please?? We are all stuck under mac *hit...
Thanks!
-----------
Galaxy S4 LTE I-9505 (unrooted pfffff)
http://m.youtube.com/watch?v=R7u-iUo5C6M&desktop_uri=/watch?v=R7u-iUo5C6M
Sent from my GT-I9500 using XDA Premium HD app
Re: Heimdall protocol error
I haven't tried rooting the S4 using Heimdall yet, but I will be doing so once I get home. Although I'll be using Slackware14.1 32bit (Linux).
I have seen those errors numerous times, though.
The first issue I commonly have is that Heimdall likes to be running as root if you are flashing anything.
sudo heimdall flash ...
Click to expand...
Click to collapse
The second issue I run into occasionally involves corruption with libusb, or sometimes missing pieces to libusb.
Libusb is a confused mess. One day it works perfectly, then you install some other totally arbitrary library and somehow libusb gets broken.
Anyway, if the above solution doesn't help, try REMOVING every piece of libusb and reinstalling. In my experience, development version installed from source code works the best with Heimdall.
Mac users will want to check out brew or macports or fink. Preferably brew. You will need Xcode for installing brew.
Windows users will want to install a real operating system.
how do i flash the update-mf3-mj9.zip after i changed the name? Thats what the file is called on my computer and Odin wont reconize it. Help please
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 ?
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.