Related
K900 Device Tree project
hi folks, a couple of months ago i decided it was time to create a working device tree at least to build cwm, since lenovo is very bad at opensource with us, it is nearly impossible to build a working cyanogen. Fortunately cwm doesn't need too much to be build so i grabbed the motorola razr i device tree from @hazou and wrote a new device tree for us. But unfortunately we still need a developer firmware from lenovo to flash recovery.img's. However, cwm builds well and i want to share my work to any interested developer who are willing to help.
Click to expand...
Click to collapse
in this github you will find all needed repos and info --> https://github.com/lenovo-k900
Click to expand...
Click to collapse
Its true, thanks for your effort QuBeX. I hope it works. I will follow.
Great job! I am also interested in hacking my K900 to enable kvm kernel module to run VMs on it.
The issue was always their stupid secure boot process which prevent use to put our kernel or even a kernel module into the system.
You refer to a developer firmware. Did you get chance to have access to one of those?
Does that turns off secure boot or you somhow got the signing key?
Please pm me if you know more details on that.
Thanks a lot.
chinabull said:
Great job! I am also interested in hacking my K900 to enable kvm kernel module to run VMs on it.
The issue was always their stupid secure boot process which prevent use to put our kernel or even a kernel module into the system.
You refer to a developer firmware. Did you get chance to have access to one of those?
Does that turns off secure boot or you somhow got the signing key?
Please pm me if you know more details on that.
Thanks a lot.
Click to expand...
Click to collapse
Lenovo hasn't provided a dev firmware yet. And I don't think they will... Anyway we now have working recovery, and we are finding out how to bypass signature check, but it is really difficult.
Talking about the kernel, have you ever tried kexec? I don't know very much of it but you can find a lot of info and stuff in google
Thanks, man. That is a briliant idea!
I have built the kexec executible and have loaded my custom kernel into the memory.
Of course when it ran the new kernel, I got a black screen for now. But it's a good start. I'll debug it and keep you guys updated with the progress.
chinabull said:
Thanks, man. That is a briliant idea!
I have built the kexec executible and have loaded my custom kernel into the memory.
Of course when it ran the new kernel, I got a black screen for now. But it's a good start. I'll debug it and keep you guys updated with the progress.
Click to expand...
Click to collapse
Just a quick update on progress.
Tried all kinds of tricks including modifying kernel code on the fly.
Still no luck on kexec yet.
But I found a loophole in the JB4.3 kernel which I used to have the kernel module signature check disabled.
Now I can load any kerenl module I built.
If anybody has interest on that tool, please PM me.
Now we have AOSP 4.3 branch in our device tree: https://github.com/lenovo-k900/android_device_lenovo_redhookbay/tree/aosp-4.3
Author: MaXxXanter
Can't wait for this. I wish i could do some support too...
Sent from my Lenovo K900_ROW using XDA Free mobile app
can i use this device tree for build cm12.1 rom?
xxx-man-by said:
Now we have AOSP 4.3 branch in our device tree: https://github.com/lenovo-k900/android_device_lenovo_redhookbay/tree/aosp-4.3
Author: MaXxXanter
Click to expand...
Click to collapse
is possible to build cm11 with that source sir?
xxx-man and qubex and any other who is putting time to get some nice roms for our K900 is greatly appreciated.
Q&A for [5.0][AOSP][port][wip] CodeROM 5.0 by LollipopS2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [5.0][AOSP][port][wip] CodeROM 5.0 by LollipopS2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Well, we will try to fix it ourselves, but it would be much faster if some skilled dev help us with fixing boot problems. I was porting this rom yesterday, and i think it is little success that we got to the bootscreen with "ANDROID" logo. Thx for all supports, we are doing our best
Error
This account's public links are generating too much traffic and have been temporarily disabled!
Thanks for good work
Wouldn't it be easier to port the note cm12 alpha build? since it uses the same hardware, would be a matter of fixing configs
Fail
Download link is K.O.
Thanks
Link
Download links is now updated now. Also, we have finished porting of CM12.
Just wanted to know if its getting past the BOOT Animation over gt-i9100 ??
read first post
Please read first post carefully. Rom isnt bootable yet. You can see boot animation, but there is a bootloop.
Thanks
Thumbs up
cm12
Bootloop is in CM12 port too. I will upload it today. We are also starting to build CM12 from sources.
Thanks
ahmedelhofy said:
@jeffreyvh hey, take a look at this.... It's already booting on N7000.. That's mostly a similar phone to the i9100... It will surely help you... Or at least you can contact the guy who made it, he might help you...
http://forum.xda-developers.com/showthread.php?t=2938649
Click to expand...
Click to collapse
THX for link dude, thanks to you and your idea im just building CM12 for i9100 from sources.
I know that you can do it!! Thanks a lot!! :beer:
Sent from my GT-I9100 using XDA Free mobile app
Lenger96 said:
Bootloop is in CM12 port too. I will upload it today. We are also starting to build CM12 from sources.
Click to expand...
Click to collapse
I'm trying to build cm12 from source too, but so far I still can't get past repo sync errors, after that I think the proprietary blobs will be the problem
build
I have passed over reco sync, but specific files copying crashed, because there isnt any files for i9100 in cm12 repo. Im out of ideas....
Lenger96 said:
I have passed over reco sync, but specific files copying crashed, because there isnt any files for i9100 in cm12 repo. Im out of ideas....
Click to expand...
Click to collapse
The breakfast command failed right? Well on the cm git there's only cm11 branch for our device, take a look here: https://github.com/CyanogenMod/android_device_samsung_i9100. Have you tried pushing files manually from cm11 branch? I think it's not gonna work too because we need a proper 5.0 kernel... Building AOSP with cm11 device tree would be even worse... I think the only way to boot some Lollipop on S2 is know what people have done in the kernels of the Note, or the S3 devices, and then do the same on our kernel. But sadly, I'm not xplodwild to do this
Yeah
Lysergic Acid said:
The breakfast command failed right? Well on the cm git there's only cm11 branch for our device, take a look here: https://github.com/CyanogenMod/android_device_samsung_i9100. Have you tried pushing files manually from cm11 branch? I think it's not gonna work too because we need a proper 5.0 kernel... Building AOSP with cm11 device tree would be even worse... I think the only way to boot some Lollipop on S2 is know what people have done in the kernels of the Note, or the S3 devices, and then do the same on our kernel. But sadly, I'm not xplodwild to do this
Click to expand...
Click to collapse
Ive sent PM to dev who built CM12 for N7000. Maybe he can help. Can i ask you to write him too? Maybe if there will be more of us who write him, he will help us sooner.
Lenger96 said:
Ive sent PM to dev who built CM12 for N7000. Maybe he can help. Can i ask you to write him too? Maybe if there will be more of us who write him, he will help us sooner.
Click to expand...
Click to collapse
I'll contact him too and maybe his steps on the Note can help us
Awesome
looking forward o boot up lolipop in our s2
re
Lysergic Acid said:
I'll contact him too and maybe his steps on the Note can help us
Click to expand...
Click to collapse
I got PM from him. All we need to do is manually copy device tree (you can find it on guthub) to /device/samsung/i9100. We can use cm11 tree.
Lenger96 said:
I got PM from him. All we need to do is manually copy device tree (you can find it on guthub) to /device/samsung/i9100. We can use cm11 tree.
Click to expand...
Click to collapse
Are you kidding? Really? Lol, If this works, maybe tonight I can give you guys a working Lollipop
EDIT: If someone here already have a fully synced CM12 source, just git clone this: https://github.com/CyanogenMod/android_device_samsung_i9100 to /device/samsung/i9100 and try building
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?
After doing some research I'm fall down at great confusion. If anyone can help me, I'll be very thankful. My Internet connection is very poor & not secure. If I will download any compressed source and Internet connection is not available at the time of Process. 'Is it possible to build a rom from that downloaded source without Internet.?'
If you don't mind then give some forums link please .
-thankyou ( @LahKeda , @corphish, @andii_nr)
Hungryhacker said:
After doing some research I'm fall down at great confusion. If anyone can help me, I'll be very thankful. My Internet connection is very poor & not secure. If I will download any compressed source and Internet connection is not available at the time of Process. 'Is it possible to build a rom from that downloaded source without Internet.?'
If you don't mind then give some forums link please .
-thankyou ( @LahKeda , @corphish, @andii_nr)
Click to expand...
Click to collapse
All you just need is just to get the compressed source of any ROM you want and then decompress it and you can build it without any problems .-I've build cm12.1 , cm13 , slimkat and slimLP from compressed source -.
By the way , you may need internet connection to get some packages are needed to build android from source like java , gcc ...etc ...
You can download any ROM you want from here ===>https://www.androidfilehost.com/?w=files&flid=87142
yeah I appreciate your Great Work.
LahKeda said:
All you just need is just to get the compressed source of any ROM you want and then decompress it and you can build it without any problems .-I've build cm12.1 , cm13 , slimkat and slimLP from compressed source -.
By the way , you may need internet connection to get some packages are needed to build android from source like java , gcc ...etc ...
You can download any ROM you want from here ===>https://www.androidfilehost.com/?w=files&flid=87142
Click to expand...
Click to collapse
one more question to you...
Is Building android from source different from having Internet or without Internet.?
And what should I download 'repo or without repo'.
Thanks for your response.
Hungryhacker said:
one more question to you...
Is Building android from source different from having Internet or without Internet.?
And what should I download 'repo or without repo'.
Thanks for your response.
Click to expand...
Click to collapse
No. We don't need repo to build a rom. As far as i know, it is used to bring fixes and updates for the source.
thanks
nagato said:
No. We don't need repo to build a rom. As far as i know, it is used to bring fixes and updates for the source.
Click to expand...
Click to collapse
if i download without repo...then I can't upload or sync with github...isn't it?
Hungryhacker said:
one more question to you...
Is Building android from source different from having Internet or without Internet.?
And what should I download 'repo or without repo'.
Thanks for your response.
Click to expand...
Click to collapse
Hungryhacker said:
if i download without repo...then I can't upload or sync with github...isn't it?
Click to expand...
Click to collapse
-If you don't have repo you won't be able to fetch new updates from ROM repository ,but you can solve this problem by installing the repo too and extract it to ROM source .
-If you don't have repo that doesn't mean that you can push to github , actually github has nothing to do with repo !
-Having internet while building isn't necessary but you will need it if you come into troubles like wrong java version or missed packages !
thanks a lot
your words gives me much clearance.... Thank You very much.... Then I may go through different guides relates to building rom from source.
Thanks for your response.
Thanks a lot
your words gives me much clearance.... Thank You very much.... Then I may go through different guides relates to building rom from source.
Thanks for your response.
So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>