Had some trouble finding this out myself, so I'm posting here to help others later.
There is a good guide on The cyanogenmod wiki for building CM-10.1 for the Xoom, but it has an error that stops you completely.
The step "Extract proprietary blobs" fails because there is no such file extract-files.sh for Stingray (nor Wingray/Everest). This is what you do instead:
(before running 'brunch stingray' or wingray)
croot
git clone git://github.com/TheMuppets/proprietary_vendor_broadcom.git -b cm-10.1 vendors/broadcom
git clone git://github.com/TheMuppets/proprietary_vendor_nvidia.git -b cm-10.1 vendors/nvidia
git clone git://github.com/TheMuppets/proprietary_vendor_motorola.git -b cm-10.1 vendors/motorola
Then continue as normal, following the mentioned guide. Otherwise your output ROM zip-file will be lacking required proprietary blobs, drivers and such.
Lets assume we've fetched the source tree
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.4 && repo sync
.. committed some local project changes and then saved a snapshot
Code:
repo manifest -o ~/snapshot.xml -r
Will another 'repo sync' wipe the snapshot from our local tree or can we still revert to that snapshot later on?
Where to find reference to the snapshot in the local tree?
aguaz said:
Lets assume we've fetched the source tree
Code:
repo init -u git://github.com/omnirom/android.git -b android-4.4 && repo sync
.. committed some local project changes and then saved a snapshot
Code:
repo manifest -o ~/snapshot.xml -r
Will another 'repo sync' wipe the snapshot from our local tree or can we still revert to that snapshot later on?
Where to find reference to the snapshot in the local tree?
Click to expand...
Click to collapse
I would have expected that the snapshot build would be reproducible even after a 'repo sync' if:
- the local changes are committed to local topic/feature branches on your local clone(s) of the omnirom git repo(s)
My impression is, if you want to be sure that your manifest snapshot remains relevant, clone the upstream git repo(s) and commit your changes to your clone on a local branch. Use a local_manifest to specify your branch/revision rather than the default branch/revision that sync'ing with upstream will change or reset.
Hopefully someone else will offer a definitive answer.
Meanwhile I'm using btrfs copy-on-write feature to store snapshots:
Before syncing make a reference of the current-tree with
Code:
cp -a --reflink=always old-tree/ new-tree/
This "copy" won't take up disk space other than for the references themselves. You can now sync new-tree/ and always go back to the old one.
I guess it's pretty similar to using btrfs' snapshot feature.
Miui 8 patch rom release, can someone port it for Nexus 4?
https://github.com/MiCode/patchrom/tree/marshmallow
I need it too...
You should contact to miui support forum or XDA devs, I hope they can build miui 8 for nexus 4
@Trickster22
Install Ubuntu.
Install Java
Guide to configure android SDK
Guide to configure repository:
Open terminal
Code:
mkdir -p ~/bin
Code:
PATH=~/bin:$PATH
Code:
cd ~/bin
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
mkdir ~/patchrom
Code:
cd ~/patchrom
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Now you'll have to configure git. Run following commands in terminal
Code:
git config --global user.email ENTER_YOUR_EMAIL_ID_HERE
Code:
git config --global user.name ENTER_YOUR_REAL_NAME_HERE
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Code:
repo sync
Wait......
after, Install the latest version of Fake nexus (marshmallow), reboot to device in mode recovery (TWRP).
PS.: After you finish generating the stockrom.zip of fake nexus, do the same for cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-mako.zip
Reboot your device for recovery, use this comand to gerate stockrom.zip and metadata folder:
Code:
/home/"YOUR-USER-NAME-UBUNTU"/patchrom/tools/releasetools/ota_target_from_phone -r
Sende me stockrom.zip and metadata folder
Source: http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
Dio_S said:
@Trickster22
Install Ubuntu.
Install Java
Guide to configure android SDK
Guide to configure repository:
Open terminal
Code:
mkdir -p ~/bin
Code:
PATH=~/bin:$PATH
Code:
cd ~/bin
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
mkdir ~/patchrom
Code:
cd ~/patchrom
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Now you'll have to configure git. Run following commands in terminal
Code:
git config --global user.email ENTER_YOUR_EMAIL_ID_HERE
Code:
git config --global user.name ENTER_YOUR_REAL_NAME_HERE
Code:
repo init -u git://github.com/MiCode/patchrom.git -b marshmallow
Code:
repo sync
Wait......
after, Install the latest version of Fake nexus (marshmallow), reboot to device in mode recovery (TWRP).
PS.: After you finish generating the stockrom.zip of fake nexus, do the same for cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J5-mako.zip
use this comand to gerate stockrom.zip and metadata folder:
Code:
/home/"YOUR-USER-NAME-UBUNTU"/patchrom/tools/releasetools/ota_target_from_phone -r
Sende me stockrom.zip and metadata folder
Source: http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984
Click to expand...
Click to collapse
Thank you sir for this valuable info/guide but I have a weak machine for Ubuntu like only 2 GB ram. This is why I was requesting others to build miui.
Trickster22 said:
Thank you sir for this valuable info/guide but I have a weak machine for Ubuntu like only 2 GB ram. This is why I was requesting others to build miui.
Click to expand...
Click to collapse
You should just generate the stockrom.zip + metadata and send me, I can do it, because I do not have the device
what ıs thıs ?
hasanben35 said:
what ıs thıs ?
Click to expand...
Click to collapse
For me to compile miui, I need the stockrom.zip plus the metadata folder generated by the patchrom, this guide shows how.
Sorry mt english
hım how long does it take
hasanben35 said:
hım how long does it take
Click to expand...
Click to collapse
This process should take around 1 hour if you already have Ubuntu installed and configured
multı rom nıtrogen os 7.1.1 and flyme ınstalled flyme remove ubuntu ınstall after _?
hasanben35 said:
mult? rom n?trogen os 7.1.1 and flyme ?nstalled flyme remove ubuntu ?nstall after _?
Click to expand...
Click to collapse
Ubuntu in PC "Desktop"
oh my god no no no waıtıng rom sorry ubuntu ınstall pc no
Okay, I'll make those files. Where should I send it?
I am trying to sync source, but repo sync is very slow compared to all other ROMs and aosp.
Code:
repo init -u git://github.com/OnePlusOSS/android.git -b oneplus/QC8998_N_7.1 repo sync
Is there a way to sync without all tags/branches being involved as well?
Any other tips?
Thank you
Before starting, yes, I know there is a project already.
Hello everyone. I've been following this step by step:
https://wiki.lineageos.org/devices/harpia/build
Only I have replaced this line:
Code:
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
For this one:
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-15.0
The problem is, I get loads of fatal errors when running:
Code:
repo sync
What am I doing wrong?
Thank you.-
Seems the error was due to a bad internet connection.
Hope it works out for you now. Good luck.
i tried too few weeks ago. can you post your roomservice.xml?