[Q] how to make boot.img from kernel ? Please help - Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl

Hai ,
I downloaded my phones kernel source and compiled with some additional configuraton..
Now I got these files .vmlinuz,image,zimage,and a tar'ed archive of zimage with name kernel_......_.tar
how can I make odin flashable (or any how flashable) rom file from this?
I tried to make boot.img with mkbootimg and initrd extracted from original stock rom
Flashing was succes according to odin But It doesnt boot.
any one please help me
I also like to know is there any way turn off splash screen and see the debug msgs from kernel during boot?
Any one please help
My phone is galaxy young GT-S5360
Update:
I figured out that problem is not with the additional configuration options I given during kernel compilation.
Problem is with the tools (or incorrect usage of tools) .
I tried making boot.img with original kernel and initramfs and that also not worked (flashing was successful.but
Booting failed).
I don't have much experience in android.i only know some linux
Any one please help me
Please please please.......
Update:
Finally I think I found how to make boot.img from kernel(zImage).The problem was with the "--base-address" option in the mkbootimg toool. I found my device's base address from kernel configuration file (.config).
now , boot.img produced from the kernel which was extracted from stock rom works well.
but boot.img produced from my custom kernel boots,but nothing displys in the screen.
I dont know how to debug it . I cant even see the debug messages from the kernel
Any one knows any clues,hints or any thing regarding this please please help me
i dont know why any no one replay to my post.
I dont have privilege to post this question in developers thread.thats why i am asking it here
Is it a wrong way? I dont know.
Click to expand...
Click to collapse

Thank you sir to be the first succefully create custom kernel...
Far before anyone can create it...
I'm always waiting ur great work again into sgy device...

Related

[Q] Issues after installing Custom boot.img

Hi,
I have downloaded kernel sources from HTC for wildfire and compiled zImage. using unpack and repack scripts I successfully installed the boot.img via update.zip. Now I see the device reboots fine, but I cannot unlock the screen, and none of the keys are functional.
I have no Idea what is still missing or have I done something wrong?? your help is need here.
Indeed I tried to compile jacobs kernel image from github but no luck.
Regards
bram

[Fix] Permanent Chinese CWM

Hello
well i also faced this issue,if ur not aware of it then let me explain a liitle.. if you have upgraded to the latest version via OTA then there are some patch files in the system which do this trick.. so in order to get permanent recovery if u flashed it via ur phone with apps like flashify or recovery tools then you need to go to
System and there you will see a file with name Recoveryfromboot.p just delete that file and flash chinese cwm and ur done :]
btw i'll try to build the english cwm as soon as i get some free time.. thanx to burakgon for releasing the kernel sources..
Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?
1manshow said:
Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?
Click to expand...
Click to collapse
i will build the cwm for our phone but i'm not getting any time to sit in front of my pc :'(
edit :
custum kernels are not working ? did you tried to compile one from the sources ? or the sources are not complete ?
I didn't tried to compile anything, but some guys did here -
http://forum.xda-developers.com/showthread.php?t=2712586
If you want, you can take a look there and contribute in your own way to resolve the issue. Thanks for your efforts so far though.

[Q] Enable ADB / USB Debugging with a broken screen

Any kernel developer can help me with this?
I have broken my lcd of my s5 and no usb debugging enabled.
So i read this here
i suggest you contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!
Click to expand...
Click to collapse
brunocssoares said:
Any kernel developer can help me with this?
I have broken my lcd of my s5 and no usb debugging enabled.
So i read this here
Click to expand...
Click to collapse
I'm a kernel developer but still new here on samsung so I can't compile a kernel for s5 yet but I can explain to you the process and maybe you have the knowledge I still don't have.
1. Get any custom kernel that's compatible to your s5.
2. Extract the ramdisk from the kernel.
3. Unpack the ramdisk and edit the rc file that's responsible for enabling adb(I think it's init.rc).
4. Repack the ramdisk.
5. Make a new boot image using the modified ramdisk and the zImage you got awhile ago when you extract the ramdisk.
6. Flash the resulting boot.img using fastboot by typing "fastboot boot <boot.img file>"
Please not that the fastboot command doesn't permanently flash the kernel and will revert back to the previous kernel after reboot.
On a second thought... I'm not sure but you can try flashing one of the recoveries here or a AOSP kernel. Most of them have USB Debugging enabled by default. At least that's true base on my past devices.
Thank you for the answer!
But unfortunately i don't know how to do this things. So, I will study a little about this and if I get a solution i will post here!
Try hard always!
One more thing: Can I use other cellphone's tutorial to do this? Like this : http://forum.xda-developers.com/showthread.php?t=1262656
sorry for my horrible english!

[SM -S920L] need someone to pull system files

As the topic says. I'm working on a custom rom...and frankly I'm ready for mine to come back to life. Much appreciated!
Sent from my HTCD200LVWPP using Tapatalk
https://drive.google.com/folderview?id=0Bza7IYQ7uyQYX2hTM1dmckdqYUE[/URL]
Here u go.. it's the full system dump for Straight Talk's.
SM-S920L~ SAMSUNG GALAXY GRAND PRIME~ All 1.71 gb of it.. I have been messing with it here & there reading + studying the methods trying to port a functional custom recovery of whichever type I can.. So far I have manged to unpack the boot.I'm & recovery.img partitions using android kitchen with cygwin.. Been trying this & that copying files from stock ramdisk and using them to replace files from an unpacked custom recovery ramdisk folder... I picked a custom recovery of a similar device to make it easier.. So far each late night attempt has ended with "SEANDROID ENFORCING" & or Odin mode as recovery.. Hopefully by putting this out there I will further development & speed up the process somewhat as the chances of me succeeding in a successful port are looking slim.. If more files are needed Im more than willing to provide whatever & also have no issue with doing the testing if the developer won't have this particular device in hand at the time.. Thank you in advance and good luck...
sdw1988 said:
https://drive.google.com/folderview?id=0Bza7IYQ7uyQYX2hTM1dmckdqYUE[/URL]
Here u go.. it's the full system dump for Straight Talk's.
SM-S920L~ SAMSUNG GALAXY GRAND PRIME~ All 1.71 gb of it.. I have been messing with it here & there reading + studying the methods trying to port a functional custom recovery of whichever type I can.. So far I have manged to unpack the boot.I'm & recovery.img partitions using android kitchen with cygwin.. Been trying this & that copying files from stock ramdisk and using them to replace files from an unpacked custom recovery ramdisk folder... I picked a custom recovery of a similar device to make it easier.. So far each late night attempt has ended with "SEANDROID ENFORCING" & or Odin mode as recovery.. Hopefully by putting this out there I will further development & speed up the process somewhat as the chances of me succeeding in a successful port are looking slim.. If more files are needed Im more than willing to provide whatever & also have no issue with doing the testing if the developer won't have this particular device in hand at the time.. Thank you in advance and good luck...
Click to expand...
Click to collapse
Change enforcing to permissive
I have been trying to do that with this phone using same techniques that have been successful on my other devices but to no avail.. I've used adb commands,terminal emulator, int.d scripts at boot + several other methods but when I run getenforce I'm still getting enforcing as a result. Can't even get it temporarily permissive.. I have the t-mobile version of this phone as well (SM-G530T) which I had no problem achieving permanent permissive with.. Although during rooting it I used sunshines kernel flash which might be where I acomplished this.. If there's anot her method I'm overlooking please let me kno how to do so

Yoga Tab 2 Kernel Compilation

Has anyone else made any serious attempts at compiling a kernel? Prompted by doctorow's thread about the wakelock issue, I got interested in compiling a kernel so it could actually be fixed. For anyone who's tried at all, there are obviously some missing files in Lenovo's release.
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
P.S.: I'm not really sure if this belongs in the dev section or not? Sorry if it's in the wrong place, but I can't start threads there anyway at my current post count.
iampanis said:
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
Click to expand...
Click to collapse
Interesting, I haven't even gotten that far when I tried to compile them. The sources are most likely not up to date or even representative of the actual firmware kernel. For example, when I looked at the battery driver, I noticed in the published sources, the polling interval was hard-coded in such a way that it would completely ignore the setting of the poll_interval kernel parameter. But we know that this is not true for the actual firmware which is in fact respecting the setting of said parameter.
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Olivier said:
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Click to expand...
Click to collapse
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
raenye said:
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
Click to expand...
Click to collapse
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
Hello, I have a 1050F too is somebody tried this kernel on 1050F? Is it possible to support wake gesture kernel extensions with this kernel?
Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
Click to expand...
Click to collapse
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
corasman said:
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
Click to expand...
Click to collapse
The kernel goes to the boot partition. So 2nd option.
raenye said:
The kernel goes to the boot partition. So 2nd option.
Click to expand...
Click to collapse
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
corasman said:
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
Click to expand...
Click to collapse
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
raenye said:
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
Click to expand...
Click to collapse
Yes to all.
I wondered if the command slashes were the right way / or \ the way I used is what I used to unlock the bootloader and install TWRP.
I have tried the slashes the other way and get the same result, as in \ .
raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Click to expand...
Click to collapse
Hmm, I'm getting a high battery_wake_lock (on the April OTA firmware) -- even when running this kernel!
Any idea how can this be?
Hi,
I was trying to play a little bit with kernel provided by @Olivier and @Grarak ...
1. Binary Image kernel-yt2-20160327.img boots up fine on 1050l, but LTE is not working. Rest seems to be fine...
2. In next steps I replaced initrd.img with a little modified stock one - and LTE started to work - I removed from initrd almost all modules leaving only bcm43241.ko.
3. Battery wakelock problem seems not be resolved - brief check at bq27x00_battery.c in repository shows that wake_lock is still set under bq27x00_battery_suspend_resume()
... so I trying to fix this battery driver but I have problem with kernel - I can compile it successfully, but it doesn't boot
@Olivier:
1. Which branch was used to build kernel-yt2-20160327.img?
2. Which config did you use ?
My procedure using android-ndk-r12b toolchain:
# git clone ...github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail
# export PATH=~/android_yoga/toolchain/bin:$PATH
# export CROSS_COMPILE=x86_64-linux-android-
# export ARCH=x86
# make cyanogenmod_YT2_10_defconfig --- if this right config?
# make -j8 ----- lot's of warninigs, but kernel is compiled sucesfully.
# abootimg --create boot_test5.img -f bootimg.cfg -k bzImage -r initrd.img ---- bzImage from arch/x86/boot
> fastboot.exe flash boot boot_test5.img
... kernel stuck somewhere, it's doesn't even come to Zygote phase (lenovo animation). Is there any way to see kernel boot messages ?
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
airmalaga said:
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
Click to expand...
Click to collapse
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Thx :good:
jasfasola said:
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Click to expand...
Click to collapse
jasfasola said:
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
Click to expand...
Click to collapse
Cool, could you push your patch to GitHub?
jasfasola said:
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
Click to expand...
Click to collapse
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Olivier said:
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Click to expand...
Click to collapse
Fixed. That was quite easy. Driver al3320 was in place. The problem was permissions set by script init.byt_t_ffrd8.rc in initrd. By default it's root/root, but it should be system/system. I already corrected paths and checked it - it's working. If you could give me permission to repo I can push the patch.
BTW: I see lot's of things are being hard-coded into initrd scripts. Since we changed config kernel, all those scripts must be checked. I can try to do it in free time...but some things are platform depended so, another original initrd from lolopop on 830f would be nice to compare...
jasfasola said:
so, another original initrd from lolopop on 830f would be nice to compare...
Click to expand...
Click to collapse
What do you need exactly? @jasfasola

Categories

Resources