[Q] can i merge aboot.img to compiled kernel ? - G3 Q&A, Help & Troubleshooting

SOLVED
----------
hey
i compiled stock kk kernel and after search in xda found "bump" method and now i can put bump'd boot.img to a flashable zip and flash it via custom recovery.(without bump method got security verfication failed at boot logo).
but after flash the kernel ,phone shows "fastboot mode started" .then have to restore boot from recovery to start phone normally.
i think my kernel doesnt work good with bootloader( doesnt have "aboot.img")
can i merge aboot.img to boot.img? or fix this issue while flashing the kernel?
------------------------
solved : just follow compile instruction supplied by LGe and use proper bump tool

Related

[Q] How to compile kernel from samsung and flash it?

So I went ahead and downloaded the kernel source from samsung.
I compiled it successfully and now I'm sitting with a zImage.
I tried putting it into a tar and flashing it with odin. Odin hangs after "Writing to nand".
I tried using koush's AnyRom zip and flashing it through adb sideload. It failed with a generic error.
I tried booting into fastboot, just to find out that this device has no fastboot.
Last thing which I haven't tried is pulling the boot.img and integrating the zImage. Not sure where to get the boot.img and I have spent too much time derping around already.
Same question here.
May be somebody would be so nice to give step by step instructions on how to build a flashable kernel package (either for odin or for recovery) from a compiled kernel zImage.
Thanks.
i found this off google:
http://forum.xda-developers.com/showthread.php?t=2152819
good luck

[Q] Kernel flashing problem

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

[Q] [Stock 4.4.2] Recovery TWRP secure booting error! boot certification verify

Hi, i'm on stock LG 4.4.2 rooted and I try to install TWRP recovery 2.8.1.0 with Flashify. I have the "secure booting error" when booting in recovery. Rom stock 4.4.2 is still working
How to fixe recovery it without reflash the old LG stock rom with PC ?
Thanks
qdh1502 said:
Hi, i'm on stock LG 4.4.2 rooted and I try to install TWRP recovery 2.8.1.0 with Flashify. I have the "secure booting error" when booting in recovery. Rom stock 4.4.2 is still working
How to fixe recovery it without reflash the old LG stock rom with PC ?
Thanks
Click to expand...
Click to collapse
The error means you didn't patch the recovery.img with loki_tool before you flashed it. Read the manual installation procedure found in the CWM recovery thread in the Original Development section.
Deltadroid said:
The error means you didn't patch the recovery.img with loki_tool before you flashed it. Read the manual installation procedure found in the CWM recovery thread in the Original Development section.
Click to expand...
Click to collapse
Yes, I know but I'm not the only one who has this problem.
The question is : How can I fixe it without re-flashing the hold stock rom (1,2Gb) with PC and lost root ?
If you can get it to boot into the system, then you should be able to fix the problem by following the manual installation instructions using loki_tool. You can find those instructions on the CWM thread.

Flashing OTA failed. I need help to restore my phone.

Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....

Flashing custom kernel to lg g8 thinq device

I trying do flash custom kernel to lg g8 device with success, I do the following steps:
I downloaded the exactly kernel sources from official lg site
Build the kernel according to instructions (README file)
Unpack the original boot image (via known script unpackbootimg.sh)
Replace the zImage and repack to new_boot.img (via known script mkbootimg.py)
Flash the kernel via fastboot ("flash boot new_boot.img")
Doing restart
Unfortunately, the operating system does not start up and doing restart again and again. Do I need to disable some features in the kernel ? I see in lg g7 everyone doing this with twrp (wipe partition and doing factory), Do I missed something ?
Thanks,

Categories

Resources