Well so after a long time, my phone's touch does not work
Well the sides were useless so I gave my phone for repair and then they repaired it ( I locked the bootloader, installed ics and then gave them)
well the touch was fixed!
then I installed JB ( unofficial) but here the touch does not work at all. Does this mean that this is a driver problem or something like that?
How can I fix this.
Some one please help me!
anyone? @Pandemic if you know?
This happened to 2011 xperia if anyone installed wrong rom... Like xperia mini's rom on xperia mini pro... From that experience,i know that the touch drivers got altered,hence touch problem occured.. There were lengthy process to recover it.. Don't know if it will work or not on our 2012
Sent from my LT22i using xda app-developers app
alone_in_dark said:
This happened to 2011 xperia if anyone installed wrong rom... Like xperia mini's rom on xperia mini pro... From that experience,i know that the touch drivers got altered,hence touch problem occured.. There were lengthy process to recover it.. Don't know if it will work or not on our 2012
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
great
can you please refer me to the link or shed some light
U need to manually replace hw_config.sh ..munjeni told this a long time before when jb was being ported from xperia p to xu ... In the jb kernel thread by devswift1... However what u can try is take necessary files from stock rom
Make a flashable zip out of it and flash in cwm... This is just a hypothesis jatin... Never tried this..
doctor_droid said:
U need to manually replace hw_config.sh ..munjeni told this a long time before when jb was being ported from xperia p to xu ... In the jb kernel thread by devswift1... However what u can try is take necessary files from stock rom
Make a flashable zip out of it and flash in cwm... This is just a hypothesis jatin... Never tried this..
Click to expand...
Click to collapse
which stock rom?
ics? @munjeni, can you please shed some light on this. sorry to bother you for this but...
jatinrungta said:
which stock rom?
ics? @munjeni, can you please shed some light on this. sorry to bother you for this but...
Click to expand...
Click to collapse
I think I misnamed the file ... munjeni knows what to do.. he is THE MASTER
@munjeni please help me just one time
Thank You
jatinrungta said:
@munjeni please help me just one time
Thank You
Click to expand...
Click to collapse
May be he has flagging notification set to off
doctor_droid said:
May be he has flagging notification set to off
Click to expand...
Click to collapse
then I will pm him
Jatin can you please post the solution here after munjeni's response....I am currently facing the same issue and don't know whether its hardware related or not.
Thanks in advance man..
AKA#1 said:
Jatin can you please post the solution here after munjeni's response....I am currently facing the same issue and don't know whether its hardware related or not.
Thanks in advance man..
Click to expand...
Click to collapse
he has yet to reply me and well I do not know if he will
jatinrungta said:
he has yet to reply me and well I do not know if he will
Click to expand...
Click to collapse
Let post hw_config.sh from Xperia U ICS firmware, file is located inside /system/etc folder ! Will try to help you!
Code:
# HW configuration file for kumquat
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex
# Audio jack configuration
dev=/sys/devices/platform/simple_remote.0
echo 0,301,1901 > $dev/accessory_min_vals
echo 300,1900 > $dev/accessory_max_vals
echo 0,51,251,511,851 > $dev/button_min_vals
echo 50,250,510,850,5000 > $dev/button_max_vals
# Proximity sensor configuration
dev=/sys/bus/i2c/devices/2-0054/
val_cycle=2
val_nburst=0
val_freq=2
val_threshold=5
val_filter=0
echo $val_cycle > $dev/cycle # Duration Cycle. Valid range is 0 - 3.
echo $val_nburst > $dev/nburst # Numb er of pulses in burst. Valid range is 0 - 15.
echo $val_freq > $dev/freq # Burst frequency. Valid range is 0 - 3.
if `ls /data/etc/threshold > /dev/null`; then
cat /data/etc/threshold > $dev/threshold # Use value from calibration
rm /data/etc/threshold # Remove temp file
else # No value from calibration, use default value
echo $val_threshold > $dev/threshold # sensor threshold. Valid range is 0 - 15 (0.12V - 0.87V)
fi
if `ls /data/etc/filter > /dev/null`; then
cat /data/etc/filter > $dev/filter # Use value from calibration
rm /data/etc/filter # Remove temp file
else # No value from calibration, use default value
echo $val_filter > $dev/filter # RFilter. Valid range is 0 - 3.
fi
@munjeni
Ok, Xperia U definitely have touchscreen firmware flasher. First of all check if hw_config.sh is identical in your not working JB and your working ICS !!! If sh file is not indentic than simple replace them and allso make sure upload 2 files (from our post)!!!
If sh file is identic and problem with your touchscreen stil exists than you can try next thing (on your own risk only! You maybe get brick! So again you doing on your own risk!!!)
Line inside hw_config.sh look like:
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex
Click to expand...
Click to collapse
These command is for firmware update! If you flashed for example Xperia Go rom to Xperia U you have definitelly flashed wrong firmware and thats reason for bad things related to your problem with phone touch screen (some guys hard bricked his phones by flashing wrong device android fiemware)!
So...
1. extract cyttsp_fwloader from your ICS zip (located in xbin or bin folder, not sure by now)
2. extract touchscreen firmware from your zip which is located in /system/etc/firmware/ttsp_fw.hex
3. put these 2 files to /data/local/tmp ,give chmod 755 to booth files
4. flash them by command:
adb shell /data/local/tmp/cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /data/local/tmp/ttsp_fw.hex
Click to expand...
Click to collapse
If you brick your phone I can not help you! Simple I have no experience with these thing (never tried!)! Good luck!
jatinrungta said:
Well so after a long time, my phone's touch does not work
Well the sides were useless so I gave my phone for repair and then they repaired it ( I locked the bootloader, installed ics and then gave them)
well the touch was fixed!
then I installed JB ( unofficial) but here the touch does not work at all. Does this mean that this is a driver problem or something like that?
How can I fix this.
Some one please help me!
Click to expand...
Click to collapse
bro your touch is not working on jb or ics or gb or in all??
bibhu059 said:
bro your touch is not working on jb or ics or gb or in all??
Click to expand...
Click to collapse
in jb!
jatinrungta said:
in jb!
Click to expand...
Click to collapse
bro in phantom 1.0.7 format cache,system,data everything and then in cwm usb mode put the rom to sd card..then 3wipes then install the zip..i
also i faced the same problem..but by doing this problem solved.so try this..good luck
bibhu059 said:
bro in phantom 1.0.7 format cache,system,data everything and then in cwm usb mode put the rom to sd card..then 3wipes then install the zip..i
also i faced the same problem..but by doing this problem solved.so try this..good luck
Click to expand...
Click to collapse
can you post . cyttsp_fwloader if you have a ics frimware
@kontini @Little Zed @NoobCoder @bibhu059
Related
anyone succeed app2sd on x10 mini pro?
some thread in this forum, still stuck in automatic mount on restart
krist28 said:
anyone succeed app2sd on x10 mini pro?
some thread in this forum, still stuck in automatic mount on restart
Click to expand...
Click to collapse
I don't think they have it at the moment. Hope there will be something when 2.1 comes up.
This would be very useful... I hope someone can develop it.
http://cleanimport.xda/index.php?threads/800555/
Shouldn't this also work on the X10 mini?
DerEineDa said:
http://cleanimport.xda/index.php?threads/800555/
Shouldn't this also work on the X10 mini?
Click to expand...
Click to collapse
probably not
On my X10 mini pro, mount_iso.sh is ignored,
and "ln -s /system/sd/app /data/app" makes the system keeps rebooting at next start up
ps.
i fixed it by del the link and mkdir /data/app using the adb shell immediately before its rebooting.
can anyone check it out if
this file
/system/drm/DxDrm/drm.sh
are not ignrored at booting??
Drm.sh is executed. You can use it for your script, but why not just use the original init script?
Regards
Bin4ry
i don't now if it work because i'ts a bit complex
and i don't want to destroy anything
from you i had now (Xperia_fs.rar) that the mount_iso.sh is excuted at start
question can i delte the Drm.sh or must i add my script??
wolfilein said:
i don't now if it work because i'ts a bit complex
and i don't want to destroy anything
from you i had now (Xperia_fs.rar) that the mount_iso.sh is excuted at start
question can i delte the Drm.sh or must i add my script??
Click to expand...
Click to collapse
Better just add it
Regards
ok
last question had the x10 minni /pro
the light at the top of the display or not,
and must i remove the link from /data/app
before the phone reboot ??
wolfilein said:
can anyone check it out if
this file
/system/drm/DxDrm/drm.sh
are not ignrored at booting??
Click to expand...
Click to collapse
i create /system/drm/DxDrm/drm.sh and chmod 777
mkdir /data/test
Click to expand...
Click to collapse
but no such folder after reboot
wolfilein said:
i don't now if it work because i'ts a bit complex
and i don't want to destroy anything
from you i had now (Xperia_fs.rar) that the mount_iso.sh is excuted at start
question can i delte the Drm.sh or must i add my script??
Click to expand...
Click to collapse
delete?
my U20i
S1 Boot Version
1229-3593 R8A026
there‘s no /system/drm/DxDrm/drm.sh
and no /etc/mount_iso.sh
This was discontinued, now you can just flash CWM recovery, it have Unified Chargemon
Good work
thank you for ur work!
this is really required as there doesnt seem to be any consistency in the 'boot hijack' script (/system/bin/chargemon) used on different roms
there is a real need for such a unified chargemon
THANKS AGAIN!
why 2 zips man!
well to be honest made me laugh xD
unified and 2 zips looked into them and why not make 1 zip?
change this line
if [ -f /system/custom.bin ]; then
to something every cm rom have!
if [ -f /system/etc/CHANGELOG.txt ]; then
this way it will look more unified xD
PD: i don't know for sure the file is called changelog.txt
it is something with changelog inside the /system/etc folder
and i know every cm rom have it!
owain94 said:
why 2 zips man!
well to be honest made me laugh xD
unified and 2 zips looked into them and why not make 1 zip?
change this line
if [ -f /system/custom.bin ]; then
to something every cm rom have!
if [ -f /system/etc/CHANGELOG.txt ]; then
this way it will look more unified xD
PD: i don't know for sure the file is called changelog.txt
it is something with changelog inside the /system/etc folder
and i know every cm rom have it!
Click to expand...
Click to collapse
if [ -f /system/etc/CHANGELOG-CM.txt ]; then
Done, thanks owain, you allways with better ideas will upload zip
D4rKn3sSyS said:
if [ -f /system/etc/CHANGELOG-CM.txt ]; then
Done, thanks owain, you allways with better ideas will upload zip
Click to expand...
Click to collapse
you are welcome mate
I just dont understand... why is this so useful? I already read that make a dev life better... and Im more than ok with that and I will flash this at this moment... but I really like if u explain me more this...
Note: If this is so usefull.. why dont u put this in every roms and flash "automaticly" (sry, i dont remember how to writte this xD)... i mean if we just need to flash that... include in your own rom and thats it...
ocovarr112 said:
I just dont understand... why is this so useful? I already read that make a dev life better... and Im more than ok with that and I will flash this at this moment... but I really like if u explain me more this...
Note: If this is so usefull.. why dont u put this in every roms and flash "automaticly" (sry, i dont remember how to writte this xD)... i mean if we just need to flash that... include in your own rom and thats it...
Click to expand...
Click to collapse
I already added it to my rom
D4rKn3sSyS said:
I already added it to my rom
Click to expand...
Click to collapse
Maybe i am stupit but google can also not tell me what and for what it is.
Can you explane ?
MiKa
D4rKn3sSyS said:
*This will NOT add any feature or something like that, it's only for make easier the work of some devs
Click to expand...
Click to collapse
It's on the first post
D4rKn3sSyS said:
It's on the first post
Click to expand...
Click to collapse
I read that but what wil be easyer for the dev's..
mika-nl said:
I read that but what wil be easyer for the dev's..
Click to expand...
Click to collapse
Developing apps, identifying device.. etc etc etc
Corrected
there is xloud for X10 big one working 50%
Try but make sure you do back up because I am a beginner
the problem was with the zip in the begining (SORRY)
instruction
build.prop
#additional build properties
add line : ro.semc.xloud.supported=true
then copy file using root explorer
sytem/etc/permission
com.sonyericsson.audioeffectif.xml file
system/lib/
libaudioeffect_jni.so file
system /etc/framework/
semc_audioeffectif.jar
system/app
audioeffectservice.apk
this are the files to makes it work!
using the damp
http://forum.xda-developers.com/showthread.php?t=1199310
big thanks for resoures
part 2 two
replace the setting, setting provider
reboot
sorry for quality
btw i am not retard there is aprove
marcoplo said:
there is xloud for X10 big one working 50%
Try but make sure you do back up because I am a beginner
Click to expand...
Click to collapse
tryed to flash it doasent work
WTF? Again these 50% things?
DON't flash this !! A dev should have a look into it, it seems to delete XREc !!!
marcoplo said:
there is xloud for x10 big one working 50%
try but make sure you do back up because i am a beginner
Click to expand...
Click to collapse
dude that is so lame... find your original promotion... 50% is allready taken by z
E cant chown/mod /system/bin/chargemon (no file or directory)
E failure at line 8
Set perm 0 0 0755 system/bin/chargemon
Install aborted.
Seems to be no contents in data. This is useless lol
NICE WORK BRO!
Sent from my X10i using XDA Premium App
pietropizzi said:
DON't flash this !! A dev should have a look into it, it seems to delete XREc !!!
Click to expand...
Click to collapse
Confirmed!!!!!!!!
Sent from my X10i using XDA Premium App
this is my first time. first, second, time does not work>> in third will work !!
IF YOU NOT TRY- WILL NOT GO ANYWHERE there have to be the first time
BTW I made correction
i got it 12.8% working
man if someone can really port this and give some volume to x10 it will be better than gb )
Would copying all these files make it work?
Where do you enable it from?
Do you have it working in the first place?
What's with the 50%?
I am really confused...
the xload is in the setting/ sound
yes need to to copy first then go to the setting/sound
marcoplo said:
system /etc/framework/
semc_audioeffectif.jar
Click to expand...
Click to collapse
It's /system/framework/semc_audioeffectif.jar
marcoplo said:
the xload is in the setting/ sound
yes need to to copy first then go to the setting/sound
Click to expand...
Click to collapse
Can we have a zip that works %100?
This doesn't work, I did everything right but I don't get the option to enable it in the Settings...
U set the corerct permissions and edit the build.prop?
Im curious about this :/
the option will not show up until you place
#additional build properties
add line : ro.semc.xloud.supported=true
find the and add the line on the right section #additional.. not at the end "build.prop" in system
My_Immortal said:
This doesn't work, I did everything right but I don't get the option to enable it in the Settings...
Click to expand...
Click to collapse
i'm no developer, but, i think you will also need the settings apk from the arc dump as well to get the option to work correctly.
Could you post a screeny to show :-D
svtfmook said:
i'm no developer, but, i think you will also need the settings apk from the arc dump as well to get the option to work correctly.
Click to expand...
Click to collapse
Or the X10 settings.apk will need editing to show the option. Maybe
Custom ROMs for ICS on Wave 1 ? If Any ? I am not sure how to proceed in this coz my phone doesnt boot in recovery mode
Sent from my Samsung Wave GT-S8500 (ICS 4.0.4) using xda premium
danishprakash said:
Custom ROMs for ICS on Wave 1 ? If Any ? I am not sure how to proceed in this coz my phone doesnt boot in recovery mode
Sent from my Samsung Wave GT-S8500 (ICS 4.0.4) using xda premium
Click to expand...
Click to collapse
No custom rom for the moment. Mike said that he made a recovery mode, let's see what will happen in the next version and if it will be possible at that moment.
Soxix said:
No custom rom for the moment. Mike said that he made a recovery mode, let's see what will happen in the next version and if it will be possible at that moment.
Click to expand...
Click to collapse
In fact, you can mod the current firmware if you know what to do... I activated the software keys on mine (you know, the home, back, applist). You just have to mount the img file, or use adb and you can try to change things.
anghelyi said:
In fact, you can mod the current firmware if you know what to do... I activated the software keys on mine (you know, the home, back, applist). You just have to mount the img file, or use adb and you can try to change things.
Click to expand...
Click to collapse
All are Under ubuntu ? or ..
hero355 said:
All are Under ubuntu ? or ..
Click to expand...
Click to collapse
Mounting the img file needs Linux (you need something like mount -t ext2 -o loop polishblood_Nightlyi1.img ../the_folder_you_created_for_mountpoint) but if you just want to make smaller modifications (eg. replacing one apk, or editing some configfile) adb on Windows is enough. If you use my kernel then you will have write access to /system, too.
As a "proof of concept" I "ported" a firmware from Galaxy S (AOKP). You can experiment with it, just replace the polisblood_Nightly1.img (and preferably replace data.img and cache.img with the original ones.)
Here you are:
http://dl.dropbox.com/u/27419363/polishblood_Nightly1.img
hero355 said:
All are Under ubuntu ? or ..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1702861
WinHex can open and extract files/folders from *.img ...
https://dms.ospserver.net/v1/device...?pkgID=FW-20120626-14658&service=fumo&wrkID=W
To build... not tested yet... But I think also more Windows Tools exists...
But for starting research WinHex is enough.
Best Regards
Thanks For your Replies
I have mounted polishblood_Nightly1.img using "sudo mount -o loop polishblood_Nightly1.img ../android"
and added some .apk files to the app folder....now how to unmount..???
umount ../android
i have edited polishblood_Nightly1.img .....thx u guys:good:
now some1 plz help me with kernel???
how to edit zImage????
does that need any tools????
Nitesh19 said:
i have edited polishblood_Nightly1.img .....thx u guys:good:
now some1 plz help me with kernel???
how to edit zImage????
does that need any tools????
Click to expand...
Click to collapse
There are no such tools... You can find scripts to extract the initramfs but that's all. You have to compile your kernel to make real changes.
anghelyi said:
There are no such tools... You can find scripts to extract the initramfs but that's all. You have to compile your kernel to make real changes.
Click to expand...
Click to collapse
is there any tut for this???
where to find scripts???
all under ubuntu????
thx :good:
anghelyi said:
In fact, you can mod the current firmware if you know what to do... I activated the software keys on mine (you know, the home, back, applist). You just have to mount the img file, or use adb and you can try to change things.
Click to expand...
Click to collapse
Could you tell me how you did that?
The tutorial is very simple,
First of all I would like to thank @NoobCoder, IF script, although is wrong! But I want to thank him!
1: unpacking the kernel, in init.rc
Search
Set this property so surfaceflinger # is not started by system_init
Setprop system_init.startsurfaceflinger 0
Let's add
# xiangxin: fix LED
Start data_restore
Then in the last added
# Xiangxin: FIX LED service
Service data_restore /sbin/data_restore.sh
User root
Oneshot
Disabled
OK, init.rc is corrected, download the attachment to data.tar, data_restore.sh
Added to the kernel, the /sbin directory!
The attachment of the system directory into your ZIP package!
OK tutorial end!
xx214718247 said:
Please moderator, don't move this post, I just write my method! Please stay one day!
Download the attachment, there is a modified file and not modified files!
Click to expand...
Click to collapse
No one will remove because you give awesome job about front camera
Sent from my ST25i using Tapatalk 2
Little Zed said:
No one will remove because you give awesome job about front camera
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Brother, you really fast!
Could you explain better what it does? For what android version it is?
Inviato dal mio Xperia U usando Tapatalk 4
Xperia_Modder said:
Could you explain better what it does? For what android version it is?
Inviato dal mio Xperia U usando Tapatalk 4
Click to expand...
Click to collapse
jb! ics works natively because it's official from sony!
I mean 4.1 or 4.2? Stock or cm?
Inviato dal mio Xperia U usando Tapatalk 4
Xperia_Modder said:
I mean 4.1 or 4.2? Stock or cm?
Inviato dal mio Xperia U usando Tapatalk 4
Click to expand...
Click to collapse
he worked only for stock...so i believe stock 4.1
It's for stock only.
He inserted a bash script in init.rc to run during boot. This script will place the light_themes and lightservice.soc in /data with the related dalvik-cache so that illumination_service can find the necessary files to light up the led bar.
Nice approach @xx214718247 bro
BTW, where's the tutorial ? Your title says it's a tutorial
NoobCoder said:
It's for stock only.
He inserted a bash script in init.rc to run during boot. This script will place the light_themes and lightservice.soc in /data with the related dalvik-cache so that illumination_service can find the necessary files to light up the led bar.
Nice approach @xx214718247 bro
BTW, where's the tutorial ? Your title says it's a tutorial
Click to expand...
Click to collapse
Now is it necessary to flash ur fix first before this or should we use this..only whileflashing Rom
Also....will this work if we wipe data/ factory reset??
Sent from my ST25i using XDA Premium 4 mobile app
kantry123 said:
Now is it necessary to flash ur fix first before this or should we use this..only whileflashing Rom
Also....will this work if we wipe data/ factory reset??
Sent from my ST25i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if all kernels include this then no need to flash my fix.
Since it's in the kernel, even after wiping data/cache, it'll work.
@xx214718247, so every time phone boots, it'll run data_restore.sh and replace light_themes and lightservice.soc. Wouldn't it remove our last saved color and set it back to default everytime ??
NoobCoder said:
It's for stock only.
He inserted a bash script in init.rc to run during boot. This script will place the light_themes and lightservice.soc in /data with the related dalvik-cache so that illumination_service can find the necessary files to light up the led bar.
Nice approach @xx214718247 bro
BTW, where's the tutorial ? Your title says it's a tutorial
Click to expand...
Click to collapse
Kernel maker, added to the kernel? My accessory, which is not a comparison?
NoobCoder said:
It's for stock only.
He inserted a bash script in init.rc to run during boot. This script will place the light_themes and lightservice.soc in /data with the related dalvik-cache so that illumination_service can find the necessary files to light up the led bar.
Nice approach @xx214718247 bro
BTW, where's the tutorial ? Your title says it's a tutorial
Click to expand...
Click to collapse
Yes, restart, manual setting! If you can find a better way, please tell me, or have a better idea, please tell me? Thank you
NoobCoder said:
if all kernels include this then no need to flash my fix.
Since it's in the kernel, even after wiping data/cache, it'll work.
@xx214718247, so every time phone boots, it'll run data_restore.sh and replace light_themes and lightservice.soc. Wouldn't it remove our last saved color and set it back to default everytime ??
Click to expand...
Click to collapse
At present, I have no better way, let him after the restart does not need to be manually set? You study? If you can, please tell me?
is this ready to flash ?
i tried and says installation aborted
NoobCoder said:
It's for stock only.
He inserted a bash script in init.rc to run during boot. This script will place the light_themes and lightservice.soc in /data with the related dalvik-cache so that illumination_service can find the necessary files to light up the led bar.
Nice approach @xx214718247 bro
BTW, where's the tutorial ? Your title says it's a tutorial
Click to expand...
Click to collapse
I have an idea? In the first boot, SH, script, create a file in data, second boot, scanning, whether to set up the file, if not, then run the SH script! If there is not running a SH script!
sv2hqx said:
is this ready to flash ?
i tried and says installation aborted
Click to expand...
Click to collapse
No. This is a kernel authors!
xx214718247 said:
No. This is a kernel authors!
Click to expand...
Click to collapse
ok
didn't know
xx214718247 said:
I have an idea? In the first boot, SH, script, create a file in data, second boot, scanning, whether to set up the file, if not, then run the SH script! If there is not running a SH script!
Click to expand...
Click to collapse
you can check if the file exists or not. If doesn't exist then run the bash script. I'm not expert in bash but it should work.
Code:
if [ -f light_themes -a -f lightservice.soc ];
then
# do nothing
else
run the script
fi
NoobCoder said:
you can check if the file exists or not. If doesn't exist then run the bash script. I'm not expert in bash but it should work.
Code:
if [ -f light_themes -a -f lightservice.soc ];
then
# do nothing
else
run the script
fi
Click to expand...
Click to collapse
I will try! Thank you very much
NoobCoder said:
you can check if the file exists or not. If doesn't exist then run the bash script. I'm not expert in bash but it should work.
Code:
if [ -f light_themes -a -f lightservice.soc ];
then
# do nothing
else
run the script
fi
Click to expand...
Click to collapse
Brother, your statement should not!
if [ -e /data/light_themes ]
then
# do nothing
exit
else
/sbin/busybox rm -r /tmp/data.tar
/sbin/busybox cp /sbin/data.tar /tmp/data.tar
busybox tar zxvf $tar_file
fi