• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [OC/UC] ButterKAT Kernel for Stock 4.4.4 [KitKat]

Masterchief87 said:
I'll make a new set of switcher zips for this kernel and upload it tonight. Also, for anyone who hasn't thought of this yet, never flash a switcher zip immediately before you flash a rom because this will leave you with no recovery installed. I spent a little while last night trying to help someone who made this mistake but it seems his phone might be permanently bricked. What he did was he flashed the switcher zip for carbon ROM along with the ROM itself (in that order) and somehow got stuck in a bootloop with no recovery installed and unable to get adb to recognize the phone. I'll be adding this warning to my thread later tonight along with the switcher & restore zips for ButterKAT Kernel.
Click to expand...
He needs to boot into field test mode (FTM) and manually flash TWRP recovery.img from ADB
 
UndacoverBrother said:
funny you ask that question. I always test a kernel and set it to its max before i set it to the frequency with best performance and stability..Ive played with this kernel for 5 hours ...using wifi,,bluetooth,watching youtube,basicly steady use. No... I repeat No heating issues as of yet...BTW ..Butternoob Rom is so smooth...nice..
Click to expand...
Oh and what do you recommend for performance and stability?
 
Quadrant benchmark
uploadfromtaptalk1437446149368.png
 
I installed your .zip in my recovery with butternoob. But its not showing up anywhere. I've looked. Am I doing something wrong? I don't have r/w installed
 
If I flash this kernel and decide I want to go back to stock kernel can I just use twrp and use my last restore point I had with stock kernel? Or do I have to wipe sytem and data then restore? Or would I have to flash a stock kernel to get back to stock rooted? :=))
 
Blackhawk1969 said:
If I flash this kernel and decide I want to go back to stock kernel can I just use twrp and use my last restore point I had with stock kernel? Or do I have to wipe sytem and data then restore? Or would I have to flash a stock kernel to get back to stock rooted? :=))
Click to expand...
Yeah you can use a restore
 
Wow... this kernel makes everything run extremely smooth.. no chop when im scrolling on webpages or app drawer or homescreens.. great job MonDillinger!!!
 
Worked like a charm, CPU at full tilt, mam you guys are top notch, and I will be looking for the new set of zips, my phone has never rebooted faster,many many thanks to all of the hard work
 
Worked like a charm, CPU at full tilt, man you guys are top notch, and I will be looking for the new set of zips, my phone has never rebooted faster,many many thanks for all of the hard work
 
OK, I'm about to dive in, not a 100% comfortable yet, so I'm going to go in and do a few things, viper mainly, if anyone has any must haves to reccomend it would be much appreciated as I would like to get it done all at once thnx I'm advance
 
anyone try this on the z987? it can run the zmax roms so wondering if anyone on cricket with the grandx max+ has tried it
 
psvita501weop said:
The phones can use the same recovery and they have the same quad core 1.2ghz Qualcomm snapdragon 400 MSM8926 SoC and 2GB of ram I think its pretty safe from my view point...
Click to expand...
So does the Moto G 4G (Sans the 2GB of RAM) but you don't go flashing haphazardly. We can't efficiently test anything on you all's device, and its a reason they are different devices. If they flash, fine, we just can't fix anything, and you all will end up flashing stuff that has problems we won't go through the trouble of fixing because it isn't designed for your device in the first place. If you really want developer support, get your community to send a phone to Ethan (guy over AICP, Ressurection Remix, etc.), get us a link to your kernel source from ZTE, and we can get cooking. However, as it stands, you all are flashing a ROM that's destined to have problems.
 
You must log in or register to reply here.
Back
Top Bottom