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
Related
Hi guys, the title say it all.
i did a full wipe in recovery, installed cm10, and flashed the boot.img, but i am still stuck at the boot screen for cyanogen mod.
any ideas?
did you do the "fasboot erase cache" command?
What hboot do you have? If it's newer than 1.12 you need a different boot.img.
how do i run the clear cache?
i think i have hboot 1.2 or something like that. which boot.img should i use?
i have hboot 1.36
just like flashing the boot.img
fastboot erase cache
fastboot flash boot boot.img
Flash this boot.img
http://db.tt/uDdWaAtH
thanks a bunch. this worked great!!
in the future, when i want to try out different roms, do i need to use this same boot image?
Always use rom-specific boot.imgs found inside rom.zip.
If the ROM needs a different boot.img, it will be said in ROM thread's OP.
Sent from my One X
No, each ROM has its own boot.img.
Team Venom ViperX: http://forum.xda-developers.com/showthread.php?t=2087443
I want to flash the ViperX Kernel#10 but that's not a flashable zip,
I wonder how to flash the boot and modules?
I usually flash kernel with boot.img in cmd or XXX.zip in recovery
Anyone helps?
Yeah flash the whole rom. Extract the boot.img. flash it through the fastboot via cmd.
Afaik viperx uses the stock kernel.
Tweaks are already in the rom
jackytsz said:
Team Venom ViperX: http://forum.xda-developers.com/showthread.php?t=2087443
I want to flash the ViperX Kernel#10 but that's not a flashable zip,
I wonder how to flash the boot and modules?
I usually flash kernel with boot.img in cmd or XXX.zip in recovery
Anyone helps?
Click to expand...
Click to collapse
I suppose the tweaks are already inside the ROM zip and you don't need to flash Kernel #10. Also the boot.img is the same.
If they do actually differ in some points, you can put the modules folder from Kernel zip in the ROM zip (in /system/lib folder) and then flash the ROM.
But as I said earlier that wouldn't be needed, as the tweaks are available in the ROM from the very first day they're developed!!!
If I helped, press the thanks button.
The boot.img #10 in the OP is the same as the one in the rom.zip......so flash the boot.img and install the rom.
And if you want to be sure .... I made a flashable zip for the #10 boot.img + modules
http://db.tt/6qFZ6PSL
so i have the desire hd and i love the phone a lot but not the os too much. so heres the deal i tryed installing cyanogenmod.I unlocked the bootloader left the s-on and installed custom recovery via fastboot without a problem. next thing is I installed 3 recoverys non touch everyone different but when i install zip file with the rom it gets stuck every time on boot screen. the thing is i tried cyanogen 7.2.0 9 and 10.1 non of them worked and got stuck right on after it at the htc green logo,. whats the problem i pulled out the battery tried with only usb nothing worked. then i got scared that it isnt bricked dowloaded the original stock rooted rom as it was and installed through the same recovery .then it worked without a problem not even a glitch . i dont get it .im confused. apologies to the admin if it isnt in the right section.
my android version is 2.3.5 withe sense 3.0 and thats it . cant figure whats the problem . i flashed ducent of phones from symbian to iphone and even java based phones and even few htc ., but never had that boot loop problem., anyone please help
Fastboot flash the ROM zip's boot.img.
bananagranola said:
Fastboot flash the ROM zip's boot.img.
Click to expand...
Click to collapse
so i need to flash boot.img from the rom and flash it with fast boot then install software with custom recovery . i use boot image from stock rom or cyanogen ?
alenkosb said:
so i need to flash boot.img from the rom and flash it with fast boot then install software with custom recovery . i use boot image from stock rom or cyanogen ?
Click to expand...
Click to collapse
No, flash ROM from custom recovery first, then the boot.img from fastboot. Use a custom, not stock, recovery (CWM, 4ext, or TWRP).
bananagranola said:
No, flash ROM from custom recovery first, then the boot.img from fastboot. Use a custom, not stock, recovery (CWM, 4ext, or TWRP).
Click to expand...
Click to collapse
i used 3 diferent custom recoverys for desire hd. ill try the method.btw you cant install cyan with stock recovery .boot img from stock rom ?
no, the boot.img inside the zip of the Rom you´re going to flash at this moment
alenkosb said:
i used 3 diferent custom recoverys for desire hd. ill try the method.btw you cant install cyan with stock recovery .boot img from stock rom ?
Click to expand...
Click to collapse
I have no idea what you're trying to say. What recoveries have you tried to flash? How have you tried to flash them? How are you trying to flash the ROM? What is "cyan," ClockworkMod (CWM) or CyanogenMod (CM)? What is a "stock recovery .boot img"? You can't flash anything from the stock recovery. You can't flash the stock ROM's boot.img with a custom ROM. Recoveries do not have boot.imgs that you need to worry about. I am saying that you need to have a custom recovery, like CWM, 4ext, or TWRP, installed. You do that through "fastboot flash recovery recovery.img." You then need to download a ROM zip, boot into recovery with power and volume-down, factory reset, and install the ROM. You then need to extract the boot.img from the ROM zip you just flashed and flash it from the computer with "fastboot flash boot boot.img."
bananagranola said:
I have no idea what you're trying to say. What recoveries have you tried to flash? How have you tried to flash them? How are you trying to flash the ROM? What is "cyan," ClockworkMod (CWM) or CyanogenMod (CM)? What is a "stock recovery .boot img"? You can't flash anything from the stock recovery. You can't flash the stock ROM's boot.img with a custom ROM. Recoveries do not have boot.imgs that you need to worry about. I am saying that you need to have a custom recovery, like CWM, 4ext, or TWRP, installed. You do that through "fastboot flash recovery recovery.img." You then need to download a ROM zip, boot into recovery with power and volume-down, factory reset, and install the ROM. You then need to extract the boot.img from the ROM zip you just flashed and flash it from the computer with "fastboot flash boot boot.img."
Click to expand...
Click to collapse
Sorry for the misunderstanding. heres the deal ive had 3 clockworkmode recoverys and different versions tried 3 zips(roms) with each one and every time de same thing.BUT now thanks to your help i flashed the boot.img file and it works perfectly
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
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.