Related
Hi,
Whether and how to can decompile / decompress zImage?
S.
What is your reason to do this?
You can download source code, kernel is OpenSource ;-)
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
I know.
I can do: source to zImage
but I can not do: zImage to source
ATomCZ said:
What is your reason to do this?
You can download source code, kernel is OpenSource ;-)
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
Click to expand...
Click to collapse
Considering how the OP dodged your question, I'd guess he wants to decompile a kernel for which no source code is / has been provided (idk, maybe he got his hands on an "experimental" kernel by Cotulla or something like that). Since that would imply some yet "unofficial" kernel, I'd say it's good that he can't decompile it
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
git, change, compile...
Anyone got anything worthwhile to say....
I have limited Linux knowledge so a few pointers would be a good start, if possible...not looking for anyone to hold my hand...but looking for something a little more than the previous post.
Thanks
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
I'm keen as well, fairly new to programming and whatnot, so this would be very helpful...
Ok so there's a little more info here: http://git.linuxtogo.org/?p=groups/...7;hb=e51cb9c975bb81ae498c286ff28efa89489c3b17
The readme explains a little about how to do it, but it looks like they assume you have a fair understanding of it already...some light reading for me tomorrow then
the_scotsman said:
Ok so there's a little more info here: http://git.linuxtogo.org/?p=groups/...7;hb=e51cb9c975bb81ae498c286ff28efa89489c3b17
The readme explains a little about how to do it, but it looks like they assume you have a fair understanding of it already...some light reading for me tomorrow then
Click to expand...
Click to collapse
thats it! its not to simple... LOL, its impossible to teach such a thing in a post
Sorry, i didn't want to be rude my friend...
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
Maybe I'm being too risk-avoiding, but I'd stay away from especially anything that has to do with undervolting and overclocking, even if it means taking the functionality from source code that works and putting it in another piece of code... that may not be the best way to learn about how that kind of coding works
+1 for me too, the reason why I want to know is there is a solution to a problem in one kernel, which I want to see how it was fixed and to see if it can be added to another kernel.
And if you ask why not use the kernel that has the fix, the answer is compatability.
A decent answer wouldn't be bad, for me either.
I recently got a cheap 3Q Q-Pad tabby, which is closed, and 1GHz + 512MB RAM + ICS 4.0.3 is not a good mix :S
Why wont you just get tytungs kernel from guthub?
I know this is developement section and i should not post like this but i want to tell that whenever i open this developement section i see some new froyo custom roms or rom upgrades with several new features , nothing more. I think it is enough creating roms like v1.0 then v1.1 then v1.2 then v1.3 and so on. Galaxy 5 uses enjoying cyanogen but we can't. All devs are in the race for providing better froyo roms but no on one wants to provide cyanogen, why? because it is not possible. If port of cyanogen is possible in g5 then not in g3. G3 is better phone then G5. Shall we have to satisfied only with froyo roms? All devs are giving their best but it is enough creating new version of froyo in every week, do something new, port CYANOGEN which we really wants.I don't know anything about programming, coding, i can't do anything but all u devs are able to port cyanogen to our device. So please stop doing like v1.0=>v1.1=>v1.2=>v1.3 and do Cyanogen.All devs please combilne at one place and give us CYANOGEN.
Cyanogen can be ported to our phone. I have no idea how can i do this, i may give it a try in summer but i will fail, it is sure. But i will start to learn coding, & kernel compiling (the basics).
Maybe a few of the devs come together, make a team and then work on this
m ready to learn and try
you are right but seriously its not EASY! you should have very good programming skills... and why is CM so good anyway? i would prefer MIUI port. when you say cyanogen mod i assume you mean the latest GB version? what is so great in GB anyway? i mean yeah its newer than froyo but still, i have my own tablet and it runs 2.3 (3.0 is coming ) and i dont think its that great... i like the edge glow and on/off animation but thats it. we CAN have the same features on froyo! and besides IF we would port GB it would take so much time that android 2.5 would be out already and then everybody would say that GB sucks... thats all
It's a lot lot of work to do it.
marcellusbe said:
It's a lot lot of work to do it.
Click to expand...
Click to collapse
Hey, like u modify kernel with coding, cant we modify the ROM from the source files??not for cyanogen but to improve froyo better??
dharammaniar said:
Hey, like u modify kernel with coding, cant we modify the ROM from the source files??
Click to expand...
Click to collapse
In fact, you must start from source files as you must compile all. No ?
In example, for gingerbread, I started compiling it from google source, but I'm stuck with libaudio library.
I took libaudio source code from sgs and I will see if I can compile them and continue.
In addition, you should adapt kernel 2.6.35 for the apollo device, and that's a big work too.
Or if we are lucky, kernel 2.6.32 could work ... I don't know.
I know it is not easy but please devs do something. If porting once started we will defenetily get Cyanogen.
The thing is cyanogen takes alot of time and there's no encouragement so I say whoever devs GB then I will donate £10 to them and I know many others will.
Sent from my GT-I5800 using XDA App
The best thing wat I feel is stopping any further froyo roms n start porting cm/miui/gb same as v0.1 > v0.2 releasing small mods I think everyone here will help testing them....i dont mind even my phone explodes...i have no idea how u techie guys do all this things all I know is flash watever u guys release n test it so we can make a better g3...
dilzo said:
The thing is cyanogen takes alot of time and there's no encouragement so I say whoever devs GB then I will donate £10 to them and I know many others will.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
I think if you want it in a raisonable delay, then it's more than a full time job for only 1 person ....
deadwood01 said:
The best thing wat I feel is stopping any further froyo roms n start porting cm/miui/gb same as v0.1 > v0.2 releasing small mods I think everyone here will help testing them....i dont mind even my phone explodes...i have no idea how u techie guys do all this things all I know is flash watever u guys release n test it so we can make a better g3...
Click to expand...
Click to collapse
Before you must have a basic framework working and only that it's really a big work to do.
can't u guys make the screen on/off animation on froyo, that would be really cool
werker123 said:
can't u guys make the screen on/off animation on froyo, that would be really cool
Click to expand...
Click to collapse
well do that as soon as the guy who already did that will release his mod
We shall ask motafoca for help, he does not have a sg3 but has a lot of knowledge and experience porting Gingerbread to sg5!
Once we have some clue or knowledge on how to start with we then can try/experiment ways to accomplish CyanogenMod.
Some proof for Sg5 having 2.3>here
As for people who want to port GB or Cyanogen flores said in this post http://forum.xda-developers.com/showpost.php?p=13132913&postcount=51 that he has already done work on gingerbread so i guess devs like apollo or other people who have experience in the kernel front can have something to work upon....... what i mean is there are a few devs who have mentioned about their incomplete works on Cyanogen/gingerbread, if an experienced developer can combine all their individual work we can have something actually working........
anant.0097 said:
As for people who want to port GB or Cyanogen flores said in this post http://forum.xda-developers.com/showpost.php?p=13132913&postcount=51 that he has already done work on gingerbread so i guess devs like apollo or other people who have experience in the kernel front can have something to work upon....... what i mean is there are a few devs who have mentioned about their incomplete works on Cyanogen/gingerbread, if an experienced developer can combine all their individual work we can have something actually working........
Click to expand...
Click to collapse
ok first of all dont take flores too seriously... he just talks too much and never does anything so i doupt that he has done anything more than looked at GB and said he can port it... i have asked about his project and quess what? nothing.
True is that we have too many custom roms, but changes only name and theme. We can customize everything in froyo rom, but we need to have some1 who can customize kernel! We have one kernel by our hero marcel and thats all! His kernel is used by every rom here. Always same:
New custom rom!
Same features as another rom
Thanks to marcellube for his kernel
We dont need gb, we dont need cm7
But
We need MORE KERNELS!!!
Sent from my GT-I5800 using Tapatalk
question for all! how can you ask for cyanogen if you wont help anyone? i have asked for people who know java (i know there are people who knows java) but nobody hasnt commented on my thread we could do it but nobody wants to help... all we need is some guys who knows java programming... so is there ANYONE? if there is contact me on this thread or my other thread in general section....
peldax said:
True is that we have too many custom roms, but changes only name and theme. We can customize everything in froyo rom, but we need to have some1 who can customize kernel! We have one kernel by our hero marcel and thats all! His kernel is used by every rom here. Always same:
New custom rom!
Same features as another rom
Thanks to marcellube for his kernel
We dont need gb, we dont need cm7
But
We need MORE KERNELS!!!
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
i totally agree! more kernels with different features like on sgs forums... we have already lost one great kernel developer gsam101 who developed the first custom and best kernels for us
OK so i have the original EVO
i want to make a rom from scratch or someones else so i can fix it even more because frankly..i have alot of time on me and people need a good rom.
it doesnt seem hard but maybe Virus or more developer can help me here.
its more because i like the sense 3.5 roms but it seems alot of little bugs and especially that sms split bug. And i want to see if i can fix all that but i need people to start helping me with links or guides.
AwesomeEvo said:
OK so i have the original EVO
i want to make a rom from scratch or someones else so i can fix it even more because frankly..i have alot of time on me and people need a good rom.
it doesnt seem hard but maybe Virus or more developer can help me here.
its more because i like the sense 3.5 roms but it seems alot of little bugs and especially that sms split bug. And i want to see if i can fix all that but i need people to start helping me with links or guides.
Click to expand...
Click to collapse
You'll need to start here:
[KITCHEN] Android Kitchen, v0.188 [Linux / Mac / Windows]
http://forum.xda-developers.com/showthread.php?t=1198035
This should help
thanks guys..im going to be a lil confused but im sure it will sort out along the way
5 threads below this is lithids guide to compile salvage mod. That should be a good place to look, too. Also his thread in the Dev forum titled 'wanna learn to dev cortectly'. Good luck.
sent from AOKP heaven
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
----------------------Edit-----------------------
I wanted to say thank to you guys! I did quite some progress by now. If you own a t230 / nu then feel free to check out my custom kernel
CTXz said:
My friend owns an samsung galaxy tab 4 t-230 and would love to upgrade it into a more pure android. Since i kind of got into android ROMs and there are no AOSP or CM roms for the tab 4 t-230 this would be a great chance for me to build a AOSP or CM rom. I have ubuntu 14.10 and a decent enough pc with 16 gb of ram and an i7. If anyone could help me abit of how to build a AOSP or CM rom for the device i would be verry thankfull.
Click to expand...
Click to collapse
Relevant post - some starting info, and check out the CM wiki he links to. Also, and this is a very basic step, but if you've never done this before it can be informative: download a rom zip file (preferably but not necessarily a stock-based kitkat rom for this device) and open it up in either 7zip or WinRar, check out the layout and structure, and familiarize yourself with the updater-script. (Actually you can do that with a firmware tar file too). Sorry I can't give you any more useful info, not a dev, definitely not a rom designer, just a guy who knows a fair amount of android stuff.
Also don't let the tone of that post discourage you; the poster was answering a guy who was basically asking about the feasibility of building a brand new rom for the sole purpose of being able to use one particular proprietary Samsung app. Yes it is difficult, but still doable, and you say you're motivated...
Yes i did forgot to say that any links for learning are appriciated
Well.. I would ask moonbutt74 for more info regarding commands and such, probably more info than I can give but.. keep in mind your going to have to download about 20+GB of source code and all that. Also a bunch more knowledge of more things I don't remember. But it is alot
-DUHA
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. Everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
CTXz said:
Well I decided to revisit this thread. Never thought I would come so far. I really want to say thanks to all of you who supported me and still support me. I mean everyone has a beginning and here was mine. Now I am actually there where I really wanted to be. Releasing a custom kernel and finally work on a custom ROM! Thank you XDA!
Click to expand...
Click to collapse
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I'm amazed on how much people learn and achieve as well as myself. I've seen people who were total newbies then later built custom recoveries, CM12, Mods, Roms etc. Anyway good luck on working your rom!
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Also I thank you my life for introducing me to moonbutt74. He learned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because he really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
CTXz said:
Also I thank you my life for introducing me to moonbutt74. He leatned me everything from how to work with custom kernels to Roms. Sadly he decided to stop developing a few Werks ago but he's doing it for his own good. I still will mention @moonbutt74 on my future projects because je really is the one who changed me from confused to knowing what is actually going on. So thanks allot !
Click to expand...
Click to collapse
the erlkönig cant stop!
I am trying to build an image for angler. Looking for make files to build the image for angler (Nexus 6P) Where can i find the vendor/make files to build the image.
How do I see the angler option when I do lunch?
Do a quick search on Github, it should have everything you need.
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
debby_8 said:
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
Click to expand...
Click to collapse
Trying to build the kernel myself, would also appreciate some info. Samsung always at least always includes some help file to specify the toolchain needed etc.
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
mehmehmen said:
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
Click to expand...
Click to collapse
Well in my case, at this point I just want to build the kernel. It's really too bad that XDA doesnt accept posts like this on their 'development' forum. On this general FAQ forum I dont think it reaches the right audience and hence no reponse from anybody yet, to this fairly simple question. I wish XDA would support developers a bit more and would allow development questions on the development forum.
I understand what you mean, although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading. I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Im currently working on the angler with a couple of guys and we have a booting fully operational OmniRom port in testing stages now, which may end up to me then posting that as a full [ROM] thread and trying to offer support on the device for that rom. The guy that built the rom himself is very good and has helped me understand a lot, with the right attitude and willingness to learn I am sure you would be welcome in the IRC channel where I personally would be happy to try and help you get your head round some things, as the next goal for me regarding the 6p in terms of our project is going to be kernel based compiling as i want to try and get a really robust kernel built now we have a seemingly stable feature full rom built and booting.
Feel free to message me if this sounds like it may be of some help
Regards
Meh
mehmehmen said:
although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading.
Click to expand...
Click to collapse
That happens on any forum.
I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
Click to expand...
Click to collapse
Sure but that would be going off topic on someone's thread.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Click to expand...
Click to collapse
Everybody has questions, regardless of their level. I was the maintainer for Cyanogenmod Note 4, so if the above would be true, I wouldnt be here I'm sure I can figure out myself how to get the Angler kernel compiling but it would save me, and others who will try the same in the future, quite a bit of trouble if someone who had done it would just post the used toolchain etc.
Anyway you used a lot of words without helping at all. That's exactly my point, when posting on a general forum you can expect these kind of replies. That's why I'd love to see a true development forum here on XDA, not just a 'developer' forum where people just support their projects. Giving support to a project, has not much to do with development.
Nah, I could have expected this. I'll figure it out myself. Thanks but no thanks.
*EDIT* I guess this will work, using toolchain 4.6 like they recommend, it's probably the latest anyway (?)
https://source.android.com/source/building-kernels.html
They dont mention Angler, but I'll try this anyway, I think it might work. And I'll let people know if it worked or not, so someone in the future who reads this thread will know how too. Although I kinda doubt a developer will search the general FAQ forum here ...
Might wanna try asking that on a kernel development thread in Dev section - kernel developers are usually friendly to people willing to rightfully use (and maybe improve) their work. They should be at least give you a vision on how go get the basic Angler kernel up and running.
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
rustyjay said:
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
Click to expand...
Click to collapse
Thanks mate ! That's what I was looking for, will try that one.
---------- Post added at 03:23 AM ---------- Previous post was at 03:03 AM ----------
Ok and it's building !
Steps I took:
1) Download angler kernel here: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-marshmallow-dr
2) Download toolchain with: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
3) add the toolchain to the path, in my case: export PATH=~/android/toolchains/aarch64-linux-android-4.9/bin:$PATH
4) go to the unpacked kernel dir
5) export ARCH=arm64
6) export SUBARCH=arm64
7) export CROSS_COMPILE=aarch64-linux-android-
8) make angler_defconfig
9) make
Thanks again @rustyjay for the toolchain info !
---------- Post added at 03:32 AM ---------- Previous post was at 03:23 AM ----------
AndyYan said:
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Click to expand...
Click to collapse
As much as I love CM (I was maintainer for the Note 4), I don't particularly see the point of running it on a Nexus device. I just want some kernel tweaks (for example that damn fuel gauge is giving me wakelocks), so I think l wont jump onto CM. But who knows ...
---------- Post added at 03:46 AM ---------- Previous post was at 03:32 AM ----------
Build completed So I guess I just insert the resulting Image.gz-dtb into the boot.img (with android image kitchen for example), right ? Will try tomorrow, but I think that should work. off to bed now ...
Yeah what it basically does when I build aosp, don't know too much about kitchen.
rustyjay said:
Yeah what it basically does when I build aosp, don't know too much about kitchen.
Click to expand...
Click to collapse
Ok I used android image kitchen to replace the Zimage, flashed it and ... it boots
Cool, so that's easy. Now for the next part: building the whole rom ! Any idea on how to do that ? Or where to even download the code ? Is there even a whole ROM to build, including the blobs etc ? I think i saw google releasing a device tree but not the whole ROM, right ? I must say I havent really googled myself this, will look into this today myself too.
*EDIT* yeah here's the device tree: https://android.googlesource.com/device/huawei/angler/ but I dont think it's the whole ROM, going to download it now ...
*EDIT2* No this definitely isnt the whole ROM,not even the device tree There's not a lot in there !?!
*EDIT3* Info here: https://source.android.com/source/running.html
*EDIT4* So as per the link above, it turns out that most drivers are blobs ! Hmm that's a bit disappointing. You buy a Nexus because supposedly it's 'open source', turns out most of it is not.... Anyway so it seems it's just a matter of compiling the sourcecode that IS there and then adding the blobs.
*EDIT5* So this section explains the whole process of setting up the environment, downloading, syncing and building: https://source.android.com/source/requirements.html looks very similar to the CM install/build process indeed !
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
rustyjay said:
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
Click to expand...
Click to collapse
Thanks for all your info, much appreciated. Currently syncing to AOSP like explained on that page I linked, will take a few hours I guess.
BTW, what are you exactly building this for ? Just some tweaks ? I saw this kernel wakelock qpnp_fg myself, I just disabled CONFIG_QPNP_FG=y in the defconfig, the wakelock is gone but like I expected, the battery gauge doesnt work anymore neither, lol. Will need to look into it for a real fix I guess.
Also I'm planning to make an option to default MTP as USB connection. It's just plain crazy Google left that out in 6.0 !
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
rustyjay said:
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
Click to expand...
Click to collapse
It's my first Nexus and am just loving it already. I mean, getting CM to run on a Samsung device is of course fun, but it's also just SO much work. I dont think I could do it all over again on another non AOSP device.
Now on nexus, just syncing directly from google and building it, what a breeze this is !
Oh yeah if your into building, nexus is really the only way to go. My first nexus was the ns in '10 and have had a nexus phone ever since
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
rustyjay said:
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
Click to expand...
Click to collapse
What are your main changes ?
Anyway I just finished building the ROM myself. It ends up with system.img, userdata.img, recover.img, ramdisk.img, ramdisk-recover.img. I'd probably just flash boot.img and system.img, right ? That userdata.img, what is that exactly anyway ? If I flash that I'll lose my user partition=installed apps, I guess ?
BTW I didnt pull any blobs so I guess it wont run anyway. I guess I first need to extract the blobs ? Does the AOSP build process include the blobs automatically ?
Thanks !