Hi all.
I have been reading around here, but I can not find any solution to my problem
I try to compile a kernel to my n8010.
I have setup umbutu and downloaded the latest GT-N8010_EUR_KK_Opensource from samsung.
I use N8010XXUDNK1_N8010XSADNK1_XSA firmware.
I follow the instruktions-
make p4notepq-w_00_defconfig
make.
I can compile the kernel without errors and I get the zImage.
I use the initramfs from the boot.img from that firmware.
I can unpack it and repack it and it work to flash .
But when I use my own kernel it do not work. I can flash it but when I restart it just sit after the samsung logo and the screen is sblack.
I know its an old device, but I figure its a good to start with, before I try with my samsung S5.
My question is what is wrong and how shall I compile this kernel so it works?
//searendil
Related
Hi Folks,
I already spent some years in customizing Linux kernels and in the last time I was already playing around with Android devices and the possibility they offer to boot customized kernel. Now, thanks to NoThrill, we have a working CWM and my interest rises again. I already compiled the Acer Kernel Sources but I got into trouble booting it. Few months ago, I did the same with a lenovo IdeaPad a1 and it should be possible on the A510 too to boot an outside kernel using the command fastboot boot kernel ramdisk.gz. Problem is, that it does download and boot the kernel - but then it returns to fastboot mode instead of booting android. First I thought, it may be due to kernel errors but it does the same if I am using the stock kernel or the boot.img provided by working ROMs. So my questions are:
Is there any possibility to test an experimental kernel without flashing it first? Do I understand correctly, that it is relatively safe to flash it to the boot partition as long as recovery keeps untouched?
What exactly does the (unexplained) command fastboot continue? I thought it may be used to continue booting process with a downloaded kernel, but unfortunately it seems like it does just the same like a normal reboot ...
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
NoThrills said:
Simply pack the kernel into a boot.img and flash it to the /boot partition. If something goes wrong, simply reboot into recovery and flash your original boot.img back. Recovery will always work because it uses its own kernel and therefor is independent of whatever kernel you flash to /boot.
A word of warning though: The Acer kernelsource contains code that could brick your tablet. That needs to be fixed before you experiment any further.
Nevertheless, any work done on the A510 kernel is always encouraged :good:
Click to expand...
Click to collapse
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
BENETNATH said:
by the way, nothrills, did you set-up a git or something like that to share kernel mods and stuff like that ?
Click to expand...
Click to collapse
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
NoThrills said:
Actually, no, because (call me stupid) I really have no clue how git works. I know how to get stuff from it, and used it alot, but never looked into actually setting something up or submitting patches.
I am very ashamed
Click to expand...
Click to collapse
THAT is something really easy you know..
but if it's something that you agree, i can upload it to my git if you don't want to use time for that.
i can clearly state about the source and then.. work can be shared and commit done.
otherwise, yu have to set-up a free account and follow this :
https://help.github.com/articles/create-a-repo
it would REALLY help you know
I hope there are some devs looking through this part of the forum.
This is NOT a request thread, I merely need some pointers as to questions I have about development so I can experiment on my own and hopefully attain results which are to some degree helpful to the community.
1) The sony stock firmwares come in these weird .sin formats, does this mean the device partitions work differently on Xperias than they do on other devices or does this stand in the way when reading general guides on e.g. cyanogenmod about flashing a certain partition?
2) The bootloader on this device acts differently than the one on my nexus 7, as in, in a weird way. I gather this is because sony made it themselves and to their liking to add flashmode.
2a) Is it normal that I can use fastboot to flash a kernel, but not use "fastboot boot boot.img" to boot e.g. extended stock temporarily? My device then hangs on the black-screen-blue-light standard fastboot look, but it doesn't power off when removing the USB cable and I have to pull out the battery. Flashing works though.
2b) Is "Flashmode" necessary for anything? Does it do anything else then allow for ftf's to be flashed, thus not having much to do with custom rom development?
2c) also, on original stock kernel, is it normal that the only way to get into recovery I have found up until now is using the Quickboot app? Using a recovery keycombo or trying from fastboot or adb does nothing, sometimes even hanging the device, so taking out the battery is necessary again...
3) How do you guys make booting images out of a compiled kernel? I can compile a kernel just fine, but I don't really figure what to do with the zImage file other than "packing it somehow". Been searching around on google for this, but I can't find any working ways to pack anything, and I don't even know where to get a ramdisk or how to make one.
4) On that note, I have been trying to figure out compiling CM, by forking some repos of taoshan and sony common, but I don't really know how for these are in correctness. Are there specific repos with the taoshan board configuration that are being worked on right now that I should/could fork to figure stuff out myself? I don't know how this forking is looked upon, if it is regarded as stealing someone's code or something, any insights about that might also be helpful.
That's what I can form off of the top of my head. I hope I get some insights from you guys at least. I have been trying and breaking my device for a week now, wishing to get something working of my own, but to no real avail
All the best.
MajorMonodon
MajorMonodon said:
I hope there are some devs looking through this part of the forum.
This is NOT a request thread, I merely need some pointers as to questions I have about development so I can experiment on my own and hopefully attain results which are to some degree helpful to the community.
1) The sony stock firmwares come in these weird .sin formats, does this mean the device partitions work differently on Xperias than they do on other devices or does this stand in the way when reading general guides on e.g. cyanogenmod about flashing a certain partition?
2) The bootloader on this device acts differently than the one on my nexus 7, as in, in a weird way. I gather this is because sony made it themselves and to their liking to add flashmode.
2a) Is it normal that I can use fastboot to flash a kernel, but not use "fastboot boot boot.img" to boot e.g. extended stock temporarily? My device then hangs on the black-screen-blue-light standard fastboot look, but it doesn't power off when removing the USB cable and I have to pull out the battery. Flashing works though.
2b) Is "Flashmode" necessary for anything? Does it do anything else then allow for ftf's to be flashed, thus not having much to do with custom rom development?
2c) also, on original stock kernel, is it normal that the only way to get into recovery I have found up until now is using the Quickboot app? Using a recovery keycombo or trying from fastboot or adb does nothing, sometimes even hanging the device, so taking out the battery is necessary again...
3) How do you guys make booting images out of a compiled kernel? I can compile a kernel just fine, but I don't really figure what to do with the zImage file other than "packing it somehow". Been searching around on google for this, but I can't find any working ways to pack anything, and I don't even know where to get a ramdisk or how to make one.
4) On that note, I have been trying to figure out compiling CM, by forking some repos of taoshan and sony common, but I don't really know how for these are in correctness. Are there specific repos with the taoshan board configuration that are being worked on right now that I should/could fork to figure stuff out myself? I don't know how this forking is looked upon, if it is regarded as stealing someone's code or something, any insights about that might also be helpful.
That's what I can form off of the top of my head. I hope I get some insights from you guys at least. I have been trying and breaking my device for a week now, wishing to get something working of my own, but to no real avail
All the best.
MajorMonodon
Click to expand...
Click to collapse
1) Not at all. Just extract .sin using flashtool and then mount the dumped .ext4 as a regular filesystem.
Xperia devices have all partitions except /recovery.
2) I can't answer your question because I didn't have any non Sony android device before.
2a) Sony bootloader doesn't allow hotbooting kernels.
2b) You can cherrypick components of firmware like baseband, kernel, system etc and flash through flashmode. Really handy!
2c) As I mentioned before, Xperia devices don't have /recovery. So any attempt to boot recovery partition is futile.
Another way round, is to load recovery.cpio as an initrd during boot by keymaps.
3) use mkbootimg. Check my git for more info.
Randisk can be obtained by extracting stock kernel.
4) maybe a cm developer can help you regarding this.
Rachit Rawat said:
1) Not at all. Just extract .sin using flashtool and then mount the dumped .ext4 as a regular filesystem.
Xperia devices have all partitions except /recovery.
2) I can't answer your question because I didn't have any non Sony android device before.
2a) Sony bootloader doesn't allow hotbooting kernels.
2b) You can cherrypick components of firmware like baseband, kernel, system etc and flash through flashmode. Really handy!
2c) As I mentioned before, Xperia devices don't have /recovery. So any attempt to boot recovery partition is futile.
Another way round, is to load recovery.cpio as an initrd during boot by keymaps.
3) use mkbootimg. Check my git for more info.
Randisk can be obtained by extracting stock kernel.
4) maybe a cm developer can help you regarding this.
Click to expand...
Click to collapse
Rachit,
Thanks a lot for the answers! This really gives me a boost, because sometimes when stuff doesn't work I'm ready to just give up!
I'll take a look at and fork your kernel repo if that is okay with you, to take a look at how you do things.
If I have an occasional question later on, would you mind me contacting you in some way, like pm?
Thanks again
(a very happy) MajorMonodon
MajorMonodon said:
Rachit,
Thanks a lot for the answers! This really gives me a boost, because sometimes when stuff doesn't work I'm ready to just give up!
I'll take a look at and fork your kernel repo if that is okay with you, to take a look at how you do things.
If I have an occasional question later on, would you mind me contacting you in some way, like pm?
Thanks again
(a very happy) MajorMonodon
Click to expand...
Click to collapse
Sure. You can do whatever you want with my sources.
Atm I think one is broken because I kinda messed it up while patching wcnss.
Better you start with stock and patch it with commits I've done. If you don't understand what the patch is all about, hit me anytime via pm. I don't browse forums frequently.
:thumbup:
Rachit Rawat said:
Sure. You can do whatever you want with my sources.
Atm I think one is broken because I kinda messed it up while patching wcnss.
Better you start with stock and patch it with commits I've done. If you don't understand what the patch is all about, hit me anytime via pm. I don't browse forums frequently.
:thumbup:
Click to expand...
Click to collapse
Thanks Rachit, I'll do that!
All the best
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
dblackburn965 said:
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
Click to expand...
Click to collapse
Good luck, did WiFi work out for you?
Hello everyone. I know how to compile roms. I use android sources and device trees already working, and sometimes, I fix bugs.
But I am tired of trying to port versions which do not boot in a specific device. I compile "successfully" all the process. But I am not that lucky when I try to install these zips.
I know how to use dmesg for example. But is there a way to know what is causing the rom to not install? Or to not boot?
How and/or what should I search/use when I want to debug such a rom? So I can port it successfully?
Thank you for your comprehension and time.
Ok, so I've successfully built Android 8.1 and my devices kernel from Samsung open source.
My issue is, previously, I've only built AOSP for my Nexus. Flashing on a google device is simple because of fastboot, but Samsungs use Odin or Heimdal. I've used Odin/Heimdal to flash Samsungs before, but the roms come packaged in a tar.gz or other format.
I tried using Heimdall to pack up the .imgs, but it hasn't gone to plan yet.
Any help would be appreciated, I've had this android build sitting in a VM for like a month now, lol. It'd be nice to clear out that 150 or so gigs, lol.
which device you have
do you have twrp for your device
It's a 2016 Tab A with s pen. SM-P580. And yes, TWRP is already in the device.
Can I flash the system.img from TWRP? Didn't think of that till now.
Also, I know I can package the kernel and flash it there, but not 100% sure how to.