Related
Here is the 100% working method. No chance to fail. Unless you make a mistake somewhere.
Download Stock ROM from below link. (thanks to Chainfire)
With bootloaders: http://www.multiupload.com/IZLCKQ3VJC
Extract the zip file to a folder. There after extract the .tar file to a folder.
Open Heimdall (you should know the drill how it works) place the files from extracted folder in respective fields .
At the place of modem, do not use the one from extracted folder. Use the link below for JPZ modem
http://www.multiupload.com/F9Z64KG9XO
unzip the file and extract modem.bin, copy in phone.
Now hit START.
After completion, reboot & immediately go to ODIN 3.1.7 download mode Oops! that’s how I worked (Heimdall & then odin ). Flash dbdata.tar as PDA (NO repartition) found in the below link.
http://forum.xda-developers.com/showthread.php?t=1073854
Reboot and relax a little. As you over worked
It will boot to Ginger 2.3.3
Still you cannot flash custom ROM’s for that you got to reboot in Odin one’s again.
Kernel for clockwork recovery (custom ROM flashable) (thanks to Chainfire)
http://forum.xda-developers.com/showthread.php?t=885734
download the last file from the list. i.e.
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip
Put in PDA and start. It will reboot and there you are ready with your flashable Gingerbread SGT.
For OVERCOME ROM 2.0 beta (Thanks to Sir Alterbridge) download the below file
http://www.multiupload.com/QW65A4Q794
copy the zip to internal SD
go to recovery, choose zip from internal SD …. Flash!
I’m waiting for BoyPPC ROM as he might probably come out with the MIUI Rom. As Mr. Alterbridge is not into eye candy stuff his work is too serious.
Is this for all verions of the SGT? IE sprint/verizon/gsm?
Odin works for me for all flash, i.e. Main rom and dbdata
Sent from my GT-P1000 using XDA Premium App
I would like to know the same also, can this be flashed with cdma version galaxy tab?
Sent from my SCH-I800 using XDA App
Would be better to title the topic better. If you was browsing teh list it would look like you was asking for help in flashing. It would be much better to make title more descriptive and tag it with [GUIDE] and take away the "??" from the end.
Probably best tu number or bullet point, make paragraphs to separate steps etc, would give it more structure.
btw, you do know that the overcome rom that is linked to in this guide comes with a very complete and precise guide to follow itself anyway?
gshadow325 said:
Is this for all verions of the SGT? IE sprint/verizon/gsm?
Click to expand...
Click to collapse
only for GSM. havn't tried on others
TheATHEiST said:
Would be better to title the topic better. If you was browsing teh list it would look like you was asking for help in flashing. It would be much better to make title more descriptive and tag it with [GUIDE] and take away the "??" from the end.
Probably best tu number or bullet point, make paragraphs to separate steps etc, would give it more structure.
btw, you do know that the overcome rom that is linked to in this guide comes with a very complete and precise guide to follow itself anyway?
Click to expand...
Click to collapse
I felt it is quiet confusing when it says there are fifteen steps to follow when actually they aren't
jacktackle said:
I felt it is quiet confusing when it says there are fifteen steps to follow when actually they aren't
Click to expand...
Click to collapse
.......................?
jacktackle said:
I felt it is quiet confusing when it says there are fifteen steps to follow when actually they aren't
Click to expand...
Click to collapse
That depends on if you want to back uo your apps or not, but for most people/everyone else it was clear instructions.
| Don't Revive Me Bro! |
GANJDROID said:
That depends on if you want to back uo your apps or not, but for most people/everyone else it was clear instructions.
| Don't Revive Me Bro! |
Click to expand...
Click to collapse
there was much more then just backup like rooting and stuff. i believe people who jump to ginger all ready went through all that process. i think Appbackup is working like charm plus you can save the apk's and flash to any device. or may be titanium is better not much into it though.
Ganjdroid, i was going through your Miui post. it's not that simple to get them working you know? i wish if some one can incorporate those files in a ROM and make it as a ready made dish Ginger without MIUI is like nothing but Froyo.
Sorry but there just isnt any need for this guide really. The overcome one isnt complicated at all and you can just skip past backup up upps section if you need to.
Plus you have no need to use heimdall and then Odin, you can just use Odin.
You also say to use a specific modem file but dont explain what version of tab that file is for, somebody may be using this "guide" that doesnt want/need that file.
If you want to successfully and accurately flash to GB stock or Overcom custom you should follow the proper guide in the Overcome thread.
TheATHEiST said:
Sorry but there just isnt any need for this guide really. The overcome one isnt complicated at all and you can just skip past backup up upps section if you need to.
Plus you have no need to use heimdall and then Odin, you can just use Odin.
You also say to use a specific modem file but dont explain what version of tab that file is for, somebody may be using this "guide" that doesnt want/need that file.
If you want to successfully and accurately flash to GB stock or Overcom custom you should follow the proper guide in the Overcome thread.
Click to expand...
Click to collapse
The reason behind this post was, i shared what iv'e experienced and there are many who could not successfully port through Odin even i faced a problem with one of the tab. i feel Heimdall for flashing Stock ROM's is more friendly then Odin.
jacktackle said:
The reason behind this post was, i shared what iv'e experienced and there are many who could not successfully port through Odin even i faced a problem with one of the tab. i feel Heimdall for flashing Stock ROM's is more friendly then Odin.
Click to expand...
Click to collapse
I kind of understand, im having the oposite experience though. I'm trying to get CM7 on my tab using heimdall but cant seem to get it to boot
tutorial needed
Hi,
For those who have flashed the JQ1 successfully using Odin3 v1.70, can you please advise the full procedure/config for an Android noob?
Understand that it should be:
- Repartition Enabled
- Shall I click "phone bootloader Update"?
- Pit: gt-p1000_mr.pit provided by Chainfire in the JQ1 Thread.
- PDA: P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar
- Phone: Pls advise how to use the JPZ-Modem.zip on the first post.
Edit: found the how to for the modem
- CSC: ¿?
Thanks and pls bear with me.
ypsmav said:
Hi,
For those who have flashed the JQ1 successfully using Odin3 v1.70, can you please advise the full procedure/config for an Android noob?
Understand that it should be:
- Repartition Enabled
- Shall I click "phone bootloader Update"?
- Pit: gt-p1000_mr.pit provided by Chainfire in the JQ1 Thread.
- PDA: P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar
- Phone: Pls advise how to use the JPZ-Modem.zip on the first post.
Edit: found the how to for the modem
- CSC: ¿?
Thanks and pls bear with me.
Click to expand...
Click to collapse
No need to explain anything. Its already all documented in teh custom GB rom thread. here. Just download guide and read.
TheATHEiST said:
I kind of understand, im having the oposite experience though. I'm trying to get CM7 on my tab using heimdall but cant seem to get it to boot
Click to expand...
Click to collapse
well, i use heimdall only for stock ROM's for rest i mean for Custom Rom's they made Clockwork.
partition check and un check play's important role also. people just ignore it sometimes while flashing Kernel's with Odin.
jacktackle said:
Here is the 100% working method. No chance to fail. Unless you make a mistake somewhere.
Download Stock ROM from below link. (thanks to Chainfire)
With bootloaders: http://www.multiupload.com/IZLCKQ3VJC
Extract the zip file to a folder. There after extract the .tar file to a folder.
Open Heimdall (you should know the drill how it works) place the files from extracted folder in respective fields .
At the place of modem, do not use the one from extracted folder. Use the link below for JPZ modem
http://www.multiupload.com/F9Z64KG9XO
unzip the file and extract modem.bin, copy in phone.
Now hit START.
After completion, reboot & immediately go to ODIN 3.1.7 download mode Oops! that’s how I worked (Heimdall & then odin ). Flash dbdata.tar as PDA (NO repartition) found in the below link.
Click to expand...
Click to collapse
<< Now that I successfully completed the above steps, my tab is no longer connecting with ODIN, no COM connected (used to see COM4 before) >> old
I rebooted while connecting to the PC and tab was then detected by Windows then back to download mode > ODIN > dbdata.tar > wipe everything > reboot
and guess what nothing more than a Samsung logo when I boot the T
jacktackle said:
Here is the 100% working method. No chance to fail. Unless you make a mistake somewhere.
Download Stock ROM from below link. (thanks to Chainfire)
With bootloaders: http://www.multiupload.com/IZLCKQ3VJC
Extract the zip file to a folder. There after extract the .tar file to a folder.
Click to expand...
Click to collapse
dbdata.rfs is missing in the tar file, where can I get it? Can I use dbdata.rfs from another package? thx in advance
DinoZ1 said:
<< Now that I successfully completed the above steps, my tab is no longer connecting with ODIN, no COM connected (used to see COM4 before) >> old
I rebooted while connecting to the PC and tab was then detected by Windows then back to download mode > ODIN > dbdata.tar > wipe everything > reboot
and guess what nothing more than a Samsung logo when I boot the T
Click to expand...
Click to collapse
this is simple and for all those who think their tab/phone do not connect to Odin.
plug in your usb to the pc. go to device manager. uninstall the samsung driver which is already there. refresh the drivers or unplug and replug the usb cable. will search for the driver and install it again. there u r connected to the ODIN.
have a nice day!
jacktackle said:
Here is the 100% working method. No chance to fail. Unless you make a mistake somewhere.
Download Stock ROM from below link. (thanks to Chainfire)
With bootloaders: http://www.multiupload.com/IZLCKQ3VJC
Extract the zip file to a folder. There after extract the .tar file to a folder.
Open Heimdall (you should know the drill how it works) place the files from extracted folder in respective fields .
At the place of modem, do not use the one from extracted folder. Use the link below for JPZ modem
http://www.multiupload.com/F9Z64KG9XO
unzip the file and extract modem.bin, copy in phone.
Now hit START.
After completion, reboot & immediately go to ODIN 3.1.7 download mode Oops! that’s how I worked (Heimdall & then odin ). Flash dbdata.tar as PDA (NO repartition) found in the below link.
http://forum.xda-developers.com/showthread.php?t=1073854
Reboot and relax a little. As you over worked
It will boot to Ginger 2.3.3
Still you cannot flash custom ROM’s for that you got to reboot in Odin one’s again.
Kernel for clockwork recovery (custom ROM flashable) (thanks to Chainfire)
http://forum.xda-developers.com/showthread.php?t=885734
download the last file from the list. i.e.
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip
Put in PDA and start. It will reboot and there you are ready with your flashable Gingerbread SGT.
For OVERCOME ROM 2.0 beta (Thanks to Sir Alterbridge) download the below file
http://www.multiupload.com/QW65A4Q794
copy the zip to internal SD
go to recovery, choose zip from internal SD …. Flash!
I’m waiting for BoyPPC ROM as he might probably come out with the MIUI Rom. As Mr. Alterbridge is not into eye candy stuff his work is too serious.
Click to expand...
Click to collapse
Hi,
i've downloaded "http://www.multiupload.com/IZLCKQ3VJC" but there is not "dbdata.rfs", only a "hidden.rfs". What file i've to put into database.data ?
Many thanks
As anyone running OS X or Linux would know, the only truly "supported" way of rooting an S4 talked about on XDA is using CF Auto Root and Odin to flash it. There used to be Motochopper, but that no longer works with recent versions of the S4 firmware.
I actually am familiar with the concepts of how flashing a device works, and upon seeing videos or pictures of selecting the CF Auto Root .tar.md5 file for "PDA" in Odin, I wondered if what was going on behind the scenes was as simple as just performing a regular flash to recovery or whatnot.
I downloaded CF Auto Root and extracted the .tar.md5 file. Why it has the .md5 extension, I'm still not sure. Perhaps it's just because Odin requires that extension? I don't know if it's actually important. Inside though, I found 2 files. They were cache.img.ext4 and recovery.img.
I did some research before posting, but didn't find anything definitive. However, I'm assuming that using Heimdall to flash would work. Because Heimdall interfaces with the device the same way Odin does, only Heimdall actually supports OSes other than Windows. Only problem is, Heimdall doesn't have a one-click "PDA" button to flash the .tar.md5 like Odin does. But would using Heimdall to flash the cache and recovery image files work? Is that all that needs to happen for the S4 to be rooted? Or does Odin also perform some additional function, some function which Heimdall wouldn't do automatically?
To make a tl;dr I guess, has anybody tried flashing cache and recovery image files from the CF Auto Root .tar.md5 file to a S4? Did it work? If so, was there anything special you had to do in order to get it to work? Any answers or insight from someone else would be greatly appreciated. If I could get this working with my S4 I might make a video tutorial so that then there's a good tutorial out there that works for OSes other than Windows.
I did it in heimdall. Worked perfectly
Sent from my SPH-L720
xchampx13 said:
I did it in heimdall. Worked perfectly
Sent from my SPH-L720
Click to expand...
Click to collapse
You just entered in the recovery.img and cache.img.ext4 files as they were and flashed? You didn't do anything else?
superriku11 said:
You just entered in the recovery.img and cache.img.ext4 files as they were and flashed? You didn't do anything else?
Click to expand...
Click to collapse
Please follow this link. I just did it a few mn ago, and it worked good. Had to do it twice (don't know why). Flash process takes only a few seconds. In case Heimdall hangs too long (> 1 mn) at " Releasing device interface" with no progress bar, power off your device and start again the process.
http://www.all-things-android.com/content/how-root-samsung-mobile-device
[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.
[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks
I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.
free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.
Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar
This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?
AT&T SGH-I337 UCUEMK2
Long story short, company is rolling out airwatch and I need to get rid of root. It's their phone, their policy. My issue is that all I have is a Mac. I've seen a few threads that link to the recovery firmware but it seems to be formatted only for Odin. Being on Mac, i'm limited to Heimdall which seems to use different files that I cannot find.
Can someone let me know where I can get the Heimdall firmware for my phone?
Thanks
Actually, you use the same firmware with Heimdall that you use with Odin. What you will start with is an "Odin flashable .tar (or .tar.md5) file". To use it with Heimdall, you will need to extract all the individual components from the tar archive. For example, you will then have files like boot.bin, sbl.bin, factoryfs.img, boot.img, data.img, hidden.img, modem.bin, etc. I'm not sure of the specific files for the S4, and I didn't open a tar archive to look, so whatever you find in the stock distribution is what you will need. Then you use them with Heimdall. There is a graphical interface and a command line tool. The command line tool may be a little more reliable. Some have had issues using Heimdall on certain versions of MAC OS.
Just wanted to post a followup. I used the instructions from here and I've got my phone back.
Thanks
HI Guys i was wondering if any one has any experience of flashing their a300fu using heimdall ?
I rooted and flashed the unofficial cyanogenmod onto the phone and have been having issue with making calls etc so wanted to go back to stock rom.
I downloaded A300FUXXU1BOJ5_A300FUBTU1BOI2_A300FUXXU1BOJ4_HOME.tar.md5 and extracted but the pit file i am using doesn’t seem to have the correct partitions ?
can any one advise how i can move this forwards the only option i can think of at the moment is to wipe Linux and install windows so i can use odin but this isn’t something which i really wish to do ? other than that does any one kn ow of a more stable rom i can flash to the device ?
I would like to know as well. Got a300fu, but I can't seem to find any roms that even flashes it. When trying to install cm13 I got patrition error, which means that somehow my device has unrooted it self and hasn't got permision. Or with cm12 I just got stuck with in bootloop. It loads the 40 apps, then restarts and It's stuck. Now I got it back on stock rom. It hasn't happened on my s3...
here's a solution I have used to succesfuly update A300FU from 4.4.4 to 6.0.1
I use XEO, ymmv.
1) Obtain correct Odin flash file (I use A300FUXXS1CQD3_A300FUXEO1CPI2_A300FUXXU1CPH3_HOME.zip)
2) Unzip
3) Untar
4) Fetch modified odin sources (https://github.com/Toxantron/Heimdall/archive/master.zip)
5) Unzip
6) Make sure to have cmake, make, libusb, zlib (I use ubuntu, so apt-get install cmake libusb-1.0-0-dev zlib1g-dev build-essentials
7) Make sure to end MTP detection (apt-get purge libmtp-runtime libmtp*)
8) Modify Odin sources to use longfile for files larger than 2GB (edit heimdall/CMakeLists.txt and make sure you have set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++11 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64") in there on line 14 (add -D_LARGE... and -D_FILE... flags)
9) cmake -DCMAKE_BUILD_TYPE=Release -DDISABLE_FRONTEND=yes
10) make
11) Backup your data (Samsung Account, Google, SD, etc) - this step is optional
12) enter Recovery, flush data/cache, boot into bootloader
13) obtain PIT file - heimdall download-pit --output youra3pit.pit
14) enter bootloader on phone (it will reboot after pit file obtained)
15) using the heimdall bin you built given its named heimdall-bin and your unzipped and untarred firmware update files reside in a300/ , ./heimdall-bin flash --APNHLOS a300/NON-HLOS.bin --MODEM a300/modem.bin --SBL1 a300/sbl1.mbn --ABOOT a300/aboot.mbn --RPM a300/rpm.mbn --QSEE a300/tz.mbn --QHEE a300/hyp.mbn --sec a300/sec.dat --BOOT a300/boot.img --RECOVERY a300/recovery.img --SYSTEM a300/system.img.ext4 --CACHE a300/cache.img.ext4 --HIDDEN a300/hidden.img.ext4 --pit youra3pit.pit --verbose
enjoy your newly updated phone
I wholeheartedly recommend this update, running non rooted stock, without greenify, it runs noticeably faster and smoother for everyday use than rooted 4.4.4 with xposed and greenify.
It's like a new life in the phone.