You are awsome bro
There is. Here's fastboot help menu for reference.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found, recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition. Can override the fs type and/or size the bootloader reports.
getvar <variable> display a bootloader variable
[B][COLOR="Red"] boot <kernel> [ <ramdisk> ] download and boot kernel[/COLOR][/B]
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disableOf course you can boot kernel from bootloader. But that was not the point. If you read carefully, you'll see that the guy suggested that you can have 3.4 and 3.10 kernels on the phone at the same time and boot them at will, which is impossible.
I spoke about booting 3.4 only for twrp, not to use it for Android. You should read all related posts before posting
This statement is pure wrong , when you do a fastboot boot boot.img , fastboot will upload that boot.img to phone and boot it without flashing it to the boot partition.
about TWRP , I will try to build it when I am free. For time being , CM recovery can do basic things and it's better than no recovery.
Doesn't matter what you use it for, you can't have that:
I think you mean fastboot FLASH boot option, but I mean fastboot BOOT (without flash) option. If you FLASH something, then yes, you've overwritten the old kernel, but if you only BOOT then you only booted (and ignored boot partition) from fastboot.
But camera is working in latest fxp aosp 5.1 buikds, with full manual controls. What about cherry picking those commits?
If that's true, I didn't know that. I just can't find any documentation in support. Moreover, if that's true, it is a huge security hole.
This is the only reason why I'm not trying out this ROM. I want to safely restore to my working rom since MM has bugs, but CWM can't do that. I don't want to do anything complicated just to get TWRP working.
nope, I even tried to apply optimumpro's death touch fix, it definitely got better but not completely.
That patch does not do much in of itself. It simply hooks the kernel to the value in /system/user/clearpad.idc file. That's why you have noticed the difference. Now, you can bring that value down to fix the screen.
I don't think that the touch problems on 3.10 kernel are caused by the same thing like in 3.4 kernel. It literally stops recognizing all touches until you pull out notification bar from top or sleep and wake the device. Maybe some bug in driver? .. I don't know
