yashsingh1/xdaforums huggingface dataset:
[Android] Speedmatze:
First of all: Thanks for the great tool!!!

I am having some trouble with the kernel building as well.

Setting 'Arch' and 'Definition Config' works. When I try pointing to the toolchain location (home/username/tc/arm-eabi-4.8), I get:

find: ‘bin/arm*gcc’: No such file or directory
[!] Toolchain Binaries not found

I have tried different toolchains (arm-eabi-4.7 & aarch64-linux-android-4.9). No Change whatsoever. What am I missing here?

When I try building the ROM there is also an error with the kernel:

build/core/tasks/kernel.mk:179: **********************************************************
build/core/tasks/kernel.mk:180: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:181: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:182: * BoardConfig.mk file *
build/core/tasks/kernel.mk:183: **********************************************************

However, in the BoardConfig.mk in the folder of the defined device, TARGET_KERNEL_CONFIG is set correctly. Do I need to set it in a different BoardConfig.mk?
[Android] Arvind7352:
Sorry for the inconvenience, but the specified error has been fixed in staging branch, and hasn't been pushed to master yet. It'd be done ASAP, things are being finalized and tested. :)

Second error, most probably related to the Sources.
[Android] knuxfanwin8:
I keep having problems with files missing, mostly XML files.

Device Details - Samsung Galaxy Grand Neo, I don't have any sources except device config downloaded. Sadly, I was unable to find any information about how to use device specific sources with this program.

ROM Details - Resurrection Remix, 0 nougat

Location of the Repo/ScriBt from '/' - /home/kfw8/scribt/ScriBt

Version of ScriBt you were using - v2.1.2

Output of ScriBt which you feel erroneous/non-working/stuck -

fatal: manifest 'default.xml' not available
fatal: error parsing manifest /home/kfw8/scribt/.repo/local_manifests/cancel.xml: no element found: line 3, column 0
[Android] NZnewbie:
How'd you get on setting up the enviroment- im trying to now!.
[Android] phreakenstein:
Are you trying on Solus?
[Android] NZnewbie:
Yes- Ive got repo sync'd but have a silly error when i mka clobber and mka to build. error 127 clang crappiety crappiety fml :D:D:D

So its a near thing. You get yours going?.
[Android] phreakenstein:
I'm sorry, I never got around to try ScriBt on Solus. You should ask on sokus IRC. I've had extremely good support there for everything Solus.
[Android] NZnewbie:
Neither did I. I just followed instructions on solus forums.

https://solus-project.com/forums/viewtopic.php?f=11&t=8790

And yeah I asked them on there. They are pretty helpful. Im compiling a rom now so it works. :good:
[Android] phreakenstein:
Nice. Don't forget to document everything. Write a nice article on medium or something so anyone coming after you had a highway ready.
[Android] NZnewbie:
Its pretty cut and dry- Updated the thread with Rsync needed as well. Completed a dirty build and just doing a clean one now- well nearly finished.

Seems as good as mint if not better looking OS and graphics. Speed i wont know till done a few builds.
[Android] Arvind7352:
[!] Update - ScriBt release 2.2

[IMG="two two"]https://github.com/ScriBt/images/raw/master/release-twotwo.png[/IMG]

[>] For changelogs and announcements Visit our Blog Post below

https://scribt.github.io/2017/08/08/Release-2.2.html

[>] To observe ScriBt in Action, you may visit these URLs below

https://asciinema.org/a/130072

https://asciinema.org/a/131683

Take a read through the Blog Post for more Information on these "asciicasts"

[>] Users have to re-clone ScriBt, since updater is suspected to fail for older versions (@TimSchumi to the rescue :fingers-crossed:)...

[>] upScriBt is Fixed in hotfix version v2.2.1

#HappyScriBting
[Android] rajit:
any way to solvde this bro
[Android] TimSchumi:
This is not a ROM building error helping thread. It's better if you ask in one of the ROM Building threads.
[Android] Nirbhay2:
Not able to initiate repo.

It tries to reach github.com only

While its github.com/lineageOS
[Android] Arvind7352:
Please read the FAQ, and Provide ScriBt's output which you find troublesome.
[Android] majorkid:
Thanks for providing this ..

I've been facing and error ,please do take a look..

https://pastebin.com/D6s1KjVE

and before facing this , I was syncing AOSPA and my pc went off without finishing the complete source syncing , so I was asking Can I resume from where it stopped , If Yes How ?

Thanks
[Android] TimSchumi:
This is not a Thread to ask for ROM Building errors. In this case, you just need to create the Directory manually.
[Android] YuriRM:
I know that this tool has been conceived for Qualcomm devices.

Nevertheless, can I use Projekt ScriBt for a MT6592 device (Estar Takee 1) ? Some clones with device trees are given below.

This is a device tree for huawei g750t01 which is based on MT6592 SoC. Powered by ferhung.

https://github.com/ferhung-mtk/android_device_huawei_g750t01

Micromax Canvas Nitro A311 Vendor Tree

https://github.com/moihack/android_vendor_Micromax_A311-cm-13.0

GitHub - Lineage OS 13 for MT6592

https://github.com/Lineage-OS-13-MT6592/android

The Device Info HW app by Audrey Efremov gives all the information needed on components and drivers for my device.

https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw

MANUFACTURER	\ BRAND \	MODEL \	REVISION \ PLATFORM	\ RESOLUTION	\ LCM \	TOUCHSCREEN \	CAMERA \	LENS \	ACCELEROMETER	\ ALSPS	\ MAGNETOMETER \	GYROSCOPE	\ CHARGER \	SOUND	\ PMIC \	RTC \	WIFI \	MODEM \	FLASH	\ OTHER	\ SCSI

ESTAR Takee - Database of Device Info HW by Audrey Efremov

http://deviceinfohw.ru/devices/index.php?platform=platform0&brand=brand0&filter=takee&submit=Search

List of ESTAR Takee clones for parts

https://xdaforums.com/showpost.php?p=74386084&postcount=1199

MT6592 ROMs by MTK Dev

http://mtk-devs.blogspot.pt/

[ROM][STABLE] MIUI 9 China BETA 7.8.28 - MT6592

[6.0.1][STABLE] Flyme 6 - 6.6.7.15R BETA - MT6592

[6.0.1][STABLE][23/05/2017] Resurrection Remix 5.7.4 r79 - MT6592

[6.0.1][STABLE][24/05/2017] LineageOS 13.0_r79 - MT6592

[ROM][STABLE][LP][r38] Temasek's CM 12.1- MT6592

[AOSP][STABLE][r79] Slim6 V2.1 - MT6592

[STABLE][AOSP][OMS] NitrogenOS_r79 - MT6592

Make ROMs Developers - blogger by Mark Kevin Flores

https://makeroms.blogspot.com/?m=1

[6.0.1] [MTK6592] Lineage OS 13.0 R79 (ChangeLog: 24/05/2017)

https://makeroms.blogspot.pt/2017/05/601mtk6592-lineage-os-130-r79.html

[6.0.1] [MTK6592] Slim 6 6.0.1 R79

https://makeroms.blogspot.pt/2017/05/601mtk6592-slim-6-601-r79.html

[6.0.1] [MTK6592] Temasek 10.8 Pixel Theme

https://makeroms.blogspot.pt/2017/04/601mtk6592-temasek-108-pixel-theme.html

[6.0.1] [MTK6592] Nitrogen OS (ChangeLog: 16/04/2017)

https://makeroms.blogspot.pt/2017/04/601mtk6592-nitrogen-os.html

There are plenty of MT6592 ROMs available and also some MT6592 sources plus device trees on GitHub. Can I use Projekt ScriBt for my device ESTAR Takee?

There are several stock 4.2.2 JellyBean ROMs by ESTAR Takee. Also available is one Custom 4.4.2 KitKat ROM by LuckasFB and one ported 6.0.1 CyanogenMod 13 ROM by VladJocker (linux kernel 3.4.67).

Takee 1 (Full Review) 3D Holographic Phone (Cheaper 2015 version with Play Store) by s7yler

https://xdaforums.com/general/devic...-review-3d-holographic-phone-t3202829/page121
[Android] kelvinvirani@gmail.com:
Is there any video tutorial for using this ?

Is it working now for build oreo and nougat roms ?

Is it helpful to make unofficial device builds

For ex build lineage os for dior(which is nit listed on repo directory)
[Android] Arvind7352:
This itself is a tutorial. I've put the Asciicasts (terminal recording) to show how it works

Available here -> https://asciinema.org/~a7r3

Nougat ROMs, yes, it works.

Oreo ROMs... I haven't built one by myself yet, so ScriBt might not support these ROMs

This is useful for you. And is not a 'quick' way of obtaining an Unofficial Build. (Yes, you can build for any device, provided you have Device-Specific source code). Once you get the gist of building a ROM by yourself, you can stop using ScriBt. Self-study is the best study
[Android] dashingdon:
I am trying to port oreo to HTC One +X AT&T version. While I know this is not the thread , if you can provide any pointers on how I can use scribt for this task that would be fantastic.

Apologize in advance for asking a silly question but I am a newbie and trying to understand the porting part. And I know this probably wont be possible as oreo source code for the device is not available. Just trying to learn.

Thanks ..

-dash
[Android] z4ck1n:
This is fantastic, actually learned from this tool.

https://asciinema.org/a/130072
[Android] miuipower:
hello everyone wanted to ask them I wanted to build lineages but I do not know what I have to put in here I get this, can you tell me what do I have to put there? thank you excuse my english
[Android] 2C.LiryC:
Hi,

I'm trying to use this tool, which looks exactly to be THE tool for me, but I can't go further than the "Install Build Dependencies" because of "unsupported distro".

I'll manually install the dependencies. Could I expect the tool to work as intended when those dependencies are installed ?

If you can add support for Ubuntu Mate (I use 17.10.1) in further versions, it could help beginners like me. :o

Anyway, thanks for the tool.

It's already very helpful to learn with it.
[Android] TimSchumi:
I added Ubuntu 17.10 to the supported distros, please clone ScriBt's staging branch and check if it works.
[Android] 2C.LiryC:
Staging branch is working.

Thanks a lot. :)
[Android] 2C.LiryC:
Starter help

It's me again. :o

I started again on a clean OS install (it's a VirtualBox machine, so it's fast enough) to have ScriBt handle all the process from its beginning.

So, I'm at the "Tools" part and install the components one after another. Everything is fine.

I take note of the advice at "7. Install ninja ~"

[!] Installed Version of ninja : 1.7.2

[!] To make use of Host versions of Ninja, make sure the build repo contains the following change

[url]https://github.com/CyanogenMod/android_build/commit/e572919037726eff75fddd68c5f18668c6d24b30[/url]

[!] Cherry-Pick this commit under the build folder/repo of the ROM you're building

To understand it clearly, it means I'll have to copy/paste the above URL as a commit in the further generated repo config file ?

Also, by continuing to install tools, after installing CCache, I go for "3. Setup ccache (After installing it)".

I allow it 40GB and give it a folder.

But whatever name and location I give to it, I can't find it where it should be.

Checking the ccache.conf, it shows only

Is it good anyway as the file and folder will be generated upon ccache 1st use (as it's only installed for now) or did I miss something ?
[Android] TimSchumi:
You don't need to do anything if you don't explicitly need the host version of ninja (i.e. in /usr/bin). If you don't do anything, it will automatically use the ninja version shipped inside the ROM tree.

However, if you do need it, you need to cherry-pick that specifoc commit to your ROM tree.

If I remember correctly, the ccache will be created inside ~/.ccache by default (your ccache.conf should be located there, too). To change this, simply set the CCACHE_DIR environment variable to whatever place you want to save your ccache.
[Android] 2C.LiryC:
Many thanks for your time, explanations and dedication. :good:

I've already made huge progresses. Mostly by studying your tool. It's really great to understand and go further each time.

But yet, I have another error. :(

I've cloned a source of the device (an Asus ZC520TL/X008D) and have correctly set everything to be ready to build.

So, at 4,

I do

1 to build the ROM

make/mka (tried both)

n for the output in the same directory

2, full clean

y to use ninja

and then, lunch

But ends with

...
============================================
Checking build tools versions...
build/core/base_rules.mk:183: *** .local/share/Trash/files/audio/audiosetting: MODULE.TARGET.SHARED_LIBRARIES.libaudiosetting already defined by .local/share/Trash/files/audio.2/audiosetting. Stop.

#### make failed to build some targets (4 seconds) ####

[!] Command Execution Successful
══════════════════════════════════════════════════════
[!] Build Status : Failed
[!] Build took 0 hour(s), 0 minute(s) and 7 second(s).
[!] Build log stored in /home/liryx/temp_compile.txt

Any idea about what's going on ? I can't see by myself.

Really sorry to have to ask. As I don't understand it, I have no clue about where to start to search.
[Android] TimSchumi:
~/.local/share/Trash is the directory of your Trash. Empty it and you should be fine (It found some deleted ROM files in your trash and treated them as they were in your source tree).

It seems though that you cloned your ROM's source directly into your home directory, which is not recommended.

Make a new folder in your home directory and move the .repo folder there. Then you should start ScriBt from inside that folder and start over at "repo sync" (which fortunately takes a much shorter time, as you moved the .repo folder).

After that, you probably should clean up your home directory, as it is clobbered up with the ROM source right now.
[Android] 2C.LiryC:
I didn't understood why it was referring to Trash. :eek:

Thank you (again) for the explanation.

And another greeting for the advice about having all the stuff in the home directory.

I was wondering if it was intended to have all this in here. ^_^'

I'll move and clean as you said and then, start again.

:good:
[Android] TimSchumi:
~/.local/share/Trash is located in your home directory (which is currently your source root as well), so it will get searched by the build system for modules to include. (~ is the bash shortcut for your home directory)
[Android] 2C.LiryC:
Many thanks!

Yes, that's what I understood when you've advised me about having all the stuff in the home folder. :o

It's confirmed, your tool is awesome.

it helped me a lot (in conjunction with many tutorials, of course) to learn what I have to know to be able to produce a build.

And finally :

:highfive:

Now I need to move to another topic for my specific new problem, building for an unsupported Asus ZC520TL (X008D) but, as I can build for my own device (a mido :)) and build it step by step (without the help of your tool), I know I have a valid environment that can build.

In fact, now that I know how to do it "by hands", I also know I'll still use your tool. :D

It's very handy for configuring all the available improvements (mka, ninja, ccache) and automation.

And I still have many things to learn from, such as kernel building. :D

So, it's a goodbye.

Thanks for all. Your tool, but also your helping hand at understand things and setting them up correctly.

You have my respect and gratitude. :)
[Android] :
Delete
[Android] TimSchumi:
There is no error in here. The Android Source is full of warnings (e.g. "Some input files use unchecked or unsafe operations"), you can ignore those though. But make sure to ask in a ROM buildimg thread next time, not here. The chat in here should be related to ScriBt, not ROM building in general.
[Android] :
How can I compile faster?
[Android] dj_chele:
Help with Rom Project Fujitsu Arrows F-02E

Hello everybody

I have a Fujitsu Arrows F-02E since 2013 with a software issues

I think that the unique solution to return device to life is building a rom to install them

At this time I am not programmer I only have knowledge about windows and basic programming

I have source code of rom for this phone in a tar.gz file but I don't know how I can get kernel and other files

It is possible that I share with you open source code file for this phone and you help me compilating a rom to install on phone through recovery?

I really appreciate your comments

Regards
[Android] TimSchumi:
We cannot help you with developing directly and build errors and questions should be posted in a ROM building thread, not here.

---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------

Get a better PC or upgrade it.

Most important:

- Faster CPU

- Better I/O (e.g. get a SSD)

- (maybe) more RAM
[Android] bertino:
Is it compatible with ubuntu 18.04, or does it need an update? I tried and it tells me

[!] No supported package manager has been found.

[!] Arch Linux or a Debian/Ubuntu based Distribution is required to run ScriBt.
[Android] TimSchumi:
It probably needs just a copy-over of the package list. I'll push it in a few hours.

EDIT: Eh, misread the error. Could you check if apt-get is still installed on your system? (And please check the command "apt-get moo", too)
[Android] Pac_MM:
Same error here.

apt-get installed ok:

pacmm79@pacmm79-VB ~/PacKitchen $ apt-get moo

(__)

(oo)

/------\/

/ | ||

* /\---/\

~~ ~~

..."Have you mooed today?"...

Thanks Team!
[Android] cyjaneczek:
Hello, how can I fix this error? https://hastebin.com/ifekabitor.pas

What size I have to set?
[Android] dargonswim:
Hello I have never done any ROM and have little idea of programming. Is there a step-by-step tutotial for dummies to compile a ROM? I've tried several times but I can't even get to step 1

Thank you
[Android] bassbounce:
When i start to build the kernel i get some strange errors.

../scripts/gcc-version.sh: line 31: printf: Is: invalid number
../scripts/gcc-version.sh: line 31: printf: your: invalid number
../scripts/gcc-version.sh: line 31: printf: PATH: invalid number
../scripts/gcc-version.sh: line 31: printf: set: invalid number
../scripts/gcc-version.sh: line 31: printf: correctly?: invalid number
../scripts/gcc-version.sh: line 31: printf: Is: invalid number
../scripts/gcc-version.sh: line 31: printf: your: invalid number
../scripts/gcc-version.sh: line 31: printf: PATH: invalid number
../scripts/gcc-version.sh: line 31: printf: set: invalid number
../scripts/gcc-version.sh: line 31: printf: correctly?: invalid number
/bin/sh: 1: [: 0000: unexpected operator
CHK include/config/kernel.release
UPD include/config/kernel.release
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
/home/bassbounce/ScriBt/kernel/Makefile:1073: recipe for target 'prepare-compiler-check' failed
make[1]: *** [prepare-compiler-check] Error 1
make[1]: Leaving directory '/home/bassbounce/ScriBt/kernel/popo'
Makefile:150: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
[Android] pezeus:
[Linux Mint] No supported Package Manager found.

[!] No supported package manager has been found.
[!] Arch Linux or a Debian/Ubuntu based Distribution is required to run ScriBt.
[!] Unsetting all variables
[!] Thanks for using ScriBt.
[</3] Failed somewhere :(

I'm using Linux Mint and I can't really figure a workaround, did it work on Mint Previously?

PS: I'm fairly new to Android ROM Development.
[Android] anonimador:
Awesome projekt... you guys make me feel that I can make some kind of android "fish and chips" flavoured ROM as my first try.

Thank you!!!
[Android] Deepansh Pandey:
i am getting the same error in 2021

how did you fixed it
[Android] datecasp:
Hi! Iḿ not sure if this thread is still active with @Arvind7352..

Iḿ starting in ROM developing and made my first build from LineageOS 14.1 for n1awifi.

Now I want to update the ROM to LineageOS 16.0 with this tool but Iḿ not sure if itś possible with the 14.1 branch repo and The Muppets proprietary blobs for 16.0

Is there anybody who tried to do something similar? Make a new source code from an older one for a now not supported device.

TIA!!
[Android] datecasp:
Hi there!

I got an error when I sync the repo. ScrBit gives me errors in main.py

Can anybody explain it please?

TIA!
[Android] ahmed.ismael:
impressive tool

Many thanks for the great work

this tool help the user to build roms from the available sources not the unreleased sources

Tow posts above yours only linux
[Android] Choochter:
Great work! Possibly add Pure Nexus to the list?

Thanks
[Android] Miustone:
Thanks for this Project Mate! Keep it up!

I'm modding Android since Years and i always wanted a own created base build on my own. But i was always to lazy to read that much and to learn all the stuff. Well, i'm now a bit more experienced with Linux and the Commands but this Project makes it even more easy for me to start! The Idea is great and it seems to work like a charm. I'm preparing my PC with Ubuntu 16.04.01 LTS for it in the next Days and i hope i can manage to use my GTX 960 to boost the building speed up a bit more. Don't know how to yet but i hope it will work... Anyways, thanks again for this Project and for giving us the chance to do what we want!

BR
[Android] Arvind7352:
ScriBt updated to v1.34

Changelogs updated in Post #3

Thanks [MENTION=6430109]sanekghost[/MENTION] for reporting an issue related to "User mentioning no Build-Type Prompt"

[MENTION=7356450]Choochter[/MENTION] I can add PureNexus or any Non-CAF ROMs available, the thing which is stopping me from doing this, is that the user may be unaware of the CAF/Non-CAF, Devices/ROMs concept and mistakenly try to build a Non-CAF ROM for a CAF Device.

Non-CAF ROM/Device : The ROM can only be built for Google Nexus Devices, since it's development is taken care of by Google

CAF ROM/Device : The ROM can be built for Google Nexus Devices as well as ALL other Qualcomm Devices which has open-source development.

[>] CAF's project "Android for MSM" provides necessary Code-Base to boot a AOSP ROM on a Qualcomm supported Device, and the ROMs listed on the OP makes use of this project.

[>] It is highly possible that the user doesn't know about this concept, so unless I/someone could do something to explain the difference while the User has chosen a Non-CAF ROM, these ROMs can't be added to ScriBt. I'd very eager to add this and some other ROMs in the list, by getting this point explained to the user in some or the other way.

P.S. : Anyone can correct me on information related to CodeAurora Forums
[Android] Choochter:
Thanks for clarifying that. It was a Nexus 9 I was looking to build for so I would have been OK, but I get your point.

Perhaps a warning placed in the script about compatibility when choosing those ROMs would suffice
[Android] kirito9:
Give this man a cookie!! Awesome work!! :highfive:
[Android] JohnRogers23:
To clarify, this is for building for devices with already available source trees, not for helping a noob like myself build for a device that gets no love (HTC One A9)? I've read a lot of guides for building devices with a developer community in place, but finding how to develop for a new device is a challenge.
[Android] Arvind7352:
ScriBt is a guide for the user to understand two basic aspects of getting into Android Development.

1. Android BuildSystem

2. Usability of Device Sources in the BuildSystem

Developing for a new device needs more than these two aspects, some of them are,

# Understanding the the working of the Device (Characteristics of the Device), and how these characteristics are brought to the Device tree

# Structure Of Device Tree

# Getting used to C/C++/Java Languages

And many more. For doing this, you've to first get a device with ongoing development and start understanding stuffs. This is a long process, and a challenge. And to be honest, I haven't completed that stage yet.