title: How to debug bootloop?
body: <p>I built custom Cyanogenmod 13.0 for <strong>Galaxy S5 Exynos (G900H)</strong>, however after I flash my ROM, the phone is <strong>stuck on bootloop</strong> with the Samsung logo turning off and on in a loop.</p>
  
  <p>since CM and LineageOS does not support my specific S5 model (G900H) - I added the missing folders (device, kernel, hardware etc.) from fevax's repositories (<a href="https://github.com/Fevax" rel="noreferrer">https://github.com/Fevax</a>).</p>
  
  <p>After fixing some compile errors and adding all of the needed fevax's repositories, I successfully built a CM ROM zip file using the 'brunch k3gxx' command.</p>
  
  <p>However, as I said, flashing it (after factorty reset) using TWRP recovery goes into bootloop. I also tried flashing only recovery/boot/system partitions using heimdall but it also leads to bootloop.</p>
  
  <p>I thought that maybe the problem was the toolchain but after a long research I found out that it was probably ok (prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-).</p>
  
  <p>In addition, fevax has published his own ROM for this exact model and I flashed it successfully and it works fine. I tried to contact him (Email, xda messages etc.) but he didn't answer me yet. I want to make my own custom ROM, so his ROM only proves that it is possile to create a custom CM ROM for this special S5 model.</p>
  
  <p>Currently I have no idea how to even understand what causes the bootloop, the 'brunch k3gxx' log does not show any unusual warnings or errors.</p>
  
  <p>So, <strong>is there any way to debug a bootloop</strong> is Samsung Galaxy S5? Or any other way to get information about why that bootloop occures?</p>