the dir and the files is alreadly ok ,but when i enter "lunch" on Terminal (ubuntu 12.04) ,i couldn't found the product i added.
please help me .....
HTML:
[email protected]:~/cm$ ./build/tools/device/mkvendor.sh jiayu h928 ~/cm/boot.img
Arguments: jiayu h928 /home/xuchonggao/cm/boot.img
Output will be in /home/xuchonggao/cm/device/jiayu/h928
gzip: ../boot.img-ramdisk.gz: not in gzip format
cpio: 归档非正常终止
Done!
Use the following command to set up your build environment:
lunch full_h928-eng
And use the follwowing command to build a recovery:
. build/tools/device/makerecoveries.sh full_h928-eng
[email protected]:~/cm$ lunch full_h928-eng
No such file: full_h928-eng
很明显，你的内核解包错误！
Related
This isn't the first time I've tried to build Cyanogenmod for my i9100 on Ubuntu 12.10; I've done it successfully a few times before. However recently, it has just refused to build.
Code:
lunch cm_i9100-userdebug && mka
gave a bunch of errors: http://pastebin.com/Mn3YLZDY.
Code:
brunch cm_i9100-userdebug
gives different errors: http://pastebin.com/xiv4ettD. Teamhacksung's build script also gives the exact same errors. I tried starting in a new directory from scratch, but I still get the same errors.
The parts that look suspicious to me are
Code:
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
/bin/bash: line 0: cd: external/apache-harmony//home/ari/android/system/external/apache-harmony: No such file or directory
(/home/ari/android/system/external/apache-harmony does exist) and
Code:
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
/bin/bash: line 0: cd: libcore//home/ari/android/system/libcore: No such file or directory
find: `src': No such file or directory
I think this could be related to a repo sync problem I had/have where it couldn't download anything properly with lots of
Code:
Connection reset by peer
errors, although I think it has now synced (df -h shows 15GB). I also ran
Code:
repo forall -c "git fsck && git gc"
which "repairs" each repository, and that didn't give any errors.
Can anyone help with getting this to build?
EDIT: I found a post on the Android Building mailing list that was similar, and the suggestion to run
Code:
export CDPATH=""
(previously, $CDPATH=".")
got CM to build much further than before. No idea how this works, but it does.
However there are now more errors later during the build, e.g.
Code:
make: *** No rule to make target `/media/build/android/out/system/target/product/i9100/obj/lib/libTVOut.so', needed by `/media/build/android/out/system/target/product/i9100/obj/EXECUTABLES/mediaserver_intermediates/LINKED/mediaserver'. Stop.
It seems to have built a .zip flashable file now:
Code:
Package complete: /media/build/android/out/system/target/product/i9100/cm-10.1-20130121-UNOFFICIAL-i9100.zip
md5: f9fe076a6f0dfe140329e94ce6aa1867
Creating kernel zip...
Bootimage found...
No instructions to create out/target/product/i9100/kernel-cm-10.1-20130121-i9100-signed.zip... skipping.
Elapsed: 47 min(s) 20 sec(s)
but it says it can't create a kernel zip?
i like my android for home use ,but as a IT maneger it will be nice to have linux on my prime as well. thar is any toturial that expline how to make my prime duel boot this 2 OS?
Overview
Follow this thread: Ubuntu | How-to install it on the Prime . NOTICE: developer-thread
Mainly there are 2 methods:
Flash-boot:
The thread starts with LilStevies work from Androidroot. There you have to flash the correspondent boot-kernel to start either android or linux. So far I don't know of an existing LilStevie rom with the kexec/kexecboot method (kexec: Linux as bootloader).
SDCard-existence-driven-init
Running linux with root_chooser_v1/2/3 form tux_mind which starts around thead-page 35 uses a modified init. Dualboot: with SDCard in slot -> linux | without SDCard in slot -> Android
See: Gentoo Wiki and hack-job if you are on Asus stock rom.
You can also use chroot method - but it's not dualboot.
I had method 1 running. But for me it is not working for daily useage. (reflashing s*c*s :angel
Now i will use the SDCard-existence-driven-init
I can't use the posted boot-blob because I'm not on the Asus stock kernel so Android starts but many processes crash so that it is not useable. I use the Energy-Rom with the Clemsyn-kernel. (Prime is unlocked, nvflash-activated and rooted)
Be warned: You could damage/ brick your device following the instructions. Backup all!! A whole nvflash backup is reccomended. Be carful. Use your brain. I'm not responsible for any damages.
Up to now I tested my own 'unchanged' fastboot boot-blob:
Enter APX-Mode: put in USB cable + hold [Vol up]+[Power] (until vibrating, screen stays black)
Code:
$ sudo wheelie -r --blob blob.bin
$ sudo nvflash -r --read 6 blobNv.LNX
$ sudo nvflash -r --go
Unpack blob:
Code:
$ abootimg -x blobNv.LNX
repack blob (be sure you have blobpack for TF201 i.e. from CM10 repo):
Code:
$ abootimg --create testNv.LNX -k zImage -r initrd.gz -f bootimg.cfg
$ blobpackTF201 testFb.blob LNX testNv.LNX
start into fastboot-mode: put in USB cable [Vol down]+[Power] (until you can choose fastboot/USB symbol)
Code:
$ fastboot -i 0x0b05 flash boot testFb.blob
$ fastboot -i 0x0b05 reboot
The blob flashes well - I can see the blue progerss-bar. By the way: this produces a backup blob of the bootpartition which you can reflash via fastboot to start android if sth went wrong.
Now I need to insert the root_chooser init into the ramdisk to get linux from SDCard started...
I got a half working root_chooser. It starts android but not linux.
Here is what I did to modify the boot-loader with Clemsyn kernel and the modified init from tux_mind:
At first I read the LNX patition from the TF201 (unlocked, nvflash-able/wheelie, rooted):
Boot into APX-mode:
Code:
$ sudo bin/wheelie -r --blob bin/blob.bin
$ sudo bin/nvflash -r --read 6 blobNv.LNX
$ sudo bin/nvflash -r --go
Unpack the blob:
Code:
$ abootimg -x blobNv.LNX
You will get bootimg.cfg, initrd.img and zImage.
Now unpack the initial ramdisk:
Code:
$ mkdir ramdisk
$ cd ramdisk
$ gzip -dc ../initrd.img | cpio -i
Clone tux_minds data and copy your extracted custom rom ramdisk to newroot:
Code:
$ cd ..
$ git clone https://github.com/tux-mind/tf201-dev.git
$ rm -r tf201-dev/initramfs/newroot/*
$ cp -r ramdisk/* tf201-dev/initramfs/newroot/
[I][SIZE="2"]#edit 22 feb 2013[/SIZE][/I]
$ cd tf201-dev/initramfs
$ mkdir data && mkdir dev && mkdir sys
$ cd ../../..
[I][SIZE="2"]#edit end[/SIZE][/I]
OPTIONAL start compile root_chooser/init via crosscompile
Change the compiler in Makefile. I use Ubuntu with arm-linux-gnueabi-gcc (maybe it would be better to use arm-linux-gnueabihf-gcc) from the repo for crosscompiling:
Edit Makefile in tf201-dev/root_chooser:
Code:
#--Head-------------------- snip
CC=arm-linux-gnueabi-gcc
LD=arm-linux-gnueabi-ld
#CC=arm-unknown-linux-gnueabi-gcc
#LD=arm-unknown-linux-gnueabi-ld
#-------------------------- snap
Now compile and copy it to the initramfs:
Code:
$ make v2
$ cp root_chooser ../initramfs/init
OPTIONAL end
Now pack the initrd, make a blob and flash it to the TP
Code:
$ cd tf201-dev/initramfs
$ find . | cpio --create --format='newc' > ../../myinitrd
$ cd ../..
$ gzip myinitrd
$ chmod 777 myinitrd.gz
$ abootimg --create testNv.LNX -k zImage -r myinitrd.gz
$ bin/blobpackTF201 testFb.blob LNX testNv.LNX
Start into fastbootmode:
Code:
$ fastboot -i 0x0b05 flash boot testFb.blob
$ fastboot -i 0x0b05 reboot
Start into andorid open Terminal Emulator and type:
Code:
$ su
# vi /data/.boot
/dev/mmcblk1p1:/:/sbin/init
[esc] :wq
I followed this guide to set up my sdCard. That's it. Insert sdCard, reboot.
Android starts but not Linux from the sdCard. I got the following message back in android:
Code:
[I][B]FIXED[/B][SIZE="2"] see edit 22 feb 2013[/SIZE][/I]
[COLOR="Silver"]$ cat /boot_chooser.log
unable to mount /sys - No such file or directory[/COLOR]
New error message (inserted sdCard occurs boot-loops, remove sdCard to start android):
Code:
$ cat /boot_chooser.log
unable to mount /dev/mmcblk1p1 on /newroot - No such file or directory
I'm feeling so close to fire up Linux on my Transformer. Who can give me hint?
gophix said:
New error message (inserted sdCard occurs boot-loops, remove sdCard to start android):
Code:
$ cat /boot_chooser.log
unable to mount /dev/mmcblk1p1 on /newroot - No such file or directory
Click to expand...
Click to collapse
got it yeah! linux and android starting up! BUT VERY INSTABILE !!!
I had to use another sdCard and recompiled the kernel with some flags activated:
My hama 16GB class 10 doesn't seem to work well with the TP. I copied some data to the sdcard in android, there the I/O stream had several stops while copying data. Some forum members reported I/O errors in the system log (dmesg). I didn't have that errors but a variing throughput while copyint to sdCard.
The kernel I prepared this way:
Code:
downloading Clemsyn-kernel source:
$ wget https://www.dropbox.com/s/pjqd2b1edn6fiwu/tfcombofinal.zip
$ unzip tfcombofinal.zip
Get the actual kernel .config form the TP via adb and compile the kernel (I didn't patch, because I got error while compiling the kernel). I diffed my config to tux_minds and aktivated some flags.
Code:
$ adb pull /proc/config.gz
$ gzip -d config.gz
$ cp config tfcombofinal/.config
$ cd tfcombofinal
// patching should be like this:
// $ wget https://github.com/tux-mind/tf201-dev/raw/master/v2/kernel/JB15.patch
// $ patch -p1 < ../JB15.patch(v1/v2?) !!! do not patch !!!
$ make menuconfig
$ make -j4 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
I didn't compile the modules.
After that I packed my kernel from tfcombo/arch/arm/boot/zImage into the blob ($ abootimg --create testNv.LNX -k zImage -r myinitrd.gz)
VERY INSTABILE !!! means: the linux starting kernel was compiled with hardfloat (arm-linux-gnueabihf-).Linux starts up and responds "a littel bit"; android starts up; work 5 mins and reboots.
So both are working the developer way
I will test an own armSF kernel next time (the way described in this post, up to now I run instable on armHF) and report if this makes android stable and additionally starts up linux.
The dual-boot works fine.
Look at lifeinarootshell.
The actual version root_chooser v6 starts linux (from SDcard, microSDcard, USB, loop-device, internal folder) and android with different kernels
It has a cofigurable bootloader via kexec.
Linux distributions (gentoo, ubuntu, arch linux, ...) are also available and are growing more and more in stability and performance.
gophix said:
The dual-boot works fine.
Look at lifeinarootshell.
The actual version root_chooser v6 starts linux (from SDcard, microSDcard, USB, loop-device, internal folder) and android with different kernels
It has a cofigurable bootloader via kexec.
Linux distributions (gentoo, ubuntu, arch linux, ...) are also available and are growing more and more in stability and performance.
Click to expand...
Click to collapse
Getting xorg to work on archlinux is somewhat messy at the moment. The tegra3 driver is built for an old xorg-server, and is not compatible with the new one in the archlinux repositories. I was able to make it work by recompiling xorg-server, though. I guess it would be easier if someone made an aur package with the old xorg-server.
Thank you very much gophix for your nice guide in the second post :fingers-crossed:
However, since the first attempts to get linux based distributions working on the TF201 like ubuntu or arch linux, there was not much progress anymore I feel this is somehow pitty due to the fact that the Prime is still a good and reasonable tablet. And it could be much more if there would be not these horrible restrictions set by Asus like encrypted bootloader.
But I don't want to criticise mainly in my post. Instead, I would like to promote a constructive discussion so that the TF201 receives new life
How about creating a new ubuntu image based on 14.04 since it receives long term support? Unfortunately, my knowledge is still rather limitted so far to do this by myself.
And what is your opinion, to go alternatively another way by using the xubuntu installation (13.04) developed for the TF300tg as shown here:
http://forum.xda-developers.com/showthread.php?t=2190847
As far as I know, both devices are quite similar. Or are there any good arguments to deny this idea?
I'm tired of asking the same question again and again but for the thousandth and the last time I'll try my best to explain y'all the jeopardy I'm in.
I'm trying to build cm-10.2 from source for Sony Xperia E (nanhu) and everything started off just fine until I had to generate the skeleton files. I decided to use the mkvendor.sh to generate em. I have no clue why, but Sony seems to be in love with .elf files. And the best part, mkvendor only works with a standard boot.img file. Since I found mkvendor.sh the only convincing option, I decided to not use the other 2 options given here.
I extracted the kernel.sin from the ftf package of the kernel I downloaded, used flashtool to in turn extract kernel.sin which produced kernel.elf. I tried two things:
1) Unpack kernel.elf (flashtool elf extractor) and then pack em into a boot.img file (Failed as I couldn't pack em because I didn;t know how to use mkbootimg)
2) Rename kernel.elf to boot.img. as suggested by a developer of CM11 for Xperia E (Worked and was also accepted by mkvendor.sh)
I used mkvendor and it said that i don't have unpackbootimg binaries. I tried to make them by using:
make -j4 out/host/linux-x86/bin/unpackbootimg
Sadly I didn't know how to proceed so I got the binary from here and copied it to /usr/bin/ and made executable using:
sudo chmod a+x /usr/bin/unpackbootimg
Rebooted and it worked but you will see below that it isn't fixed 100% but it just works. I moved on and decided to use the script again on the renamed kernel.elf file(i.e. boot.img)
This is the following error I encounter while using mkvendor:
[email protected]:~/tools/FlashTool$ cd ~/source/cm/branch/cm-10.2
[email protected]:~/source/cm/branch/cm-10.2$ ./build/tools/device/mkvendor.sh sony nanhu ~/Desktop/boot.img
Arguments: sony nanhu /home/carbogen-chemist/Desktop/boot.img
Output will be in /home/carbogen-chemist/source/cm/branch/cm-10.2/device/sony/nanhu
*** Error in `unpackbootimg': free(): invalid next size (fast): 0x09793170 ***
./build/tools/device/mkvendor.sh: line 84: 3943 Aborted (core dumped) unpackbootimg -i $BOOTIMAGEFILE > /dev/null
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cp: cannot stat ‘/tmp/carbogen-chemist/bootimg/boot.img-zImage’: No such file or directory
Creating initial git repository.
~/source/cm/branch/cm-10.2/device/sony/nanhu ~/source/cm/branch/cm-10.2
Initialized empty Git repository in /home/carbogen-chemist/source/cm/branch/cm-10.2/device/sony/nanhu/.git/
[master (root-commit) d49b660] mkvendor.sh: Initial commit of nanhu
7 files changed, 95 insertions(+)
create mode 100644 AndroidBoard.mk
create mode 100644 AndroidProducts.mk
create mode 100644 BoardConfig.mk
create mode 100644 cm.mk
create mode 100644 device_nanhu.mk
create mode 100644 recovery.fstab
create mode 100644 system.prop
~/source/cm/branch/cm-10.2
Done!
Use the following command to set up your build environment:
lunch cm_nanhu-eng
And use the follwowing command to build a recovery:
. build/tools/device/makerecoveries.sh cm_nanhu-eng
Since the script seems to look up for boot.img-ramdisk.gz and boot.img-zImage, I decided to investigate a bit further. I renamed boot.img to kernel.elf and used flashtool elf extractor to unzip kernel.elf. I obtained four files as a result of the extraction:
1) kernel.elf.bootcmd
2) kernel.elf.cert
3) kernel.elf.Image
4) kernel.elf.ramdisk.gz
Since mkvendor needed boot.img-ramdisk.gz and boot.img-zImage, I renamed all the files:
1) kernel.elf.bootcmd >> kernel.img-bootcmd
2) kernel.elf.cert >> kernel.img-cert
3) kernel.elf.Image >> kernel.img-zImage
4) kernel.elf.ramdisk.gz >> kernel.img-ramdisk.gz
Now I repackaged them using mkelf.py script. Since I couldn't find any command specific to nanhu, I edited it to fit for the device:
python mkelf.py -o edited.elf [email protected] [email protected],ramdisk [email protected],cmdline
This command throws no error and produces edited.elf. All of the files are packed in except kernel.img-cert as I didn't know the arguments for it ([email protected]?x????????,cert). I rename the edited.elf to boot2.img.
But I get the same error as the one I get when I use the unedited kernel (boot.img)
What should I do to get out of this format abyss? Would I have better luck with mkbootimg? If so, could you point me out to a thread or tell me here itself how to use it?
Thank you all!
TheUltimateNoobist said:
I used mkvendor and it said that i don't have unpackbootimg binaries. I tried to make them by using:
make -j4 out/host/linux-x86/bin/unpackbootimg
Sadly I didn't know how to proceed so I got the binary from here and copied it to /usr/bin/ and made executable using:
sudo chmod a+x /usr/bin/unpackbootimg
Rebooted and it worked but you will see below that it isn't fixed 100% but it just works. I moved on and decided to use the script again on the renamed kernel.elf file(i.e. boot.img)
Click to expand...
Click to collapse
Fixed it myself. How did I miss that note at cyanogenmod porting?
Cd'ed to my working directory. Ran :
sudo make -j4 otatools
and grabbed unpackbootimg from WORKING_DIR/out/host/linux-x86/bin/unpackbootimg and pasted to /usr/bin
Made it executable by running:
sudo chmod a+x /usr/bin/unpackbootimg
Reboot!
It would also be very helpful if anyone could point out what the correct config for Xperia E is. (For EG >> blue_mint_defconfig is for Xperia T, semc_zeus_defconfig is for Xperia Play)
There is a file called README_Xperia, which contains the configuration names for the different phones in the kernel source can be used for. But my source doesn't contain it. So I would be very grateful if someone pointed it out!
Thank you!
TheUltimateNoobist said:
I'm tired of asking the same question again and again but for the thousandth and the last time I'll try my best to explain y'all the jeopardy I'm in.
I'm trying to build cm-10.2 from source for Sony Xperia E (nanhu) and everything started off just fine until I had to generate the skeleton files. I decided to use the mkvendor.sh to generate em. I have no clue why, but Sony seems to be in love with .elf files. And the best part, mkvendor only works with a standard boot.img file. Since I found mkvendor.sh the only convincing option, I decided to not use the other 2 options given here.
I extracted the kernel.sin from the ftf package of the kernel I downloaded, used flashtool to in turn extract kernel.sin which produced kernel.elf. I tried two things:
1) Unpack kernel.elf (flashtool elf extractor) and then pack em into a boot.img file (Failed as I couldn't pack em because I didn;t know how to use mkbootimg)
2) Rename kernel.elf to boot.img. as suggested by a developer of CM11 for Xperia E (Worked and was also accepted by mkvendor.sh)
I used mkvendor and it said that i don't have unpackbootimg binaries. I tried to make them by using:
make -j4 out/host/linux-x86/bin/unpackbootimg
Sadly I didn't know how to proceed so I got the binary from here and copied it to /usr/bin/ and made executable using:
sudo chmod a+x /usr/bin/unpackbootimg
Rebooted and it worked but you will see below that it isn't fixed 100% but it just works. I moved on and decided to use the script again on the renamed kernel.elf file(i.e. boot.img)
This is the following error I encounter while using mkvendor:
[email protected]:~/tools/FlashTool$ cd ~/source/cm/branch/cm-10.2
[email protected]:~/source/cm/branch/cm-10.2$ ./build/tools/device/mkvendor.sh sony nanhu ~/Desktop/boot.img
Arguments: sony nanhu /home/carbogen-chemist/Desktop/boot.img
Output will be in /home/carbogen-chemist/source/cm/branch/cm-10.2/device/sony/nanhu
*** Error in `unpackbootimg': free(): invalid next size (fast): 0x09793170 ***
./build/tools/device/mkvendor.sh: line 84: 3943 Aborted (core dumped) unpackbootimg -i $BOOTIMAGEFILE > /dev/null
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cp: cannot stat ‘/tmp/carbogen-chemist/bootimg/boot.img-zImage’: No such file or directory
Creating initial git repository.
~/source/cm/branch/cm-10.2/device/sony/nanhu ~/source/cm/branch/cm-10.2
Initialized empty Git repository in /home/carbogen-chemist/source/cm/branch/cm-10.2/device/sony/nanhu/.git/
[master (root-commit) d49b660] mkvendor.sh: Initial commit of nanhu
7 files changed, 95 insertions(+)
create mode 100644 AndroidBoard.mk
create mode 100644 AndroidProducts.mk
create mode 100644 BoardConfig.mk
create mode 100644 cm.mk
create mode 100644 device_nanhu.mk
create mode 100644 recovery.fstab
create mode 100644 system.prop
~/source/cm/branch/cm-10.2
Done!
Use the following command to set up your build environment:
lunch cm_nanhu-eng
And use the follwowing command to build a recovery:
. build/tools/device/makerecoveries.sh cm_nanhu-eng
Since the script seems to look up for boot.img-ramdisk.gz and boot.img-zImage, I decided to investigate a bit further. I renamed boot.img to kernel.elf and used flashtool elf extractor to unzip kernel.elf. I obtained four files as a result of the extraction:
1) kernel.elf.bootcmd
2) kernel.elf.cert
3) kernel.elf.Image
4) kernel.elf.ramdisk.gz
Since mkvendor needed boot.img-ramdisk.gz and boot.img-zImage, I renamed all the files:
1) kernel.elf.bootcmd >> kernel.img-bootcmd
2) kernel.elf.cert >> kernel.img-cert
3) kernel.elf.Image >> kernel.img-zImage
4) kernel.elf.ramdisk.gz >> kernel.img-ramdisk.gz
Now I repackaged them using mkelf.py script. Since I couldn't find any command specific to nanhu, I edited it to fit for the device:
python mkelf.py -o edited.elf [email protected] [email protected],ramdisk [email protected],cmdline
This command throws no error and produces edited.elf. All of the files are packed in except kernel.img-cert as I didn't know the arguments for it ([email protected]?x????????,cert). I rename the edited.elf to boot2.img.
But I get the same error as the one I get when I use the unedited kernel (boot.img)
What should I do to get out of this format abyss? Would I have better luck with mkbootimg? If so, could you point me out to a thread or tell me here itself how to use it?
Thank you all!
Click to expand...
Click to collapse
Nevermind :/ Fixed it myself.
Repacked the edited files using mkbootimg.
mkbootimg --kernel kernel.img-zImage --ramdisk kernel.img-ramdisk.gz --cmdline kernel.img-bootcmd -o boot.img
Hi guys i have a question, i want to get my device tree with the mkvendor.sh on the cyanogenmod source build/tools/device folder, y run this line using the previusly boot.img extracted:
./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img
But the problem is that that some files are missing, i got this:
Code:
Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
My boot.img is from a dell venue 8 3830, its from a android 4.4 stock image from here: http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2
Anyone can help and explain me please?
Thanks
Hi, im starting to learn to port roms following cyanogenmod guide but now i have this problem trying to generate the device tree of the dell venue 8 3830, i hope anyone can help me.
I run this:
Code:
./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img
And i got this:
Code:
Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
quevon24 said:
Hi, im starting to learn to port roms following cyanogenmod guide but now i have this problem trying to generate the device tree of the dell venue 8 3830, i hope anyone can help me.
I run this:
Code:
./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img
And i got this:
Code:
Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
Click to expand...
Click to collapse
Intel's provided their own custom boot image, thus default Google's unpack tool has no effect on it. Luckily, there are many dev shared their tool to unpack/repack it, i.e @shakalaca, or @social-design-concepts of your dell. You should find those repo, and download or build by yourself follow their guide, then place compiled tool to your path. After that, You can change at line 20 as below
Before:
Code:
UNPACKBOOTIMG=$(which unpackbootimg)
After modified:
Code:
UNPACKBOOTIMG=$(which unpack_intel)
P/s: unpack_intel here is just an example,only. In facts, it's maybe has different, depending its name on makefile. Good luck:laugh:
How to get the mkvendor.sh ?
quevon24 said:
Hi, im starting to learn to port roms following cyanogenmod guide but now i have this problem trying to generate the device tree of the dell venue 8 3830, i hope anyone can help me.
I run this:
Code:
./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img
And i got this:
Code:
Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
Click to expand...
Click to collapse
Hey can you please help me? I am trying to build device tree. I have done all the previous steps. But theres no mkvendor.sh file in my cm14.1 repo. Please help.
bnayagrawal said:
Hey can you please help me? I am trying to build device tree. I have done all the previous steps. But theres no mkvendor.sh file in my cm14.1 repo. Please help.
Click to expand...
Click to collapse
I didn't keep trying, but if you are trying for the same device, you can't use cm 14.1, but I think you need to use cm 12, there's no any development for other android versions.