Database Users

[ADDON][NDK] Built the Android NDK for Android. Want to port a lot of GNU tools.

Hi,
For description, look here http://my-android-travels.blogspot.com/2012/02/android-build-system-ndk-toolchain.html and here http://my-android-travels.blogspot.com/2012/02/android-build-system-ndk-toolchain_21.html
https://docs.google.com/open?id=0B2qClbkV-4gpYWY5ZTE5NWYtYmU0ZC00MTAzLWIwN2MtNjQ4YTZmNzgyNTZj
Just place it on your sdcard, su, cd /, tar xzf /mnt/sdcard/ndk.tar.gz
When done, you find it in /data/local
I'm searching for people which wants to help me port in the first step the whole tools known as build-essential in debian. In a second step apt. If you are seeing yourself doing that, have the needed knowledge or the will to learn, please pm me
Have Fun
Ralph

I tried your NDK build on a 2.2 device (a Toshiba AC100) but, I run into a weird error when I try to run some of the executables:
Code:
/storage/home/t/data/local/bin $ file ./ar
./ar: symbolic link to `arm-linux-androideabi-ar'
/storage/home/t/data/local/bin $ ls -l ./arm-linux-androideabi-ar
-rwxr-xr-x 2 10035 10035 651482 Feb 20 20:47 ./arm-linux-androideabi-ar
/storage/home/t/data/local/bin $ file ./arm-linux-androideabi-ar
./arm-linux-androideabi-ar: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=0x5ee70e99463cef4692571cb07050ebf3819024ad, not stripped
/storage/home/t/data/local/bin $ strace ./arm-linux-androideabi-ar
execve("./arm-linux-androideabi-ar", ["./arm-linux-androideabi-ar"], [/* 16 vars */]) = -1 ENOENT (No such file or directory)
write(2, "strace: exec: No such file or dir"..., 40) = 40
exit(1) = ?
I cannot figure out why the command fails to run , and I'm hoping that you can help me out here,

try it on an android 4
also be sure that its located on an ext partition. put it into /data/local

Hi Ralph,
I'm running the binaries off an ext4 partition (and tried it from /data/local path(/data is ext4), as per the instructions). However, I don't have the luxury of using ICS. I'm stuck on FroYo as Toshiba no longer provides updates for my device , and doesn't release the sources either .
Could you give me some insight on why the binary will run on ICS, yet fail on FroYo?
Code:
/storage/home $ cd /data/local/bin/
/data/local/bin $ for i in arm-* ; do echo ------$i------- ; $i --help >/dev/null ; done
------arm-linux-androideabi-c++-------
------arm-linux-androideabi-cpp-------
------arm-linux-androideabi-g++-------
------arm-linux-androideabi-gcc-------
------arm-linux-androideabi-gcc-4.4.3-------
------arm-linux-androideabi-gcov-------
------arm-linux-androideabi-gdb-------
Segmentation fault
------arm-linux-androideabi-run-------
Segmentation fault
------arm-linux-androideabi-addr2line-------
sh: arm-linux-androideabi-addr2line: not found
------arm-linux-androideabi-ar-------
sh: arm-linux-androideabi-ar: not found
------arm-linux-androideabi-as-------
sh: arm-linux-androideabi-as: not found
------arm-linux-androideabi-gccbug-------
sh: arm-linux-androideabi-gccbug: not found
------arm-linux-androideabi-gprof-------
sh: arm-linux-androideabi-gprof: not found
------arm-linux-androideabi-ld-------
sh: arm-linux-androideabi-ld: not found
------arm-linux-androideabi-nm-------
sh: arm-linux-androideabi-nm: not found
------arm-linux-androideabi-objcopy-------
sh: arm-linux-androideabi-objcopy: not found
------arm-linux-androideabi-objdump-------
sh: arm-linux-androideabi-objdump: not found
------arm-linux-androideabi-ranlib-------
sh: arm-linux-androideabi-ranlib: not found
------arm-linux-androideabi-readelf-------
sh: arm-linux-androideabi-readelf: not found
------arm-linux-androideabi-size-------
sh: arm-linux-androideabi-size: not found
------arm-linux-androideabi-strings-------
sh: arm-linux-androideabi-strings: not found
------arm-linux-androideabi-strip-------
sh: arm-linux-androideabi-strip: not found
/data/local/bin $ mount |grep data
/dev/block/mmcblk3p5 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)

Rooting just not working

Hello,
I have tried searching these forums for an eligible solution however all my attempted search terms came back with threads that did not quite explain what i am experiencing. Or for that matter were understandable by me. So excuse me in advance if you believe this question has been answered somewhere else. Instead of expressing your rage please feel free to send me a message pointing me in the right direction.
I have tried multiple ways to obtain root access to my tablet. Sadly all of them failed.
What I understand from this is that somehow there is not enough memory on a partition in order to succeed.
Here's the conflict Does one need root access to say, enlarge or change a partition?
DooMLoRD's method seemed to get the furthest but ultimately failed.
--- checking free space on /system
19 KB/s (439 bytes in 0.021s)
df: /mnt/.lfs: Function not implemented
--- Free space on /system : 0 bytes
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
[1] Segmentation fault /system/xbin/bus...
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
GT-P1000
Firmware version 2.3.6
Baseband version P1000XXJPZ
Kernel version 2.6.35.7
GINGERBREAD.XWJQ8

you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752

edan1979 said:
you are just simply in a wrong forum....
better find your answer on Original Galaxy Tab 7.0
http://forum.xda-developers.com/forumdisplay.php?f=752
Click to expand...
Click to collapse
Valid point, Moving thread.

[OSX] stuck on rooting defy+

hi there,
today i got my first android phone motorola defy plus and i´m really stuck on rooting android the whole day.
first, i got ADB, installed and checked if it will find my phone. :good:
then, i downloaded "easy root toolkit and started it via terminal. this is what i got:
CONFIRM ALL THE ABOVE THEN
Press any key to continue...
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
cannot stat 'files/zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
cannot stat 'files/busybox': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
cannot stat 'files/su': No such file or directory
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
cannot stat 'files/Superuser.apk': No such file or directory
--- cleaning
rm failed for *, No such file or directory
--- rebooting
ALL DONE!!!
Click to expand...
Click to collapse
i really got no chance to root my phone via windows pc so i was going to ask for help here.
my defy+ is running following software:
2.3.4.
Build: 4.5.1.-134_DFP-74
Baseband EPU93_U_00.60.00
thank you very much in advance for your help.

try this tool maybe will help you http://forum.xda-developers.com/attachment.php?attachmentid=1235958&d=1343854436
on my defy red bl4 it work
with this tool (if it work on your defy+) can check bl version, can root and can install bootmenu

I just got my Defy+ rooted by following this http://forum.xda-developers.com/showthread.php?t=1820282
Actually i couldnt get it rooted by my self, but i flashed SBF that was rooted allready.

vaserbanix said:
try this tool maybe will help you http://forum.xda-developers.com/attachment.php?attachmentid=1235958&d=1343854436
on my defy red bl4 it work
with this tool (if it work on your defy+) can check bl version, can root and can install bootmenu
Click to expand...
Click to collapse
yeah. great.
but this is an executable and osx does not support exe-files.
so both methods are not suitable for OSX

[SCRIPT] FixPermissions without rebooting into recovery !!

Hi
I want to bring you the fix permission script , t exactly same as the one in cwm/twrp ! The whole codes are written by cwm and cyanogen mod developers . I did some changes and modification to make it run on android enviroment .
How to use ?
You have two ways to use this script :
1- Using Script Manager :
Just change it names from fp.txt to fp.sh and run it in root mode
2- Using terminal emulator :
rename it to fp.sh . move it to /system/bin . change permissions to rwxrwxrwx ( 777 ) . open terminal and type :
Code:
su
fp.sh
Credits
cyanogen mod team

777 is a good permission? Sorry but this makes the file world-writable. Maybe learn something about permissions in linux before providing a script?
Nexus 4 cihazımdan Tapatalk 4 Beta ile gönderildi

droidjam said:
777 is a good permission? Sorry but this makes the file world-writable. Maybe learn something about permissions in linux before providing a script?
Nexus 4 cihazımdan Tapatalk 4 Beta ile gönderildi
Click to expand...
Click to collapse
But I don't think he need it all the time!
Maybe he want remove it after run it
Sent from my GT-I9300 using Tapatalk 4 Beta

droidjam said:
777 is a good permission? Sorry but this makes the file world-writable. Maybe learn something about permissions in linux before providing a script?
Nexus 4 cihazımdan Tapatalk 4 Beta ile gönderildi
Click to expand...
Click to collapse
All busybox applets + system applets are moded in 777 !
I is just an small script and you have to remove it when you done your work . IT IS NOT A SYSTEM FILE OR A SYSFS FILE to be concerned about !!!!!!

Good! I needed some times something like this thanks for the scripts
regards!

Hello alireza7991 and thank you for this script!
I tried it on my Galaxy Tab 3 running RocketTab v3.1 ROM (excellent stuff, Android 4.1.2) using SSH Droid and Terminal (on my Mac) but I get a "Bus Error" for each application.
The fp.sh permissions are correct, and running it as "su" too, but I still get this below. Any idea what's wrong, please?
I think it starts by the fact it's not mounting properly. (please note this is run live, in Terminal via SSH) Check the "applet not found" error...
Code:
[email protected]:/data/data/berserker.android.apps.sshdroid/home # ./fp.sh
mount: applet not found
./fp.sh started at 02-08-2014 22:50:32
Processing (1 of 113): com.google.android.location...
Bus error
Processing (2 of 113): com.imdb.mobile...
Bus error
Processing (3 of 113): com.sec.android.app.phoneutil...
Bus error
[…]
Processing (112 of 113): com.google.android.syncadapters.contacts...
Bus error
Processing (113 of 113): com.google.android.backup...
Bus error
./fp.sh ended at 02-08-2014 22:50:57 (Runtime:0m25s)
[email protected]:/data/data/berserker.android.apps.sshdroid/home #

konsti said:
Hello alireza7991 and thank you for this script!
I tried it on my Galaxy Tab 3 running RocketTab v3.1 ROM (excellent stuff, Android 4.1.2) using SSH Droid and Terminal (on my Mac) but I get a "Bus Error" for each application.
The fp.sh permissions are correct, and running it as "su" too, but I still get this below. Any idea what's wrong, please?
I think it starts by the fact it's not mounting properly. (please note this is run live, in Terminal via SSH) Check the "applet not found" error...
Code:
[email protected]:/data/data/berserker.android.apps.sshdroid/home # ./fp.sh
mount: applet not found
./fp.sh started at 02-08-2014 22:50:32
Processing (1 of 113): com.google.android.location...
Bus error
Processing (2 of 113): com.imdb.mobile...
Bus error
Processing (3 of 113): com.sec.android.app.phoneutil...
Bus error
[…]
Processing (112 of 113): com.google.android.syncadapters.contacts...
Bus error
Processing (113 of 113): com.google.android.backup...
Bus error
./fp.sh ended at 02-08-2014 22:50:57 (Runtime:0m25s)
[email protected]:/data/data/berserker.android.apps.sshdroid/home #
Click to expand...
Click to collapse
install busybox and try :
Code:
export PATH=${PATH}:/system/xbin
before running it.

alireza7991 said:
install busybox and try :
Code:
export PATH=${PATH}:/system/xbin
before running it.
Click to expand...
Click to collapse
Thank you alireza7991, I am not an expert yet on Android (despite knowing some UNIX) so how can I first check if BusyBox is (properly) installed on this device? Is there a simple way to check, by means of e.g. a test command?
The ROM I am using is excellent RocketTab v3.1 for my Galaxy Tab 3 7" but unfortunately the thread is now locked (to ask). However, there is mention that BusyBox is installed... perhaps only the PATH environment was missing?
Many thanks again!

konsti said:
Thank you alireza7991, I am not an expert yet on Android (despite knowing some UNIX) so how can I first check if BusyBox is (properly) installed on this device? Is there a simple way to check, by means of e.g. a test command?
The ROM I am using is excellent RocketTab v3.1 for my Galaxy Tab 3 7" but unfortunately the thread is now locked (to ask). However, there is mention that BusyBox is installed... perhaps only the PATH environment was missing?
Many thanks again!
Click to expand...
Click to collapse
It's pretty similar to UNIX. type 'busybox' in terminal if busyox has not been installed shell will says the command not found or sth similar.

Hi again alireza7991, thanks for your info. Typing "busybox" on the terminal window on my Mac (via SSHDroid) I get:
Code:
BusyBox v1.21.0 (2013-07-08 16:00:47 CEST) multi-call binary.
Now, your export command although accepted, didn't work. So I figured typing it as I find it on my Mac:
Code:
export PATH="/system/xbin/":$PATH
[B]instead of[/B]
export PATH=${PATH}:/system/xbin
And now the script works, I tried it with -s option (for simulation) and get nothing as error(s) for apps. Does that mean I am OK in terns of "fixed" permissions?
However, as you can see, the last part of the script still has issues? Or is it the "simulation" flag?
Your comment is appreciated again… I think it's that last bit in your script (chmod 644 /system/app/*) which I am not sure what it serves for… or is it /system/ not properly mounted as r/w?
Many thanks:
Code:
[B][email protected]:/data/data/berserker.android.apps.sshdroid/home #[/B] [COLOR="DarkRed"]./fp.sh -s[/COLOR]
./fp.sh started at 02-15-2014 13:56:44
Processing (1 of 113): com.google.android.location...
Processing (2 of 113): com.imdb.mobile...
Processing (3 of 113): com.sec.android.app.phoneutil...
[...]
Processing (111 of 113): com.bigeyes0x0.trickstermod...
Processing (112 of 113): com.google.android.syncadapters.contacts...
Processing (113 of 113): com.google.android.backup...
./fp.sh ended at 02-15-2014 13:58:18 (Runtime:1m34s)
chmod: /system/app/AllshareService.apk: Read-only file system
chmod: /system/app/ApplicationsProvider.apk: Read-only file system
[...]
chmod: /system/app/minimode-res.apk: Read-only file system
chmod: /system/app/serviceModeApp.apk: Read-only file system
[B][email protected]:/data/data/berserker.android.apps.sshdroid/home #[/B]
alireza7991 said:
It's pretty similar to UNIX. type 'busybox' in terminal if busyox has not been installed shell will says the command not found or sth similar.
Click to expand...
Click to collapse

konsti said:
Hi again alireza7991, thanks for your info. Typing "busybox" on the terminal window on my Mac (via SSHDroid) I get:
Code:
BusyBox v1.21.0 (2013-07-08 16:00:47 CEST) multi-call binary.
Now, your export command although accepted, didn't work. So I figured typing it as I find it on my Mac:
Code:
export PATH="/system/xbin/":$PATH
[B]instead of[/B]
export PATH=${PATH}:/system/xbin
And now the script works, I tried it with -s option (for simulation) and get nothing as error(s) for apps. Does that mean I am OK in terns of "fixed" permissions?
However, as you can see, the last part of the script still has issues? Or is it the "simulation" flag?
Your comment is appreciated again… I think it's that last bit in your script (chmod 644 /system/app/*) which I am not sure what it serves for… or is it /system/ not properly mounted as r/w?
Many thanks:
Code:
[B][email protected]:/data/data/berserker.android.apps.sshdroid/home #[/B] [COLOR="DarkRed"]./fp.sh -s[/COLOR]
./fp.sh started at 02-15-2014 13:56:44
Processing (1 of 113): com.google.android.location...
Processing (2 of 113): com.imdb.mobile...
Processing (3 of 113): com.sec.android.app.phoneutil...
[...]
Processing (111 of 113): com.bigeyes0x0.trickstermod...
Processing (112 of 113): com.google.android.syncadapters.contacts...
Processing (113 of 113): com.google.android.backup...
./fp.sh ended at 02-15-2014 13:58:18 (Runtime:1m34s)
chmod: /system/app/AllshareService.apk: Read-only file system
chmod: /system/app/ApplicationsProvider.apk: Read-only file system
[...]
chmod: /system/app/minimode-res.apk: Read-only file system
chmod: /system/app/serviceModeApp.apk: Read-only file system
[B][email protected]:/data/data/berserker.android.apps.sshdroid/home #[/B]
Click to expand...
Click to collapse
I think I 've forgot to mount system rw before. this was used to fix a bug which caused bootloop in my device.
however this is an extremely old job and I do not remember what I have done, sorry .

alireza7991 said:
I think I 've forgot to mount system rw before. this was used to fix a bug which caused bootloop in my device.
however this is an extremely old job and I do not remember what I have done, sorry .
Click to expand...
Click to collapse
how to be included on my build rom?

[Guide][G800F/M/Y][7.1.2][UNOFFICIAL] Build Slim ROM 7 Nougat from Source

Overview
I've created a very simple #!/bin/bash script (attached) to automate the initial build or subsequent rebuild of SpookCity138's ROM:
Slim Rom 7 for the Samsung S5 mini G800f (kminilte). The script simply automates the steps and processes created by others (none of which is my own work - all credit goes to the original creators). I have only tested this script on my own working environment: Gnome Ubuntu 17.04; 16GB RAM; i7-7700HQ; If your environment differs from this your experience may differ from mine.
How to Execute script
See readme at: https://github.com/fidoedidoe/build_scripts
Thanks
@spookcity138, @jimmy999x. Taking the time to educate me at each and every tentative step and demonstrating great patience
Contributors
spookcity138
jimmy999x
Script Source
The latest version of the script (and others for different devices) can be found here: https://github.com/fidoedidoe/build_scripts
SpookCity138's ROM
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-slim-rom-7-nougat-t3558926
Created 2017-09-20
Last Updated 2017-12-09

There are sources to build this ROM for the Snapdragon variant (G800H)? It's a very good device, but simply there is not a single Nougat ROM for it...

wow, excellent, I have reviewed the code (I have not executed it yet) looks pretty good, it should work, I have to copy your script and modify it for other roms, thanks!
edit 1: it is possible to use this script (I use it and it works perfect) to automate even more the process of configuring the compilation environment https://github.com/akhilnarang/scripts
Also, for Ubunt 16.04 I added a couple more to make it easier some things:
cmake
nautilus (optional)
phablet-tools
unrar
silversearcher-ag (this is optional, but extremely useful for me, allows me to find the problematic lines inside a document or folder)

lfom said:
There are sources to build this ROM for the Snapdragon variant (G800H)? It's a very good device, but simply there is not a single Nougat ROM for it...
Click to expand...
Click to collapse
You need to apply some SELinux, CAF, And CM/LOS Patches to build a Nougat ROM for G800H, or that rom will not boot, or will shall not pass from build errors.
Is not a easy task.....

lfom said:
There are sources to build this ROM for the Snapdragon variant (G800H)? It's a very good device, but simply there is not a single Nougat ROM for it...
Click to expand...
Click to collapse
i found this on YT
so far so good for me
give it a try
https://youtu.be/UPOpJgqnlf8

not working for me -- using xubuntu 17.10

ko_taka said:
not working for me -- using xubuntu 17.10
Click to expand...
Click to collapse
Script updated on github (follow links for build_slimrom7_kminilte.sh). Tested on my laptop (Ubuntu gnome 17.04) and SlimRom7 version 1.17 builds successfully (although I have yet to test the build on the device). I'll update the attached zip in the opening page in the coming days, but as a general rule github is the best place to find latest version(s).
Thanks to @spookcity138 (again) for taking time the time and offering sound help / advice identifying the issues and resolve (the issue was within applying device specific patches ./apply.sh).

I am on 40GB partition. Not enough?
perly terminated.
Fetching projects: 70% (381/544) fatal: unable to access 'https://android.googlesource.com/platform/hardware/akm/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
Fetching projects: 73% (398/544) fatal: unable to access 'https://android.googlesource.com/platform/system/connectivity/shill/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
fatal: unable to access 'https://android.googlesource.com/platform/external/jsr330/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
Fetching projects: 74% (403/544) fatal: unable to access 'https://android.googlesource.com/platform/external/jsr330/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
error: Cannot fetch platform/external/jsr330
Fetching projects: 78% (425/544) fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: write error: No space left on device
fatal: index-pack failed
error: index-pack died
fatal: index-pack failed
fatal: index-pack failed
fatal: index-pack failed
fatal: index-pack failed
fatal: index-pack failed
error: Cannot fetch SlimRoms/frameworks_base
Click to expand...
Click to collapse

ko_taka said:
I am on 40GB partition. Not enough?
Click to expand...
Click to collapse
Yeah,you're running out of space. I don't recall exactly what the sources and the build of a nougat ROM take,space wise. It seems a little weird you were running out of space syncing the sources. If I recall correctly nougat sources are somewhere between 25-30GB. I could be wrong though. The actual build itself (the out folder) also takes a fair bit of space. Again,just guessing,but around 15-20GB. I would say 60GB would be what you need.

hi spookcity138, nice to see you around
I haven't coded that so I'm feeling a bit lost
The process finally ended (now I am on 80GB partition)
I do not know where is the build if that built anything
those are the last lines
build_slimrom7_kminilte.sh: 176: build_slimrom7_kminilte.sh: [[: not found
Remove references to OmniRom recovery...
remove config_uriBlruEnabled references, spoils the build...
alter local manifest files for slimrom 7 build compatability...
insert text into file: frameworks/base/core/res/res/values/config.xml...
delete file cm_arrays.xml...
remove flipflap stuff from device/samsung/smdk3470-common/smdk3470-common.mk...
build_slimrom7_kminilte.sh: 205: read: Illegal option -t
build_slimrom7_kminilte.sh: 210: build_slimrom7_kminilte.sh: [[: not found
patching file include/telephony/ril.h
Hunk #1 FAILED at 31.
Hunk #2 succeeded at 395 (offset -1 lines).
Hunk #3 succeeded at 409 (offset -1 lines).
Hunk #4 succeeded at 569 (offset -1 lines).
Hunk #5 succeeded at 624 (offset -1 lines).
Hunk #6 succeeded at 1023 (offset -1 lines).
Hunk #7 succeeded at 5217 (offset -1 lines).
Hunk #8 succeeded at 5866 (offset -1 lines).
1 out of 8 hunks FAILED -- saving rejects to file include/telephony/ril.h.rej
manually reapplying failed Hunk #1...
patching file ril/Android.mk
patching file ril/libril/Android.mk
patching file ril/libril/ril.cpp
patching file ril/libsecril-client/Android.mk
applying frameworks_av to frameworks/av
Applying: av: Add samsung wfd service
Applying: add Android M MediaBufferGroup:MediaBufferGroup() for libwvm.so
applying frameworks_native to frameworks/native
Applying: Revert "Remove Parcel::writeIntPtr."
Applying: add missing const getSensorList() for MM gpsd (G800FXXU1CPK5)
applying hardware_libhardware to hardware/libhardware
applying hardware_ril to hardware/ril
Applying: ril: recover on crash
applying hardware_samsung_ril to hardware/samsung/ril
Applying: add SetAudioMode and SetSoundClockMode for MM audio-ril
applying packages_services_Telephony to packages/services/Telephony
./apply.sh: line 24: cd: /home/ferran/android/build_scripts/packages/services/Telephony: No such file or directory
build_slimrom7_kminilte.sh: 238: read: Illegal option -t
build_slimrom7_kminilte.sh: 243: build_slimrom7_kminilte.sh: [[: not found
prepare device specific code...
build_slimrom7_kminilte.sh: 249: build_slimrom7_kminilte.sh: source: not found
build_slimrom7_kminilte.sh: 250: build_slimrom7_kminilte.sh: lunch: not found
running croot...
build_slimrom7_kminilte.sh: 253: build_slimrom7_kminilte.sh: croot: not found
build_slimrom7_kminilte.sh: 262: read: Illegal option -t
build_slimrom7_kminilte.sh: 267: build_slimrom7_kminilte.sh: [[: not found
running mka bacon...
build_slimrom7_kminilte.sh: 273: build_slimrom7_kminilte.sh: mka: not found
Click to expand...
Click to collapse

ko_taka said:
hi spookcity138, nice to see you around
I haven't coded that so I'm feeling a bit lost
The process finally ended (now I am on 80GB partition)
I do not know where is the build if that built anything
those are the last lines
Click to expand...
Click to collapse
The build did not start. It applied the patches successfully (all but one where there was an error) Then it is just a serious of failures. I have not used this script so I cant say specifically where you are going wrong. Does the script have executable permissions? (I assume so as it partially worked) Do you have all of the need dependencies for building Android? Thats not the issue I don't think,but you need them either way. Other than that I am not real sure honestly. You may need to wait for @fidoedidoe to help you. I'll reply back if any possible reason comes to mind.

ko_taka said:
hi spookcity138, nice to see you around
I haven't coded that so I'm feeling a bit lost
The process finally ended (now I am on 80GB partition)
I do not know where is the build if that built anything
those are the last lines
Click to expand...
Click to collapse
Hi @ko_taka
@spookcity138 is correct, the script failed...when it succeeds it's pretty clear the last few messages published will read along the lines of: "Package Complete: .../out/target/product/kminilte/Slim-kminilte-7.1.2.build.1.17-UNOFFICIAL-20171209-1401.zip" followed by "#### make completed successfully (24:30 (mm:ss)) ####" (note the build time will vary depending on the power of your build machine and utilisation of ccache). Oh, FYI - my build folder is ~95GB in size (the ../out/ folder is 26GB and the ../.repo/ folder is 47GB!!)
Back to the script failure....first verify the following variable in the build_slimrom7_kminilte.sh is defined correctly for your environment:
Code:
WORK_DIRECTORY="$HOME/android/slimrom7"
For my personal build environment I keep the script (build_slimrom7_kminilte.sh) in a separate folder to where the source is located and the build is output to (just so i can purge those folders without losing the build script). FYI on your laptop your folder structure should look something like that shown below, with build_slimrom7.kminilte.sh stored in the folder .../build_scripts
Code:
/home/ferran/android/build_scripts
/home/ferran/android/slimrom7
Once the above is verified...the primary issue you have is every time you see "...[[: not found", the script is hitting an issue. Check that the first line of the script contains the line "#!/bin/bash ", this is called "shebang" and it tells your shell what program to interpret the script with, in our case we need "Bash". I'm now wondering what OS / Shell you're using (I use Ubuntu Gnome 17.04 with Bash version 4.4.7) does yours differ from this? To verify your Bash version:
Code:
$ bash -version
GNU bash, version 4.4.7(1)-release (x86_64-pc-linux-gnu)
Copyright © 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
You could try forcing your shell to use bash (from memory), by switching to the /build_scripts/ folder and running the following command (do not use sudo or any elevated permissions):
Code:
$ cd /home/ferran/android/build_scripts
$ ./build_slimrom7_kminilte.sh
Let me know how you get on, in essence the script is failing on the evaluation lines where "if [[....]]" is used. if we can't get it to work, in your case, the script may need to be altered to change the evaluation (perhaps "if [...]" would be more suitable). Anyway - give me some feedback and lets see if we can get you a little further.

my bash is 4.4.12
working directory had been set correctly
I removed the double [[ leaving a simple [ same with ]] closing brackets
it says Illegal option -t in line 238
this is line 238: read -r -p "6/7. Initialise environment for Build <Y/n>? (automatically continues unprompted after 10 seconds): " -t 10 -e -i Y PROMPT
it also says [: Y: unexpected operator on line 243
this is line 243: if [ ! $PROMPT =~ ^[Yy]$ ]; then

Timte to time I was getting errors while fetching
TLS errors
I found it is due gnutls package and applied the following solution:
compile git with openssl. To do this, run the following commands:
sudo apt-get update
sudo apt-get install build-essential fakeroot dpkg-dev libcurl4-openssl-dev
sudo apt-get build-dep git
mkdir ~/git-openssl
cd ~/git-openssl
apt-get source git
dpkg-source -x git_1.7.9.5-1.dsc
cd git-1.7.9.5
(Remember to replace 1.7.9.5 with the actual version of git in your system.)
Then, edit debian/control file (run the command: gksu gedit debian/control) and replace all instances of libcurl4-gnutls-dev with libcurl4-openssl-dev.
Then build the package (if it's failing on test, you can remove the line TEST=test from the file debian/rules):
sudo dpkg-buildpackage -rfakeroot -b
Install new package:
x86_64: sudo dpkg -i ../git_1.7.9.5-1_amd64.deb
Click to expand...
Click to collapse
I'm using git-openssl build now
Just started the fetching process again
I'm under virtual machine on a host with a proper firewall configuration -- maybe that caused the connection problems while fetching

ko_taka said:
my bash is 4.4.12
working directory had been set correctly
I removed the double [[ leaving a simple [ same with ]] closing brackets
it says Illegal option -t in line 238
this is line 238: read -r -p "6/7. Initialise environment for Build <Y/n>? (automatically continues unprompted after 10 seconds): " -t 10 -e -i Y PROMPT
it also says [: Y: unexpected operator on line 243
this is line 243: if [ ! $PROMPT =~ ^[Yy]$ ]; then
Click to expand...
Click to collapse
Sounds like we're making progress. This is good. So, reading around the subject of square brackets vs double. It transpires converting the evaluations from double square brackets ([[..]]) to singles ([..]) may** change how variables are referenced. In my script I was forced to use double square brackets to correctly evaluate the response from the "read -r....." (read input) command (where it evaluates when upper or lower case Y is entered). If this command is changed from double square brackets to single ones the command then fails (on my setup). Further to this, in your reply it appears you're also having issues with the "read" command, for some reason your version doesn't support the -t directive (which waits for N seconds - ie: -t 5 will wait 5 seconds for user input).
For now the easiest thing to do is to remove *all* of the steps in the script that awaits input from the user to continue processing the script (they are non essential vanity items primarily used while I was building out the script). There are 7 is these in the script (look for "1/7", "2/7", "3/7", etc etc), just comment out (insert # at beginning of each line) for all 7 instances. There are ~10 lines per instance, examples of how instance #1 and #7 should look after editing is below. Just do the same for all 7 instances in your script and re run the script.
Code:
...
...
#PROMPT=""
#read -r -p "1/7. Initialise/Reinitialise Repo, first 'repo init' will take hours <Y/n>? (automatically continues unpromted after 5 seconds): " -t 5 -e -i Y PROMPT
#echo
#if [ -z "$PROMPT" ]; then
# PROMPT="Y"
#fi
#if [[ ! $PROMPT =~ ^[Yy]$ ]]; then
# echo "Response: '$PROMPT', exiting!"
# exit 1
#fi
...
...
#PROMPT=""
#read -r -p "7/7. Build rom (this segment can take hours) <Y/n>? (automatically continues unprompted after 10 seconds): " -t 10 -e -i Y PROMPT
#echo
#if [ -z "$PROMPT" ]; then
# PROMPT="Y"
#fi
#if [[ ! $PROMPT =~ ^[Yy]$ ]]; then
# echo "Response: '$PROMPT', exiting!"
# exit 1
#fi
...
I'd be really interested in knowing what OS you're using (Ubuntu, Mac, etc along with version) perhaps I can use this detail to come up with a more generic version of the script.
Good luck, let me know how you get on.

ko_taka said:
Timte to time I was getting errors while fetching
TLS errors
I found it is due gnutls package and applied the following solution:
I'm using git-openssl build now
Just started the fetching process again
I'm under virtual machine on a host with a proper firewall configuration -- maybe that caused the connection problems while fetching
Click to expand...
Click to collapse
I'd also try changing the value of the variable: REPO_SYNC_THREADS in the script to something lower (more suitable to your internet bandwidth / performance), try 2 or 4 and build up from there. ie: REPO_SYNC_THREADS=2

I think the problem was on GIT .. confusing I think so
I would be waiting a message like (file doesnt exist or something like that)
anyway I still with compiling errors but now is quite different
I am using virtualbox (Xubuntu 17.10) on Mac OS 10.13.2 Mac Mini 2014 entry level
applying packages_services_Telephony to packages/services/Telephony
./apply.sh: line 24: cd: /home/ferran/android/slimrom7/packages/services/Telephony: No such file or directory
6/7. Initialise environment for Build <Y/n>? (automatically continues unprompted after 10 seconds): Y
prepare device specific code...
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-mips64/vendorsetup.sh
including device/generic/mini-emulator-mips/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/samsung/kminilte/vendorsetup.sh
build/envsetup.sh: line 1716: vendor/slim/build/envsetup.sh: No such file or directory
build/core/product_config.mk:250: *** _nic.PRODUCTS.[[device/samsung/kminilte/slim.mk]]: "vendor/slim/config/common_full_phone.mk" does not exist. Stop.
build/envsetup.sh: line 624: vendor/slim/build/tools/roomservice.py: No such file or directory
build/core/product_config.mk:250: *** _nic.PRODUCTS.[[device/samsung/kminilte/slim.mk]]: "vendor/slim/config/common_full_phone.mk" does not exist. Stop.
cat: /home/ferran/android/slimrom7/vendor/slim/build/envsetup.sh: No such file or directory
cat: /home/ferran/android/slimrom7/vendor/slim/build/envsetup.sh: No such file or directory
build/core/product_config.mk:250: *** _nic.PRODUCTS.[[device/samsung/kminilte/slim.mk]]: "vendor/slim/config/common_full_phone.mk" does not exist. Stop.
** Don't have a product spec for: 'slim_kminilte'
** Do you have the right repo manifest?
running croot...
mka clean/clobber needed...
./build_slimrom7_kminilte.sh: line 257: mka: command not found
7/7. Build rom (this segment can take hours) <Y/n>? (automatically continues unprompted after 10 seconds): Y
running mka bacon...
./build_slimrom7_kminilte.sh: line 273: mka: command not found
Click to expand...
Click to collapse

ko_taka said:
I think the problem was on GIT .. confusing I think so
I would be waiting a message like (file doesnt exist or something like that)
anyway I still with compiling errors but now is quite different
I am using virtualbox (Xubuntu 17.10) on Mac OS 10.13.2 Mac Mini 2014 entry level
Click to expand...
Click to collapse
Thanks for the feedback. At first glance it looks to me like your issue is less to do with the script and more to do with not having all the source locally. Seeing commands such as running ./apply.sh (puled down with the source) error reporting "file not found" is the smoking gun.
Right now I'd be tempted to say ensure you've successfully pulled the primary SlimRom7 source locally. It may be easier to do this outside of the script by running the following:
Code:
$ cd /home/ferran/android/slimrom7/
$ repo forall -vc "git reset --hard" --quiet
$ repo sync --jobs="2"
Keep an eye out of timeouts / 404 while it's syncing the repo's (the third of the three commands above). If you get errors just keep rerunning the "repo sync" command given above while in the correct directory until it completes without error. Once you have that done successfully, change the the build_scripts directory and re-run the script. If you see timeouts / 404 in the script output then you might have to manually run the "git clone" commands to see which one is causing the issue(s).

why does need that much space?
I was executing
$ repo forall -vc "git reset --hard" --quiet
$ repo sync --jobs="2"
Click to expand...
Click to collapse
I am getting the message "out of space"
80GB full of source code and even need more space??

ko_taka said:
why does need that much space?
I was executing
I am getting the message "out of space"
80GB full of source code and even need more space??
Click to expand...
Click to collapse
Use a disk usage analysis tool to find out whether earlier failed attempts pulled source down to multiple locations (when the script was failing).. I mentioned in an earlier post the size of the repo, look back 5 or 6 posts. Don't forget the bulk of the source will be contained in a hidden folder named /.repo/ check this folder doesn't exist outside of the build folder (/slimrom7/)...looking at earlier attempts I'd fist check your /build_scripts/ folder for the hidden .repo folder and if there delete it. Good luck