How do you find the kernel config file and copy it?
What do you mean exactly ? The kernel is related to two things.
1: the boot.img file
2: the modules that are part of/installed with a rom
Mr Hofs said:
What do you mean exactly ? The kernel is related to two things.
1: the boot.img file
2: the modules that are part of/installed with a rom
Click to expand...
Click to collapse
Im looking for the kernal config file that was used to compile and install a kernal on my device. Isnt there some sort of related config file?
Im looking to use a config file that would allow me to compile a new kernel in linux.
I think you need to start with decompiling the boot.img.
Mr Hofs said:
I think you need to start with decompiling the boot.img.
Click to expand...
Click to collapse
What would be away to access the boot image? Terminal Emulator? If so what would be some useful commands? Thank you.
Related
I want to apply this fix http://forum.xda-developers.com/showthread.php?t=1824533 on stock PA RC2 kernel. Is it possible to unpack boot.img file?
vaderx10minipro said:
I want to apply this fix http://forum.xda-developers.com/showthread.php?t=1824533 on stock PA RC2 kernel. Is it possible to unpack boot.img file?
Click to expand...
Click to collapse
this fix is applied to the source, even if you did unpack the boot.img and the kernel, it would not be a simple comment out of the line
bagofcrap24 said:
this fix is applied to the source, even if you did unpack the boot.img and the kernel, it would not be a simple comment out of the line
Click to expand...
Click to collapse
So do I have to live with multitouch screen issue? I don't want to update coz RC2 is the only version where I can have full tablet mode.
I started making my ROM with Android Kitchen and I dumped system folder from ftf file.
But I cannot find META-INF and boot.img to use for ROM.
I tried using MIUI v4 META-INF and boot.img but I get status 6 error while installing ROM. By Kitchen's FAQ it means something is up with update-script. So, I need to find stock boot.img for latest ICS Arc S firmware and associated META-INF with update-script.
I searched for those files for more than 8 hours, still can't find them.
I hope if anyone posts them that I could be able to normally install ROM without a problem.
Thank you in forward.
Err, there is no stock boot.img. All stock kernels are provided in the stock firmware packages also known as FTF files.
Depending on what you need it for, you can download the source code(, make the modifications) and compile it yourself.
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Sahaab said:
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Click to expand...
Click to collapse
Yeah, that's what I though after someguyfromhell wrote a post and I made a new zip without boot.img and deleted write_raw_image line from update-script.
Right now I am searching for solution to other problem(some folders and files are not showing up on my sdcard while viewing it in Windows, so I have no space to drop ROM in there, will try when I fix this).
Thank you both for replies, will try to fix this soon.
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
If you are going to do a ROM for locked bootloaders, then there is no boot.img needed at all. Locked bootloader means stock kernel, means no boot.img.
Also, it is not needed. Some ROM developers supply their own kernels together with the ROM, however it is not a requirement.
I'm playing around with a number of configurations on my phone and need to get a hold of a stock kernel. I'm bouncing between 4.16.1540.8 and 4.16.401.10. I do have a system dump of 4.16.401.10 - not sure if there's something in there I'm not seeing.
Any ideas?
This what you're looking for?
https://drive.google.com/file/d/0B-5KYf7UQ2lZUkNVUkVYaFdualU/view?usp=sharing
No, don't think so. Believe this is the bootloader
diceman725 said:
No, don't think so. Believe this is the bootloader
Click to expand...
Click to collapse
boot.img is the kernel not the bootloader. If you open any rom around here you will find the boot.img included
Nice. Ok. Thanks
TempestZ said:
boot.img is the kernel not the bootloader. If you open any rom around here you will find the boot.img included
Click to expand...
Click to collapse
What about the stock kernel modules?
Aren't they in the ROM?
Bobbi lim said:
What about the stock kernel modules?
Aren't they in the ROM?
Click to expand...
Click to collapse
Yes of course they are, the "kernel" in its completeness exists of the :
Boot.img file and the kernel module files which are indeed inside the rom.
Thought you would know that as you released a rom on the HTC one X ?
I have an SM-807T tablet, which has very little available for it so far and i need a selinux permissiveable kernel. Being seasoned in programming linux and compiling i attempted to create my own, so i got the correct source code from samsung, changed the selinux flag and compiled, no problems. Everything compiled correctly, so i got the stock boot.img tore it apart, replaced the kernel and put it back together. attempted to flash it and it got stuck in an infinite loop. Backtrack, thanks to some stellar members here in an earlier thread i got ahold again of the stock kernel and restored my tablet, fast forward a few more days i still cant get it to work, only thing i can find is people saying that when you compile the kernel you need to replace the drivers on the ramdisk... i understand that however it seems that this kernel all modules are self contained. Can anyone direct m on what i may be doing wrong? i can provide any information that may be needed, i just dont know what could be required so i hope the explanation itself can surfice until someone can let me know what kind of information i need to post.
Thank you.
Are you compiling a kitkat or lollipop kernel and is your boot loader and current Rom compatible with that kernel?
Have you looked at the kernel logs?
ashyx said:
Are you compiling a kitkat or lollipop kernel and is your boot loader and current Rom compatible with that kernel?
Have you looked at the kernel logs?
Click to expand...
Click to collapse
Thank you for the reply, It is a kitkat kernel as it is the only available version, lollipop source has not been released yet. My rom version is the same of the source
KOT49H.T807TUVU1ANK SuperSkillRom Build
T807TUVU1ANK source code.
also what kernel logs are you referring too, are there logs in the android os that may be logging the restart error?
the baseband version is T807TUVU1BOE1, is it possible that could be causing my issue?
ashyx said:
Have you looked at the kernel logs?
Click to expand...
Click to collapse
I missed this part the first read What kernel logs are you referring to, compile logs or logs in the android os that might be logging the error? If it is the later, where exactly would i find those?
In an android terminal such as adb or recovery. su then cat /proc/last_kmsg > /sdcard/last_kmsg
This has to be done immediately after the last boot.
ashyx said:
In an android terminal such as adb or recovery. su then cat /proc/last_kmsg > /sdcard/last_kmsg
This has up be done immediately after the last boot.
Click to expand...
Click to collapse
Thank you for that, i found what happened though im still at a loss at how to fix it. My linux knowledge stops at things i haven't encountered before.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
is the panic line. I will attach the whole log if you think there might be more helpful information in there.
Which config did you use when building and where did you get the ramdisk from?
ashyx said:
Which config did you use when building and where did you get the ramdisk from?
Click to expand...
Click to collapse
the ramdisk used was the boot.img from my rom i am using, superskill v1
the config i used to compile was chagalllte_usa_tmo_00_defconfig.
Ceirnos said:
the ramdisk used was the boot.img from my rom i am using, superskill v1
the config i used to compile was chagalllte_usa_tmo_00_defconfig.
Click to expand...
Click to collapse
When you say from the Rom do you mean the boot.img was included with it or you pulled it from the device itself?
ashyx said:
When you say from the Rom do you mean the boot.img was included with it or you pulled it from the device itself?
Click to expand...
Click to collapse
Included with it, should i have pulled from the device instead? i had figured it would have been the same after the flash.
Again I thank you for your time and patience helping me with this.
Ceirnos said:
Included with it, should i have pulled from the device instead? i had figured it would have been the same after the flash.
Again I thank you for your time and patience helping me with this.
Click to expand...
Click to collapse
No it shouldn't make a difference. I think your problem is with the ram disk. Did you build the kernel with the ramdisk or just repack it and did you change anything?
If it's a repack, have you tried to repack the working kernel with the same ramdisk to make sure its not something to do with the way you are repacking the kernel with the ramdisk?
ashyx said:
No it shouldn't make a difference. I think your problem is with the ram disk. Did you build the kernel with the ramdisk or just repack it and did you change anything?
If it's a repack, have you tried to repack the working kernel with the same ramdisk to make sure its not something to do with the way you are repacking the kernel with the ramdisk?
Click to expand...
Click to collapse
The simplest things cause the biggest headaches, upon your advice i tried repacking the working kernel and it did not work. i attempted a different method and no i have a working permissive-able kernel. Thank you very much. I will rebuild it into a stock boot.img as well an test it out in order to allow the SM-T807T users who dont want to mess with compiling a more flexible kernel as well.
Your help was invaluable as i dont think i would have considered my repacking method to be the fault.
No worries, glad you got it sorted.
There any way to edit the build.prop without root and locked bootloader ?
leonardo_hd5 said:
There any way to edit the build.prop without root and locked bootloader ?
Click to expand...
Click to collapse
not possible. need root and unlocked bootloader..
I dont want to say anyones wrong normally u do have to have unlocked bl. I have ls991 no bl unlock ever. But does have root. I edit my build prop all the time. Some phones are picky and u have to mount the sys as r/w thought
leonardo_hd5 said:
There any way to edit the build.prop without root and locked bootloader ?
Click to expand...
Click to collapse
You can dump your system.img from device using Send_Command.exe and edit build.prop inside the image
Al0n said:
You can dump your system.img from device using Send_Command.exe and edit build.prop inside the image
Click to expand...
Click to collapse
yeah, i had thought about it . However, I don't now which commands use to extract and flashing the image back . I did something similar to flash the root img when I was using the lollipop .
I tried to extract the .cab file to get system.img within the KDZ , but he always gives error. I am following some guides on how to extract files .kdz .
leonardo_hd5 said:
yeah, i had thought about it . However, I don't now which commands use to extract and flashing the image back . I did something similar to flash the root img when I was using the lollipop .
I tried to extract the .cab file to get system.img within the KDZ , but he always gives error. I am following some guides on how to extract files .kdz .
Click to expand...
Click to collapse
You have to use the same commands from Lollipop on Marshmallow.
Al0n said:
You have to use the same commands from Lollipop on Marshmallow.
Click to expand...
Click to collapse
I could not find anywhere else on how to extract the system.img image from my phone using send_comand .
I tried in every way to extract the KDZ , but without success , it seems that the old tutorials do not work in the new KDZ :crying:
I managed to pull the system.img to my folder of the phone. I can see the file, but I get an error when copying it to the PC. I used the following code
dd if=/dev/block/mmcblk0 bs=8192 skip=55296 count=529920 of=/data/media/0/system.img
Click to expand...
Click to collapse
When trying to copy by using adb pull , he says I 'm not allowed . The file is in the / sdcard / .
What are u guys doing. I just use build prop editor. I has a ls991. I dont have to dimp my system image.
Sorry apparantly i didnt read. Didnt see no root
The idea is sound, as the bootloader lock should only check for an unmodified boot image (kernel).
Theoretically you could install exposed, etc. on the image. I had it in mind to build something for the Canadian variant once I have time.
Yes, the Sprint LG G4 staff even has a modified system.img marshmallow . I believe I'm 90 % of been way , just need to figure out how to get permission to move the system.img from / sdcard / to my PC.
Check out the low effort root thread, there are commands for dumping the system partition for each model. You'll then need a Linux distribution installed to mount and modify the image. There are also instructions for flashing modified system image back to the phone in the thread through download mode commands. Be very careful you are using the right command for your model.
If I have time I'll try to get more details to you but you should be able to find everything you need right here on XDA.
Thank you so much guys! I managed to extract and edit the system.img on ubuntu and I've done the flash. Everything working 100% , finally my phone seems to have 5.5 -inch true. I'm using 530dpi now modified in build.prop without adb bugs (Marshmallow ROM)
I took the trip and already and enabled all apps in double window too!
leonardo_hd5 said:
Thank you so much guys! I managed to extract and edit the system.img on ubuntu and I've done the flash. Everything working 100% , finally my phone seems to have 5.5 -inch true. I'm using 530dpi now modified in build.prop without adb bugs (Marshmallow ROM)
I took the trip and already and enabled all apps in double window too!
Click to expand...
Click to collapse
Ohh thats great new my friend!!Can u write step by step how u done it?which model u have??
I would like to write a tutorial in English, but my English is very bad . I wrote a tutorial in Portuguese , I can use google translate and risk making one in English, if there is no problem..
Leonardo, good job and thank you for writing back.
Did you run into any issues? I am hoping to do xposed if time allows.
wolfy said:
Leonardo, good job and thank you for writing back.
Did you run into any issues? I am hoping to do xposed if time allows.
Click to expand...
Click to collapse
I'm running here without any problem ! No graphic bug or something , everything ok! You can install Xposed only in img, without root?
I would like to disable some apps and install some who originally comes in .zip format , but need to research about it
leonardo_hd5 said:
I'm running here without any problem ! No graphic bug or something , everything ok! You can install Xposed only in img, without root?
I would like to disable some apps and install some who originally comes in .zip format , but need to research about it
Click to expand...
Click to collapse
I checked before, xposed without root should be okay, just need to replace the correct file on the system image.
I will replace and pasted the files downloaded from Xposed .zip. From what I saw in the scripts, there is no line to be added. But I will not have time for flash in this week ..
leonardo_hd5 said:
I would like to write a tutorial in English, but my English is very bad . I wrote a tutorial in Portuguese , I can use google translate and risk making one in English, if there is no problem..
Click to expand...
Click to collapse
Hi! I'm Portuguese, send me your tutorial! Thanks
Enviado do meu LG-H815 através de Tapatalk