So I just switched to a Pixel 3 XL yesterday from an OG Pixel XL and I've having some issues with the kernel.
I build my own kernel with a couple of patches and I don't know how to flash it through fastboot on this device. On my OG XL I could just do "fastboot flash kernel" with the image I had built, but on my 3 XL that command returns "Not allowed to flash (kernel)" when I run it. Do I really have to make a flashable zip now?
Secondly, when I just try to boot the kernel, it takes quite a while to boot and then my touch screen doesn't work once it boots. The buttons all work so the device isn't frozen, but I can't unlock it or touch anything. I thought it might be one of my patches (even though they have nothing to do with the touchscreen) so I completely removed the kernel source from my PC, re-downloaded and rebuilt it (as per this page: https://source.android.com/setup/build/building-kernels) and even with the resulting bone stock kernel, my touch screen does not accept inputs when I boot the kernel through fastboot.
I suggest you use FK manager from Playstore to flash the kernel you made. It can flash any zip file. I would flash stock back and then try your kernel once you are in full stock. just to make sure it's not problem left over from your a possiblly corrupt installation of other thing.
Sent from my Pixel 3 XL
Eudeferrer said:
I suggest you use FK manager from Playstore to flash the kernel you made. It can flash any zip file. I would flash stock back and then try your kernel once you are in full stock. just to make sure it's not problem left over from your a possiblly corrupt installation of other thing.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Not really an answer to my question. The OG Pixels can flash the way I want to do it and I want to know if this has changed for the Pixel 3 and whether or not I can make fastboot allow it. The whole point is to avoid the step of making a flashable zip, since I never had to before.
If you've unlocked the bootloader and used the correct command to flash the boot image to the active slot or both slots, then all should be well!
Good luck.
I think the command you're looking for is "fastboot flash boot boot.img" where boot.img will be the name of your kernel
JeromeLeung said:
I think the command you're looking for is "fastboot flash boot boot.img" where boot.img will be the name of your kernel
Click to expand...
Click to collapse
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Homeboy76 said:
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Click to expand...
Click to collapse
This is bad advice.
mitchdickson said:
This is bad advice.
Click to expand...
Click to collapse
Please explain.
I think since the Pixel 2 the kernel has been included in the boot.img. Correct me if I'm wrong though
homeboy76 said:
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Click to expand...
Click to collapse
JeromeLeung said:
I think since the Pixel 2 the kernel has been included in the boot.img. Correct me if I'm wrong though
Click to expand...
Click to collapse
You are correct to flash the stock kernel you flash the boot.img to both slots: fastboot flash boot boot img --slot all
Homeboy76 said:
You are correct to flash the stock kernel you flash the boot.img to both slots: fastboot flash boot boot img --slot all
Click to expand...
Click to collapse
Ok, but I'm not flashing a complete boot image. I want to just flash the kernel by itself, which you could do on the original Pixels by typing "fastboot flash kernel" and I'm pretty sure the kernel was part of the boot image on those phones too.
Related
Hi.
I've unlocked my bootloader last night successfully, and went on to flash a custom boot.img.
First I did "fastboot.exe flash boot boot.img", it went through no problems. However after that, my phone boots up to Sony Ericsson logo, it goes away and screen remains black.
I've tried to flash generic global ROM ( "fastboot flash system boot.img" ) to see if I can at least restore my phone to default ROM, it still acts the same..
Anyone mind helping ?
fastboot flash boot boot.img - flash kernel
fastboot boot boot.img -hotboot kernel
what file you flash for rom?.ftf or img?if .ftf you need flashtool,but for .img just use fastboot
Sent from my LT18i using xda premium
I've used "fastboot flash boot boot.img" as my first step.
The file was .img, obviously.
Flash it back to stock with FlashTool and try it again.
Sent from my iPad 2 using Tapatalk
Heh, I haven't realised that .ftf files flash the entire thing INCLUDING kernel to the phone. Oh well, we learn every day
Thanks guys !
Hi, here is the situation. I got one half-broken Desire.
Fully formatted, s-off,cwm 5.0.2.0 with broken volume up and down keys.
So, when I get into the bootloader I can't get into the recovery to flash zip.
Anyone has some rooted image with boot.img, system.img data.img so I can flash it via fastboot?
Thanks.
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
byglet said:
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
Click to expand...
Click to collapse
Thanks didn't know that... But pretty much useless since community roms don't contain android-info.txt file and some other related stuff.
However, I've figured out that after flashing boot.img via fastboot, it shows itself up in adb devices command so I managed to get into recovery by adb reboot recovery and flashed.
Hey guys, I think i screwed up big time. I have just received my Htc one M8 from rogers (with no bloatware on it .. weird lol ) And i wanted to root it in order to use titanium back up.
So i followed a guide to root the phone everything went well execpt that now my phone boots straight into philz custom recovery....
When i was entering the fastboot commands to flash the recovery to the phone i made a mistake i wrote :
fastboot flash boot recovery.img
instead of
fastboot flash boot recovery recovery.img
....
So my guess is that i have overwritten the boot.img of the phone with the custom recovery which is bad... now i can't use the phone...
Is there a way to flash the stock boot image back? of to restore the phone like it was brand new?
Thanks for you help
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Mr Hofs said:
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Yeah this is what i wanted to do but i couldn't find a boot.img. I did find it eventually. here it is in case anyone needs it
Straight, just saying.
The boot.img is always in the rom....Most roms contain the stock boot.img. or check my backup collection and download the stock rom. It has the stock boot.img inside
Thanks a lot.
Hi,
when I flash kernel (LX11 kernel) with fastboot and install rom with cwm then i reboot and the old kernel flashes back (original sony logo).
I tried various rom-s and kernel, but always the same problem
gmocibob said:
Hi,
when I flash kernel (LX11 kernel) with fastboot and install rom with cwm then i reboot and the old kernel flashes back (original sony logo).
I tried various rom-s and kernel, but always the same problem
Click to expand...
Click to collapse
You are using wrong command to flash the kernel.
You are using
Code:
fastboot boot boot.img
but you must use
Code:
fastboot flash boot boot.img
If you miss the 'flash' part, you will hotboot the kernel, that means this kernel is used for first boot after the flashing, afterwards the kernel on phone memory is used.
Someguyfromhell said:
You are using wrong command to flash the kernel.
You are using
Code:
fastboot boot boot.img
but you must use
Code:
fastboot flash boot boot.img
If you miss the 'flash' part, you will hotboot the kernel, that means this kernel is used for first boot after the flashing, afterwards the kernel on phone memory is used.
Click to expand...
Click to collapse
Thanks, now I know something new
Hey guys I think i have a problem
I was trying to flash v4a, and realized that I needed to downgrade twrp from RC2 to RC1. My phone had been rooted by SU.
I proceeded to do the flash and then flashed the v4a mod but now my phone can't get out of TWRP. When I click reboot, it boots into the recovery mode.
Any ideas on how to solve this? I cannot use my phone now
Use fastboot to flash stock boot on both slots
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot boot twrp.img
Then flash twrp and all should be fine
mikaole said:
Use fastboot to flash stock boot on both slots
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Fastboot boot twrp.img
Then flash twrp and all should be fine
Click to expand...
Click to collapse
Just wanted to chime in so people in the future can see that this worked, at least for me on my Pixel 2 XL.
hey, I tried this method to boot back into system but lost TWRP recovery... any way to install TWRP without flashing boot.img again? or which boot.img should I be flashing back to slot A and B.. i extracted the boot.img from factory images but i lose TWRP recovery