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
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.
Michael McGeagh
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.
Kind Regards,