Recent content by clemsyn

BLADES!!!!!! Been awhile =)

Just got a hold of support and says that our bootloaders are LOCKED... so a modified boot.img will brick the device :( hopefully they release an unlock tool soon so we can start developing.

I have compiled a kernel for the Ze550ml using ASUS released kernel sources and I got a kernel file. Usually when unpacking boot.img file, I usually see just two files.... the kernel and the ramdisk. With this original boot.img I found a third one which is "second bootloader" file. I...

kernel I have compiled a kernel via instructions from ASUS for the ZE550ml but I have a couple of questions (been so long since I did this :) ) so I need help. Instead of the usual zImage file, I got a kernel file and a bzImage file (both files have the same size as the original zImage)...

Don't think this is true, just looking at the dates of the comments, it doesn't add up. I have a feeling that doesnt a fastboot oem unlock (with a droidboot.img) can brick the device. BTW, I have compiled a kernel using the instructions by ASUS but I need help. It gave me an output of...

It might :) Looks like the bootloader is unlocked because root was possible via system.img fastboot flash. Looks like ASUS also released their stuff appropriately so it's just a matter of time before a hard working dev would release an AOSP :) I could be wrong though and bootloader is not...

If root is successful, then I guess bootloader is unlocked? Is it just a process of flashing our boot.img and flashing it back to original if it doesn't work? Same with system.img or does it need to be signed? Sorry it's been a very long time since I developed kernels but I just got this...

The GPU is not overclocked. Google just optimized the GPU core in JB that is why we are getting higher scores, but the GPU clock is basically the same at 300mhz. I have OC'd the GPU to 400 and I have to say, this thing flies :)

It is the nominal voltages set in the kernel that is causing the SOD in some devices. I lowered it a bit and fixed some timings for 1704 (which I doubt will be stable anyways). The changes are in fosser2's git in "overclock" branch.

I can say for certain that this is due to the voltages set in the kernel (core and rails)... some devices just can handle it better than others that is why some don't have the issue. If I get the time tonight, I'll look at the fosser's github soon and fix this issue :)

:) Not yet, but will start working on a new kernel after the holidays... Been really busy especially with kids off school.

Big Thanks to musicadkinson for the donation :)

Thanks for your donation :)

Wish I could try this :) Sent from my Malata SMBA1002 using xda app-developers app

Thanks to steveman29 for another donation :)