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
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 !
Hey all,
So I've attempted this multiple times, and looked around for answers - founds some, but didn't quite understand them.
The name says it all: I have a PrimoU device and I am trying to install Paranoid Android. I have done the following:
Full wipe: wiped everything and formatted /system.
Then, I install the ROM from my SD card.
Next, I go to bootloader, fastboot, and flash the boot.img (Hellboy Kernel i think)
Finally, I install gapps.
Am I doing something wrong/ can anyone offer me a solution. I've seen forums saying that I am stuck in a "boot loop" and that I need to flash the boot.img... which I thought I did. I also tried to go inside the ROM and flash that boot.img but it made me loop on the HTC boot.
Regards.
gdomingo said:
Hey all,
So I've attempted this multiple times, and looked around for answers - founds some, but didn't quite understand them.
The name says it all: I have a PrimoU device and I am trying to install Paranoid Android. I have done the following:
Full wipe: wiped everything and formatted /system.
Then, I install the ROM from my SD card.
Next, I go to bootloader, fastboot, and flash the boot.img (Hellboy Kernel i think)
Finally, I install gapps.
Am I doing something wrong/ can anyone offer me a solution. I've seen forums saying that I am stuck in a "boot loop" and that I need to flash the boot.img... which I thought I did. I also tried to go inside the ROM and flash that boot.img but it made me loop on the HTC boot.
Regards.
Click to expand...
Click to collapse
Ensure that you use the proper command
fastboot flash boot boot.img.
Does the cmd say 'finished' at the end?
mihirengg19 said:
Ensure that you use the proper command
fastboot flash boot boot.img.
Does the cmd say 'finished' at the end?
Click to expand...
Click to collapse
Yes I used that command, and it says finished at the end. Which boot.img am I supposed to be flashing though? The kernel right?
gdomingo said:
Yes I used that command, and it says finished at the end. Which boot.img am I supposed to be flashing though? The kernel right?
Click to expand...
Click to collapse
Hellboy kernel,the latest one from the list.
mihirengg19 said:
Hellboy kernel,the latest one from the list.
Click to expand...
Click to collapse
So it goes: Wipe, install ROM, flash kernel (fastboot flash boot boot.img), install gapps... reboot?
gdomingo said:
So it goes: Wipe, install ROM, flash kernel (fastboot flash boot boot.img), install gapps... reboot?
Click to expand...
Click to collapse
Yes,just a change of order
Flash kernel,wipe,flash rom,reboot into rom,again into recovery and flash gapps.
(order doesnt affect much)
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
1ceb0x said:
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
Click to expand...
Click to collapse
Enter 1ce
Exit mihirengg19
1ceb0x said:
try like this
install kernel - latest hellboy kernel 15022013 - BE SURE TO NOT FLASH THE 4.2 ONE - flash only the one that has CM10 in its name.
boot in recovery
do a factory reset and then wipe system
install rom
reboot
reboot into recovery
install gapps
Click to expand...
Click to collapse
Thank you so much, I was flashing the 2013 kernel not the one with CM10.
No problem !
Hi,
I am using ARHD 21.0 with XM kernel 188v4. I want to use ViperX ROM with XM Kernel, So do I need to "fastboot flash boot boot.img" the boot.img is the one present inside ViperX.zip or I can directly flash the ViperX.zip from CWM Recovery without doing "fastboot flash boot boot.img".
monsterdoodle said:
Hi,
I am using ARHD 21.0 with XM kernel 188v4. I want to use ViperX ROM with XM Kernel, So do I need to "fastboot flash boot boot.img" the boot.img is the one present inside ViperX.zip or I can directly flash the ViperX.zip from CWM Recovery without doing "fastboot flash boot boot.img".
Click to expand...
Click to collapse
no. you still have to flash the boot.img of the rom and the kernel separately. everytime you flash a different rom you have to flash boot.img. same with kernel.
flash boot.img(rom)
flash zip(rom)in recovery
flash boot.img(kernel)
flash zip(kernel) in recovery
robchongke said:
no. you still have to flash the boot.img of the rom and the kernel separately. everytime you flash a different rom you have to flash boot.img. same with kernel.
flash boot.img(rom)
flash zip(rom)in recovery
flash boot.img(kernel)
flash zip(kernel) in recovery
Click to expand...
Click to collapse
Many Thanks
How do i flash the DooMKernel through recovery?
How do i get in recovery in the first place? lol
EDIT: Btw, i have a LT26i with .96 and i have it rooted with an unlocked bootloader
Minecraftian said:
How do i flash the DooMKernel through recovery?
How do i get in recovery in the first place? lol
EDIT: Btw, i have a LT26i with .96 and i have it rooted with an unlocked bootloader
Click to expand...
Click to collapse
Sony stock recovery cannot be used to flash recoveries (Even you can only boot into stock recovery using ADB commands).
Firstly you will need to flash CUSTOM recovery. this can be done via fastboot commands.
fastboot flash recovery recovery.img where recovery.img is the name of your custom recovery. (you will need fastboot drivers and platform tools, if you arenot sure what I am talking about ask in details)
Next you will need to flash kernel via recovery by holding volume+down button while sony logo shows when you restart your phone.
Or simply you can just flash kernel directly via fastboot commands without any need to flash recovery
Good Luck!
Hnk1 said:
Sony stock recovery cannot be used to flash recoveries (Even you can only boot into stock recovery using ADB commands).
Firstly you will need to flash CUSTOM recovery. this can be done via fastboot commands.
fastboot flash recovery recovery.img where recovery.img is the name of your custom recovery. (you will need fastboot drivers and platform tools, if you arenot sure what I am talking about ask in details)
Next you will need to flash kernel via recovery by holding volume+down button while sony logo shows when you restart your phone.
Or simply you can just flash kernel directly via fastboot commands without any need to flash recovery
Good Luck!
Click to expand...
Click to collapse
Thanks, i figured it out. I downloaded the DooMKernel's recovery and flashed it with the flashtool. Thanks
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.