Related
Here are 2 different way to get new BOOTANIMATION. Special thanx 2 ibussa & attn1 for helping me with this.
IF YOU ARE FLASHING NEW ROM AND WANT TO CHANGE ANIMATION WITH THE NEW FLASH
1. Open the ROM of your choose.zip
2. Navigate to System\Media and look for bootanimation.zip
3. Extract the original boot animation
4. Open it and delete the bootanimation.zip file, copy the new one of your choose or drag it the new one in.
5. Put Rom.zip on SD card.
6. Reboot into recovery.
7. Install zip and wait for it to finish.
IF YOU ALREADY HAVE ROM AND JUST CHANGING BOOT ANIMATION
1. Copy the NEW bootanimation.zip of your choice in SDK Folder
2. Open up CMD
3. cd C:\AndroidSDK\tools (or were ever you SDK files are)
4. adb remount
The filesystem is mounted read only. You need to mount it read/write.
5. adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
6. adb push bootanimation.zip /system/media/bootanimation.zip
7. adb push bootanimation.zip /data/local/bootanimation.zip
To return to read only,
8. adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
9. Reboot and there you go
I managed to get one on and working a few days ago. I don't remember/know what finally made it work, but I tried the adb push method.
But the thing is, I got curious and instead of moving it, I tried removing the old bootscreen before I tried to push the new on.
I'm not sure if that is what finally made it work though, so don't take my word for it. All I know is after I rebooted after the adb push, it worked.
Well this is how I did it. I delete the bootanimation in the rom zip file and then inject thw new bootanimation and reflash the rom.
ibussa said:
Well this is how I did it. I delete the bootanimation in the rom zip file and then inject thw new bootanimation and reflash the rom.
Click to expand...
Click to collapse
How did you extract and inject the new bootanimation? unzip and then re zipped? Oh and what ROM are you using it on?
No, I open the zip, navigate thru the file and extract the original boot animation, then open it and delete the animation file, copy the new one and drag it or inject the new one into the Rom zip and reflash it.
Sent from my HTC Liberty using XDA App
def changing my animation now!
ibussa said:
No, I open the zip, navigate thru the file and extract the original boot animation, then open it and delete the animation file, copy the new one and drag it or inject the new one into the Rom zip and reflash it.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hmm... I have tried that and for some reason it wont let me extract delete or replace it..I will keep trying tho thank you
Edit: Scratch that I opened with WinRAR instead of zip and that allowed me to extract delete & replace it..Thnx Again
Try with the rooted Rom beta of att
Sent from my HTC Liberty using XDA App
What is the OP's boot animation? Where can I find some cool boot animations to try? I've seen some but not many that I really liked.
sfernandez said:
I am trying to change my boot screen animation to a new one and have tried multiple ways. Any help would be greatly appreciated. I have attached the file I am trying to install.
I placed the bootanimation on sd card & in C:AndroidSDK\tools
I have tried in recovery mode to install from zip on sd card and no luck
I have tried going thru OI file manager and deleting/renaming bootanimation.zip on system and no luck.
I have also tried to delete/move/copy bootanimation.zip threw Driod Explored and nothing
I have tried to remove the old bootanimation and no luck
adb shell rm/system/media/bootanimation.zip
adb shell rm/data/local/bootanimation.zip
I have even tried pushing and no luck
cd C:\AndroidSDK\tools
adb remount
adb mv( I tried with and without this command)
adb push bootanimation.zip /system/media/bootanimation.zip
adb push bootanimation.zip /data/local/bootanimation.zip
adb reboot
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The filesystem is mounted read only. You need to mount it read/write.
try
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
to return to read only,
adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
attn1 said:
the filesystem is mounted read only. You need to mount it read/write.
Try
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
to return to read only,
adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
hell yeah that work :d thank you thank you thank you
Can't you just get a regedit and do it on the phone itself like on windows mobile?
I remember I changed my splash screen on my HTC Pure it only took like a second.
TheChemist187 said:
Can't you just get a regedit and do it on the phone itself like on windows mobile?
I remember I changed my splash screen on my HTC Pure it only took like a second.
Click to expand...
Click to collapse
Not to my knowledge. I know WM you were able to but yea, but not android. Ether way this is a very easy way 2 do it.
Wheres the best place to get boot screens?
SysAdmNj said:
Wheres the best place to get boot screens?
Click to expand...
Click to collapse
Check the g1 forum on xda and look for the boot animations thread.
Hi, I want to replace my bootscreen with this one.
I downloaded the zip files from the thread. I did what you said, but the only thing i saw when i rebootted was a black screen.
What format are the bootscreens in? I need video size, format, and length please. Also, If I do make one, do I just zip it? Thanks in advance.
Rubinski_be said:
Hi, I want to replace my bootscreen with this one.
I downloaded the zip files from the thread. I did what you said, but the only thing i saw when i rebootted was a black screen.
Click to expand...
Click to collapse
hocplyr98 said:
What format are the bootscreens in? I need video size, format, and length please. Also, If I do make one, do I just zip it? Thanks in advance.
Click to expand...
Click to collapse
Often the black screen is caused by either improper resolution or the desc.txt file having some incorrect verbiage or syntax. The issue may also be caused by zipping up the bootanimation.zip using compression. When zipping bootanimation.zip, it's a good practice to use no compression. You can try my bootanimiation.zip for formatting to see if it works. It was created specifically for the Aria. (This one is the stock looking HTC logo with the green android peeking out from behind the logo.)
http://forum.xda-developers.com/attachment.php?attachmentid=359230&d=1278999405
I'm using a HTC Tattoo, and i think that the resolution of the bootscreen was wrong. The bootscreen wasn't original for the Tattoo, so it had another resolution. I changed the *.gif-files to 240*320 (Tattoo's resolution). I made a new zip (without compression) and tried to push it. But the files who where allready in there are not replaced :s
Someone needs to come up with an animation of Android peeing on Apple logo, Calvin & Hobbes style.
Hi, this is my first time posting on this site and I apologizes if this is in the wrong place. I just recently rooted my evo and was wondering when I want to apply a customization such as a new notification bar how do I know to use either flashing the file from the sd card or to run a command in adb? Is there an important difference, or can either be used? Thanks in advance for the help.
rafroehlich2 said:
Hi, this is my first time posting on this site and I apologizes if this is in the wrong place. I just recently rooted my evo and was wondering when I want to apply a customization such as a new notification bar how do I know to use either flashing the file from the sd card or to run a command in adb? Is there an important difference, or can either be used? Thanks in advance for the help.
Click to expand...
Click to collapse
Most files can be flashed, if they are in a .zip form, you should be okay. However for things like the bootscreens, the recommended method is to use ADB and push the bootanimation.zip file to the specified folder on the phone. However, this has been extremely simplified by user-made tools here on the EVO forums, not many people like using ADB (don't know why)... so there are tools to make it easier for people.
Usually the person that is distributing the file should say whether you need to flash or use ADB commands, just read the OP's post.
Thanks so much for your help.
rafroehlich2 said:
Thanks so much for your help.
Click to expand...
Click to collapse
Sure, no problem!
pseudoremora said:
Most files can be flashed, if they are in a .zip form, you should be okay. However for things like the bootscreens, the recommended method is to use ADB and push the bootanimation.zip file to the specified folder on the phone. However, this has been extremely simplified by user-made tools here on the EVO forums, not many people like using ADB (don't know why)... so there are tools to make it easier for people.
Usually the person that is distributing the file should say whether you need to flash or use ADB commands, just read the OP's post.
Click to expand...
Click to collapse
If I use the flashing method will the files be moved to the correct system folder or will it just deposit it in the ROM? When you use adb you specify the target, if I'm not mistaken. I just don't want my system to get cluttered with random files. Sorry if this isn't worded well.
rafroehlich2 said:
If I use the flashing method will the files be moved to the correct system folder or will it just deposit it in the ROM? When you use adb you specify the target, if I'm not mistaken. I just don't want my system to get cluttered with random files. Sorry if this isn't worded well.
Click to expand...
Click to collapse
When using ADB, the system won't get "cluttered"... mainly because when you're are using the adb push (copy) command, you will be overwriting the file that is currently residing on your phone.
For example, if I wanted to replace my bootanimation -- I would type:
Code:
adb push bootanimation.zip /system/customize/resource
This would copy the new bootanimation.zip over to the directory being specified (/system/customize/resource -- where the bootanimation resides), upon copying, it explicitly overwrites any file/folder with the name "bootanimation" -- unless you set a parameter when typing the command to ask you if it should overwrite. You don't need to worry about this though, almost always you'll overwrite the files.
As long as you push (copy) any and all files to its correct directory, nothing should ever get cluttered and if it does, then you can always remove it just as easily.
pseudoremora said:
When using ADB, the system won't get "cluttered"... mainly because when you're are using the adb push (copy) command, you will be overwriting the file that is currently residing on your phone.
For example, if I wanted to replace my bootanimation -- I would type:
Code:
adb push bootanimation.zip /system/customize/resource
This would copy the new bootanimation.zip over to the directory being specified (/system/customize/resource -- where the bootanimation resides), upon copying, it explicitly overwrites any file/folder with the name "bootanimation" -- unless you set a parameter when typing the command to ask you if it should overwrite. You don't need to worry about this though, almost always you'll overwrite the files.
As long as you push (copy) any and all files to its correct directory, nothing should ever get cluttered and if it does, then you can always remove it just as easily.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm new to this and any time I see command line I get hesitant. Thanks again for the thorough answer.
rafroehlich2 said:
Thanks for taking the time to answer. I'm new to this and any time I see command line I get hesitant. Thanks again for the thorough answer.
Click to expand...
Click to collapse
Yup, no problem. I try to usually give a detailed answer, as I'm sure not everyone will understand vague answers.
pseudoremora said:
Yup, no problem. I try to usually give a detailed answer, as I'm sure not everyone will understand vague answers.
Click to expand...
Click to collapse
Since you seem to be knowledgeable what is the difference between flashing a rom by its name.zip as opposed to renaming it update.zip? Does the former start new and the latter maintain all apps/settings?
Sent from my PC36100
rafroehlich2 said:
Since you seem to be knowledgeable what is the difference between flashing a rom by its name.zip as opposed to renaming it update.zip? Does the former start new and the latter maintain all apps/settings?
Sent from my PC36100
Click to expand...
Click to collapse
No difference.
The naming conventions don't mean anything really. There used to be a time when all packages had to be called "update.zip", but the Devs that built the recoveries made it so you could name the .zip files whatever you wanted.
You'll see ROM's/theme's/etc with fancy names -- that's just so its easier for the end user to identify what he/she is actually going to flash.
When I say "update.zip", I just mean that the file can be flashed via recovery and won't require command line/terminal/ADB.
However, there are certain files that will always have a static name (bootanimation.zip) -- that can't change because the phone is programmed to look for that specified file. So whenever someone uploads a bootanimation and calls it: "Nexus-bootanimation.zip" --- this should be renamed to bootanimation before adb pushing or flashing to its specified directory.
Now I understand the idea behind flashing a radio, however I don't understand flashing a kernel. How do I know when to do this and do the risks of radio apply to the kernel? Also, are there any other major components that I'll eventually have to flash? Thanks for answering my many questions.
Sent from my PC36100
rafroehlich2 said:
Now I understand the idea behind flashing a radio, however I don't understand flashing a kernel. How do I know when to do this and do the risks of radio apply to the kernel? Also, are there any other major components that I'll eventually have to flash? Thanks for answering my many questions.
Sent from my PC36100
Click to expand...
Click to collapse
There are risks with both.
Flashing a kernel or radio has the potential to brick your phone. The radio is used for controlling all the "wireless" functions (3G, 4G, x1 connections (texting/calling)) -- pretty much anytime the phone connects to the Sprint towers, the radio is playing its part. So if you flash it incorrectly; the consequences are obvious.
The kernel is the heart of the Android. The kernel itself is actually Linux. Android is built upon Linux, so pretty much Google took the already existing Linux kernel and built Android on top of it (the UI, the apps, etc) and made Android into a Mobile OS, which can run on virtually any platform or device.
How do you know? You don't -- it's a matter of wanting to be curious enough to test. Some devs will put out kernels that overclock your device, others will add different features (screen fixes, loopback interface, underclocking, etc). The kernel controls all the hardware on the phone and how everything functions -- so when devs mess with source code, they are essentially making the hardware function differently for your device.
Some of the major components? -- The biggest ones so far are the wireless driver and 4G driver. When the EVO came out -- the battery life wasn't great; but after the new update (1.47 and the accompanying radio's); battery life on the device have improved significantly and people have experience better WiFi reception and such.
Hope that helps.
pseudoremora said:
There are risks with both.
Flashing a kernel or radio has the potential to brick your phone. The radio is used for controlling all the "wireless" functions (3G, 4G, x1 connections (texting/calling)) -- pretty much anytime the phone connects to the Sprint towers, the radio is playing its part. So if you flash it incorrectly; the consequences are obvious.
The kernel is the heart of the Android. The kernel itself is actually Linux. Android is built upon Linux, so pretty much Google took the already existing Linux kernel and built Android on top of it (the UI, the apps, etc) and made Android into a Mobile OS, which can run on virtually any platform or device.
How do you know? You don't -- it's a matter of wanting to be curious enough to test. Some devs will put out kernels that overclock your device, others will add different features (screen fixes, loopback interface, underclocking, etc). The kernel controls all the hardware on the phone and how everything functions -- so when devs mess with source code, they are essentially making the hardware function differently for your device.
Some of the major components? -- The biggest ones so far are the wireless driver and 4G driver. When the EVO came out -- the battery life wasn't great; but after the new update (1.47 and the accompanying radio's); battery life on the device have improved significantly and people have experience better WiFi reception and such.
Hope that helps.
Click to expand...
Click to collapse
That does help. This is my first time with android and my first time attempting to actually mess with it.
rafroehlich2 said:
That does help. This is my first time with android and my first time attempting to actually mess with it.
Click to expand...
Click to collapse
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!
pseudoremora said:
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!
Click to expand...
Click to collapse
The bug has already bit me. I appreciate the help. It's nice to know there is a community to get good answers from when needed.
Sent from my PC36100
pseudoremora said:
There will be a lot more "firsts", believe me. Some things will be harder than others; but if you stick with it and actually take the time to learn, you'll realize that working Android can be a helluva lot of fun and unbelievably addictive!
Click to expand...
Click to collapse
Instead of posting a new thread perhaps you can help me on this. When I attempt to use adb to remove a bundled app.
adb shell
cd /system/app
ls
rm app.apk
I get Disk space read only. I have full root and NAND I assume. I used the OTA method and am able to flash custom ROMs. I am using the rooted stock 1.47.651.1
rafroehlich2 said:
Instead of posting a new thread perhaps you can help me on this. When I attempt to use adb to remove a bundled app.
adb shell
cd /system/app
ls
rm app.apk
I get Disk space read only. I have full root and NAND I assume. I used the OTA method and am able to flash custom ROMs. I am using the rooted stock 1.47.651.1
Click to expand...
Click to collapse
When a "read-only" message is returned, it usually means that you don't have RW (read-write access), to circumvent this, run this command:
Code:
adb remount -- Should always be run if you plan on changing something that requires RW access
Then:
adb shell
cd /system/app
ls
rm app.apk
If for some reason you get a error message with adb remount (most likely due to permissions), then you'll need to use the full "remount" command, for that, run:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Hope that helps.
pseudoremora said:
When a "read-only" message is returned, it usually means that you don't have RW (read-write access), to circumvent this, run this command:
Code:
adb remount -- Should always be run if you plan on changing something that requires RW access
Then:
adb shell
cd /system/app
ls
rm app.apk
If for some reason you get a error message with adb remount (most likely due to permissions), then you'll need to use the full "remount" command, for that, run:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Hope that helps.
Click to expand...
Click to collapse
I tried your method, but I get another error. It looks like:
Code:
mac-mini:~ rafroehlich2$ adb remount
remount failed: Operation not permitted
mac-mini:~ rafroehlich2$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: exec /usr/sbin/mount_yaffs2 for /System: No such file or directory
Is there a preventable reason
Code:
adb remount
fails? Thanks for the help.
rafroehlich2 said:
I tried your method, but I get another error. It looks like:
Code:
mac-mini:~ rafroehlich2$ adb remount
remount failed: Operation not permitted
mac-mini:~ rafroehlich2$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount: exec /usr/sbin/mount_yaffs2 for /System: No such file or directory
Is there a preventable reason
Code:
adb remount
fails? Thanks for the help.
Click to expand...
Click to collapse
I figured you might have trouble with the ADB remount -- again, this is usually due to permissions. For testing purposes, try booting into recovery and then issuing the adb remount command.
In regards to the full remount command -- I'm wondering if you have busybox (it contains all the Linux command line tools) so that you can run the above commands.
Can you issue and then paste the output back here?:
Code:
cat /proc/mounts
Also, run this:
Code:
adb shell
cd /system/xbin
ls
If you can see a huge list of files -- then that means you do in fact have Busybox installed.
Also, what ROM are you running?
pseudoremora said:
I figured you might have trouble with the ADB remount -- again, this is usually due to permissions. For testing purposes, try booting into recovery and then issuing the adb remount command.
In regards to the full remount command -- I'm wondering if you have busybox (it contains all the Linux command line tools) so that you can run the above commands.
Can you issue and then paste the output back here?:
Code:
cat /proc/mounts
Also, run this:
Code:
adb shell
cd /system/xbin
ls
If you can see a huge list of files -- then that means you do in fact have Busybox installed.
Also, what ROM are you running?
Click to expand...
Click to collapse
After
Code:
cat /proc/mounts
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock4 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
tmpfs /app-cache tmpfs rw,size=8192k 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Code:
mac-mini:~ rafroehlich2$ adb shell
$ cd /system/xbin
$ ls
wireless_modem
dnsmasq
su
I download the BusyBox app to keep it up to date and also installed it through the "problems" section on titanium backup. However, that's all I got.
The ROM I am using is the fully rooted stock RUU. I'd post a link, but am not sure if I'm allowed to yet. It is the one posted by whitslack.
*****THIS IS FOR 2.1 ONLY*****
*****YOU MUST BE ROOTED*****
This will theme well over 90% of everything you see that has to do with the android os and blur if its still there.
Download my files here http://www.megaupload.com/?d=59KOD7MS
By downloading this you agree to take full responsibility for the actions you are about to preform.
Original files if needed http://www.megaupload.com/?d=0RNAMSQ3
If you have kousch's recovery installed, make a back up, if not use root explorer and make a back up of the following file.
/system/framework/blur-res.apk
download the other original system files here
Sorry no MM method only terminal emulator, so you have to suffer through typing about 10 lines of commands....
Unzip the entire contents onto your sdcard
open terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Services.jar /system/framework
cp /sdcard/framework-res.apk /system/framework
your phone will auto reboot. If you havent already applied a changed services or framework the boot animation will take a long time. If it by chance freezes, or does the boot sound but never shows the screen do a battery pull.
Once your phone reboots you will see a new lock screen and dark status bar with white font, if this is not the case you need to redo the steps above.
If you have root explorer, long press on the /system folder choose permissions. Make note of what permissions are set, grant everything permission for now. Change this back when your done. Failure to do so may cause an apk to not apply.
If you prefer you can reboot after each line command by simply typing reboot and hitting enter, just to make sure it boots clean, but its really not needed.
Put capitol letters when seen!!!! failure will cause duplicate applications!!!
Dont apply anything blur you deleted and dont want on your phone.
In terminal emulator
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurPhone.apk /system/app
cp /sdcard/BlurCalendar.apk /system/app
cp /sdcard/BlurContacts.apk /system/app
cp /sdcard/BlurHome.apk /system/app
cp /sdcard/Browser.apk /system/app
cp /sdcard/Gallery3D.apk /system/app
cp /sdcard/Music.apk /system/app
cp /sdcard/Settings.apk /system/app
this one goes to new directory so pay attention, dont get type happy
cp /sdcard/blur-res.apk /system/framework
now type reboot and hit enter
phone may or may not have an extended boot.
If you use handcent and want it themed, uninstall your old one
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.handcent.nextsms.apk /system/app
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Enjoy
Credit to
Me
prodigy
skyraider
tparker76
Teenfaces
stewart1champ
quadjacks
hacku
RinTinTigger
Taypotts
moto
htc
928droid
fabulous
I learned a lot from looking at how everyone else themed to get ideas for mine.
all images came from google searches. Then edited as needed.
reserved for me
please wait... an operator will be with you shortly...
Whens the download going to be up?
Ok. Now that i reverted to stock i can't get my themed google maps to install.... sucks. Also my themed launcher pro keeps my registation code. So if i release that its stealing. I will work on these two tonight and see what i can do.
Either way, a dl will be posted in the morning.
Sorry
Sent via your mom and tapatalk
Maybe try re-signing it then install via adb install command as per the the autosign.bat method in my other post.
ignorant question. Can i install this using Rom manager?
No sir. But you have rom manager and haven't switched to 2.2?
sent by your mom on tapatalk
Yep but I used sbf switched back to 2.1......2.2 had a few bugs that drove me crazy
Sent from my DROIDX using Tapatalk
running this theme
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
catalystsupreme2 said:
Ok backup made through rom mamnger. So im currently running rooted 2.1. Ive download the files and they are upzip on the root of the SD..can i simply type the codes in termnal emulator app on the phone and this should work?
Click to expand...
Click to collapse
yup just follow the codes in the OP, you can omit what ever you dont want.
bad4u6669 said:
yup just follow the codes in the OP, you can omit what ever you dont want.
Click to expand...
Click to collapse
Big thanks for the help..everything worked flawlessly..very beautiful theme
catalystsupreme2 said:
Big thanks for the help..everything worked flawlessly..very beautiful theme
Click to expand...
Click to collapse
any time, head over to my 2.2 thread for a few upgrades, they still work for users on 2.1
Hi,
I bought a Creative Ziio with the expectation that it would be rootable. However, I have searched the entire internet and there, unfortunately, isn't any app that can root the Ziio easily. The only clue I have is from these forums, by a member called bagienny, who posted that he managed to root his Ziio after gaining temporary root by using SuperOneClick. However, I have no idea how to replicate the rough steps which he posted, and I don't think he's active on these forums any more. Is there any one who can interpret his rough guide into usable steps for a novice user? I know it's not much to go on, but any kind of light shed would be wonderful...
I'm trying to root Ziio 7 unit I got for a review for PurePC.pl, and so far so good I installed SuperUser app and su and busybox binaries. Now using terminal I can su without any problems. But the thing is, SU only seems to be working in terminal emulator. I've tried using some apps that should use root like ShootMe and ScreenshotIt, SetCPU and they just doesn't work.
ShootMe says "Starting Server failed", plus info that i need to have root access and enabled access to lower graphics (whatever it is).
ScreenshotIt just doesn't work without any information why, and SetCPU FC's after selecting profile. Although it gets me a nice SuperUser dialog, but that's as far as it goes, cause it crashes right after that.
Am I missing something to have a complete root? Interesting thing is that on this device, preferred PATH for executable binaries is /data/busybox/, and not a usual /system/bin. Interestingly, my su binaries refused to work from /data/busybox directory, so I moved them to /system/bin. Rest of the utilities and such are still in /data/busybox, but I don't know if this information is important in any way.
Click to expand...
Click to collapse
OK, I know why su gave me permission denied when running from /data/busybox. The /data partition was mounted with nosuid. But still the applications such as ShootMe won't work.
Click to expand...
Click to collapse
SuperOneClick won't work by itself on Creative Ziio 7 Tablet, but thanks to the temprary shell root I was able to root it myself
Seems like the application is trying to get mountpoint for /system partition, but on this device, there's no /system. Instead there's /data partition in which are stored most of the system utilities, and the PATH /data/busybox has the highest priority when running commands globally. Moreover, the /data and / are mounted with nosuid option.
Click to expand...
Click to collapse
Maybe you can try to create symbolic links of the missing directories so it applies to the normal situation of the Android OS. I don't know if that device has the command 'ln' inside it. I'm going to a friend of mine to try to root the ZiiO of his wife to get the normal market on it. So thx for the info you wrote here it surely will be usefull for me. If i make some progress beyond your writing i'll post it here. I myself have a Xoom, and those things are scary easy to root. but also scary expensive .
I've had some progress on this as well but I've not gotten permanent root yet. I've also gotten most of the Google Apps on but wifi suddenly stopped working and the only cure was a factory reset.
So I'm back to square one. :-(
OK, I don't have enough posts yet to post in the development forums. I've gotten pretty far with SuperOneClick v1.9.1, but full root still fails.
Here's the log:
Running psneuter...
ROOTED
Pushing busybox...
3321 KB/s (1062992 bytes in 0.312s)
OK
chmod busybox...
OK
Getting mount path...
rootfs on / type rootfs (rw)
/tmp/nods/mmcblk_OS1 on / type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
none on /acct type cgroup (rw,cpuacct)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mmcblk_cache1 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk_data1 on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/vold/246:1 on /mnt/sdcard type vfat (rw,dirsync,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/246:1 on /mnt/secure/asec type vfat (rw,dirsync,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0602,dma
FAILED
I need help!
BUMP! Any ZiiO hackers out there?
Still no good ideas... I've tried using SuperOneClick and getting permanent root from there but have no idea how to do so.
Ah well...
I remember reading that ClockworkMod is available on the ZiiO market. Is that true? If it is then you could make a backup of your rom and try to hack it that way.
ziio
I just bought 10" version and I'm very disapointed with ROOT - hawe somenone rssolved this problem ?
Still no luck yet. I've been trying for a while but it just doesn't seem to be a device that anyone with skills cares about.
Yeah so this works. http://forum.xda-developers.com/showpost.php?p=15903421&postcount=5
Thanks so much!
BTW it appears that there's a way to get the Google Apps on the Ziio now too: www.androidtablets.net/forum/creati...-fully-working-android-market-ad-hoc-fix.html
Boys, you made my day.
Market + root now on my ZiiO
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
TheAtreus said:
I have the Pantech Discover
My phone is rooted because of WiFi issues
It only remembered the first 2 WiFi networks I came across after I bought the phone.
So I did all kinds of stuff to it to fix it. But I apparently screwed something up while fixing it, kind of. lol
Every time my phone restarts I have to go to the WiFi files and change the permissions in order for WiFi to turn on.
Other than that it works like a champ. This however isn't the problem.
I want to start fresh. Factory Rom would be great, but nobody has one.
There is an update to 4.1 jellybean for my phone OTA but It gets an error every time I try to update it.
Is there anything I can do?
ANY suggestions or help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
NOTE: Download and use the VooDoo OTA Rootkeeper application to temporarily unroot. You can use the app to restore root after the update. If you lose root several users have reported Framaroot 1.6 works with Jellbean, download here: http://forum.xda-developers.com/showthread.php?t=2130276.
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
sandnap said:
The update validates that dozens of files in /system including everthing in /system/app is there and unmodified. The user gj23 was kind enough to provide the original ICS /system files here: http://www.mediafire.com/folder/r3n3loxxlrv08/systemext4. I was able to help another user with the same problem get updated and suggest the following procedure.
Do this at your own risk. I do not recommend that you try to replace a file unless you are sure you removed or modified it or it shows up as invalid in the log. This can be tedious but far less tedious and risky than reconstructing the entire /system partition (voice of experience).
Dowload the JB update on the phone and choose to delay the update.
Install an sd card in the phone and using a root explorer copy the update to the external sd card. The update is called gota_package.bin and is in /cache/recovery.
Rename the file you copied to the external sd card to gota_package.zip.
Open the last_log file in the /cache/recovery folder with a text editor, scroll to the bottom, and look for a message indicating which file failed the checksum validation.
Download the valid version of the file that failed from the site I posted above. If there is a file with the same name in the same folder but with a different extension (e.g. myfile.apk & myfile.odex) dowload both.
Using a root explorer copy the file(s) you downloaded to the appropriate directory on your device.
Access recovery mode. To do this shutdown the phone, hold the volume up key and the power key down, when you see "pantech" flash on then off let go of the power button. You should be at the green robot screen, if not try again. From here, hold down power, press up volume, then let go of both. You should see a menu of options if not try again.
Use the volume keys to navigate to the option that allows you to install an update from the external sd card, press power, select gota_package.zip, press power again to run the update.
If the update fails go back to step 4 and repeat the process.
If you know which /system/app files you removed you can download and copy all of them (both apk & odex) at once.
Ask if you have questions.
Click to expand...
Click to collapse
Can someone provide the gota_package.bin file?
jose makalolot said:
Can someone provide the gota_package.bin file?
Click to expand...
Click to collapse
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
sandnap said:
Uploading gota_package.zip (renamed already), I'll PM you a link in a while.
Click to expand...
Click to collapse
thank you sir
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4
Wow... Totally lost hope in finding a solution.. I'm not sure which files have been modified due to me allowing apps to try and fix issues with my phone and getting the permissions to "stick" I'll take a look at what you've presented here and try to figure out which files I need to change
Sent from my PantechP9090 using xda app-developers app
attnav.apk first delinquent lol... I removed that soon after rooting.. so no surprise there. Ill let you know how it all goes
Update 1:
currently downloading (slowly) the update file.
While I wait I am checking my phones files with the list of files in the link above.
Ive created a mirror image of the folder structure on my computer where i download all the missing files in the appropriate folders. So far in the apps folder in the "A"s ive deleted 4 files family map.. the stupid driving app attnav and some other att bull..
I knew it would come down to this but wasn't anything I could do without the original files... THANK YOU GUYS sooo much
Update 2:
Final Count in the app folder was 16 missing files... Question. Should I remove the superuser.apk file?
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
TheAtreus said:
Well anyone who has this phone and does this... It works GREAT. BTW my root was still in place but superuser temporarily unrooted my phone and had rootkeeper enabled... I just unchecked temp unroot and its back in business...
Still does anyone know how to make the permissions stick... OR could Greg Jennings upload just the wifi files.
I know there are multiple files but all known associated files to the operation of wifi would be great. I was hoping this update would fix the issue but it didnt.
Click to expand...
Click to collapse
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
TheAtreus said:
Okay.... update worked... but now wifi isnt working... i cant change the wpa_ sup file to get wifi back on... sooooo anybody know how to root this version.. or possibly fixing the permissions on those GOD forsaken files so i dont have to keep changing them everytime i turn my phone on.
Click to expand...
Click to collapse
I updated the tutorial above to address maintaining root or rerooting after the update.
sandnap said:
What exactly do you do to get it working after a reboot? Can you access it with adb? More than likely you just need to mount the partition as read/write before making the changes
---------- Post added at 07:02 AM ---------- Previous post was at 06:50 AM ----------
I updated the tutorial above to address maintaining root or rerooting after the update.
Click to expand...
Click to collapse
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
TheAtreus said:
I got root back... luckily the superuser app is smarter than me.
When I turn the phone on, it wont even let the wifi turn on for a second... So I go to /data/misc/wifi and change the permission of wpa_supplicant.conf from rw-rw---- to rwxrwxrwx ... but it always reverts back if my phone ever turns off.
There are some other files I do the same way. I am doing this using ES File Explorer. Also that wpa file along with some others have root for the owner and for the group.
Im just tired of having to do that and remembering all the passkeys to all my friends networks because my phone cant.
Click to expand...
Click to collapse
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Alright will do
Sent from my PantechP9090 using xda app-developers app
sandnap said:
If you have adb access to the phone type (hit enter after each line):
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
If you don't have access to adb download the "Android Terminal Emulator" app from the Play Store, open it and type:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p25 /data
Now, make your permission changes, reboot, and report back. If that doesn't work give me the full path of all files causing the issue and I will write a script that will take care of it.
Click to expand...
Click to collapse
Okay i followed the directions.
I rebooted my phone first
Connected it to my computer after it finished booting
Opened my command prompt
made sure my phone was detected
Ran adb shell (said it was out of date)
Here is a copy of what I did
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p14 /system
mount -o rw,remount /dev/block/mmcblk0p14 /system
[email protected]:/ # mount -o rw,remount /dev/block/mmcblk0p25 /data
mount -o rw,remount /dev/block/mmcblk0p25 /data
[email protected]:/ #
Also here is a list of my mounts after reboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,relatime,data=orde
red 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,rel
atime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,relatime,noauto_da
_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatim
e,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000
,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=low
er,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
None of what i did before stuck
Here is a list of the files, the status of the files, and what I change on each file.
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O root G root CHANGED TO rwxrwxrwx (i didnt change the owner or group on any of them)
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi CHANGED TO rwxrwxrwx
/data/misc/wifi/wpa_suplicant/wlan0 STAYED AFTER TRYING YOUR FIX it is rwxrwxrwx O wifi G wifi
/dev/network_latency rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/network_throughput rw-rw---- O root G root CHANGED TO rwxrwxrwx
/dev/wcnss_wlan rw-rw---- O root G root CHANGED TO rwxrwxrwx
After reboot they all except the one I told you about changed back.
I honestly dont know what files do what for wifi... so I just changed these try and make the networks STICK... All I need to do to get wifi to actually turn on and act right is change that first file and it will turn on and take a network passkey and continue working until phone reboots. then i have to change the permissions again and re-enter the passkey for the networks.
Just read that wifi is controlled by the kernel.. When I rooted my phone (using the guide found here at xda ultimate... ) I believe it had the original ics kernel. Would that help?
Sent from my PantechP9090 using xda app-developers app
If you need any more information just let me know
Sent from my PantechP9090 using xda app-developers app
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
sandnap said:
The permissions and ownership for the same files on my JB discover are:
/data/misc/wifi/wpa_supplicant.conf rw-rw---- O system G wifi
/data/misc/wifi/WCNSS_qcom_cfg.ini rw-rw---- O system G wifi
/data/misc/wifi/wpa_suplicant/wlan0 rwxrwx--- O wifi G wifi
/dev/network_latency rw------- O root G root
/dev/network_throughput rw------- O root G root
/dev/wcnss_wlan rw------- O root G root
It looks like the ownership is different for the first file but you have the same ownership and equal or looser permissions on the rest of the files. Try changing the ownership of wpa_supplicant.conf:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /data
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
exit
exit
adb reboot
Click to expand...
Click to collapse
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
TheAtreus said:
That worked half way. Now I dont have to change any permissions in order to get wifi to turn on but now I have to enter in the passkey for the network every 3 minutes or so because it wipes it or something
UPDATE
Im the type to just fiddle with stuff till it works.. While this hasn't really fixed my issue it might explain whats going on more to you that know the inner workings of Android linux OS better than i do. After I type the passkey in for my wifi network I wait for it to connect and before it shuts off on me I restart my phone... I tried it with the regular connection I have and after that I was think OH maybe it just needed to restart to fix it so i tested with my 5G connection. I put the passkey in and turned my wifi off and then back on it lost the info for 5G and still had the regular... So I typed it in again and restarted my phone and now both are stored permanently (i assume)
Click to expand...
Click to collapse
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
sandnap said:
So it seems to be okay for now? It's strange that it wipes after a few minutes. In Settings > Backup & Reset do you have the "Back up my data" checkbox checked? It's a long shot but I wonder if it's synchronizing with the google server and your settings are being overwritten. If you have this selected you can try unchecking it. Have you tried doing a factory data reset?
On a different topic, have you tried booting to the recovery-evita.img since you updated to Jellybean? I am pretty sure they locked the bootloader with the JB update but wanted to confirm with others.
Click to expand...
Click to collapse
This is what I got when I tried
C:\Users\Atreus\Downloads>fastboot devices
6603452b fastboot
C:\Users\Atreus\Downloads>fastboot boot recovery-evita.img
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.656s
C:\Users\Atreus\Downloads>
So it looks like they patched that... If somebody wanted root their phone like our. they would need to revert back to ICS do you know how to do that?