I am starting this thread in hopes of building Sailfish OS for this device and I certainly know that it may have some parts missing or in the wrong place, but lets help each other to make this happen.
I'll add the defconfig and corrected mountpoints to use as well.
Please feel free to continue where I left off.
This is how far the HADK has taken me.log
drive.google.com
Here's the defconfig: https://drive.google.com/file/d/1tmanetCbeBKpLyNtCG2UwU-3uPh6Ynlt/view?usp=sharing
Here's the mountpoints file that you need to replace the current one with. Otherwise hybris won't know them
fixup-mountpoints
drive.google.com
Related
Update:
Fixed kaiser and polaris version info for NBH
Fixed issue where if a source code pull failed, any later attempts would fail as well
Fixed issue with updating bootenv
It's my first meaningful contribution! I put together a couple of scripts and some other stuff to make it really easy for me to create a flashable NBH from the latest kaiser kernel sources.
Many thanks to dzo, JeckyllHavok, quitlahok, rzk333, -Arturo-, kallt_kaffe, the folks at www.codesourcery.com, poliva at the htc-flasher project on googlecode, and all the people who contribute to developing, testing, etc Android on HTC devices.
Note that none of the files these scripts download are mine. They were not created by me. They all belong to other people who have contributed much to the community.
The only things that I've made are:
- crnbh (which uses commands from scripts in the htc-flasher project)
- update-workspace
- everything under the patches and signatures directories
(just the patches, not the things they patch)
This requires an active internet connection to use. I don't plan on maintaining this but I thought I'd put it out there in the hopes that it could be put to good use or something.
Download the attached file
Extract to your home folder (important)
Read the README
If you want to change it, make it better, please do! Just mention me in the credits. Also please PM me so that I know it was helpful. Thanks!
Good luck!
May I ask what this does differently than my NBHCreator?
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
LoveMyPhone said:
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
Click to expand...
Click to collapse
NO...NO...NO...
Don't be sorry...
I don't care if you make your own and post it...
I was only wondering because your OP was lacking in information as to what this did.
Actually the same thing happened to me just before I released my nbhcreator, loserskater released his nbh editor.
Your creator does some things mine doesn't (YET)
like actually pulling tinboot etc...
things like that I was putting off as an option for a later release.
other than that I am building the output very similar.
Now that I am in this deep I wish I would have gone without the GUI.
Seems to be creating cross-platform issues.
Well, please feel free to integrate any of it into yours. The two files are just shell-scripts written for bash... nothing more
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Hey guys!
I just got my serranoltexx and am fairly happy. However, I really would like to try and get AOKP running. Could any devs point me in the direction of where to start, you know, just bootstrap me with some reading? I have a background in Linux and UNIX, have developed some networking stack API projects on windows and have written a ****load of bash, perl etc. scripts in the past. I've also worked on the Matroska container format. Compiling etc. pose no challanges for me. However, I have never fumbled around with Android and I have no idea what drivers and other components might be needed. And how to start finding out what's missing...
I do know how to bootstrap my source repository and sync it... and in theory also how to compile AOKP - for supported devices, that is. What I don't know is: how do I start resolving unmet dependencies, and, you know, generally port a rom to a new device?
Please don't post if you haven't even compiled your own ROM yet. More likely than not, you'd be wasting your time.
I've posted on xda-dev as well, not sure which is the more suitable forum, possibly this one... Link to the other thread:
http://forum.xda-developers.com/showthread.php?t=2501539
And please don't post me to this guide right here as it is only of limited help. As I said, I know how to do it in general... You know, this guide:
http://aokp.co/learn/so-you-want-to-build-aokp-jb-ubuntu-1204
I tried to build it, but many things are missing once i flashed the *.zip.
Maybe i messed up with sources and patches.
Tell us if you have success! :good:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
madde on Fairphone Forum said:
Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.
Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...
Click to expand...
Click to collapse
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
I'm very interested by a portage of Firefox OS to the Fairphone
Don't have enought time to test for now, but I stay connected
Newluck77 said:
Continuing the discussion from Firefox OS is the way to go!
Hi guys!
I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.
I am following this guide: Porting Firefox OS
Currently I am stuck at the following: Create a manifest for the new device
[edit]
Which changes do I have to make to the hamachi manifest mentioned there?
I figured out, that most of the stuff is hamachi-specific and thus not required. My current manifest is attached. Could you please take a look and tell me, if this is enough?
These files are at hand:
I am inviting @madde-, @_keesj and @chrmhoffmann, I hope you, or others, can help me out.
Thanks in advance, Stefan
PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.
Edit: My current manifest is attached.
Click to expand...
Click to collapse
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
madde- said:
Did you try your file out? I's think it's probably best to cut down on just the relevant settings.
Click to expand...
Click to collapse
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Porting#Create_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Newluck77 said:
Yes, the config.sh got stuck at like 93%.
Also I have no idea, what exactly I have to include into the manifest file. I think I need a toolchain, but I am not sure where to get one, and how to apply it. (I somehow know what it is though, I think... )
Ok, running the config.sh comes at the very end, so I probably should continue with the configuration tree[1]...
Does everything in here [2](@chrmhoffmann's repo android_device_fp_FP1) go to the configuration tree?
[1]: https://developer.mozilla.org/en-US...reate_a_configuration_tree_for_the_new_device
[2]: https://github.com/chrmhoffmann/android_device_fp_FP1
PS.: Sorry, not allowed to post links...
Click to expand...
Click to collapse
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
madde- said:
any progress on that? Might be able to help you a little bit in the next few weeks.
Cheers!
Click to expand...
Click to collapse
No haven't been able to work on this.
I still have no idea, where and how to build this configuration tree. Do you have advice on this?
Thank you, Stefan
Fyi, a build is now available. As a new user on XDA, I can not post link here (what a ****ty rule), but check bug 1139642 on bugzilla and search Fairphone on the Mozilla Developer Network (MDN) to have more info.
Wrong phone (FP1(U) vs FP2)
The build, you are referring to, is for FP2, not for FP1.
A Firefox OS for FP1 could possibly be built using the source by @chrmhoffmann: http://forum.xda-developers.com/fairphone/orig-development/rom-fairphone-fp1-kitkat-4-4-2-t3243623
My plan is to flash a GSI image (LineageOS) for android 9. Specifically the following
- https://github.com/LineageOS/android/tree/lineage-16.0
- https://github.com/AndyCGYan/lineage_build_unified/tree/lineage-16.0
Is there a chance of getting this to run on my device? Please see the attached file for the output of the Treble Info app.
I cannot find any information about the impact of VNDK version 27.0 so any help is much appreciated.
Device info:
- Processor: Rockchip 3399
jossdb said:
My plan is to flash a GSI image (LineageOS) for android 9. Specifically the following
- https://github.com/LineageOS/android/tree/lineage-16.0
- https://github.com/AndyCGYan/lineage_build_unified/tree/lineage-16.0
Is there a chance of getting this to run on my device? Please see the attached file for the output of the Treble Info app.
I cannot find any information about the impact of VNDK version 27.0 so any help is much appreciated.
Device info:
- Processor: Rockchip 3399
Click to expand...
Click to collapse
I have the same issue, only thing I could find out, some features not gonna work, (who know what), if you install a newer vndk you wont be able to return to an older one. Be honest, Project Treble is made for seamlessly update phones, but it is a mess, versions, vndks, legacy phones, A-B-A/B images, etc. it doesnt do what it meant to do.
The XDA forum was a good place to ask questions like this, it was, still remember to get answer about my 10 years old phone, however things really changed over the years. Members change their phones on montly basis, so dont expect any professional answer.
Hi, you ma find usefull information in:
Frequently Asked Questions (FAQ)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com