I just got my Pixel 3 XL today and have unlocked to the bootloader so I could flash my custom kernel but fastboot returns "Not allowed to flash (kernel)" when I run "fastboot flash kernel Image.lz4-dtb".
This is how I did it on my OG Pixel XL, and I'm wondering if something has changed now from the Pixel 3 XL?
Which kernel, usually custom kernels are flashed in twrp.
wangdaning said:
Which kernel, usually custom kernels are flashed in twrp.
Click to expand...
Click to collapse
My own kernel, that I built myself. I know people who release kernels typically make them into flashable zips but for my purposes that is extra work that I never had to do because "fastboot flash kernel" worked fine on the Pixel XL.
Well, the kernel is the boot partition, so you might need "fastboot flash boot /yourkernel" However, I am not sure about the format of your kernel, I have only flashed them as .img files.
wangdaning said:
Well, the kernel is the boot partition, so you might need "fastboot flash boot /yourkernel" However, I am not sure about the format of your kernel, I have only flashed them as .img files.
Click to expand...
Click to collapse
The kernel is not the whole boot partition and I'm pretty sure if I flash the whole boot partition with my kernel image, the phone will no longer boot. As for the format of my kernel, it's the exact same format that was output when I used to build kernels for my OG Pixel XL and if you read the section on building kernels here: https://source.android.com/setup/build/building-kernels, you'll see that it is the correct format.
Related
Hey,
So I've been trying to get certain roms such as Cyanogen or the ParanoidAndroid rom working however I can never get past the boot screen. I've followed the instructions, flashed the boot.img, cleared the cache etc but they just get stuck on the boot animation. Stock based roms such as LeeDroid or TrickDroid work fine even when I need to flash the boot.img. I've got an s4 model and am running the latest version of twrp. Any ideas why they won't boot? I'm sure I must be making as mistake somewhere but I can't seem to figure it out. Any help would be much appreciated.
Seems like a kernel issue if you could only boot sense-based roms.
Did you flash the boot.img via fastboot or you relied on TWRP?
Also you wiped everything? (factory reset/cache/dalvik)?
Pheroh said:
Seems like a kernel issue if you could only boot sense-based roms.
Did you flash the boot.img via fastboot or you relied on TWRP?
Also you wiped everything? (factory reset/cache/dalvik)?
Click to expand...
Click to collapse
What Pheroh said. Dont trust TWRP flashing boot.img for you. If you have ADB working you can check kernel version to try figure out if it was flashed properly by checking the date in the output of
Code:
adb shell uname -a
even if it pretty early in the boot process, just keep spamming it.
Hello everyone,
Excuse my noviceness here but I have a few questions. Im NOT new to flashing roms on Android but NEW to flashing roms on HTC Devices. I came fresh off a Galaxy S2 where things were more simple.
I have a STOCK Rooted HTC ONE S (TMO USA VERSION) and want to install TrickDroid. In the install instructions it asks to install Stock HTC kernel for Android 4.0.4 (BOOT FLASH SCRIPT).
Do I have to do this since I am running the stock rom (never changed or touched kernel) with TWRP recovery? Can I skip this step? See below the section in BOLD UNDERLINED... Must I follow these steps at this point or skip them?
Instructions:
Download ROM
Download tweak package
Copy ROM and tweak package to your sdcard
Fullwipe (data and cache)
Flash the ROM
Reboot into bootloader
Go into fastboot mode
Flash the stock boot.img from the ROM with fastboot, TWRP does not help!! (You can also use the Boot_Flash_Script I deliver you which runs every command for you)
Fastboot erase cache if you do not use the Boot_Flash_Script
Let the ROM boot
Flash the tweak package
Enjoy
And for those who are wondering if i did read through the threads and tips... I have, I spent several hours looking for an answer before i had to resort to asking!
Thanks to whoever can answer and educate me as to why I must or must not have to flash the boot image.
you can try without them first and if it doesn't work, rewipe and flash the boot.img from the trickdroid rom (just extract the .zip file on your computer and there it will be)
Can I push it with root explorer or with TWRP once i get the boot.img?
jgentry151 said:
And for those who are wondering if i did read through the threads and tips... I have, I spent several hours looking for an answer before i had to resort to asking!
Thanks to whoever can answer and educate me as to why I must or must not have to flash the boot image.
Click to expand...
Click to collapse
It's just the way HTCDev unlock the bootloader, it doesn't allow for certain partition to be flash. Boot is one of them so you'll need to flash the boot.img separately.
TWRP work for some but not others to flash the boot.img.
Just like HidaKureku said, just flash using TWRP if it boot up fine. If it doesn't just bootback into fastboot and flash boot.img
Thanks for the valuable info.... I risked it and was rewarded. i was able to install the rom and the tweaks without touching the boot.img...
Now for future refrence...
How can I Flash the stock boot.img from the ROM with fastboot? Do i just pull the boot.img and go into bootloader and do it from there?
Funny thing is that on my phone not only I can flash the boot.img with TWRP, I noticed that I don't even have to flash it at all! When I installed the ROM using TWRP it automatically installed the boot.img.
jgentry151 said:
Thanks for the valuable info.... I risked it and was rewarded. i was able to install the rom and the tweaks without touching the boot.img...
Now for future refrence...
How can I Flash the stock boot.img from the ROM with fastboot? Do i just pull the boot.img and go into bootloader and do it from there?
Click to expand...
Click to collapse
Just copy the boot.img to your fastboot.exe folder
CD to that folder in Command Window
Type: fastboot flash boot boot.img
I don't remember if "fastboot erase cache" is recommended after you flash the boot.img
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1954060
http://forum.xda-developers.com/showthread.php?t=1955303
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
as mentioned in other threads.. if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it
To clarify, flashing the boot image from fastboot is only necessary if you are on hboot 1.14 b(coming from AT&T firmware 2.20). Previous hboot versions, the kernel is flashed automatically when you flash the ROM.
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
Yes there is a sense kernel and one for non-sense roms (aosp)
Usually the dev will have a kernel link posted on their page
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
redpoint73 said:
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
Click to expand...
Click to collapse
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file. So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
If you can point me to a how-to on this, I'd appreciate it - I hate filling boards with asinine questions.
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
viper doesn't require you to flash the boot image, it does it for your.
For cm10 or liquidsmooth you need to, an easy way is using Flash GUI. its available on the market and xda. you don't need to hook up to a computer to flash boot image, makes things much easier and faster.
originalseven said:
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
Click to expand...
Click to collapse
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
originalseven said:
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file.
Click to expand...
Click to collapse
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
originalseven said:
So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
Click to expand...
Click to collapse
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Awesome - thank you so much. Cleared that up completely.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
originalseven said:
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
Click to expand...
Click to collapse
flashimagegui is perfectly supported. got support awhile back. [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
nothing, it should work fine
Sent from my Nexus 5 using XDA Free mobile app
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As jd1639 said... Yes, flashing the stock boot.img should be just fine.
Probably easier though, you can also just dirty flash the ROM that your currently running on your N5 without wiping anything and then while still in recovery, just flash the custom kernel that you want to switch too and done.
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
simonarturo said:
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
Click to expand...
Click to collapse
Very true... Some kernels do modify the system and that's why I find it easier to just dirty flash the ROM that I'm currently using, since it wipes the system partition and then you don't run into issues.
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
maroc84 said:
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
Click to expand...
Click to collapse
Yeap.. Nothing will be erased.
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
maroc84 said:
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
Click to expand...
Click to collapse
If you mean the flash-all.bat, it will erase all data! Just flash the /system and /boot images and then flash the custom kernel..
Or, you can dirty flash the stock 4.4.4 rom and then flash the custom kernel.
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
maroc84 said:
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
Click to expand...
Click to collapse
No need to flash radio as well. Flashing boot.img and system.img will do the job is you're on stock and you're guaranteed to not lose your data. I think that will only happen if you flash userdata.img
Just flash the rooted stock zip ROM.
Sent from my Nexus 5 using Tapatalk