I would need help with this http://forum.xda-developers.com/showthread.php?t=1866675
When i am trying to run dualboot-rom-convert script there comes this error
[email protected]:~$ /home/juho/Lataukset/dualboot-rom-convert/convert.sh cm.zip
Dualboot Rom Converter
Converts GT-P31xx Roms
to run from external
SD card and dualboot.
mkdir: cannot create directory `tmp/': File exists
cp: cannot stat `cm.zip': No such file or directory
Extracting boot image...
unzip: cannot find or open tmp/cm.zip-dualboot.zip, tmp/cm.zip-dualboot.zip.zip or tmp/cm.zip-dualboot.zip.ZIP.
mkdir: cannot create directory `tmp/unpack': File exists
Unpacking boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 13: ./unpackbootimg: No such file or directory
mkdir: cannot create directory `tmp/unpack/ramdisk': File exists
cpio: premature end of archive
Modifiying boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 18: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 19: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 20: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 21: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
Repacking boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 24: ./mkbootfs: No such file or directory
cat: tmp/unpack/boot.img-base: No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 25: ./mkbootimg: No such file or directory
cp: cannot stat `tmp/boot.img': No such file or directory
cp: cannot stat `patches/system/': No such file or directory
zip warning: name not matched: tmp/boot.img
zip error: Nothing to do! (tmp/cm.zip-dualboot.zip)
zip warning: name not matched: system/
zip error: Nothing to do! (try: zip -r cm.zip-dualboot.zip . -i system/)
Modifiying updater-script
unzip: cannot find or open tmp/cm.zip-dualboot.zip, tmp/cm.zip-dualboot.zip.zip or tmp/cm.zip-dualboot.zip.ZIP.
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 35: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 36: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 37: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
Repacking updater-script...
mkdir: cannot create directory `tmp/META-INF': File exists
mkdir: cannot create directory `tmp/META-INF/com': File exists
mkdir: cannot create directory `tmp/META-INF/com/google': File exists
mkdir: cannot create directory `tmp/META-INF/com/google/android': File exists
mv: cannot stat `tmp/updater-script': No such file or directory
zip warning: name not matched: META-INF/com/google/android/updater-script
zip error: Nothing to do! (cm.zip-dualboot.zip)
cp: cannot stat `tmp/cm.zip-dualboot.zip': No such file or directory
Complete!
I have given executable permissions to: unpackbootimg,, mkbootfs, and whatever the last one is (I forgot the last file name).
Did you try running the script ad root?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Did you try running the script ad root?
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Yes, I tried
It looks like the script can't find the file. Try putting a "./' before "cm.zip".
Posted from my Galaxy Tab 2 with CM10.1
i did super cid using supercid.sh file in mac to my HTC one XL/at&t
and i got this error
please help me..
mkdir: tmp: File exists
./supercid.sh: line 43: ./adb: cannot execute binary file
./supercid.sh: line 44: ./adb: cannot execute binary file
Copying your misc partition to your sdcard partition...
./supercid.sh: line 47: ./adb: cannot execute binary file
Making a backup copy of the file, just in case...
./supercid.sh: line 50: ./adb: cannot execute binary file
Copying the file to your computer so we can work with it...
./supercid.sh: line 53: ./adb: cannot execute binary file
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Converting the image file to text...
xxd: tmp/mmcblk0p4: No such file or directory
Checking to see what your CID is now...
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
grep: tmp/mmcblk0p4.txt: No such file or directory
We don't recognize your current CID.
You need to provide more information. What are your bootloader details? Are you perm rooted? What tutorial were you following? What commands came before the text you have posted here? What do you mean by you've lost the file?
PS. You've posted this in the General Section, I'll ask for it to be moved to the Q&A Section for you.
Sent from my Evita
Today I've tried both Philz 6.58.7 and TWRM 2.8.5.0 (latest for both) and both failed to backup my /data partition.
Errors like this one (TWRM):
E:Error adding file '/data/property/persist.atvc.allow_res_core' to '/data/media/0/TWRP/BACKUPS/TA8900FK5I/2015-03-14--21-59-55 LXB22.46-28.1//data.f2fs.win001'
I:ERROR tarList for thread ID 0
E:Error creating backup.
Does anyone know a working custom recovery (version) that can backup /data alright?
Oh and a bonus question: I can't get the (partial failed) backups to show up in Root Explorer when I navigate to the backup dirs. I guess it's related to the Lollipop security, but is there a way to access it alright?
I'd like to backup my backups to my laptop..
restorecon -vR /data/media
sub77 said:
restorecon -vR /data/media
Click to expand...
Click to collapse
I get these errors on the problematic files:
Code:
/data/dalvik-cache # restorecon -vR *
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: /data/dalvik-cache/[email protected]@[email protected]: No such file or directory
restorecon: error while labeling /data/dalvik-cache
/data/property # restorecon -vR *
restorecon -vR *
restorecon: stat(persist.atvc.allow_all_core): No such file or directory
restorecon: stat(persist.atvc.allow_res_core): No such file or directory
restorecon: stat(persist.radio.adb_log_on): No such file or directory
Any more ideas?
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
3. Extracting boot.img from your device
What we need
1. A rooted phone
2. Enable Usb Debugging in Developer Mode
3. ADB command knowldge
connect your phone via usb cable ensure that usb debugging is enabled
open terminal and type adb devices
if it is showing your device’s serial no than we are ready to go
C. type
adb shell
su
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
please note this command may vary by device to device. What we are doing here we want to know partition scheme of your device.
note down block name of /boot partition
example it will be like boot -> /dev/block/mmcblk0p7
d. type this
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
now boot.img succesfully transfered to your SD card Copy it to your Desktop
now path should be /home/user/Desktop/boot.img or similar but remeber path name alternatively you can type pwd in terminal to know this
creating device/Vendor-Name/Device-codename
cd to your working directory
Syntex: ./build/tools/device/mkvendor.sh Vendor-Name Device-CodeName ~/Path to your/boot.img
Example:
./build/tools/device/mkvendor.sh GIONEE GIONEE_WBL7511 ~/Desktop/boot.img
Now it will create following file in /device/Vender-Name/Device_CodeName
AndroidBoard.mk
cm.mk
recovery.fstab
AndroidProducts.mk
device_GIONEE_WBL7511.mk
system.prop
BoardConfig.mk
kernel
Note1: Please creater vendorsetup.mk file in this directory manualy. To use source build/envsetup.sh
Note2: Please double check BoardConfig.mk file and ensure every partition size is correct in this file. Also check recovery.fstab showing correct mount point
Note3: Here kernel is prebuilt kernel. If you want to compile kernel as well as download your kernel source in /kernel/Vender-Name/Device_CodeName dirtectory. You will find kernel related config in BoardConfig.mk
Please note it will not create vendorsetup.sh file and following Directory
1./vendor/Vender-Name/Device_CodeName
2. /kernel/Vender-Name/Device_CodeName
Wait for next post for more info
Thank You
Thank you very much for the tutorial I will try to do it
Enviado desde mi A7010a48 mediante Tapatalk
Also here http://azodik.com/how-to-create-device-tree-for-android-rom-building/
Are you ready with the post about creating the vendor tree?
thanks mate, but there's more than this, for example different flags for build for mtk device and different flags for qualcomm devices
Thank you for this great tut, but I have a noob error that I couldn't found "mkbootimg" and "unpackbootimg" in "/bootimg-tools-master" folder
But in "/bootimg-tools-master/mkbootimg" I found "bootimg.h, mkbootimg, mkbootimg.c, mkbootimg.o, unmkbootimg, unmkbootimg.c, unmkbootimg.o"
Also, I have read your note:
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
but I couldn't figure out what to do to check that
Additional info. : I am doing that to build a LineageOS Rom
Tree and API dependance
Amazing tutorial yet a small query - are the device (and vendor) trees android version dependant?
Could I use the boot.img of say Android 6.0 for building a 7.0 Nougat based ROM?
i am getting errors !
[/QUOTE][/QUOTE]
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
3. Extracting boot.img from your device
What we need
1. A rooted phone
2. Enable Usb Debugging in Developer Mode
3. ADB command knowldge
connect your phone via usb cable ensure that usb debugging is enabled
open terminal and type adb devices
if it is showing your device’s serial no than we are ready to go
C. type
adb shell
su
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
please note this command may vary by device to device. What we are doing here we want to know partition scheme of your device.
note down block name of /boot partition
example it will be like boot -> /dev/block/mmcblk0p7
d. type this
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
now boot.img succesfully transfered to your SD card Copy it to your Desktop
now path should be /home/user/Desktop/boot.img or similar but remeber path name alternatively you can type pwd in terminal to know this
creating device/Vendor-Name/Device-codename
cd to your working directory
Syntex: ./build/tools/device/mkvendor.sh Vendor-Name Device-CodeName ~/Path to your/boot.img
Example:
./build/tools/device/mkvendor.sh GIONEE GIONEE_WBL7511 ~/Desktop/boot.img
Now it will create following file in /device/Vender-Name/Device_CodeName
AndroidBoard.mk
cm.mk
recovery.fstab
AndroidProducts.mk
device_GIONEE_WBL7511.mk
system.prop
BoardConfig.mk
kernel
Note1: Please creater vendorsetup.mk file in this directory manualy. To use source build/envsetup.sh
Note2: Please double check BoardConfig.mk file and ensure every partition size is correct in this file. Also check recovery.fstab showing correct mount point
Note3: Here kernel is prebuilt kernel. If you want to compile kernel as well as download your kernel source in /kernel/Vender-Name/Device_CodeName dirtectory. You will find kernel related config in BoardConfig.mk
Please note it will not create vendorsetup.sh file and following Directory
1./vendor/Vender-Name/Device_CodeName
2. /kernel/Vender-Name/Device_CodeName
Wait for next post for more info
Thank You
Click to expand...
Click to collapse
Adityas-Mac-Pro:android aditya$ . build/tools/device/mkvendor.sh htc m8et /Users/aditya/Desktop/boot.img
Arguments: htc m8et /Users/aditya/Desktop/boot.img
dirname: illegal option -- b
usage: dirname path
dirname: illegal option -- b
usage: dirname path
-bash: pushd: no other directory
-bash: popd: directory stack empty
Output will be in //device/htc/m8et
mkdir: //device/htc/m8et: Permission denied
mkdir: /tmp/aditya/bootimg: Permission denied
cp: /tmp/aditya/bootimg: No such file or directory
-bash: pushd: /tmp/aditya/bootimg: No such file or directory
error: could not load image 'boot.img'
mkdir: ramdisk: File exists
gunzip: can't stat: ../boot.img-ramdisk.gz (../boot.img-ramdisk.gz.gz): No such file or directory
0 blocks
cat: /tmp/aditya/bootimg/boot.img-base: No such file or directory
cat: /tmp/aditya/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/aditya/bootimg/boot.img-pagesize: No such file or directory
-bash: /tmp/aditya/bootimg/sedcommand: No such file or directory
cp: /tmp/aditya/bootimg/boot.img-zImage: No such file or directory
-bash: popd: directory stack empty
find: /Volumes/android/.DocumentRevisions-V100: Permission denied
find: /Volumes/android/.TemporaryItems: Permission denied
find: /Volumes/android/.Trashes: Permission denied
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/AndroidManifest: No such file or directory
-bash: //device/htc/m8et/AndroidManifest.tests: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_tests_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/layout: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/strings: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/FrameworkDatabase: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build_rule: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/target: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/tools_def: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/click_events: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/stylus.prop: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/temp.arg: No such file or directory
cat: /Volumes/android/external/clang/test/CXX/temp/temp.arg/temp.arg.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/index.html: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/testResults.php: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/customTest.xml: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/testing.properties: No such file or directory
-bash: //device/htc/m8et/plugin.xml: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/Common.pl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build-local.properties: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
cat: /Volumes/android/external/icu/icu4j/eclipse-build/features.template: Is a directory
-bash: //device/htc/m8et/features: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/plugins: No such file or directory
cat: /Volumes/android/external/icu/icu4j/eclipse-build/plugins.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/Version.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
cat: /Volumes/android/external/libcxx/test/std/experimental/string.view/string.view.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
cat: /Volumes/android/external/libcxx/test/std/strings/string.view/string.view.template: Is a directory
-bash: //device/htc/m8et/NativeLibraries: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_event_cpp: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_event_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_eventhandler_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_eventhandlerfile_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/knobs: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/README: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/compile_commands.json: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverRS.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverView.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverRS.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/jmxremote.password: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/snmp.acl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/jmxremote.password: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/snmp.acl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
cat: /Volumes/android/prebuilts/ndk/r13/sources/cxx-stl/llvm-libc++/test/std/experimental/string.view/string.view.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/revision: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/AndroidManifest: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/activity: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/launcher_intent_filter: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/layout: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/preference_intent_filter: No such file or directory
-bash: //device/htc/m8et/string: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/strings: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/test_instrumentation: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/test_uses-library: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/uses-sdk: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/prefs: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build_gradle: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/uibuild: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/asan.options.off: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
mv: rename //device/htc/m8et/device.mk to //device/htc/m8et/device_m8et.mk: No such file or directory
Creating initial git repository.
-bash: pushd: //device/htc/m8et: No such file or directory
Reinitialized existing Git repository in /Volumes/android/.git/
Click to expand...
Click to collapse
I tried to search but cannot get anything I'm using mac os x 10.12.6
thumbs up
Scripts to extract device vendor files and generate AOSP makefiles.
https://github.com/pdsouza/android-generate-vendor
Set of scripts to automate AOSP compatible vendor blobs generation from factory images
https://github.com/anestisb/android-prepare-vendor
Will these scripts work on MTK devices?
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Click to expand...
Click to collapse
Did not get what you meant by host tools been built
Sparker0i said:
Did not get what you meant by host tools been built
Click to expand...
Click to collapse
Same question from me.
You are supposed to get two files in step two. I only got one - unpackbootimg is missing.
How to set up android build environment and install host tools? Is there a guide somewhere around?
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
Thank You
Click to expand...
Click to collapse
Is this thread dead or any hope of further guidance.
What fo you mean source code
does this work for MTK devices?
adityaparmar07 said:
i am getting errors !
Click to expand...
Click to collapse
[/QUOTE]
I tried to search but cannot get anything I'm using mac os x 10.12.6
[/QUOTE]
several years late, but you had a space between . and build instead of a /
FeyoMx said:
Thank you very much for the tutorial I will try to do it
Enviado desde mi A7010a48 mediante Tapatalk
Click to expand...
Click to collapse
what source are you talking about sir?
I keep getting this error when trying to install it and the error told me to post my error logs here
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
WARNING: linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
- Disabling OTA survival
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
/tmp/updater: line 1620: /tmp/supersu/arm/chattr: not found
- Removing old files
rm: /system/etc/install-recovery.sh: Too many symbolic links encountered
rm: /data/su.img: No such file or directory
rm: /cache/su.img: No such file or directory
- Creating space
- Placing files
mkdir: '/system/bin/.ext': No such file or directory
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext: No such file or directory
chmod: /system/bin/.ext: No such file or directory
rm: /system/bin/.ext/.su: No such file or directory
/tmp/updater: line 1620: can't create /system/bin/.ext/.su: nonexistent directory
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
rm: /system/xbin/su: No such file or directory
/tmp/updater: line 1620: can't create /system/xbin/su: nonexistent directory
chown: /system/xbin/su: No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
rm: /system/xbin/daemonsu: No such file or directory
/tmp/updater: line 1620: can't create /system/xbin/daemonsu: nonexistent directory
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chmod: /system/xbin/daemonsu: No such file or directory
rm: /system/app/Superuser.apk: No such file or directory
/tmp/updater: line 1620: can't create /system/app/Superuser.apk: nonexistent directory
chown: /system/app/Superuser.apk: No such file or directory
chown: /system/app/Superuser.apk: No such file or directory
chmod: /system/app/Superuser.apk: No such file or directory
rm: /system/etc/install-recovery.sh: Too many symbolic links encountered
/tmp/updater: line 1620: can't create /system/etc/install-recovery.sh: Too many symbolic links encountered
chown: /system/etc/install-recovery.sh: Too many symbolic links encountered
chown: /system/etc/install-recovery.sh: Too many symbolic links encountered
chmod: /system/etc/install-recovery.sh: Too many symbolic links encountered
rm: /system/etc/init.d/99SuperSUDaemon: Too many symbolic links encountered
/tmp/updater: line 1620: can't create /system/etc/init.d/99SuperSUDaemon: Too many symbolic links encountered
chown: /system/etc/init.d/99SuperSUDaemon: Too many symbolic links encountered
chown: /system/etc/init.d/99SuperSUDaemon: Too many symbolic links encountered
chmod: /system/etc/init.d/99SuperSUDaemon: Too many symbolic links encountered
/tmp/updater: line 1620: can't create /system/etc/.installed_su_daemon: Too many symbolic links encountered
chown: /system/etc/.installed_su_daemon: Too many symbolic links encountered
chown: /system/etc/.installed_su_daemon: Too many symbolic links encountered
chmod: /system/etc/.installed_su_daemon: Too many symbolic links encountered
- Restoring files
- Post-installation script
rm: /system/toybox: No such file or directory
rm: /system/toolbox: No such file or directory
/tmp/updater: line 1620: /system/xbin/su: not found
- Unmounting /system
- Done !
I:Updater process ended with RC=0
I:Install took 1 second(s).
Updating partition details...
Iata backup size is 1597MB, free: 23224MB.
...done
I:Set page: 'flash_done'
Iperation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing zip file '/sdcard/Download/VerifiedBootSigner-v3.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
********************************
* Android Verified Boot Signer *
* v3: (c) Chainfire 2017-05-07 *
********************************
mount: losetup failed 1
cat: /fstab.*: No such file or directory
System: /dev/block/bootdevice/by-name/system_b
Boot: /dev/block/bootdevice/by-name/boot_b
Abort: dalvikvm not found
umount: /system_root: Invalid argument
Something unexpected has happened. Please pull /tmp/recovery.log and post it to the thread on XDA
Updater process ended with ERROR: 1
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/VerifiedBootSigner-v3.zip'
Updating partition details...
Iata backup size is 1597MB, free: 23224MB.
...done
I:Set page: 'flash_done'
Iperation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
Iperation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
Click to expand...
Click to collapse