Originally Posted by robak1965
miked63017, you appear to be very knowledgeable about recovery builds, and as you know "unified" builds are rarely grand unified which is all inclusive. S5, S5 Sport, S5 Active, etc. The builds just don't work across all variants, so in my opinion it shouldn't be called unified.
Anyway, what I wanted to pick your brain about was in fact the S5 Sport variant, specifically if it might be the same issue, or if you have experimented with TWRP build for this?
I am trying compile my own build setup but as a beginner I am probably many weeks away from putting anything together. More of just a slow learning process for me.
Sent from my BN Nook HD using XDA Premium HD app
Honestly I haven't ever compiled TWRP from source. I compiled the s5 kernel from source, after tweaking the config. I got a few hints on what needed to be tweaked by asking around. After that I basically injected the different kernel into the official build, similar to how you would do it if you were using a kitchen. IMO though kitchens are too confusing and you never really know exactly what they are doing unless you read the source of the kitchen. That's basically how I learned to do everything I can do, dig through the source of various android kitchens. I have compiled kernels and lots of other stuff before I ever picked up an android device so I guess I had a little head start in that regard. The s5 uses a kernel with dtb, which was new to me when I got the s5, so it is slightly more complicated than the older devices I was used to. @sleshepic
wyn gave me some really useful pointers when I got my s5, thanks guys. I could go into how to do it here, but if you google, or search the forums, you will find many in detail tutorials. Try searching "how to unpack boot.img android". The process is the same across all devices pretty much, the newer ones require a newer version of the tool. Basically once unpacked you can swap out kernels and modify the initramfs, then repack and flash. I attempted to make one for the sport using the sport kernel, and fstab files from the sport, but apparently it boots to recovery then immediately reboots to system. I don't have a sport so really not inclined to try much more. If you want to try, do a little research and get going
, send me a pm along the way if you get stuck and I will try to help or point you in the right direction.
I have compiled AOSP and CM from source so I would imagine TWRP and CWM are not much harder. The hardest part, and most time consuming, IMO is setting up the device tree for a new device. I usually leave the device tree to the experts, mainly because of the time commitment. I preach Linux to everybody I know, but it is almost a requirement for doing things like this so if you don't have it get it Ubuntu is usually the easiest to setup a build env and get the needed tools. Recently I was inspired by TN to give my first Linux love, opensuse, another try and I did yield a successful AOSP build for the emulator. So my Ubuntu VM on my opensuse system will most likely not be used much anymore.
Anyway, read sources, get Linux, experiment...good luck and pm me if you get stuck.