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?
Related
Introduction: It has come to my attention that many of us windows users are still using odin for upgrading to Ginger bread and recovering from soft bricks. I have found the heimdall one click method is easier to use and more stable for flashing your phone from a computer. I am trying to make this guide as noob proof and simple as possible. Given how simple the one click method is it should not be hard (although if you are new to this device it can prove to be difficult if you don't read and understand everything).
Please be sure to format your sd card if this is the first time you are flashing ginger bread. If you have problems converting to ext4 using one of the rooted one clicks it is suggested you create a 2048 partition in cwm.
The first five steps are to help get heimdall and everything needed to use it installed on your windows computer. If you already have heimdall you can skip to steps 6&7.
Please read everything in this guide before proceeding and be sure to read everything else mentioned in this guide. proceed slowly if this is your first time. I recommend a print out, double check everything, and cross off each step as you go. Slow and methodical = smooth = fast and efficient with perfect results. Remember the best way to gain knowledge and learn to do almost anything is to READ.
If you have used the one click method and have any suggestions for this guide please feel free to comment.
Disclaimer: You are flashing your device at your own risk. No one but you can be held responsible if you make a mistake. Some one click packages contain bootloaders and flashing incorrect bootloaders may hard brick your device. Never flash a one click package that is not clearly labeled for your device by model number.
Warning: if you are on a Mac running osx 10.5 or higher there is a problem with the re partition function in heimdall. since you must flash boot loaders these packaged are designed to re partition automatically. It is recommend you use a windows or Linux parallel to flash.
On to the guide:
1: first you will need to download and unzip the lastest heimdall front end. This package can be found at http://www.glassechidna.com.au/products/heimdall/
Please read and understand everything that this website has to offer about the program before use.
2: after you have unziped the heimdall front end package open the containing folder and click on the "Read Me" text file. This file contains troubleshooting tips, driver installation, installation procedures, and instructions for flashing other heimdall supported files to your device. Oh yeah and they don't call it Read Me for nothing
3: you will also need to download and install the package labeled "Microsoft Visual C++ 2010 redistributables" and get java 1.6 do I have Java?. Simply download and run (double click) the executable files.
4: Once you have downloaded and unziped heimdall front end, installed java 1.6, and installed the C++ packages you will need to install your device drivers (this process is also explained in the read me file you should have read).
A: Place your device into download mode and plug it into your computer. How to get into download mode
B: Open the unziped heimdall folder then open the the "drivers" folder and run (double click) the "zadig" application
C: Click the "options" menu and make sure "list all devices" is checked.
D: from the drop down menu choose "Samsung USB composite device"
E: Click the "install drivers" button and let it do its thing.
Note: if you have trouble installing drivers try again. If "Samsung USB composite device" is not an option unplug your device re run zadig and take note of what options have disappeared.
5: Now it is time for you to choose your one click package. If you would like help choosing the package that is right for you please feel free to ask.The threads I am linking to are only for the Samsung Galaxy S 4G device from T-Mobile, Model# SGH-T959V. If this is not your device do not flash the one click packages I am linking to. If this is your device these are the ONLY one click packages available. Again, never flash a firmware package not clearly labeled with the exact same model number as the device you are flashing to.
Choose and download the one click package of your choice. Remember to read the OP of each thread before making your decision. If you have a question feel free to ask here.
A: kj6 one click collection
This thread contains three one click packages to choose from. All are from the official Galaxy S 4G Ginger Bread Upgrade to 2.3.6 or KJ6. Read the OP to choose the one that is right for you.
B: kf1 one click package
This was the first one click package we obtained for the Samsung Galaxy S 4G. It was from a leaked version of gingerbread 2.3.3 or KF1. I, and Most, do not recommend you use it because the boot loaders change the button mapping for recovery and download modes (this can cause problems trying to revert) ;but, I would like to give credit to the creator of the one click packager and will include his thread and work as such.
6: Now that you have installed heimdall and chosen a one click package its time to flash. Close your heimdall folders and forget about them for now. put your device in download mode and connect it to your computer How to get into download mode
A: Run (double click) your "oneclick.jar" package. Yes, they are supposed to be executable files (be patient it may take a minute to load)
B: Read the "package information" section and ensure you are flashing a one click package designed specifically for your device by model number.
C: do nothing else except click "flash"
D: wait for device to reboot
E: If you are upgrading to GB from froyo do not close your "oneclick.jar". You will need to repeat step 6 a second time with the "flash bootloaders" box checked. Please also ensure you have read the disclaimer.
7: At this point your device will be in one of these three states
A: rebooted and running as factory
B: in the stock Samsung 3E blue recovery in which case you should use the volume buttons to navigate to reboot device and use the power button to select reboot device
C: In a CWM recovery where you should use the volume buttons to navigate to reboot device and use the power button to select reboot device.
That's It! Happy flashing!
Credits
Benjamin Dobell - Creator of heimdall
Adam Outler - creator of the one click packaging system
Bhundven - For assembling the kj6 update packages for the t959v
Fbis251 - wiki links and general support
odin vs. heimdall comparison
Most of us here are used to Odin and can make it work; however, it is an unstable, proprietary, windows only, unsupported program. It often will not recognize your device or you get a better experience with v 1.7 or v 1.85 or maybe it is just picky with your computer or device. I had both the above mentioned versions installed on my desktop in case I had problems with one or the other. This, to me, is totally unacceptable. Now we have heimdall and I encourage you to make the switch. It is an ongoing project that is cross platform, supported, and open source. This means it is based on the same fundamentals as Android proving any developer the opportunity to help make it better, faster, or more user friendly. Take the one click project for example: now, with heimdall installed on your system, you can simply execute a pre programmed flash and your done with your device flashed as the developer intended. I admit it is a few clicks not just one but, it hasn't given me any problems, it tells me exactly what it's doing in a language I understand, and it is super easy. So at least give it a shot, bet you will like it
NICEEEEE!
Sent from my SGH-T959V using xda premium
Choosing the right driver
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
mandogand said:
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
Click to expand...
Click to collapse
Was your phone in download mode?
Unplug your device and re run zadig. Take note if any options disappear. If so re plug your device and try it. If not report back.
Sent from my SGH-T959V using XDA App
Sticky!
Sent from my SGH-T959V using XDA App
its honestly the far superior option and comeing from a linux based world where i dindt have to deal with odin as much Its great tried odin on windows and really its far superior and alot more stable then odin.. its worth learning tbh
Further adventures in un-bricking with Heimdall
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
mandogand said:
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
Click to expand...
Click to collapse
You are currently in recovery mode running whatever bad boot loaders you flashed. Use this method to enter download mode
1 pull out battery
2 hold Vol up Vol down at the same time
3 plug USB cable into phone and computer
4 re insert battery and continue to hold both Vol buttons until your phone displays something.
unfortunately it is possible the bad boot loaders you flashed may have messed up your button mapping. if you try the above mentioned method for download mode multiple times and only end up back in the same recovery screen please direct me to the thread you flashed the bad boot loaders from
Good luck
Sent from my SGH-T959V using XDA App
How to get into download mode
FBis251 said:
How to get into download mode
Click to expand...
Click to collapse
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
More Heimdall recovery....
Cool. OK followed instructions and now have a screen as below:
What next?
M
More Heimdall recovery....
Hit the up button and now get the digging android icon (Digging)...what next experts! You guys rock by the way!
Thanks!
M
Bassmanjames said:
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yup, anyone can update the wiki I'm going to add guides little by little into it so we can just link new users to it. I realized after typing for the 20th time how to get into download mode that it'd be easier to just use the wiki.
mandogand said:
Cool. OK followed instructions and now have a screen as below:
What next?
M
Click to expand...
Click to collapse
Is it fine if we use your picture in the wiki? People would really appreciate it.
Now that you're in download mode you can use the one click to recover your phone.
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
mandogand said:
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
Click to expand...
Click to collapse
Well with bad boot loaders you might have.
So success?
Sent from my SGH-T959V using XDA App
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
mandogand said:
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
Click to expand...
Click to collapse
Do me a favor and pull your battery. post a pic of the device info but edit out your imei number
Sent from my SGH-T959V using XDA App
Here you go.
Serial end with a W.
Thanks,
M
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
So I rooted my phone for the first time via Odin. And it worked -- after that, I tried to install a custom ROM (slim bean) -- I ended up uploading the non zipped version on my SD card. And I went through all the steps to install up until "format/system" to realize that I didn't have the zipped files.
Now my phone is stuck on the Samsung Icon. I just tried to use Odin to flash the stock gingerbread again, but there it gets stuck on "Setup Connection".
Please help! Total newb at this, and clearly it failed.
---
My phone wouldn't turn off even with Odin closing, so I took out the battery -- so now my startup screen is
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
How do I fix this?
That is kind of a secondary download mode.. odin or heimdall should detect your phone.
Make sure you have a good usb cable and maybe try switching usb ports.
Sent from my SGH-I997 using xda app-developers app
Right. To add to andros11's post, was the top left box yellow in Odin before you clicked start? Odin will acknowledge that your phone is connected immediately (the box should be yellow if you your phone is connected properly). Of course, make sure you have all of the appropriate drivers (i.e. download Kies for the Infuse).
Also, for future reference, I have a fix for situations like yours so you don't have to go back to stock. Basically, you can use adb to push the correct zip file to your sdcard. What you do is:
Download and install the Android SDK: http://developer.android.com/sdk/index.html
Make sure to install platform tools (a separate download from within SDK)
In Mac and Linux, open up Terminal. I can't remember how Windows works, sorry! Navigate to wherever the platform tools folder is. You have to do this using command line, so, cd <the/path/to/your/folder> (the easiest way is to just type cd, hit the space bar and then drag the folder to the Terminal window).
Once there, connect your phone to your computer. It can be in CWM or Download mode
Type in Terminal: adb devices
The next line - the response - should tell you if your phone is recognized. If it's blank, try again. If it's still blank, you might try disconnecting usb phone cable and reconnecting again. You might also try going into download mode.
Okay. Next type: adb push <here, just drag the zip file to your terminal window> /sdcard/
Give it time to push the file to the sd card. Repeat if necessary (if you have more than one zip)
Exit terminal, disconnect phone from computer, go back into recovery, navigate to the sdcard to flash and lo and behold! The proper zip file is there for you!
This might sound long, but it's so easy. Getting SDK set up is probably the biggest pain and it's not really that much of a pain!
You may want to give Heimdall a try rather than Odin.
Put the phone into download mode and try this:
http://forum.xda-developers.com/showthread.php?t=1331381
Thanks so much everyone. Seriously.
So, Whizzpopper -- I *think* I installed SDK, but since my phone still says, "Firmware upgrade encountered issue. Please select Recovery mode in Kies and try again." I tried connecting it to Kies -- and it says "connecting" but never connects.
And even if I try the key combo to get to Download Mode or Recovery, it never gets away from that Firmware message.
How can I just get out of that mode?
how to keep fb sync on custom rom?
Hi I am a fairly new member, I have been following different threads for a long time but have recently signed up, so if i am posting in the wrong thread I sincerely apologize. moving on...
I have been using the Aeon 1.4 rom for awhile now and have been loving it. I first downloaded the rom without the stock libs and found that it is much faster than the stock libs rom, even after manually removing most of my stock apps via sd maid pro. But it has been the only way to keep the option to share with FaceBook. and being able to add facebook in my accounts and sync are in system settings. system settings>accounts and sync>add account.
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
andros11 said:
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
ONE CLICK UNBRICK HAS GOTTEN ME OUT OF THAT GODFORSAKEN FIRMWARE MESSAGE.
Thank. You. So. Much.
... Now to follow the rest of the steps to try and get it back to some sort of operating phone!
and please note that it would be best to uninstall kies- it has been a source of problems for a countless number of users.
Thank you so much for your help!
So the terminal adb push worked -- and I installed my ROM (went through all the installation wizard parts, etc.) but now at reboot, I'm still stuck at the Samsung logo.
What happened?
@andros11 -- I saw your comment on how to best get from GB to JB
http://www.android.gs/install-unoff...pdate-to-ice-cream-sandwich-4-0-3-custom-rom/
I tried to follow those instructions to install ICS first, (I was previously too eager and went straight to JB!) and still I'm stuck at the Samsung screen.
Anybody have any threads, recos to get my phone to bootup to any system?
Sorry for the newbness!
Enter download mode to Go back to stock gb and then work your way up again up to jb.
Sent from my SGH-I997 using xda app-developers app
To add to that, use qkster's link to get back to stock.
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda premium
Okay so I tried the Heimdall One Click Stock --
unfortunately, it stops working at the "clearing interface" stage -- says it failed. And I've changed the cables but still the same result.
You are on the right track... just that something is missing.
Be sure to get rid of kies.
Be sure you have the latest version of Java. http://www.java.com/en/
Use the link in post 13 that psal gave you - read at least posts 1 and 2 all the way through, then go through and perform each step.
The first time is a process, after that it is quick and easy. Thanks to qkster. :good:
Here is an award winning-less video of the process that you might want to watch as you may see a step in the video that you are missing. Hope this helps.
http://www.youtube.com/watch?v=sHyY7WHx4zc
Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated failures. Persistence and determination alone are omnipotent.
Calvin Coolidge
So, last night I had huge trouble, and spent a good 6 hours researching and looking for answers to no avail. I messaged andros11 (thank god I did) and suggested some methods I could try. I made this guide because I see a couple of people with similar problems, and I hope this could help them, too.
[PROBLEM/DIAGNOSIS]
* I "lost" IMEI, but /efs seems intact.
* ODIN cannot see the phone, even if drivers are installed
* Phone appears as "Unknown Device" or "Gadget Serial" on computer (made sure it actually is my phone, remove all other unnecessary USB devices and see that my phone actually appears so)
* Heimdall sees the phone, but the one-click method throws up an error when it tries to match PIT (probably because this is a ROGERS phone, model SGH-I997R and slightly different from the ATT model)
* Phone still boots up fine, both recovery and system
[WHAT I USED]
The GB PIT file from the UCLB3 Unbrick at http://forum.xda-developers.com/showpost.php?p=27283140&postcount=1
Stock Rogers Kernel UXKG3
Stock Rogers ROM UXKG3
Heimdall Suite
** you can use the files for UCLB3 if you aren't on a Rogers Infuse 4G
[PROCEDURE]
1. Went to Download Mode
2. Open Heimdall front end, click on Utilities tab and click on Detect to see if Heimdall can see the phone. If it does, we're good to go. Otherwise, it may tell you that the wrong drivers are installed or it can't see the phone at all. Heimdall uses it's own drivers. Open zadig.exe under /driver to install. (make sure your phone is selected on the drop down then click install. Once complete, go back to detect your device)
3. Extract infuse_gb.pit from UCLB3 Unbrick.
4. If you are using the UCLB3 files, feel free to do so. Extract PDA and PHONE.
5. Extract the contents of BOTH the PDA and PHONE fies (they're probably .tar.md5, to extract them change file extension to .tar and extract contents) you will now have these files:
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
zImage
modem.bin
6. Back to Heimdall frontend, select Flash tab, and click BROWSE on the PIT section. Select infuse_gb.pit
7. Click on ADD on the right (partitions), and then on the dropdown selection under PARTITION NAME select PARAM
8. Just below it, under file, click BROWSE and select the param.lfs file you extracted earlier.
9. Do 7 and 8 for: MODEM, CACHE, DBDATA, and FACTORYFS. Make sure you match it with the correct file.
10. Do 7 and 8 for: RECOVERY, but for the file select the zImage
11. Do 7 and 8 for: KERNEL, and use the zImage file
12. You can check Repartition, if you want to, all this will do is match your partition to UCLB3 making One-Click back to stock work in the future. You can leave it unchecked if you don't wish to change your partitions. (you will not loose contents of you internal storage, regardless if you check this or not)
13. Click on START to flash. Once it completes successfully, you will be booted back to stock. Depending on the files you flash, you will end up with a stock Rogers ROM with root, or stock ATT ROM. What you flash is what you get.
**NOTE: I am back on track and things work fine (IMEI is there, working calls, etc). However, I am still stuck with ODIN unable to see the phone. Neither does Kies.
Glad you got it running again.
Went all the way up to jb ?
andros11 said:
Glad you got it running again.
Went all the way up to jb ?
Click to expand...
Click to collapse
Thanks! Yup, CarbonROM running and everything I'll be much more cautios next time! hehe
screw it i give up i still cant get my phone to show up on odin or heimdall. so now i cant get it rooted again. ever since i used heimdall to restore my phone to factory. my phone now wont show up on any computers and i have used multiple cables and multiple computers. im pretty sure heimdall screwed up my phone.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
im smexyy said:
screw it i give up i still cant get my phone to show up on odin or heimdall. so now i cant get it rooted again. ever since i used heimdall to restore my phone to factory. my phone now wont show up on any computers and i have used multiple cables and multiple computers. im pretty sure heimdall screwed up my phone.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
after using heimdall, u have to reinstall the corrrrect drivers for your device, i recommend using the android sdk asd download, then use device manager to install thee right driver (root\adt-bundle-windows-x86\sdk\extras\google\usb_driver):victory:
Sir you're the best.
However, I flashed AT&T on my Rogers phone.
zaghy2zy said:
So, last night I had huge trouble, and spent a good 6 hours researching and looking for answers to no avail. I messaged andros11 (thank god I did) and suggested some methods I could try. I made this guide because I see a couple of people with similar problems, and I hope this could help them, too.
[PROBLEM/DIAGNOSIS]
* I "lost" IMEI, but /efs seems intact.
* ODIN cannot see the phone, even if drivers are installed
* Phone appears as "Unknown Device" or "Gadget Serial" on computer (made sure it actually is my phone, remove all other unnecessary USB devices and see that my phone actually appears so)
* Heimdall sees the phone, but the one-click method throws up an error when it tries to match PIT (probably because this is a ROGERS phone, model SGH-I997R and slightly different from the ATT model)
* Phone still boots up fine, both recovery and system
[WHAT I USED]
The GB PIT file from the UCLB3 Unbrick at http://forum.xda-developers.com/showpost.php?p=27283140&postcount=1
Stock Rogers Kernel UXKG3
Stock Rogers ROM UXKG3
Heimdall Suite
** you can use the files for UCLB3 if you aren't on a Rogers Infuse 4G
[PROCEDURE]
1. Went to Download Mode
2. Open Heimdall front end, click on Utilities tab and click on Detect to see if Heimdall can see the phone. If it does, we're good to go. Otherwise, it may tell you that the wrong drivers are installed or it can't see the phone at all. Heimdall uses it's own drivers. Open zadig.exe under /driver to install. (make sure your phone is selected on the drop down then click install. Once complete, go back to detect your device)
3. Extract infuse_gb.pit from UCLB3 Unbrick.
4. If you are using the UCLB3 files, feel free to do so. Extract PDA and PHONE.
5. Extract the contents of BOTH the PDA and PHONE fies (they're probably .tar.md5, to extract them change file extension to .tar and extract contents) you will now have these files:
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
zImage
modem.bin
6. Back to Heimdall frontend, select Flash tab, and click BROWSE on the PIT section. Select infuse_gb.pit
7. Click on ADD on the right (partitions), and then on the dropdown selection under PARTITION NAME select PARAM
8. Just below it, under file, click BROWSE and select the param.lfs file you extracted earlier.
9. Do 7 and 8 for: MODEM, CACHE, DBDATA, and FACTORYFS. Make sure you match it with the correct file.
10. Do 7 and 8 for: RECOVERY, but for the file select the zImage
11. Do 7 and 8 for: KERNEL, and use the zImage file
12. You can check Repartition, if you want to, all this will do is match your partition to UCLB3 making One-Click back to stock work in the future. You can leave it unchecked if you don't wish to change your partitions. (you will not loose contents of you internal storage, regardless if you check this or not)
13. Click on START to flash. Once it completes successfully, you will be booted back to stock. Depending on the files you flash, you will end up with a stock Rogers ROM with root, or stock ATT ROM. What you flash is what you get.
**NOTE: I am back on track and things work fine (IMEI is there, working calls, etc). However, I am still stuck with ODIN unable to see the phone. Neither does Kies.
Click to expand...
Click to collapse
Hi, same thing happened to me last week and I've found that I have to put my phone in download mode to get the rest of the drivers completely installed. Odin has recognise my phone right away after the installation process.
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.