******* Hi all ********I have developed this little tool containing a few utilities that should help anyone do a host of stuff like building Cyanogenmod..Compiling kernels..Play with ADB..GIt tools..etc
DARK_Multitool1.0
My tool is divided into five Modules(More to come in future if people find it useful)
Module 1 : CyanogenMod Tools
- Installing the necessary libraries for compiling Cyanogenmod
- Initializing your repository and getting the Cyanogenmod source code
- Getting prebuilt apps/Device proprietary blobs
- Building Cyanogenmod for your device
Module 2 : ADB tools
- Creating logcat to debug your phone
- Installing apps via ADB
- Push/Pull stuff to/from your android device
Module 3 : Kernel tools
-Sony Kernel
Unpack Kernel Source
Create zImage of various devices(any Xperia)
Extract kernel.sin from ftf file
Unpack kernel.sin(to get zImage and ramdisk)
Make dt.img(For Xperia Z1 and Z ultra)
Make kernel.elf or boot.img depending on device
Test your kernel.elf/boot.img without flashing fully(Test run)
-Nexus Kernel
Getting the source code
Checkout the source code
Building zImage
-Samsung kernel
(Is under development as i develop for Xperia devices and not too familiar with samsung atm)
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
pearl script unpack or umkbootimg unpack
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Take kernel log : Thanks @ricky310711 for the commit
Module 4 : Backup TA partition for Sony or EFS partition on samsung
-Backup TA partition for Sony(By dd Method only)
-Backup or restore efs partition for Samsung(tar or dd method)
Module 5 : GIT tools
-Download GIT package on your linux
-Change directory where you want to initialize git
-Git repository setup(New git setup/Changes to old git setup)
-Update your local and remote git repository
-Commit your additions/deletions
-Push/Pull to/from your github repository
-Automatic push commits to your repository(After git setup is done)
-Download any repository using GIT
Download link
Dark_multitool1.0(With Update 1)
Update 2 added...Will upload soon..You can download this and update via tool to the latest version
Its better to download from XDA DevDB. You can either use the link above or click on downloads on top of the thread to download
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf dark_multitool1.0.gz
How to run it??
cd to the folder dark_multitool1.0 and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin(Tested on Cygwin by kevinrus123 : Some utilities are working)
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Sources
My github source : https://github.com/Smk1989/dark_multitool1.0
Mods : Please Move the thread if its in the inappropriate section
Updates
Latest update = Update 1
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
[TOOL][ANDROID]Dark_Multitool-CyanogenMod building.kernel developMent.ADB tool..etc.., a Tool/Utility for the Android General
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-11
Last Updated 2014-01-03
FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition and EFS partition backup doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel or Cyanogenmod work directory?
Answer ; Navigate to the kernel or Cyanogenmod work directory and type in Terminal : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed. You can install from the tool itself under GIT tools
>Libraries missing while compiling kernel or cyanogenmod build errors on 64 bit machine??
Answer : Download libraries from cyanogenmod import libraries option( I will incorporate this in the next release) and for 64 bit compile error type : BUILD_HOST_32bit=1(Fixed and added in update 1)
Bugs and Suggestions
Please let me know
Changelogs
Update 2
>Added Xperia J in the build list of the tool
>Added Take kernel log in kernel options..Thanks @ricky310711 for the commit
>Added dry run option for Sony
-Lets you test your kernel.elf/boot.img(In case the kernel doesnt boot up..just restart phone and try again)
Update 1
>Cm-11.0 branch added while initializing repo(thanks mithun shanoj for the commit)
>Added umkbootimg unpack method
>Added import libraries option
>Added BUILD_HOST_32BIT=1 for 64 bit machines
Last one
No one tried??
Sent from my Micromax A110 using xda app-developers app
Maybe I am blind but where do I get the download?
Download Link?
Dude where is the download link???
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
Dovidhalevi said:
Maybe I am blind but where do I get the download?
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Well well well.:beer: cheers.
Dovidhalevi said:
Maybe I am blind but I'll alwhere do I get the download?
Click to expand...
Click to collapse
rhar**** said:
I had always been waiting for a tool like this one. Great job :good:
---------- Post added at 04:51 PM ---------- Previous post was at 04:50 PM ----------
To download, sync this repository
https://github.com/Smk1989/dark_multitool1.0
Thats it. navigate to the local repository and run run menu from terminal
Click to expand...
Click to collapse
adityak74 said:
Dude where is the download link???
Click to expand...
Click to collapse
Guys see the download tab on top of the thread.. I'll also add a download link if u want
Edit: Added a download link to the post
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
welcome to the world of kitchen creators goodjob!
Nice job man ?
Sent from my Nexus 7 using Tapatalk
Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..
i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
actually i learnt alot by viewing the content of tools, viewing it in raw format and learning how things work.
it encouaged me to find a way to make a kitchen for windows users and noobs.
so i guess im the perfect example
Daniel_GT said:
I'm sorry @Dark Wraith, but is this not another nail in the coffin that was a developer's community? I'm not cheapening the hard work you've obviously put in creating this tool, it's an achievement for sure but to what end? I know this toolkit argument has been had many times before (and someone has to say it first here), but how does this actually help anyone learn the basics? Xda is full of people who just want the results without the work and surely this only encourages more of the same?
Click to expand...
Click to collapse
You have every right to express your opinion, but that being said, your post makes you sound like a real elitist, one who's upset that his elevated place in the exclusive club is about to be disrupted by those "filthy ruffians" who didn't earn their developer's chops by clawing their way up from the gutter. In my opinion, anything that brings in more developers to the community is a good thing. Sure, there are going to be plenty who use this tool as a shortcut to doing any hard work, but there are going to be those who use it as a starting point to further their knowledge of ROM building and modifying. Everyone needs a place to start, after all, but implying they'll never be "one of the boys" without beating their head bloody against a desk isn't at all helpful. Dark Wraith should be commended for creating a tool that will help bring new blood into the community.
Dark Wraith said:
No need to apologize.You have every right to criticize. In my defense i would say that when i wanted to make a kernel..i used championswimmer's kernel tools..i used dxdia's kitchen to work on Roms but that doesnt mean i took a shortcut..i used a toolkit out there to get started. I still had to learn stuff to make changes to a kernel/Rom and i was intrigued by the idea of how the tool was working. And while studying Dxdia's sources i actually came to know about a lot more than i would have done myself. many people want to know how to build a kernel and then they get discouraged if they feel its tough..yes..there will be people who will use it as a shortcut..but there will also be people who would start kernel building because a tool is out there to help them or atleast get them started.
p.s.Sorry for no punctuation marks..comma doesnt work on my laptop...:silly:
Click to expand...
Click to collapse
That's one side of the argument, if you re-read the first several pages of @championswimmer's kernel kitchen thread you'll be reminded just how strongly some people feel about this... I'm not in either camp by the way.
My point is that xda is not what it was, if we continue to post toolkits here it will only dilute the pool of serious development further. You just have to dive into an official CM Dev thread (N4 is a good example) at any point and browse, say, 25 pages to see exactly what I'm talking about...
For every one person that takes your tool, pulls it to bits to figure out how it works and goes on to do their own original work and contribute back, I feel sure that there'd be many more that just go ahead without any real understanding of what they're doing, expecting you and I to bail them out when it goes wrong... I hope that's overly cynical but, ironically, from evidence I don't think that is.
Your toolkit might have a place, and again all credit to you for putting it together. Personally I believe it's more hand holding (even more so than ROM or kernel kitchen) which ultimately helps no one.
Sent from my Nexus 4 using Tapatalk
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Good stuff
Sent from my Nexus 5 using Tapatalk
Marsealdelo said:
hey dude., i have a question
* (my device doesn't support CM) can i use this tool for building CM for my device?
Thanksssss
Click to expand...
Click to collapse
no bro..its not about support. Cm11 can run on ur device and you can build for it provided that you have the kernel source of your device available..For officially supported devices you will have the kernel source in cyanogenmod repository. For a device with no kernel source you cannot build cyanogenmod. What you are talking about is cyanogenmod porting to an unsupported device. Take a look around in cyanogenmod's wiki. I might add porting options in the tool in future but atm you can build only for offcially supported devices
Related
Hey Guys,
We all know that there is very little chance that we are going to get G3 support for ROM Manager. So as we have been doing from a long time, lets take that task in our own hands
We shall create a team, and make a ROM Manager for G3 supporting most of the Custom ROM's and Kernel's.
What all we need:
Recovery - I will provide the recovery from G3MOD, separately, so that everyone can install even with Fugumod.
App Developers - Please Post in the thread if you are interested.
Server - If anyone can provide us with a server with good storage and bandwidth? OTA for all ROM's and Kernels can be included in the software.
Anyone Else who has any idea, and wants to help in this project is welcome
Advantages of this Project:
1) Odin flashing will no longer be required.
2) ROM's and their Updates can be provided from the Server directly.
3) You can try any new ROM, without loosing data from your previous ROM.
Note to ROM Developers:
1) You will need to provide your ROM's as System.img files
2) Those interested in providing your ROM's using this ROM Manager, please let us know.
Thanks To:
Koush for the superb recovery and ROM Manager.
Functions We Can Have for the ROM Manager + Recovery:
1) Update Recovery - App
2) List of ROM's with Features. - App
3) List of Kernel's with Features. - App
4) OTA Updates for all ROM's and Kernel's - App
5) Switching ROM's - CWM
6) Backup Data - CWM
7) Restore Data - CWM
8) Backup Current ROM - CWM
9) Reboot to Recovery - App
Also Reserved
Kudos to you Dharam. This is simply amazing what you are doing.
Send from my Samsung GT-5800.
Digibonez said:
Kudos to you Dharam. This is simply amazing what you are doing.
Send from my Samsung GT-5800.
Click to expand...
Click to collapse
we just need enough support from everyone and this thing can be done
Coding the UI like in the famous ROM Managee shouldn't be hard 'cause it's basically an Options-Menu. The question is what's behind that. If we just need to fire Linux Shell Commands it shouldn't be hard - i set up an Script Executer for my first app allready.
Sent from my Galaxy 3 running CM7
s3th.g3ck9 said:
Coding the UI like in the famous ROM Managee shouldn't be hard 'cause it's basically an Options-Menu. The question is what's behind that. If we just need to fire Linux Shell Commands it shouldn't be hard - i set up an Script Executer for my first app allready.
Sent from my Galaxy 3 running CM7
Click to expand...
Click to collapse
Well, we already have the source for ROM manager, by koush...
https://github.com/ClockworkMod
So i dont think it will be very difficult to do it...
We just need as many app developers possible, so that we can have the project up and running fast
I am trying to mod the recovery in a better way, so switching between ROM's via CWM is faster and also there is no loss of data
dharamg3 said:
Well, we already have the source for ROM manager, by koush...
https://github.com/ClockworkMod
So i dont think it will be very difficult to do it...
We just need as many app developers possible, so that we can have the project up and running fast
I am trying to mod the recovery in a better way, so switching between ROM's via CWM is faster and also there is no loss of data
Click to expand...
Click to collapse
I'll have a look on the source and write back if i see something interesting
Sent from my Galaxy 3 running CM7
Great Work!!
R u also working on a kernel which can support CM7 on multiboot?
Coz currently we have only 2 kernels for CM7, one by marcel himself and the other by apollo but in both the kernels music experience is very bad due to noise. Now, since marcel and apollo are very less active on XDA due to may be they get very less time from their work, there is only one option left and that is you
I really want to keep CM7 on my mobile but can do that with dual or multiboot only as it is not yet complete.
I hope this project will give life to G3 forum.
Post Removed due to some reason
dharamg3 said:
Well, we already have the source for ROM manager, by koush...
https://github.com/ClockworkMod
So i dont think it will be very difficult to do it...
We just need as many app developers possible, so that we can have the project up and running fast
I am trying to mod the recovery in a better way, so switching between ROM's via CWM is faster and also there is no loss of data
Click to expand...
Click to collapse
I don't find any Java Source for the ROM Manager... somehow he posted only the /res folder which contains .xml (layouts, etc...) and drawables (images).
s3th.g3ck9 said:
I don't find any Java Source for the ROM Manager... somehow he posted only the /res folder which contains .xml (layouts, etc...) and drawables (images).
Click to expand...
Click to collapse
ok, lets see..if we get enough developers, maybe we can develop our own code..
we dont need to have a similar app + recovery...
dharamg3 said:
ok, lets see..if we get enough developers, maybe we can develop our own code..
we dont need to have a similar app + recovery...
Click to expand...
Click to collapse
Sure we can, but to be honest... i have no clue how it works in the background.
Good Start Man!
I will look into the code, and get back to you.
I am a beginer for Anroid, I may need more help from you.
Siva.
Well this really is my kind of game
Since I already have the code to download files from a server this shouldn't be that hard.
I'll look into the source later on.
Would really like to be part of this
Dympy.
Great initiative
Why can't you just help with cyanogenmod?
Smonic said:
Why can't you just help with cyanogenmod?
Click to expand...
Click to collapse
Because i dont have the knowledge to work on that...waiting for marcellusbe to to explain me some stuff....
Sent from my GT-I5800 using XDA App
Count on me too
Hi dharam
I want to get in.
I can help as far as it is C code.
I checked the github repo, but all you can find are the resources needed for the layout and such. So we COULD use that, but that would mean we have to write all the underlying Java code by ourselves..
Dympy.
Hi devs and users of g3 community...!!
I learned alot abt kernel development
tried n tried ..... atlast found success in my work
this thread is mainly concentrated on custom kernel development
after my work on ecliar ., i will start kernel compilation for froyo and cm7
hope u guys understand the purpose of the thread
changelog :
adb root and busybox support
file system support
cwm
1% battery mod
features to be added :
5 touch support
overclocking - complicated one ( will be last priority )
wish list :
choice is yours
CREDITS :
dharam maniar - for his tutorial and guidence
moikop - supporting me with his github
marcellusbe - made me to learn indepth abt overclocking
dor2 - for motivating me to work on ecliar kernel
testers - my g3
DOWNLOADS :
austin's gradient kernel 1.0
download link :
http://code.google.com/p/my-project-austinkernel/downloads/list
downloads will be added soon
test kernel :
only for testing
working cwm
file system
sd card recognition fixed
link...
http://www.4shared.com/file/O7etQOD0/zImage.html
HOW TO FLASH :
requirements : flash tools [odin]
sg3 drivers must be installed in pc
procedure :
- flash odin
- tick one package option
- select one package option and select zImage .tar file
- put ur g3 on download mode
- connect to pc with usb
- flash the .tar file
and enjoy....
RESERVED
reserved
nice work....actually I'm also making a kernel like this for purumod btw, where is the source?
HERE'S THE INFO
Downloading Sources
1. Download Samsung Source from https://opensource.samsung.com/
2. If you download from https://opensource.samsung.com/ then you will not have the initramfs.
3. To get stock initramfs, you need to extract it from one of the stock kernel(I will explain it later).
have you thought about helping with the kernel 3.0 project?
Sent from my GT-I5800 using XDA
Am a noob
i need a lot of knowledge to do that
may marcel can
request him... He can do it for us
Stucks at GT-I5800 Logo on stock XXJK1
DoR2 said:
Stucks at GT-I5800 Logo on stock XXJK1
Click to expand...
Click to collapse
I think this is for froyo wait, is this for froyo or eclair?
---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------
austin266 said:
HERE'S THE INFO
Downloading Sources
1. Download Samsung Source from https://opensource.samsung.com/
2. If you download from https://opensource.samsung.com/ then you will not have the initramfs.
3. To get stock initramfs, you need to extract it from one of the stock kernel(I will explain it later).
Click to expand...
Click to collapse
Nah, I meant to say, how did you compile the kernel for eclair? the same way as froyo?
austin266 said:
Am a noob
i need a lot of knowledge to do that
may marcel can
request him... He can do it for us
Click to expand...
Click to collapse
ok, although I'm sure even a n00b can contribute in it and you can't be that n00bish if you've managed to do a kernel release already lol
Sent from my GT-I5800 using XDA
I'm pretty sure you have to post your sources as well because of the license.
@simbawimba what he did/will do and what the 3 project will do are in different ballparks.
stubborn_d0nkey said:
I'm pretty sure you have to post your sources as well because of the license.
@simbawimba what he did/will do and what the 3 project will do is a whole different ballpark.
Click to expand...
Click to collapse
Not necessary, because those features are only included in the "initramfs" folder...but if he start to add features that are included in the "Kernel", then the source is required.
What about the features he is planning to add? I guess I bunched them together
@ jason
check the post 3 for the sources
am using ecliar sources for the ecliar
actually i incorporated all the changelog of moikop's kernel in my version 1.0
but ecliar is buggy... so i got plenty of errors while compiling
so, i just want to build a base kernel and add the features gradually... this will be the best choice of work with minimal errors
@ stubbirn donkey
check the first post
there u will find features to be added
in my kernel., i will try to add a recovery which will be new and simple
if u hav any ideas ., share here.. i will try to add those features
@ dor2
i didnt get any bootloop
tested on my g3
better reflash it
if it still encounters ., i will upload another image
austin266 said:
@ dor2
i didnt get any bootloop
tested on my g3
better reflash it
Click to expand...
Click to collapse
What rom I shall use with your kernel?
austin266 said:
@ jason
check the post 3 for the sources
am using ecliar sources for the ecliar
actually i incorporated all the changelog of moikop's kernel in my version 1.0
but ecliar is buggy... so i got plenty of errors while compiling
so, i just want to build a base kernel and add the features gradually... this will be the best choice of work with minimal errors
@ stubbirn donkey
check the first post
there u will find features to be added
in my kernel., i will try to add a recovery which will be new and simple
if u hav any ideas ., share here.. i will try to add those features
@ dor2
i didnt get any bootloop
tested on my g3
better reflash it
if it still encounters ., i will upload another image
Click to expand...
Click to collapse
Those errors suppose to appear while compiling. It seems like it is still much better to build kernels in Froyo...anyways, thanks for the reply, and also, you should add Voodoo Sound v10 in your kernel! here is a clean commit I made : https://github.com/JPurungrit/PuruKernel-G3/commit/c7bf85a4f8d83204c792fb8411407ce07958219f Try it in Eclair! I'm too curious
Have you tried on GT-I5801 or on GT-I5800? I can't understand what is going wrong/
DoR2 said:
Have you tried on GT-I5801 or on GT-I5800? I can't understand what is going wrong/
Click to expand...
Click to collapse
dude, both of them are exactly the same except the soft keys If it doesn't boot up, then it means he did something wrong...
Jason-EX said:
dude, both of them are exactly the same except the soft keys If it doesn't boot up, then it means he did something wrong...
Click to expand...
Click to collapse
Maybe you could try If you can't boot with this kernel than austin have done smth wrong
@dor2
Just chill guys... I will reupload it
@ Jason
I will check ur commit tonight and reply u... thanks for ur cooperation....
Due to errors. , am going to build a froyo kernel to make it ideal for ecliar work...
Plz be patient guys., am having only 2 days of free time.. I will try to sort out the problems
cm7 by marcellusbe
800mhz kernel
This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!
Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.
whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...
mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4
scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!
TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.
Hi,
New to building Android and want to build the code by cr3pt for the p700.
I have check out the base CM 11 code but I am guessing there is additional code by cr3pt to build the LG 7 p700 parts. Are these available to download and if so where?
I am assuming, and I could be wrong, that either the additional code is independant of the base code or the two can be merged. I have never used GIT so it is all a bit new but I am sure it will be no harder than svn (probably easier).
Any howtos gratefully received.
Thanks,
bibble_235 said:
Hi,
New to building Android and want to build the code by cr3pt for the p700.
I have check out the base CM 11 code but I am guessing there is additional code by cr3pt to build the LG 7 p700 parts. Are these available to download and if so where?
I am assuming, and I could be wrong, that either the additional code is independant of the base code or the two can be merged. I have never used GIT so it is all a bit new but I am sure it will be no harder than svn (probably easier).
Any howtos gratefully received.
Thanks,
Click to expand...
Click to collapse
You can check out xda university.
But the basics are a kernel that works, correct libs for accessing your devices hardware, and using logcat/dmesg/strace to debug everything else.
I have never used git either, but kgit is a nice kde gui for git.
You should look around for tutorial's on git. (There has got to be one.)
Lgrootnoob said:
You can check out xda university.
But the basics are a kernel that works, correct libs for accessing your devices hardware, and using logcat/dmesg/strace to debug everything else.
I have never used git either, but kgit is a nice kde gui for git.
You should look around for tutorial's on git. (There has got to be one.)
Click to expand...
Click to collapse
Thanks this is a fine place to start.
Good place to start indeed. Sound like all I need to do is change
lunch cm_i9100-userdebug
to
lunch cm_p700-userdebug
I wouldn't know. Im not a rom dev. But I do know that for testing builds, the userdebug will have adb and everything ready.
So you got that right.
Anyways, you can use the tool in my signature to help debug your rom.
It has strace, auto logcat capture, and is about to add auto dmesg but you can do that by typing.
Code:
adb shell dmesg | more
or for output to notepad
Code:
(adb shell dmesg > dmesgout.txt)&(notepad dmesgout.txt)
Just not in linux though.
If you plan on becoming a rom dev full on, then you can link to my post and have your windows users collect logcats with my tool (For eaasy debugging) and upload the txt file output.
Code:
lgctnp
Well lunch did not work. Guessing the p700 code is not on the cm11 branch
Sent from my GT-N8013 using Tapatalk
bibble_235 said:
Well lunch did not work. Guessing the p700 code is not on the cm11 branch
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
This is what I want I think, I case others find my thread.
http://forum.xda-developers.com/showthread.php?t=2329641
Just a lil' heads up:
Code:
#include
/*
* I am not responsible for bricked devices, or any problems
* that you might run into when you do these mods.
* Point your finger at me if you goof up and I'll smack you
* over the internet with my handy tennis racket.
*/
SOURCES
Kernel - Here
GPS Fix - Here
Device Tree - Here
Proprietary vendor files can be found linked in the README.md file in the device tree.
Make sure to have an unlocked boot loader before doing any of this: unlockbootloader.sonymobile.com
I've built KitKat for the Xperia L once again, this time with updated sources and a few much-awaited fixes. Most of the procedures remain the same.
I'm going to keep this thread clean and simple. Just follow the instructions and you shouldn't run into any problems.
The GPS fix may not be "complete", so please don't spam the thread with crazy insults, death threats, etc.
DOWNLOADS
boot.img - Download.
userdata.img - Download.
system.img - Download.
GAPPS - Download.
If you want the CRT lock animation, download this and flash with CWM or TWRP -
Download.
INSTRUCTIONS
cd to the directory which contains the downloaded files [ex: cd ~/Downloads] and execute the following commands (assuming you have fastboot and adb set up in your command line.) -
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
COOL STUFF AND NOT-SO-COOL STUFF
What's working?
Code:
- Wi-Fi
- GPS {kinda}
- NFC
- Camera
- Deep Sleep
- Other essentials
What's still smoked?
Code:
- Bluetooth
- Internal storage shows up as 2GB and not 4GB
CREDITS -
@raffaele88 - For the CRT Lock Animation Toggle
@Shivam Kuchhal - For the kernel
Reserved
Reserved.
Reserved
Reserved, yet again.
Does this Rom include the latest fix from Brinly? Is GPS fully working or just via WiFi and mobile network?
And some screenshots would be good.
Good to see a new rom!
what difference is there from other aosp roms ????
freakzapster said:
what difference is there from other aosp roms ????
Click to expand...
Click to collapse
It based on latest AOSP maybe (Android 4.4.2_r2)
Sent from my C2105 using XDA Premium 4 mobile app
Provide proper kernel and device tree sources and not just Sony AOSP ones so that others can see how you fixed GPS.
Also, are you sure GPS works? Brinly's fixes were incomplete, does turn by turn navigation works?
Signal Keeps resetting ???????????
Edit
I found that somethings wrong with my phone
Shivam Kuchhal said:
Provide proper kernel and device tree sources and not just Sony AOSP ones so that others can see how you fixed GPS.
Also, are you sure GPS works? Brinly's fixes were incomplete, does turn by turn navigation works?
Click to expand...
Click to collapse
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
kinetic_soul said:
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
Click to expand...
Click to collapse
Did you use this fix?
It's working but it's using the wifi/data to locate your location
kinetic_soul said:
Brinly's GitHub has the fixes. I am yet to test the turn-by-turn nav. I'll keep updating the OP with the latest info.
Click to expand...
Click to collapse
Do you understand that you're breaking GPL right now? Brinly's github doesn't have "sources", they're just incomplete docs for fixing GPS and if you used those fixes then I guess GPS is still broken and mobile is using WiFi and mobile network to detect location. I advise you to upload proper and latest sources on "your" git before some MOD takes some action against you.
That's true mate, You shouldn't say that this is a GPS fix because it isn't
Sent from my C2105 using xda app-developers app
All of you calm down. I've updated the OP with the details required.
Shivam Kuchhal said:
Do you understand that you're breaking GPL right now?
Click to expand...
Click to collapse
Sorry for the off-topic, but I don't think he's breaking something.
Android kernel is under GPL, but software is under Apache —meaning the developer chooses whether he/she makes the sources public.
It is just preferred in the custom ROM world that sources are out so others can modify or reuse them.
Or at least that's what I understand from here, correct me if I'm wrong.
nicholas said:
Sorry for the off-topic, but I don't think he's breaking something.
Android kernel is under GPL, but software is under Apache —meaning the developer chooses whether he/she makes the sources public.
It is just preferred in the custom ROM world that sources are out so others can modify or reuse them.
Or at least that's what I understand from here, correct me if I'm wrong.
Click to expand...
Click to collapse
Yes you're right that kernel is covered under GPL but here at xda, a developer needs to provide both kernel source and device tree and that's how power of open source prevails. You can look into any original ROM thread and you'll obviously find a proper source given there and contradictory to my advice, OP still chose not to provide any kernel source and device tree. Anyways, I am no MOD so better let a authorized person deal with this stuff.
Shivam Kuchhal said:
Yes you're right that kernel is covered under GPL but here at xda, a developer needs to provide both kernel source and device tree and that's how power of open source prevails. You can look into any original ROM thread and you'll obviously find a proper source given there and contradictory to my advice, OP still chose not to provide any kernel source and device tree. Anyways, I am no MOD so better let a authorized person deal with this stuff.
Click to expand...
Click to collapse
Nope, I need to correct you there. XDA only requires you to publish the kernel sources due to the GPL. The device tree, however, can ofc be closed source. But you also are kinda right, even though we do allow closed source stuff, we sure encourage people to make their stuff open source so other people can help bug fixing, tweaking, but also use it (if allowed).
As I can see kernel sources are provided in the OP, so there's nothing to do for me anymore, except moving it into Android Development, as this doesn't yet qualify as original dev
Cheers
Link for download removed..:/
Raj joshi said:
Link for download removed..:/
Click to expand...
Click to collapse
Fixed. Sorry about that.
The links for Google drive not work
kinetic_soul said:
Fixed. Sorry about that.
Click to expand...
Click to collapse
is a bit mess there , on first link i got boot.img, second link userdata.img say the file has been removed....nothing, the third link say system.img but you download userdata.img...and the Gapps as well say is been removed...is any chance to fix this?
watch here 1 minute to understand what i am talking about
https://www.youtube.com/watch?v=1EyN9qoEikA