Can someone tell me how to flash new ROMs with a Mac? - Captivate General

So I was able to get to the stock 2.2 Froyo leak ROM which has been okay all things considered, but I want to try some custom ROMs! I can't use Odin, and Heimdall always asks for more files than are included with Odin packages to flash back to stock...
I wish I could avoid the flashing back to stock process altogether, but ROM Manager always says it can't validate or something when I try and flash from recovery mode from the rom manager application.
If anyone could give me a basic run-through I would greatly appreciate it.

http://forum.xda-developers.com/showthread.php?t=909213
3e recoverey with no verification, might be worth a read.

Get VMWare Fusion and find an old XP install someplace. Yes, it seems the "long way" to do it, as it would be nice if we could just use Odin on our Macs, but I have found that having a virtual windows XP environment on my Mac makes life easier and gives me access to windoze stuff when I need it. When I don't need it, windows XP is off and not using any system resources.
The other cool thing about VMWare fusion is you can have multiple virtual installs. Win XP, Win 7, Linux, etc. Again, they don't use any system resources when you are not using them, but it sure is handy to have around!

heimdall works great on os x. i've used the JH- and JF- firmwares without issue. other than that you can use one-click root on os x, and rom manager for everything else.
edit: are you using --repartition with heimdall? don't. the heimdall help shows two cases. with --repartition a lot of things aren't optional. the second usage lets you flash whatever you want, e.g. just a modem, just a kernel, etc.

Related

[Guide/How-To] Install, Use Heimdall, and flash back to stock

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?

[link][tutorial] heimdall 1.1 how to aka how to get root and cwm the fast way

i still see questions about rom manager cwm popping up but rom manager will shortly be irrelevent once 2.3.5 drops. modded 3e and root via rage against the cage are a thing of the past. exploits that are no longer open.
this is how rooting and cwm will be done from here on out. get used to it. don't be scared it's not hard.
i did not create the how to video only did 12 seconds of searching on google. things that will be different from the video are that you will only flash the kernel. (zimage)
what you will need:
*heimdall, any version will do but this video is heimdall 1.1. 1.3 would need another video but if i find it ill add it to the op.
*an att infuse 4g or infuse 4g galaxy s if you are canaidian
*a computer, any will do
*a micro usb cable
*an archive program
*a custom kernel (community kernel or defuse for 2.2.1 att users) hellraiser or entropy for rogers users or users that in the future get the 2.3.5 update on att
windows specifics:
drivers- these are available through kies. any version should be fine. the drivers are also on the samsung site without kies
visual c++ redistributable 2010 (should be available through the microsoft download center, google it or bing it if you prefer)
mac specifics:
codeless kext (i have zero experience with this but will see if i can find a tutorial explaining that)
instructions:
-take the kernel downloaded from a link in the dev section (search is you friend) and open it with an archive manager like win rar 7zip or other.
-extract the zimage. this is the actual kernel. if it is a flashable .zip file you will find it in the kernel folder or the updates folder.
-review the video, take note of the driver install. this shouldnt be an issue on win7 32 bit but may be a problem on other versions
-put the zimage in the kernel slot, no other slots are relevant.
-connect the phone in download mode via the data cable (volume bar+usb cable)
-flash!
enjoy your rooted phone with custom kernel cwm and voodoo lagfix! that was easy
video: http://www.youtube.com/watch?v=6TgyaUbjcm4&feature=related
heimdall: http://www.glassechidna.com.au/products/heimdall/
drivers: http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
Perfect timing. I was just researching this on a suggestion from Entropy in another thread. From what I gather once I uncompress one of these roms I can use heimdall to flash without going into recovery? Does that sound right? You will be in download mode instead of clockwork?
You state "enjoy your rooted phone with custom kernel cwm and voodoo lagfix". I assume that all comes as part of the roms? Is clockwork added in case you want to change roms or wipe data? I was taking it to mean heimdall replaced clockwork but you seem to state it will be on the phone after you flash.
Thanks for the links and all.
Not exactly. This was more about it being used as an alternative to rooting and using rom manager.
Heimdall can flash roms as well obviously but they need to either be a rom dump or extracted Odin package. They need to be in special archives in our case rfs. This is not to say a custom rom can't be manipulated into an Odin or heimfall flashable form. An easy way to do this is to take an existing Odin package and open the factoryfs.rfs image in magic iso and over write the contents with the contents of the /system folder from a custom rom. But permissions can be a problem doing these things in windows so I don't recommend this because it is a little more difficult to change the permissions inside the image than a normal archive and flashing the rom without checking the permissions could lead to a brick. The proper way to do it involves terminal and mounting the image to a loop device for editing which I have never tried. Its a bit more advanced than flashing Roms. This is where you get into some command line skills which are not too common today in our world of GUI.
Thanks for the clarification. This is just to get a custom kernel and be rooted since that is going away then? You will still need to flash using cwm or whatever to get the rom on. I guess I kind of jumped the gun because most of the heimdall flashes that i have seen on YouTube seen to be the whole rom. That's too bad. It almost seems easier that way.
Thanks for responding before I screwed up.
Sent from my SAMSUNG-SGH-I997 using XDA App
rxnelson said:
Thanks for the clarification. This is just to get a custom kernel and be rooted since that is going away then? You will still need to flash using cwm or whatever to get the rom on. I guess I kind of jumped the gun because most of the heimdall flashes that i have seen on YouTube seen to be the whole rom. That's too bad. It almost seems easier that way.
Thanks for responding before I screwed up.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
What you use for flashing is up to the rom developer. There have been Odin roms in the pastfor the galaxy s and the bootloader may need to be updated this way for people who don't choose the use the the 2.3.5 update to get the bootloaders. That means some rom developers may choose to package the rom for Odin or heimdall to get the bootloaders.

[Request][App] TWRP Flasher apk

This is a challenge to any of you ingenious bastards, to create an apk that flashes TWRP. What Rom Manager does for ClockworkMod.
I don't know to much about making apps but after reading the problems people have flashing TWRP using ADB, Fastboot and the drivers associated with said programs this is my logic: Remove the middle man(PC) and flash it staight from the phone. Trust me, people would be really grateful if they didn't need to worry about the ADB, Fastboot or the drivers, including me. $20 to whoever comes up with a solid working apk.
Thought using this Kindle Fire Utility was about as easy as it gets.
As u can tell by the forum people are still having problems with it. An apk would make it incredibly simple and universal. It wouldn't matter if u had Windows or Mac cause all the work would be done on the device.

[Q] Heimdall ROMs?

[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...

[Galaxy S4] Trying to root using Heimdall.

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

Categories

Resources