There is no twrp for "moto g 5g" yet, but the source was available.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
You can download the code from here.
I downloaded the code from here and placed it in /twrp/device/motorola/kiev
Code:
repo init -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
repo sync
Code:
make clean
. build/envsetup.sh
export LC_ALL=C
lunch omni_kiev-eng
make -j4 recoveryimage 2>&1 | tee twrp_$(date '+%Y%m%d_%H-%M-%S').log
This was the first time I built a twrp.
I used bbqlinux in VirtualBox.
The build was somehow successful.
I was able to control it with otg.
However, the touch does not work.
How can I fix this?
Related
I have been trying to compile Froyo source for days now. Reason: I need a ROM tweaked to my needs. I would'nt say I am entirely unsuccessful except for boot.img. Cutting long story short. Let my script do the talking:
cd ~/mydroid
git clone git://android.git.kernel.org/kernel/msm.git
cd ~/mydroid/msm
make ARCH=arm msm_defconfig
make ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- zImage -j4
Click to expand...
Click to collapse
It takes time but source does compile without much hassle. I get the .img(s) in ~/mydroid/out/target/product/dream directory. Now the problem is my boot.img refuses to boot the phone. ddms doesn't show any logs either. Just to be sure I even downloaded, renamed (as <msm>) & compiled the original kernel source from
wget http://member.america.htc.com/download/RomCode/Source_and_Binaries/dream_9af60ed4.tar.bz2
Click to expand...
Click to collapse
but no success. Temporarily I am using superF's boot.img and gapps from CM6. ROM is very fast and looks stable. Probably the only thing that's broken is wifi. Which I assume can be interrelated.
Can anyone please guide me in the right direction.. Screenies to show that I am mostly on the right track except for boot.img fsck up!
P.S. I hope I have posted in correct section; it says Android development.
Even though the thread remained unanswered; I even been working on this issue on my own. I have tried every trick (that I can think of) of the trade.
1st attempt: I pulled .config from the brand new CM6, replaced existing .config and commented out msm def_config and did:
PHP:
make ARCH=arm CROSS_COMPILE=$SOURCE_FOLDER/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- oldconfig
make ARCH=arm CROSS_COMPILE=$SOURCE_FOLDER/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- zimage
Upon compiling; the system asked a dozen question which I bypassed by pressing enter. After a while I got boot.img in --/out/--directory which did'nt work after using fastboot.
./fastboot boot /home/amit/mydroid/out/target/product/dream/boot.img
Click to expand...
Click to collapse
The phone just froze with a standard Vodafone splash screen.
2nd attempt: Replaced contents of existing msm def_config with content of .config that I pulled earlier from CM6 and did standard "make ARCH=arm msm_defconfig". Same fsking result upon compiling .
I have a feeling that I have been $crewing up on .config but I may be wrong. I request all of you stalwarts to step in & help me out. I have pasted my script for reference:
PHP:
#!/bin/bash
#git clone git://android.git.kernel.org/kernel/msm.git
#unzip the proprietary files from HTC for Sapphire
cd /home/amit/mydroid
if [ ! -d vendor/htc/dream/proprietary ]
then
cd ~/mydroid/device/htc/dream/
./unzip-files.sh
fi
cd ~/mydroid/msm
make ARCH=arm msm_defconfig
#make ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- oldconfig
make ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- zImage
if [ -f ~/mydroid/msm/arch/arm/boot/zImage ]
then
cp ~/mydroid/msm/arch/arm/boot/zImage ~/mydroid/device/htc/dream/kernel
fi
cd ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32
make KERNEL_DIR=~/mydroid/msm/ ARCH=arm CROSS_COMPILE=~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- -j4
if [ -f ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32/wlan.ko ]
then
cp ~/mydroid/system/wlan/ti/sta_dk_4_0_4_32/wlan.ko ~/mydroid/device/htc/dream/wlan.ko
fi
cd ~/mydroid
. build/envsetup.sh
lunch
make otapackage
#get to compiled folder
cd ~/mydroid/out/target/product/dream
echo 'Your files ready for flashing are here:'
ls *.zip
Hey guys,
could someone of you that is compiling working nightlys for the DEFY+ tell me if there is anything special to consider? I don't see a seperate defy+ device when I look at the repo. Looking at the defy README it says:
CyanogenMod 7.2 for Motorola Defy (Android 2.3.7 AOSP)
Download:
=========
repo init -u git://github.com/CyanogenDefy/android.git -b gingerbread
repo sync
Download RomManager (DELETED IN BUILD)
======================================
mkdir vendor/cyanogen/proprietary
cd vendor/cyanogen && ./get-rommanager
Build:
======
optional :
export PLATFORM_DIR=$(pwd)
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export TARGET_OUT_INTERMEDIATES=out
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export PATH=$PLATFORM_DIR/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$JAVA_HOME/bin:$PATH
cd $PLATFORM_DIR
export CYANOGEN_NIGHTLY=true
rm -rf out/target
. build/envsetup.sh
brunch jordan
or...
lunch cyanogen_jordan-eng
mka bacon
Use the signed zip to update the defy with Second Init recovery, or CM7 bootmenu recovery, not the ota package
Will a build using these steps work on my defy+, or do I need to do anything else to build for Defy+?
thanks
boba
I don't think the CyanogenDefy builds will work for Defy+.
Not sure if these are the correct steps but this is how I did it and it worked for me:
I used Epsilon's git://github.com/tpruvot/android.git repo and not the CyanogenDefy one.
Before building I checked out the gingerbread-plus branches of android_device_motorola_jordan and proprietary_vendor_motorola. I did this using the EGit plugin of Eclipse. You can also switch branches using the git command line instead of using the Eclipse plugin.
Hello xda,
I had a little time on my hands the other night, and wanted to figure out a way that I could work on any of the project repositories needed to build say, aokp, cyanogenmod, aosp, etc... without having to connect to the internet.
Mirroring is not new. Simple enough to:
Code:
mkdir cm-mirror
cd cm-mirror
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1 --mirror
repo sync -j[dl-jobs]
then create a working directory:
Code:
cd ..
mkdir cm-work
cd cm-work
repo init -u file:///Volumes/Android/cm-mirror/CyanogenMod/android.git --reference /Volumes/Android/cm-mirror/ -b cm-10.1
repo sync # no jobs needed. super fast.
But at this point you only have what you need for cm-10.1. What if you also have work you are doing for 10.1.0? Or an old update to make for cm-7.2.0?
I originally started looking for a solution to sync every branch in the manifest one at a time, but while talking with cdesai he showed me a really clean way of getting the repositories directly from gerrit.
Anyways, here is the resulting script. Let me know your thoughts.
I've moved the script to a git repository here: https://github.com/bhundven/repo-mm
in case anyone wants to contribute.
I've also written a post on my blog about using the new gerrit-mirror.sh on gh.
ChangeLog
Changes:
[06/30/13]: Announce some updates to gerrit-mirror.sh, and blog post.
[06/24/13]: Moved gist to github project.
GitHub for repo-mm.
if u dont have internet connection to make a ROM this guide is for you and you dont need to have download for GB's of file
first im taking carbon ROM for example
1.You will need to set up some directories in your build environment:
To create them run:
mkdir -p ~/bin
mkdir -p ~/carbon
2.Install the Repository
Enter the following to download the "repo" binary and make it executable:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
You may need to reboot for these changes to take effect. Now enter the following to initialize the repository:
cd ~/carbon
Repositories:
Before you continue --> run this in the terminal:
repo init -u https://github.com/CarbonDev/android.git -b kk
3.now open carbon folderand press ctrl + H if u see .repo folder u can continue to next
repo sync --> firsy sync for 5mins to load the folder and then stop syncing by closing terminal
4.after that see the manifest.xml with notepad or any suitable one and you can see link for the packages EXAMPLE: android_art search in the cyanogenmod or in which u want to build
5.im sharing link database of packages for building carbon rest u have the job to search and typer in github
package which to be downloaded for carbon ROM is here http://d-h.st/zru
6.after making source proper --> Building the System --->>>Initialize the environment with the envsetup.sh script. Note that replacing "source" with a single dot saves a few characters, and the short form is more commonly used in documentation.
. build/envsetup.sh
lunch
Enter the number of the build you want to start and press enter:
make carbon -j7 = Run Squisher/Run Opticharger
make otapackage -j7 = No Squisher/No Opticharger
optional --> Submitting Patches
Patches are always welcome! Please submit your patches via CarbonDev Gerrit! You can do this by using these commands:
Setting up for repo upload: (run these commands once)
git config --global review.review.carbonrom.org.username <Your username registered at CarbonDev gerrit>
git config --global review.review.carbonrom.org.email <Your email registered at CarbonDev gerrit>
(From root android directory)
. build/envsetup.sh
repo start kk .
(Make your changes and commit)
repo upload .
Note: "." meaning current directory For more help on using this tool, use this command: repo help upload
Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel) Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>
To view the status of your and others' patches, visit EAMPLE:Carbondev Code Review
if you want to build :
CYANOGENMOD -->do steps upto initialisng repo ------------https://github.com/CyanogenMod/android
OMNIROM -->do steps upto initialisng repo ------------https://github.com/omnirom/android
CARBON -->do steps upto initialisng repo ------------https://github.com/CarbonDev/android
dont click thanks if i helped you because thanks button is gonna damage
CREDITS:
---------> Ramsudharsan madhavan for teaching me
---------> Guru sanjay my friend helping me to download
---------> and me for thinking this idea in my school time
Goin gud. keep it up.
Awesome man!
Worth for Portal!
Sent from my Xperia Sola using XDA Premium 4 mobile app
Nevermind.
Okay So you we have flashed many custom ROMs in your device, but have you wonder , how developers build custom ROMs , Well as a matter of fact we will Cover this Topic , So To build Custom Rom we need to mainly sync a source. Let's say it's LineageOS , so We have to first initialise the source via
Code:
repo init -u "clone url" -b "branchname"
You need to have a linux distro with atleast 8 cores and atleast 12 gb ram and 130 gb of HDD.
For example :
Let's take lineageOS For pie so the branch will be lineage-16.0
Code:
repo init -u git://github.com/LineageOS/android.git -b lineage-16.0
As we have initialised the source Let's Sync it , but before that you might want to configure your GitHub username and email , here we will do it globally , so that you don't have to do that again and again.
To configure GitHub username
Code:
git config --global user.name "FIRST_NAME LAST_NAME"
To configure GitHub email
Code:
git config --global user.email "YOUR EMAIL"
Now let's sync the Source
Code:
repo sync -j$(nproc --all)
Now as we synced the source , we just need to add device tree , vendor blobs and kernel source. After that we can start the bring up by
Code:
. build/envsetup.sh
lunch lineage_devicename-userdebug
brunch devicename
The build should Start
Well For more detailed explanation refer to my guide which I made for Rookies
Guide :- https://github.com/TheGlitchh/CustomRom_Building_Guide/
You can always pm me at Telegram for build errors and bug fixes ,I will try my best to help you out
Telegram username :- TheGlitchh
========O=======