hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
anyone willing to help?
anyone? ???
kcisrael said:
hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
Click to expand...
Click to collapse
Found this on:
https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
---------- Post added at 10:37 PM ---------- Previous post was at 10:29 PM ----------
kcisrael said:
hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
Click to expand...
Click to collapse
Converting a ZIP ROM to a system.img
This is basically for Rockchip ROMs.
OK so first lets understand the difference.
system.img is nothing more than a image file that is formatted EXT4 and mounted in Linux.
You make the image file using DD and then format it EXT4 (or EXT3 for older devices).
Then you mount it in Linux and copy all your stuff into it.
Now this is EASY when you mount an existing system.img and copy it into a new system.img Why? Because that original system.img has all the symbolic links and permissions already set!
However, if you get a update that is a ZIP file this is not the case. Or if you get a CWM backup and untar it, you can loose the symlinks and permissions.
So one day I got a ROM that was only supplied as a zip. It used what is called a edify script to install it which that script copies all the files into system then does all the file permissions and setup up the needed symlinks.
The commands in the script do not map in Linux! Thus I had to convert them. Let me tell you this was somewhat a pain and special thanks to 900Supersport and Petrus for helping me understand and convert.
So here is how you do it.
First create a directory to unzip or un-tar all the files into. I called mine system_orig
Then this is my script to build a system.img The harder part is getting the IMG file size correct. You have to watch out making it too big as the parameter file defines how big system can be. If yours is bigger than what the parameter file allows, you will need to adjust the parameter file. I believe most parameter files today allow up to 500megs.
#create the system dir
mkdir system2
# create the system image using DD. Set size here:
dd if=/dev/zero of=system.img count=471000000
#format the image you just created. This is EXT4 but you can use anything the kernel allows as defined in init.rc
sudo /sbin/mkfs.ext4 -q system.img
#Now mount it in Linux
sudo mount -o loop system.img system2
# Now copy everything from your unzipped folder into the new image.
sudo cp -r system_orig/* system2
#OK lets create all the symbolic links
#make symlinks
sudo ln -s Roboto-Bold.ttf system2/fonts/DroidSans-Bold.ttf
sudo ln -s Roboto-Regular.ttf system2/fonts/DroidSans.ttf
sudo ln -s mksh system2/bin/sh
sudo ln -s toolbox system2/bin/cat
sudo ln -s toolbox system2/bin/chmod
sudo ln -s toolbox system2/bin/chown
sudo ln -s toolbox system2/bin/cmp
sudo ln -s toolbox system2/bin/date
sudo ln -s toolbox system2/bin/dd
sudo ln -s toolbox system2/bin/df
sudo ln -s toolbox system2/bin/dmesg
sudo ln -s toolbox system2/bin/getevent
sudo ln -s toolbox system2/bin/getprop
sudo ln -s toolbox system2/bin/hd
sudo ln -s toolbox system2/bin/id
sudo ln -s toolbox system2/bin/ifconfig
sudo ln -s toolbox system2/bin/iftop
sudo ln -s toolbox system2/bin/insmod
sudo ln -s toolbox system2/bin/ioctl
sudo ln -s toolbox system2/bin/ionice
sudo ln -s toolbox system2/bin/kill
sudo ln -s toolbox system2/bin/ln
sudo ln -s toolbox system2/bin/log
sudo ln -s toolbox system2/bin/ls
sudo ln -s toolbox system2/bin/lsmod
sudo ln -s toolbox system2/bin/lsof
sudo ln -s toolbox system2/bin/md5
sudo ln -s toolbox system2/bin/mkdir
sudo ln -s toolbox system2/bin/mount
sudo ln -s toolbox system2/bin/mv
sudo ln -s toolbox system2/bin/nandread
sudo ln -s toolbox system2/bin/netstat
sudo ln -s toolbox system2/bin/newfs_msdos
sudo ln -s toolbox system2/bin/notify
sudo ln -s toolbox system2/bin/printenv
sudo ln -s toolbox system2/bin/ps
sudo ln -s toolbox system2/bin/r
sudo ln -s toolbox system2/bin/reboot
sudo ln -s toolbox system2/bin/renice
sudo ln -s toolbox system2/bin/rm
sudo ln -s toolbox system2/bin/rmdir
sudo ln -s toolbox system2/bin/rmmod
sudo ln -s toolbox system2/bin/route
sudo ln -s toolbox system2/bin/schedtop
sudo ln -s toolbox system2/bin/sendevent
sudo ln -s toolbox system2/bin/setconsole
sudo ln -s toolbox system2/bin/setprop
sudo ln -s toolbox system2/bin/sleep
sudo ln -s toolbox system2/bin/smd
sudo ln -s toolbox system2/bin/start
sudo ln -s toolbox system2/bin/stop
sudo ln -s toolbox system2/bin/sync
sudo ln -s toolbox system2/bin/top
sudo ln -s toolbox system2/bin/touch
sudo ln -s toolbox system2/bin/umount
sudo ln -s toolbox system2/bin/uptime
sudo ln -s toolbox system2/bin/vmstat
sudo ln -s toolbox system2/bin/watchprops
sudo ln -s toolbox system2/bin/wipe
#OK now lets set all the permissions
sudo chown -R 0:0 system2
sudo chmod -R 0755 system2
sudo find system2 -type d -exec chmod 0755 {} \;
sudo find system2 -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/bin
sudo chmod 0755 system2/bin
sudo find system2/bin -type d -exec chmod 0755 {} \;
sudo find system2/bin -type f -exec chmod 0755 {} \;
sudo chown 0:3003 system2/bin/netcfg
sudo chmod 2750 system2/bin/netcfg
sudo chown 0:3004 system2/bin/ping
sudo chmod 2755 system2/bin/ping
sudo chown 0:2000 system2/bin/run-as
sudo chmod 6755 system2/bin/run-as
sudo chown -R 1002:1002 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo find system2/etc/bluetooth -type d -exec chmod 0755 {} \;
sudo find system2/etc/bluetooth -type f -exec chmod 0440 {} \;
sudo chown 0:0 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo chown 1000:1000 system2/etc/bluetooth/auto_pairing.conf
sudo chmod 0640 system2/etc/bluetooth/auto_pairing.conf
sudo chown 3002:3002 system2/etc/bluetooth/blacklist.conf
sudo chmod 0444 system2/etc/bluetooth/blacklist.conf
sudo chown 1002:1002 system2/etc/dbus.conf
sudo chmod 0440 system2/etc/dbus.conf
sudo chown 1014:2000 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chmod 0550 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chown 0:2000 system2/etc/init.goldfish.sh
sudo chmod 0550 system2/etc/init.goldfish.sh
sudo chown 0:0 system2/etc/install-recovery.sh
sudo chmod 0544 system2/etc/install-recovery.sh
sudo chown -R 0:0 system2/etc/ppp
sudo chmod -R 0755 system2/etc/ppp
sudo find system2/etc/ppp -type d -exec chmod 0755 {} \;
sudo find system2/etc/ppp -type f -exec chmod 0555 {} \;
sudo chown -R 0:2000 system2/vendor
sudo chmod -R 0755 system2/vendor
sudo find system2/vendor -type d -exec chmod 0755 {} \;
sudo find system2/vendor -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/xbin
sudo chmod -R 0755 system2/xbin
sudo find system2/xbin -type d -exec chmod 0755 {} \;
sudo find system2/xbin -type f -exec chmod 0755 {} \;
sudo chown 0:0 system2/xbin/librank
sudo chmod 06755 system2/xbin/librank
sudo chown 0:0 system2/xbin/procmem
sudo chmod 06755 system2/xbin/procmem
sudo chown 0:0 system2/xbin/procrank
sudo chmod 06755 system2/xbin/procrank
sudo chown 0:0 system2/xbin/tcpdump
sudo chmod 06755 system2/xbin/tcpdump
# Note I added this to ROOT the new ROM. I simply copied in SU and Superuser and busybox.
# However if you want stock remove this area.
# Also note, some only put busybox and SU in /bin or /xbin. I usually do both.
sudo chown 0:0 system2/bin/su
sudo chmod 06755 system2/bin/su
sudo chown 0:0 system2/xbin/su
sudo chmod 06755 system2/xbin/su
sudo chown 0:0 system2/bin/busybox
sudo chmod 6755 system2/bin/busybox
sudo chown 0:0 system2/xbin/busybox
sudo chmod 6755 system2/xbin/busybox
sudo chown 0:0 system2/app/Superuser.apk
sudo chmod 6755 system2/app/Superuser.apk
# OK now lets unmount system.img
sudo umount system2
# for clean up I usually delete system2 folder.
sudo rm -f -R system2
That should do it!
FYI, you do not RKCRC system.img.
Hope this helps
Help
azithro said:
Found this on:
https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
---------- Post added at 10:37 PM ---------- Previous post was at 10:29 PM ----------
Converting a ZIP ROM to a system.img
This is basically for Rockchip ROMs.
OK so first lets understand the difference.
system.img is nothing more than a image file that is formatted EXT4 and mounted in Linux.
You make the image file using DD and then format it EXT4 (or EXT3 for older devices).
Then you mount it in Linux and copy all your stuff into it.
Now this is EASY when you mount an existing system.img and copy it into a new system.img Why? Because that original system.img has all the symbolic links and permissions already set!
However, if you get a update that is a ZIP file this is not the case. Or if you get a CWM backup and untar it, you can loose the symlinks and permissions.
So one day I got a ROM that was only supplied as a zip. It used what is called a edify script to install it which that script copies all the files into system then does all the file permissions and setup up the needed symlinks.
The commands in the script do not map in Linux! Thus I had to convert them. Let me tell you this was somewhat a pain and special thanks to 900Supersport and Petrus for helping me understand and convert.
So here is how you do it.
First create a directory to unzip or un-tar all the files into. I called mine system_orig
Then this is my script to build a system.img The harder part is getting the IMG file size correct. You have to watch out making it too big as the parameter file defines how big system can be. If yours is bigger than what the parameter file allows, you will need to adjust the parameter file. I believe most parameter files today allow up to 500megs.
#create the system dir
mkdir system2
# create the system image using DD. Set size here:
dd if=/dev/zero of=system.img count=471000000
#format the image you just created. This is EXT4 but you can use anything the kernel allows as defined in init.rc
sudo /sbin/mkfs.ext4 -q system.img
#Now mount it in Linux
sudo mount -o loop system.img system2
# Now copy everything from your unzipped folder into the new image.
sudo cp -r system_orig/* system2
#OK lets create all the symbolic links
#make symlinks
sudo ln -s Roboto-Bold.ttf system2/fonts/DroidSans-Bold.ttf
sudo ln -s Roboto-Regular.ttf system2/fonts/DroidSans.ttf
sudo ln -s mksh system2/bin/sh
sudo ln -s toolbox system2/bin/cat
sudo ln -s toolbox system2/bin/chmod
sudo ln -s toolbox system2/bin/chown
sudo ln -s toolbox system2/bin/cmp
sudo ln -s toolbox system2/bin/date
sudo ln -s toolbox system2/bin/dd
sudo ln -s toolbox system2/bin/df
sudo ln -s toolbox system2/bin/dmesg
sudo ln -s toolbox system2/bin/getevent
sudo ln -s toolbox system2/bin/getprop
sudo ln -s toolbox system2/bin/hd
sudo ln -s toolbox system2/bin/id
sudo ln -s toolbox system2/bin/ifconfig
sudo ln -s toolbox system2/bin/iftop
sudo ln -s toolbox system2/bin/insmod
sudo ln -s toolbox system2/bin/ioctl
sudo ln -s toolbox system2/bin/ionice
sudo ln -s toolbox system2/bin/kill
sudo ln -s toolbox system2/bin/ln
sudo ln -s toolbox system2/bin/log
sudo ln -s toolbox system2/bin/ls
sudo ln -s toolbox system2/bin/lsmod
sudo ln -s toolbox system2/bin/lsof
sudo ln -s toolbox system2/bin/md5
sudo ln -s toolbox system2/bin/mkdir
sudo ln -s toolbox system2/bin/mount
sudo ln -s toolbox system2/bin/mv
sudo ln -s toolbox system2/bin/nandread
sudo ln -s toolbox system2/bin/netstat
sudo ln -s toolbox system2/bin/newfs_msdos
sudo ln -s toolbox system2/bin/notify
sudo ln -s toolbox system2/bin/printenv
sudo ln -s toolbox system2/bin/ps
sudo ln -s toolbox system2/bin/r
sudo ln -s toolbox system2/bin/reboot
sudo ln -s toolbox system2/bin/renice
sudo ln -s toolbox system2/bin/rm
sudo ln -s toolbox system2/bin/rmdir
sudo ln -s toolbox system2/bin/rmmod
sudo ln -s toolbox system2/bin/route
sudo ln -s toolbox system2/bin/schedtop
sudo ln -s toolbox system2/bin/sendevent
sudo ln -s toolbox system2/bin/setconsole
sudo ln -s toolbox system2/bin/setprop
sudo ln -s toolbox system2/bin/sleep
sudo ln -s toolbox system2/bin/smd
sudo ln -s toolbox system2/bin/start
sudo ln -s toolbox system2/bin/stop
sudo ln -s toolbox system2/bin/sync
sudo ln -s toolbox system2/bin/top
sudo ln -s toolbox system2/bin/touch
sudo ln -s toolbox system2/bin/umount
sudo ln -s toolbox system2/bin/uptime
sudo ln -s toolbox system2/bin/vmstat
sudo ln -s toolbox system2/bin/watchprops
sudo ln -s toolbox system2/bin/wipe
#OK now lets set all the permissions
sudo chown -R 0:0 system2
sudo chmod -R 0755 system2
sudo find system2 -type d -exec chmod 0755 {} \;
sudo find system2 -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/bin
sudo chmod 0755 system2/bin
sudo find system2/bin -type d -exec chmod 0755 {} \;
sudo find system2/bin -type f -exec chmod 0755 {} \;
sudo chown 0:3003 system2/bin/netcfg
sudo chmod 2750 system2/bin/netcfg
sudo chown 0:3004 system2/bin/ping
sudo chmod 2755 system2/bin/ping
sudo chown 0:2000 system2/bin/run-as
sudo chmod 6755 system2/bin/run-as
sudo chown -R 1002:1002 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo find system2/etc/bluetooth -type d -exec chmod 0755 {} \;
sudo find system2/etc/bluetooth -type f -exec chmod 0440 {} \;
sudo chown 0:0 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo chown 1000:1000 system2/etc/bluetooth/auto_pairing.conf
sudo chmod 0640 system2/etc/bluetooth/auto_pairing.conf
sudo chown 3002:3002 system2/etc/bluetooth/blacklist.conf
sudo chmod 0444 system2/etc/bluetooth/blacklist.conf
sudo chown 1002:1002 system2/etc/dbus.conf
sudo chmod 0440 system2/etc/dbus.conf
sudo chown 1014:2000 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chmod 0550 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chown 0:2000 system2/etc/init.goldfish.sh
sudo chmod 0550 system2/etc/init.goldfish.sh
sudo chown 0:0 system2/etc/install-recovery.sh
sudo chmod 0544 system2/etc/install-recovery.sh
sudo chown -R 0:0 system2/etc/ppp
sudo chmod -R 0755 system2/etc/ppp
sudo find system2/etc/ppp -type d -exec chmod 0755 {} \;
sudo find system2/etc/ppp -type f -exec chmod 0555 {} \;
sudo chown -R 0:2000 system2/vendor
sudo chmod -R 0755 system2/vendor
sudo find system2/vendor -type d -exec chmod 0755 {} \;
sudo find system2/vendor -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/xbin
sudo chmod -R 0755 system2/xbin
sudo find system2/xbin -type d -exec chmod 0755 {} \;
sudo find system2/xbin -type f -exec chmod 0755 {} \;
sudo chown 0:0 system2/xbin/librank
sudo chmod 06755 system2/xbin/librank
sudo chown 0:0 system2/xbin/procmem
sudo chmod 06755 system2/xbin/procmem
sudo chown 0:0 system2/xbin/procrank
sudo chmod 06755 system2/xbin/procrank
sudo chown 0:0 system2/xbin/tcpdump
sudo chmod 06755 system2/xbin/tcpdump
# Note I added this to ROOT the new ROM. I simply copied in SU and Superuser and busybox.
# However if you want stock remove this area.
# Also note, some only put busybox and SU in /bin or /xbin. I usually do both.
sudo chown 0:0 system2/bin/su
sudo chmod 06755 system2/bin/su
sudo chown 0:0 system2/xbin/su
sudo chmod 06755 system2/xbin/su
sudo chown 0:0 system2/bin/busybox
sudo chmod 6755 system2/bin/busybox
sudo chown 0:0 system2/xbin/busybox
sudo chmod 6755 system2/xbin/busybox
sudo chown 0:0 system2/app/Superuser.apk
sudo chmod 6755 system2/app/Superuser.apk
# OK now lets unmount system.img
sudo umount system2
# for clean up I usually delete system2 folder.
sudo rm -f -R system2
That should do it!
FYI, you do not RKCRC system.img.
Hope this helps
Click to expand...
Click to collapse
Can you help me with this ?
http://forum.xda-developers.com/showthread.php?p=46541879#post46541879
Related
Many ppl seem to want to reinstall mediascape..
well as far as i know you can't reinstall mediascape after rooting; however, it is possible to NOT DELETE mediascape in Step 4.
You follow the root guide in the stick up to step 3, then before you run step 4 (well i guess it's better to do it before you start rooting) open cleanup.sh in step 4 and remove mediascape and mediascapeplugin from the list... so it should look like this
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm -R /sdcard/apps
mkdir /sdcard/apps
cd /system/app
cp AndroidQuadrapop* /sdcard/apps
cp docomo_market* /sdcard/apps
cp EManual* /sdcard/apps
cp LatinIME* /sdcard/apps
cp LatinImeTutorial* /sdcard/apps
cp Launcher* /sdcard/apps
cp LearningClient* /sdcard/apps
cp MixiPlugin* /sdcard/apps
cp moxiermail* /sdcard/apps
cp officesuite* /sdcard/apps
cp pocket_rashinban* /sdcard/apps
cp SemcIME* /sdcard/apps
cp trackid* /sdcard/apps
rm AndroidQuadrapop*
rm docomo_market*
rm EManual*
rm LatinIME*
rm LatinImeTutorial*
rm Launcher*
rm LearningClient*
rm MixiPlugin*
rm moxiermail*
rm officesuite*
rm pocket_rashinban*
rm SemcIME*
rm trackid*
rm /data/app/*.zip
rm /data/app-private/jp.*
rm -r /etc/semc/startupshow
rm -r /etc/semc/preset/app
rm -r /etc/*.iso
then run step 4..
personally i don't know exactly what's changed on my phone other than the fact that i now have a zeam home launcher instead, titanium backup says my phone's been rooted, i didn't have to restore anything because everything (all data/apps i installed personally) were kept the same, mediascape still there, and i lost korean keyboard/option to switch to korean menu which came with the R2BA020 update...
oh and my step 3a wasn't working properly so i just skipped it.. but regardless i can type 'su' into better terminal, and titanium backup says my phone's rooted so i don't really care..
although if the devs could release another one with the korean keyboard/menu from the new R2BA020 update, it'd be great
oh and i went from x10a(rogers 014) -> x10i (R2BA020) -> root
Thanks Dude!!! This is just what I needed. No timescape?? What if I wanted timescape, is there a way to prevent it from removing that?
Fuzalert2k said:
Thanks Dude!!! This is just what I needed. No timescape?? What if I wanted timescape, is there a way to prevent it from removing that?
Click to expand...
Click to collapse
it doesn't remove timescape..
Retrying for the fourth time, I managed to root the phone, then I saw you could keep mediascape, and the original keyboard... tried opening and saving the sh file with notepad, wordpad, write... don't know if it modifies something but once we get to the uninstalling part I get 'No such files or directory'...
found the solution, do not edit shell file in windows with notepad,
http://sourceforge.net/projects/eme...-editor-2.72-r286/cedt-286-setup.exe/download
works pretty well on windows, so you can decide to keep whatever you want
mayamo said:
Many ppl seem to want to reinstall mediascape..
well as far as i know you can't reinstall mediascape after rooting; however, it is possible to NOT DELETE mediascape in Step 4.
You follow the root guide in the stick up to step 3, then before you run step 4 (well i guess it's better to do it before you start rooting) open cleanup.sh in step 4 and remove mediascape and mediascapeplugin from the list... so it should look like this
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm -R /sdcard/apps
mkdir /sdcard/apps
cd /system/app
cp AndroidQuadrapop* /sdcard/apps
cp docomo_market* /sdcard/apps
cp EManual* /sdcard/apps
cp LatinIME* /sdcard/apps
cp LatinImeTutorial* /sdcard/apps
cp Launcher* /sdcard/apps
cp LearningClient* /sdcard/apps
cp MixiPlugin* /sdcard/apps
cp moxiermail* /sdcard/apps
cp officesuite* /sdcard/apps
cp pocket_rashinban* /sdcard/apps
cp SemcIME* /sdcard/apps
cp trackid* /sdcard/apps
rm AndroidQuadrapop*
rm docomo_market*
rm EManual*
rm LatinIME*
rm LatinImeTutorial*
rm Launcher*
rm LearningClient*
rm MixiPlugin*
rm moxiermail*
rm officesuite*
rm pocket_rashinban*
rm SemcIME*
rm trackid*
rm /data/app/*.zip
rm /data/app-private/jp.*
rm -r /etc/semc/startupshow
rm -r /etc/semc/preset/app
rm -r /etc/*.iso
then run step 4..
oh and i went from x10a(rogers 014) -> x10i (R2BA020) -> root
Click to expand...
Click to collapse
So what i understand is that If I want to keep the Default home then I should be removing the Launcher from the list as well. Also is Backup and Restore Included which is there in new firmware.... as I do not want to go for limited backup tool.
hotfile.com/dl/51161486/a67bb41/step4.zip.html
Click to expand...
Click to collapse
moded
step4 with mediaspace
How to manually root. Download and unzip the SuperOneClick zip file and...
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
shawnbuck said:
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Click to expand...
Click to collapse
Could you? I have this same problem trying to root on my mac.
Sent from my MB860 using XDA App
I basically have this:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v1 /sdcard/
./adbmac push su-v2 /sdcard/
./adbmac push busybox /sdcard/
./adbmac push Superuser.apk /sdcard/
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
./adbmac remount
./adbmac shell
(the following 3 steps may fail which is OK)
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# mv /system/xbin/busybox /system/xbin/busybox.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
(try to execute both su-v*, whichever works keep and renamed to su. For this example we'll assume su-v2 is the correct su)
# rm /system/xbin/su-v1
# mv /system/xbin/su-v2 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox cp /sdcard/busybox /system/xbin
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# busybox ln -s /system/xbin/su /system/bin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
In this steps you put up previously, you missed remount the /system partition rw.
Also, what OS & software are you guys using? I'm curious to find out what is causing this problem, so we can correct it in SuperOneClick.
Ubuntu 10.10 x64
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# mount -o remount,rw -t yaffs2 /system
Click to expand...
Click to collapse
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# busybox mv /data/local/tmp/su /system/xbin
Click to expand...
Click to collapse
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
gdanko said:
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Whoops, that slipped by. In any case, you can check what /system is mounted on by checking /etc/mtab.
Still getting permission denied when I type su
How are you using su directly?
Also, have you installed superuser and root checker from the market?
Add these steps to the end:
# chmod 06755 /system/xbin/su
# chmod 0755 /system/xbin/busybox
# reboot
When the phone is up, adb shell back in
Unlock the phone
Type su in the console
Accept the Superuser prompt
I am now rooted
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
I've noticed that the phone doesn't like when you call reboot from the terminal on it.
Also, put the instructions in the first post for anyone in the future.
gdanko said:
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
Click to expand...
Click to collapse
Perfect, thanks!
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
agentdr8 said:
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
Click to expand...
Click to collapse
I can confirm this, typing `chmod 06755` doesn't work for me.
Is there a reason we need to set the sgid bit as well?
Probably doesn't need setgid but I left it since it was part of the original instructions.
try with acer liquid mini failed
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
busybox 'permission denied'
what should i do? i am using ubuntu 10.10..thanks for your help...
hi guys!
recently, i got a phone,i want to root it,but not success. this is the information of my phone: 1. not root,2.access bootloader,3.can use adb and fastboot .
i want to try this method:
(1). backup system partition,i copyed the whole file in /system/ to the /sdcard/system/, using RE file manager.
(2). add root file and root it
sudo cp su /sdcard/system/bin/
sudo cp busybox /sdcard/system/xbin/
sudo cp Superuser.apk /sdcard/system/app/
sudo chown root:root /sdcard/system/bin/su
sudo chmod 4755 /sdcard/system/bin/su
sudo chown root:root /sdcard/system/xbin/busybox
sudo chmod 4755 /sdcard/system/xbin/busybox
sudo chown root:root /mnt/system/app/Superuser.apk
sudo chmod 644 /sdcard/system/app/Superuser.apk
(3).make system image
sudo ./mkyaffs2image /sdcard/system/ $HOME/system.img
(4).fastboot flash it
fastboot flash system system.img
i doubt with this method,this method can root my phone???? help help
Thanks Yupandra2012, my Tablet S 4.0.3 r1a finally rooted.
Ref: http://forum.xda-developers.com/showpost.php?p=31408901&postcount=12
The original steps(this link) was written in Japanese, I've just translate it into Eng. But sorry for my bad English.
UPDATE:
A semi automatic script can be found at here.
Files you need:
adb tools
SonyTabletICS-2.zip
Superuser-3.1.3-arm-signed.zip
VpnFaker.apk (Attachment)
For those who are no using the US firmware, the attached VpnFaker.apk may not suitable for your tablet.
Please follow this steps(click me) to resign the VpnFaker.apk. Thanks.
***Pls Execute the command line by line***
Unzip those files into a dir, Open cmd console, cd to that dir
Run the following command and press Restore on your tablet
Code:
adb restore settings.ab
Check the result
Code:
adb shell ls -ld /data/data/com.android.settings/a
[I][COLOR="DarkGreen"]drwxrwxrwx system system a[/COLOR][/I]
And continue, ignore the "rm -r a" permission denied error
Code:
adb shell
cd /data/data/com.android.settings
rm -r a
while : ; do ln -s /data a/file99; done
While the loop is running, open another cmd console and run
Code:
adb restore settings.ab
Once the restore process is completed, you can press CTRL+C on the 1st cmd console to break the loop
Check the /data permission
Code:
adb shell ls -ld /data
[I][COLOR="DarkGreen"]drwxrwxrwx system system data[/COLOR][/I]
Then continue
Code:
adb push busybox /data/local/tmp
adb push rootkit.tar.gz /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 busybox
./busybox tar zxf rootkit.tar.gz
exit
Push the resigned VpnFaker.apk(resign by ZipSigner 2) and update the timestamp
Code:
adb push VpnFaker.apk /data/local/tmp
adb shell
touch -t 1346025600 /data/local/tmp/VpnFaker.apk
exit
Now, replace the VpnDialogs, ignore "cp: can't open 'system/xxxxxxx': Permission denied" while you execute "/data/local/tmp/busybox cp -r system system2"
Code:
adb shell
cd /data
/data/local/tmp/busybox cp -r system system2
[COLOR="DarkGreen"]#Pls ignore "cp: can't open 'system/xxxxxxx': Permission denied"[/COLOR]
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 system
mv app app-
mkdir app
mv /data/local/tmp/VpnFaker.apk /data/app
Make sure the datatime is 2012/08/27 00:00
Code:
TZ=0 ls -l /data/app
[I][COLOR="DarkGreen"]-rw-r--r-- shell shell 198580 2012-08-27 00:00 VpnFaker.apk[/COLOR][/I]
Generate the packages.xml
Code:
/data/local/tmp/busybox sed -f /data/local/tmp/packages.xml.sed system-/packages.xml > system/packages.xml
And double check the result
Code:
/data/local/tmp/busybox grep vpndialogs system/packages.xml
[I][COLOR="DarkGreen"]<updated-package name="com.android.vpndialogs" codepath="/system/app/VpnDialogs.apk" nativelibrarypath="/data/data/com.android.vpndialogs/lib" flags="1" ft="136f14be668" it="136f14be668" ut="136f14be668" version="15" shareduserid="1000">
<package name="com.android.vpndialogs" codepath="/data/app/VpnFaker.apk" nativelibrarypath="/data/data/com.android.vpndialogs/lib" flags="1" ft="1396560b400" it="1396560b400" ut="1396560b400" version="45" shareduserid="1000">[/COLOR][/I]
Exit adb shell and reboot, you should see something like "Android is updating" during startup.
Code:
exit
adb reboot
Start the injected Terminal Emulator
Code:
adb shell am start -n com.android.vpndialogs/.Term
Unlock your tabet, The Terminal Emulator should appeared. If not, post your "adb logcat".
Now, in the Terminal Emulator
Code:
id
You should see the uid is 1000(system)
Still in the Terminal Emulator, ignore the script error
Code:
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
Now back to the cmd console
Code:
adb shell
/dev/sh
id
Check the uid is 2000(shell)
And
Code:
chown 0.0 /data/local/tmp/_su
chmod 6755 /data/local/tmp/_su
/data/local/tmp/_su
id
Check the root access uid 0(root)
Backup /system (you may just skip it)
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/system.ext4 bs=128K
Copy su & Superuser.apk to /system
Code:
/data/local/tmp/busybox mount -o rw,remount /system
/data/local/tmp/busybox cp /data/local/tmp/_su /system/xbin
chown 0.0 /system/xbin/_su
chmod 6755 /system/xbin/_su
/data/local/tmp/busybox cp /data/local/tmp/su /system/xbin
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
/data/local/tmp/busybox cp /data/local/tmp/Superuser.apk /system/app
/data/local/tmp/busybox mount -o ro,remount /system
sync
exit
Check the /system _su is working or not
Code:
_su
id
Should be uid 0(root)
And move the original /data/app & /data/system back (the original steps will keep the VpnFaker.apk, but i skip it)
Code:
cd /data
mv app app2
mv app- app
mv system system2
mv system- system
exit
exit
Now, you Tablet S should be rooted.
I'm getting permission denied rm -r a... hopefully someone can make a batch file for this.
SWFlyerUK said:
I'm getting permission denied rm -r a... hopefully someone can make a batch file for this.
Click to expand...
Click to collapse
You may just skip that error.
You can't delete that folder actually, just fake the system.
WonderEkin said:
Thanks Yupandra2012, my Tablet S 4.0.3 r1a finally rooted.
Ref: http://forum.xda-developers.com/showpost.php?p=31408901&postcount=12
The original steps(this link) was written in Japanese, I've just translate it into Eng. But sorry for my bad English.
Click to expand...
Click to collapse
Good job and thank you. You beat me to the finish line, I was also translating (slowly) the original Japanese post into English by tediously using [B]http://www.bing.com/translator/[/B] and [B]http://translate.google.com/[/B] as my translators.
For convenience, those who do this rooting method may also want to copy the ADB files adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll (or download and extract ADB_v1.0.29.zip) into the same directory where they put the rooting files SonyTabletICS-2.zip, Superuser-3.1.3-arm-signed.zip, and VpnFaker.apk.
Now I just need to get an unrooted Sony Tablet S to test this method on. Perhaps I will unrooted my granddaughter's tablet.
This stopped working for me when I had to launch VpnDialogs, activity not found - also had permission denied which meant I couldn't go further, mkdir app said mkrdir not found:
Code:
/data/local/tmp/busybox cp -r system system2
= Permission Denied.
A couple questions,
Couldthis method brick my tablet, or is safe try it?
Would this work doing it on Ubuntu Linux?
Thanks in advance!
SWFlyerUK said:
This stopped working for me when I had to launch VpnDialogs, activity not found - also had permission denied which meant I couldn't go further, mkdir app said mkrdir not found:
Code:
/data/local/tmp/busybox cp -r system system2
= Permission Denied.
Click to expand...
Click to collapse
Same Problem here, what to do now?
WonderEkin said:
Thanks Yupandra2012, my Tablet S 4.0.3 r1a finally rooted.
Ref: http://forum.xda-developers.com/showpost.php?p=31408901&postcount=12
Now, you Tablet S should be rooted.
Click to expand...
Click to collapse
Thanks a lot for your hard work.
Before I start this root, I want to confirm with you whether this root will wipe out my installed app data?
SWFlyerUK said:
This stopped working for me when I had to launch VpnDialogs, activity not found - also had permission denied which meant I couldn't go further, mkdir app said mkrdir not found:
Code:
/data/local/tmp/busybox cp -r system system2
= Permission Denied.
Click to expand...
Click to collapse
Can you post the full command log?
WonderEkin said:
Can you post the full command log?
Click to expand...
Click to collapse
Sure, i tried it two times: (for any reason i can't copy the full log, sry)
C:\STS>adb shell
[email protected]:/ $ cd /data
cd /data
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox cp -r system system2
cp: can't create directory 'system2': Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox find system2 -type f -exec chmod
666 {} \
d system2 -type f -exec chmod 666 {} \ <
> /data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \
> mv system system-
mv system system-
find: -exec requires an argument
1|[email protected]:/data $ mv system2 system
mv system2 system
failed on 'system2' - No such file or directory
255|[email protected]:/data $ cd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 systemcd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
cp: can't create directory 'system2': Permission denied
daniel910821 said:
A couple questions,
Couldthis method brick my tablet, or is safe try it?
Would this work doing it on Ubuntu Linux?
Thanks in advance!
Click to expand...
Click to collapse
Modify /data won't brick the device, you can wipe it if /data really corrupted.
For /system, those steps should be harmless
If you have and for Linux, then yes, should works on Linux
I can't get the restore settings part to work. All the files are extracted to the same folder as adb any ideas
Sent from my Sony Tablet S using xda app-developers app
rrlu21 said:
Thanks a lot for your hard work.
Before I start this root, I want to confirm with you whether this root will wipe out my installed app data?
Click to expand...
Click to collapse
I'm not sure this root will keep the installed app or not, as i've wipe my tablet many times to test the VpnFaker.apk...
But the steps will rename the original app folder and rename it back in the final steps. Should be no data lost.
TomaHawk93 said:
Sure, i tried it two times: (for any reason i can't copy the full log, sry)
C:\STS>adb shell
[email protected]:/ $ cd /data
cd /data
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox cp -r system system2
cp: can't create directory 'system2': Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox find system2 -type f -exec chmod
666 {} \
d system2 -type f -exec chmod 666 {} \ <
> /data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \
> mv system system-
mv system system-
find: -exec requires an argument
1|[email protected]:/data $ mv system2 system
mv system2 system
failed on 'system2' - No such file or directory
255|[email protected]:/data $ cd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 systemcd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
cp: can't create directory 'system2': Permission denied
Click to expand...
Click to collapse
Seeme you paste multi lines of command at one time, am I correct?
Those command should execute one by one.
You can simple wipe the device and redo again
or
Can you execute the following code in adb shell so that I can give you the fallback command?
Code:
ls -la /data
My brother has this tablet and I plan on attempting to root this evening...
[/COLOR]video tut maybe ?
Resign VpnFaker.apk
Hi
Do I have to resign the file VpnFaker.apk? If yes can someone explain hoe this is done.
I can do all commands until the replacement of the VpnDialogs. Then I get stuck with 'permission denied'.
Regards Paul
Can we use this method to may root Xperia tablet s on 4.0.3?
im stuck @ replace the VpnDialogs
i get Permission denied for all
c:\sony>adb shell
[email protected]:/ $ cd /data
/data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 system
c
d /data
mv app app-
mkdir app
mv /data/local/tmp/VpnFaker.apk /data/app /data/local/tmp/busybox
cp -r system system2
/data/local/tmp/busybox find system2 -type f -exec chmod 666 {} \;
/data/local/tmp/busybox find system2 -type d -exec chmod 777 {} \;
mv system system-
mv system2 system
mv app app-
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
mkdir app
cp: can't create directory 'system2': Permission denied
d system2 -type f -exec chmod 666 {} \; <
find: system2: No such file or directory
d system2 -type d -exec chmod 777 {} \; <
find: system2: No such file or directory
1|[email protected]:/data $ mv system system-
failed on 'system' - Permission denied
255|[email protected]:/data $ mv system2 system
failed on 'system2' - No such file or directory
255|[email protected]:/data $
255|[email protected]:/data $ mv app app-
failed on 'app' - Permission denied
255|[email protected]:/data $ mkdir app
mkdir failed for app, File exists
255|[email protected]:
zorbakun said:
Can we use this method to may root Xperia tablet s on 4.0.3?
Click to expand...
Click to collapse
It says so in the first post and the thread title also referrs to 4.0.3 r1a
How to copy device files from a folder (src) to proprietary/ and have the blobs build. ????
(I really dont want to connect my device to the pc all the time!)
I have my device (Rom files) in the folder: src
My device tree is in: home/ICS/device/YG/m805_892x/
This is what i have sow far now. Well what i found and changed a bit:
#!/bin/sh
if [ $# -lt 1 ]
then
echo "Usage:" $0 "<Source>"
exit
fi
SOURCE=$1
VENDOR=YG
DEVICE=m805_892x
rm -r ../../../device/$VENDOR/$DEVICE
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary
# Pull needed standard libs voorbeeld:
cp -a $SOURCE/system/lib/libaudio.so ../../../device/$VENDOR/$DEVICE/proprietary
cp -a $SOURCE/system/lib/libaudiopolicy.so ../../../device/$VENDOR/$DEVICE/proprietary
#and sow on.
./setup-makefiles.sh
Any one?
Well i got something working. Here a small example of my copy-files.sh
#!/bin/sh
VENDOR=YG
DEVICE=m805_892x
#MANUFACTURER=YG
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/bin
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/bluetooth
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/dhcpcd
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/permissions
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/ppp
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/ril
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/etc/wifi
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/fonts
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/framework
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/lib/egl
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/lib/hw
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/lib/modules
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/media/audio/alarms
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/media/audio/notifications
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/media/audio/ringtones
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/media/audio/ui
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/idc
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/keychars
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/keylayout
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/share/zoneinfo
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/srec/config/en.us/dictionary
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/srec/config/en.us/g2p
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/srec/config/en.us/grammars
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/usr/srec/config/en.us/models
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/vendor/lib/egl
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/vendor/lib/hw
mkdir -p ../../../device/$VENDOR/$DEVICE/proprietary/wifi
cp -a src/lib/libril.so ../../../device/$VENDOR/$DEVICE/proprietary/lib/libril.so
cp -a src/key_921600.psr ../../../device/$VENDOR/$DEVICE/proprietary/key_921600.psr
cp -a src/key_3000000.psr ../../../device/$VENDOR/$DEVICE/proprietary/key_3000000.psr
cp -a src/ts.conf ../../../device/$VENDOR/$DEVICE/proprietary/ts.conf
cp -a src/bin/bugmailer.sh ../../../device/$VENDOR/$DEVICE/proprietary/bin/bugmailer.sh
cp -a src/bin/busybox ../../../device/$VENDOR/$DEVICE/proprietary/bin/busybox
cp -a src/bin/chkntfs ../../../device/$VENDOR/$DEVICE/proprietary/bin/chkntfs
cp -a src/bin/flash_eraseall ../../../device/$VENDOR/$DEVICE/proprietary/bin/flash_eraseall
cp -a src/bin/hostapd ../../../device/$VENDOR/$DEVICE/proprietary/bin/hostapd
cp -a src/bin/hostapd_cli ../../../device/$VENDOR/$DEVICE/proprietary/bin/hostapd_cli
cp -a src/bin/hostapd_wps ../../../device/$VENDOR/$DEVICE/proprietary/bin/hostapd_wps
cp -a src/bin/iptables ../../../device/$VENDOR/$DEVICE/proprietary/bin/iptables
cp -a src/bin/iwconfig ../../../device/$VENDOR/$DEVICE/proprietary/bin/iwconfig
cp -a src/wifi/wlan.ko ../../../device/$VENDOR/$DEVICE/proprietary/wifi/wlan.ko
./setup-makefiles.sh
my copy-files.sh