FORUMS

[ROMS][GITHUB] List with Repo initialization commands.

n/a posts
Thanks Meter: 0
 
By raC-A, Guest on 20th February 2014, 11:13 AM
Post Reply Email Thread
Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories

For syncing the full repo,

After you initialize certain repo in the working folder, you have to give the following command :

Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.

ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!

1. CyanogenMod

Link to Github sources :
Command for initializing the repo in the working folder :

Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode

Link to github sources :
Command for initializing the repo in the working folder:

Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS

Link to github sources :
Command for initializing the repo in the working folder:

Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>

I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks
The Following 26 Users Say Thank You to raC-A For This Useful Post: [ View ] Gift raC-A Ad-Free
20th February 2014, 03:26 PM |#2  
TheEdgeOfRage's Avatar
Senior Member
Flag Novi Sad
Thanks Meter: 536
 
More
I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:

Code:
Fetching projects:  99% (433/437)  fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos
The Following 2 Users Say Thank You to TheEdgeOfRage For This Useful Post: [ View ] Gift TheEdgeOfRage Ad-Free
20th February 2014, 04:31 PM |#3  
SMillerNL's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 1,068
 
Donate to Me
More
Why the -c and -f arguments with repo sync? Doesn't it run fine without them?

Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
raC-A
20th February 2014, 05:02 PM |#4  
Guest
Thanks Meter: 0
 
More
Wink
Quote:
Originally Posted by paxy97

I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:

Code:
Fetching projects:  99% (433/437)  fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos

Try to sync again.. this time, don't use the -f arguments.

Quote:
Originally Posted by SMillerNL

Why the -c and -f arguments with repo sync? Doesn't it run fine without them?

Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu

Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).
The Following User Says Thank You to For This Useful Post: [ View ] Gift Ad-Free
20th February 2014, 05:40 PM |#5  
SMillerNL's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 1,068
 
Donate to Me
More
Quote:
Originally Posted by PixCM

Try to sync again.. this time, don't use the -f arguments.



Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).

So what will -c do then?

Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
raC-A
20th February 2014, 06:46 PM |#6  
Guest
Thanks Meter: 0
 
More
Wink
Quote:
Originally Posted by SMillerNL

So what will -c do then?

Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu

-c: command and arguments to execute. The command is evaluated through /bin/sh and any arguments after it are passed through as shell positional parameters.
23rd February 2014, 12:50 PM |#7  
Anu6is's Avatar
Senior Member
Thanks Meter: 2,367
 
Donate to Me
More
Quote:
Originally Posted by PixCM

Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories

For syncing the full repo,

After you initialize certain repo in the working folder, you have to give the following command :

Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.

ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!

1. CyanogenMod

Link to Github sources :
Command for initializing the repo in the working folder :

Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode

Link to github sources :
Command for initializing the repo in the working folder:

Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS

Link to github sources :
Command for initializing the repo in the working folder:

Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix

Link to github sources :
Command for initializing the repo in the working folder:

Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>

I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks



The ParanoidAndroid repo is actually
https://github.com/AOSPA for Nexus devices
or
https://github.com/AOSPA-legacy for non-Nexus
The Following 2 Users Say Thank You to Anu6is For This Useful Post: [ View ] Gift Anu6is Ad-Free
23rd February 2014, 01:20 PM |#8  
zeetherocker's Avatar
Senior Member
Flag Bangalore
Thanks Meter: 927
 
Donate to Me
More
I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?
23rd February 2014, 01:21 PM |#9  
Christiancs1969's Avatar
Senior Member
Flag london
Thanks Meter: 3,417
 
Donate to Me
More
Thanks for including CyanFox....... ....

Sent from my GT-I9100 using Tapatalk
raC-A
23rd February 2014, 02:29 PM |#10  
Guest
Thanks Meter: 0
 
More
Talking
Quote:
Originally Posted by zeetherocker

I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?

Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).

I suppose that its a exiting repo error and not a exciting repo sync error :P . for that, use the flag "-f" , for example. repo sync -f

Check if this works
23rd February 2014, 06:34 PM |#11  
zeetherocker's Avatar
Senior Member
Flag Bangalore
Thanks Meter: 927
 
Donate to Me
More
Quote:
Originally Posted by PixCM

Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).

I suppose that its a exiting repo error and not a exciting repo sync error :P . for that, use the flag "-f" , for example. repo sync -f

Check if this works

I'm sure it's excited repo sync error... I'll post a Screenshot later... For now I've deleted a few folders... I'll try syncing repos again in the morning... And I'll do whatever u said and report back if I get errors..
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes