I want to use DS5 in Samsung Galaxy S5 phone (SM-G900H) having a Mali T628 GPU. Should I follow the tutorial as in Nexus 10 from the link below and download Android 4.4.2 kernel or download a specific SM-G900H from opensource.samsung.com?
Using DS-5 Streamline with Mali on Google Nexus 10
Will either of those kernel build-ups work equally well? Moreover, in the tutorial using on Galaxy Note 3, ODIN is used to insert a custom kernel. Is that the case with Samsung Galaxy devices also? I was not able to access the bootloader using this command below:
adb reboot bootloader
Using ,the phone was just re-starting up and not going to bootloader. Is that the general case with S5 devices? Is there any work-around for inserting the new custom boot.img file?
Thanks
Hi shabby26,
We have not yet tried DS-5 on the Samsung Galaxy S5 device so have no official guide for this as of yet.
I would also suggest following this guide instead Using DS-5 Streamline with Mali on Samsung Galaxy Note 3 & 10.1, as the Galaxy Note devices will be closer to the S5 than the Nexus 10 is.
You must use the exact same kernel sources as samsung provide for the intended device. It will not work to use the kernel sources from a different device.
The bootloader for Samsung Galaxy devices differ to that of Google's Nexus devices. adb reboot download would be what you need to enter ODIN mode and flash your custom generated boot image.
If you have success, please do let others know, whether in this location, or feel free to write your own guide and publish it on the community.
I will also let you know if/when we write a guide.
Kind Regards,
Michael McGeagh
Hi Michael
I would surely write a sequence for S5 once I am done with getting a gator.ko file. I was trying to build the kernel 'in tree' by making a gator folder in drivers directory and copying all the gator-driver files. This technique worked for me while building and extracting gator.ko for Nexus 10. On menuconfig, I selected the options same as those mentioned in Using DS-5 Streamline with Mali on Samsung Galaxy Note 3 & 10.1 . Now, without in tree insertion of gator folder, the kernel is building up and zImage file is coming out. But on adding a gator folder and selecting Gator support from menuconfig and then trying to make, I get the following error:
In file included from ./drivers/gpu/arm/midgard/malisw/arm_cstd/arm_cstd.h:55:0,
from ./drivers/gpu/arm/midgard/malisw/mali_stdtypes.h:44,
from ./drivers/gpu/arm/midgard/malisw/mali_malisw.h:35,
from ./drivers/gpu/arm/midgard/mali_kbase.h:23,
from drivers/gator/gator_events_mali_midgard_hw.c:25:
./drivers/gpu/arm/midgard/malisw/arm_cstd/arm_cstd_compilers.h:244:65: error: "MALI_GCC_WORKAROUND_MIDCOM_4598" is not defined [-Werror=undef]
cc1: all warnings being treated as errors
make[2]: *** [drivers/gator/gator_events_mali_midgard_hw.o] Error 1
make[1]: *** [drivers/gator] Error 2
make: *** [drivers] Error 2
Is it something you have encountered before? Please let me know if you have any suggestions here. I also did this change and tried without that also:
Thanks!
Without testing, you could set MALI_GCC_WORKAROUND_MIDCOM_4598 define to be 0... e.g:
-DMALI_GCC_WORKAROUND_MIDCOM_4598=0
Does that help?
Note that that workaround is only needed for arm-eabi-4.7. If you use a different toolchain, it shouldnt be required.
Yeah that helped. I have one more question. I downloaded the stock FW for the device which comes as a zip file inside which there is a md5 file which contains a boot.img which I extracted and recreated using the new built kernel. In Using DS-5 Streamline with Mali on Samsung Galaxy Note 3 & 10.1 you generated a boot.odin file by subtracting a 272 byte signature specific to that model. How did you get that signature value? Do I need to follow a similar approach by generating a boot.img.tar.md5 and use ODIN to simply PDA/AP+Start to flash that up? I tried using
heimdall flash --BOOT boot.img
but that did not work even after drivers installation followed by stuff mentioned in their tutorials and troubleshooting sections.
In my experience, heimdall only worked on the S2 and S3 devices. I never managed to get it working for the Note 3, 10.1 (2014) or 4. This is why I recommend using ODIN instead.
I am uncertain why the 272 byte signature is required for the Note 3 and 10.1, however it is not needed for the Note 4. Therefore I cannot state whether the S5 will or will not need a signature, and if it does, whether it will also be 272 bytes, etc.
What I can suggest is, obviously after making a backup and having the ability to recover the device... just experiment and try with and without the signature.
Again, apologies for not having a better answer for you, without having the device and going through it myself, I can only offer suggestions.
Using ODIN is leading to the device getting in bootloop. I had to remove the soft brick by reinstalling the backed up kernel. Please let me know if you are aware of any other technique.
I have had bootloops before and it was not due to ODIN, but rather the boot.img.tar.md5 being incorrect for the particular device.
I do not believe Heimdall or any other method will fix this, as I believe the problem lies in how you generate the boot.img itself.
These are the steps I would take:
Do you have a working boot.img (stock or otherwise)?
Test it by making it a boot.img.tar.md5 (do not modify the kernel or any other contents) then flash this via ODIN.
If it doesnt boot, then it is not due to updating the boot.img with custom content, but rather the procedure to turn a boot.img into a boot.img.tar.md5 (most likely the signature part)
Have you tried with and without the 272 byte signature?
Assuming this does work, then the problem lies in updating a working boot.img to contain your custom kernel.
I have had mixed success with mkbootimg and unpackbootimg.... perhaps try alternative methods, such as abootimg?
I hope some of that was useful for you. Please keep us informed of your progress.