[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...
Related
I AM NOT RESPONSIBLE FOR ANY DAMAGES!!!
Please please read this guide carefully (from beginning to end), and over and over again before you first start!! This guide is for advanced users!! If you are a newbie then I will try to "tone" it down a bit . But it is your Kuleana for making sure that you understand and do everything correctly! The installation part is only going to be for Windows as I am running Windows.
Helpful Threads to check out before starting:
http://forum.xda-developers.com/showthread.php?t=1049294
http://forum.xda-developers.com/showthread.php?t=878686
Original Thread: http://forum.xda-developers.com/showthread.php?t=755265
------------------------------------------------
Heimdall can run on:
Microsoft Windows (XP and up)
Mac OS X
Linux (Debian)
32 bit and 64 bit
------------------------------------------------
Prerequisites:
Microsoft Visual 2010 C++ Redistributable (Note! Only for Windows users.)
32 bit - http://www.microsoft.com/downloads/en/details.aspx?familyid=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84
64 bit - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD512D9E-43C8-4655-81BF-9350143D5867
WinRAR (or your preferred extracting software. Note must be able to unpack .tar files.) - http://www.win-rar.com/
Downloading and Installing Heimdall (http://www.glassechidna.com.au/products/heimdall/)
Step 1
Download the appropriate Heimdall for your system, please make sure you only download Heimdall Frontend or Suite (Windows, Mac only) as will we only be working with that.
WINDOWS INSTALLATION FROM THIS POINT ON!
Step 2 (refer to Capture1 Photo)
Unzip the .zip file. Now navigate to the location/folder. Make sure you remember where the location is because this is where you’re going to be running Heimdall.
Step 3 (Installing the drivers)
Open up the “Drivers” folder and there should be a program called “zadig”. What this program will do is that it will replace the Samsung USB Composite Device driver (Download mode driver) with a generic driver called WinUSB (libusb 1.0).
Note: This will only replace the driver on one usb port (Port-by-Port basics)! For example if I have three usb ports, the one usb port that you are replacing the driver will only work with heimdall(download mode only) and the other two will continue work with OdinOneClick/Odin3 only.
(Refer to Capture2 Photo)
1. Reboot your phone into download mode
2. Run zadig as administrator, then connect your phone
3. On the menu bar (Device,Options,Help) Click Options --> List All Devices
4. Under USB Device select “Samsung USB Composite Device”
5. Okie Dokie you can now click Install Driver
Note: If you get a popup about not being able to verify the publisher, just click install anyways. The drive installation may take a while.
6. Once zadig finishes installing you can close it and disconnect your phone. Just do a battery pull, and restart normally
If my driver installation instructions are confusing or hard to understand lol just read the “readme” file.
WINDOWS INSTALLATION DONE!
Preparing a ROM for use with Heimdall (For an example I will be using JF6 stock)
Step 1 - Downloading the rom and extracting the rom if it is in a compressed form (.rar file, etc).
Go to http://www.samfirmware.com/WEBPROTECT-i897.htm . Please register (its free!! ) or login. Under Firmware, download “I897UCJF6” (or whichever version you want). Using WinRar (or your preferred software) extract the .rar file. When it asks for a password, it’s underneath the last file, “I897UCJH7” on the website (in dark black color! Highlight it so you can see it ).
Note: OdinOneClick brings the Captivate back to Stock JF6
Step 2 – Extracting the .tar/.md5 file
After extracting the .rar file, it will provide you with a .tar file. Now normally for Odin3 users all we would do is pop that straight into the PDA section and hit start. But that’s not what we’re going to do today lol. Now using WinRar (or again your preferred extracter) extract the UCJF6 .tar file
Step 3 – Just a FYI step (refer to Capture4 Photo)
After extracting the .tar, it will now provide you with multiple files. Now most of these files should look familiar or sound familiar, if not than omg you should not be playing around with these files! Okie Dokie we are now done for this section
Note: Notice that there is no boot.bin (Primary Bootloader), or sbl.bin (Secondary Bootloader). If you need 2.1/2.2 bootloaders because you flashed Gingerbread bootloaders, I will post them at the end .
Using Heimdall(I will be flashing stock JF6 as an example)
If you downloaded the Suites package there is two heimdall’s. One is the frontend which uses a user interface, and the other is command line based. I prefer to use frontend because that includes a GUI (user interface) to work with. If you know how to use command line then feel fine to use that instead, but note again that this guide is only for frontend.
Step 1
Run/Execute “heimdall-frontend”
Step 2
When Heimdall opens there will be different slots to put files. Now use your common sense and browse for the files that you extracted out of the .tar files.
Example:
Under FactoryFS click browse and find the FactoryFS.rfs file that you extracted out of the .tar file from the section before. Now finish up the rest ! When you’re finish double check that the correct files are in the correct place!! Make sure that you do not checkmark repartition device!
Note: Please be ultra-careful when flashing with bootloaders!! Do not flash only one bootloader, always flash two at a time!!
Step 3 (refer to Capture3 Photo)
Check again that all the necessary files are in the right place and necessary checkboxes are checked. When you’re finish reboot your phone into download mode and connect it to the usb port that you reinstalled the drivers to (Windows and Mac only). Wait for about 5 secs. (to let your OS know you plugged in something) then click Start. Wait for Heimdall to complete uploading everything and yay!! You should get a “flash completed successfully”! Then your phone will now restart.
Note: If you need to do a Master Clear wait for the phone to completely boot up and then type in the phone dialer *2767*3855#. The internal SD card will completely be reformatted (Please remove your external SD card if you have one).
And there we have it! A phone flashed back to stock using Heimdall. You can use this guide if you wanna flash a different rom after .Make sure you read all of the threads in the first section(especially Mac users!!!) before starting. Again always be carefully with flashing with bootloaders!! Another thing to be careful with is the repartition device checkbox:
Benjamin Dobell said:
The reason is that when you repartition several partitions are being wiped, including the primary and secondary bootloaders. I don't know if the device is smart enough to back-up the bootloaders prior to the wipe and restore them afterwards. However I'm not particularly keen to find out either. If the device doesn't back-up and restore the bootloaders when you repartition then your device will be unable to boot at all i.e. hard bricked.
Click to expand...
Click to collapse
(From original thread.Post#764 Page#77)
Now after reading that please make sure that when you repartition, to include both bootloaders when you flash!! (unless someone can confirm that our Captivate does backup the bootloaders)
Please send me a PM if anything is incorrect, and I will be glad to change anything ! If you have any questions, post below or in the original thread! Consider donating to Benjamin Dobell (http://forum.xda-developers.com/donatetome.php?u=2710388) who is a genius and creator of Heimdall! If this guide was helpful please hit my thanks button .
Please note that this is only a guide, and I do not take credit for any programs or threads listed above
Just thought if give this a bump
Sent from my SAMSUNG-SGH-I897
Shouldn't this be stickied in the development section or stickied here in general.
Sent from Gingerbread on a Captivate using XDA Premium App
Rhiannon224 said:
Shouldn't this be stickied in the development section or stickied here in general.
Sent from Gingerbread on a Captivate using XDA Premium App
Click to expand...
Click to collapse
It better be. Been looking for this awhile back.
Mods, please?
Perfect timing I have always used Odin on my desktop PC, but now that I have a macbook I figured out how to get Heimdall running on my Mac.
My problem though is after I flash everything works but it goes like this:
1. AT&T Screen
2. 3G Jet across
3. Galaxy "S"
4. Black screen.
Happens everytime and then I have to use Odin to flash back to stock when Heimdall gives me the black screen.
Any idea why.
*Note everytime this happened I tried coming back to stock ROM the same exact method I use on Odin from CM7 then I tried with a JVO ROM. Both gave me the same result.
I did this a couple weeks ago with Andro3. I ran into one small problem which I finally figured out. When I ran Zadig, I had no listing for "samsung usb device". I had a device listed as "USB Gadget". Turns out, this was my Captivate. Just thought i'd share that incase any of you run across it. Once I got the proper driver in, everything went fine. Had one small hiccup when I hit start, but hit it a second time and it went through fine. I'm running W7 64bit.
Huh, so I gave this a go tonight. It kept having issues with being unable to flash the factoryfs.rfs file, but then after 4 tries it worked just fine, happily flashing to stock JF6 with no kinks or anything. All pre-requisites were met, drivers were loaded properly, nothing was out of place, computer is clean, etc.
Is the program itself somewhat unstable, or could it have just been a funky download?
No apparent changes between 1&4, but in the last attempt it worked?
Weird. You might try the command line instead of the gui ( shouldn't make a difference, but what you described shouldn't happen). I use Heimdall cli with Linux extensively and. never had a hiccup. Not even when my port had a short.
mac bull****
Oh god why did i switch to mac.....all of this crap for no valid reason!
On windows 10 I keep getting error " The application was unable to start corectly" when trying to run heimdall. Installed all microsoft c++ 2010,2012,2015,2017,2019 still same problem. Net framework version 4+ installed. What is the problem here?
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
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.