So I posted this previously a few hours ago and I got forwarded to the "how to" guide by jaekar99 from androidcentral on two ways to install bootanimation.
Flashing didnt' work because the zip wasn't designed for cwm.
I tried the root explorer method, and copy / pasted to my system\media root on my fascinate.
Both did not work.
I've searched long and hard for a fix but I've been drawing up blanks.
Can someone help? Thanks!
What kernel are you using? You have to have a kernel that supports custom boot animations.
Yes, you'll need to post up your setup to get help on this. Some kernels are able to change boot animation, some are not.
Also need to know what you are placing in there for boot animation - one of the ones floating around or custom?
Swyped on my Fascinate - please excuse any swypo's...
M00NEY said:
Yes, you'll need to post up your setup to get help on this. Some kernels are able to change boot animation, some are not.
Also need to know what you are placing in there for boot animation - one of the ones floating around or custom?
Swyped on my Fascinate - please excuse any swypo's...
Click to expand...
Click to collapse
I'm running frankenclean 2.9.2. voodoo with the pb&j kernel.
And the bootanimation I'm trying to run is that decepticon bootanimation.
I can't post links yet =/
Basically I flashing the bootanimation didn't work because it wasn't made for that, so I tried the alternative method and tried to copy \ paste it to the system \ media folder, but nothing happened.
Is the animation you're referring to the one where pieces come together to form the decepticon logo? I found it here at Android Forums:
http://androidforums.com/motorola-droid/29230-decepticon-droid-boot-animation.html
If so, I did try that out on my phone (SC 2.8 with JT's EC10 kernel) and it worked perfectly. I know that JT's EC10 kernel isn't exactly the same as the PB&J kernel, but it is the base for PB&J. I doubt imnuts would have removed this feature.
The other thing I can think of is that /system/ wasn't mounted as R/W when you tried to put the animation in there. Doing a search on it this morning, it looks like there are some issues with Root Explorer not correctly mounting /system/ as R/W. Some possible fixes mentioned were select R/O, then select R/W again or remove Root Explorer from the Superuser remembered list.
I personally use Super Manager, not Root Explorer. I have had no issues with it mounting /system/ as R/W. You could use Super Manager right now until the issue with Root Explorer is fixed or you find a good work around (like mentioned above).
Did you rename it to bootanimation.zip?
If you're trying to paste into /system/media you need to make sure /system is mounted as r/w as it is read-only by default. Probably why nothing happened when you tried to paste it there.
imnuts said:
If you're trying to paste into /system/media you need to make sure /system is mounted as r/w as it is read-only by default. Probably why nothing happened when you tried to paste it there.
Click to expand...
Click to collapse
That's exactly what it was. I could've sworn I put on r/w both times I tried this previously, but apparently I didn't.
Funny thing was, both times when I wasn't in r/w mode, it at least visually showed that I pasted the file there. I even went back into root explorer to double-check.
since I can not post directly in the discussion, I have to open a separate thread.
I used the file for dual touch using insmod and it worked.
Now I wanted to make sure that it is fixed with the phone, I read the procedure and tried to follow her, but I do not find any files bulid.prop ....
Where is it?
Please help me.
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Ray_jai said:
build.prop is in
root, system folder
tell me if it works for you, I tried this and I couldn't get it to work.
Click to expand...
Click to collapse
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Thanks! I found the file "build.prop",
Where is the other file "hw_config.sh"? Because what I found I had no voice "insmod" ...
Click to expand...
Click to collapse
hw_config.sh is in ur "etc" folder... are you using root explorer???
You do know you can use the search function OF the root editor too...
DomusX10 said:
using it without changing the files, it works QuickPic, Copilot.
In google maps does not work. Not even in browsers like Opera or Ninesky.
But I thought that by modifying these files, worked in the rest.
Click to expand...
Click to collapse
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
teapea said:
Not sure what ROM you're using, but you may need this file to get the other apps using dualtouch:
http://forum.xda-developers.com/showpost.php?p=13497850&postcount=49
Click to expand...
Click to collapse
this is the problem?? I've Stock ROM 2.1update1 with firmware 2.1.1.A.06
then, I have to create that file and copy it into /system/etc/permissions with rootexplorer...
now I try this...and you know I do!
EDIT: NOT WORKING...I have create that file (copy and paste the code in the frame in a txt file, and renamed android.hardware.touchscreen.multitouch.xml) then I've paste it into /system/etc/permissions and associated it permission rw-r-r
rebooted and not working...single touch.
yet launched from the console does the dual touch working in some applications ... why?
EDIT 2: Please do not send me to hell, but by creating the file and rebooting, if I launch "insmod" from the console, dual touch works in all apps!
How is it possible, however, that the changes to make it start with phone not work?
I want to work "even" when I restart the phone!
Did you try this version?
http://forum.xda-developers.com/showpost.php?p=13498769&postcount=56
I couldn't get it to work when doing it manually. but when I load it from the SD card through adb it works.
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Ray_jai said:
I ended up using the AAIS script and replacing the module in the AAIS with the one in the link.
Click to expand...
Click to collapse
I use that on the first post dedicated at my firmware 2.1.0.A.06
http://forum.xda-developers.com/showthread.php?t=1064558
manually loaded by terminal emulator work in every app. But, the procedure to autorun this module with telephone when start, don't work.
I do not know which is doing a script AAIS, because I'm not well prepared ... I do not know how to do it ...
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Ray_jai said:
use this.
http://forum.xda-developers.com/showthread.php?t=951274
Click to expand...
Click to collapse
thanks!
With this script you can enable and disable a lot of things ... I can just see if it works ...and let you know ...
I wanted to ask, but what is JIT? what does it do?
thank you in advance for availability ..
EDIT: Works!!! without launching the script, I went just to see how the command was written in the file "hw_config.sh" ...
I corrected, and after restarting, it works!
I was wrong because we put the quotes, but no need to write.
The correct lines of code to be included in the file "hw_config.sh" (at bottom) are:
# load multi touch driver
insmod /system/lib/modules/cy8ctma300_ser.ko
sleep 1
After you have copied into system/lib/modules "cy8ctma300_ser.ko" , mounted it as rw-rr , and edit the file "build.prop" as indicated in the post.
works!!!
thanks!!!!
Last time i flashed cm9 on my p7500 i had to remove the first line of the updater-script for cwm to flash it. now i got the same problem with an other build. i wonder if i could change it somehow without the need of a computer. root explorers text editor doesnt seem to work inside a zip file and fully extracting and repacking seems a bit to much for just little modifications.
got any advice for me?
Sent from my SGH-T859 using XDA Premium HD app
Tyrado said:
Last time i flashed cm9 on my p7500 i had to remove the first line of the updater-script for cwm to flash it. now i got the same problem with an other build. i wonder if i could change it somehow without the need of a computer. root explorers text editor doesnt seem to work inside a zip file and fully extracting and repacking seems a bit to much for just little modifications.
got any advice for me?
Sent from my SGH-T859 using XDA Premium HD app
Click to expand...
Click to collapse
Get root explorer, unextract to a folder, edit with notepad or text editor, then find a zip program to zip it back, Truth be told, why not just get something like WiFi Explorer so you don't need to bring the cable with you everywhere, do the changes on a laptop and send it via WiFI to the folder you want, Kinda like an FTP. It's zipping back that's the problem, most support for editing in zip's changes the permission which can cause issues later.
Hey.
Im trying to add Root Explorer to a ROM, so whenever I install that ROM, Root Explorer is installed. But Im having problems.
I tried adding Rootexplorer.apk to system/app but when I install ROM and try to run it, it force close and says something about (com.speedsoftware.rootexplorer)
Then I tried to add rootexplorer.apk to data/app
Doesn't appear installed.
I really don't know how to do it and need help. I don't know if im doing something wrong...
i think when you ad any .apk too system/app you need to change the permission to rw-r--r-- and then reboot it should work!!
ninad2407 said:
i think when you ad any .apk too system/app you need to change the permission to rw-r--r-- and then reboot it should work!!
Click to expand...
Click to collapse
The problem is that im adding the .apk to a .zip file
So I can't set any permission until I install that .zip
Camera.apk and mms.apk added to system/app and they worked.
Rootexplorer.apk won't =/
Tovagulet said:
The problem is that im adding the .apk to a .zip file
So I can't set any permission until I install that .zip
Camera.apk and mms.apk added to system/app and they worked.
Rootexplorer.apk won't =/
Click to expand...
Click to collapse
ive tried that some .apk's dont work like quickpic but i generally install root explorer not as a system app.But if its a zip then maybe some other problem !!
ninad2407 said:
ive tried that some .apk's dont work like quickpic but i generally install root explorer not as a system app.But if its a zip then maybe some other problem !!
Click to expand...
Click to collapse
Im sure I have used ROMs that come with root explorer installed.
Not sure how they did it, but there must be a way.
I download ROM.zip and trying to add rootexplorer.apk
thats it
Tovagulet said:
Im sure I have used ROMs that come with root explorer installed.
Not sure how they did it, but there must be a way.
I download ROM.zip and trying to add rootexplorer.apk
thats it
Click to expand...
Click to collapse
i think when you make a ROM you need a software that can also set the permissions in the zip file i had seen it yesterday but i dont remember the name
i saw it in the development section in a ROM making guide see if you can find it all the best !!
There's no need of any such software. Whenever a rom installs,all the required permissions are set automatically by the updater-script. And well, if you are planning to release the ROM on xda, Do *not* include root explorer in it. Root explorer is a paid app and adding warez to roms is not allowed on XDA.
Sent from my Nokia 1100 Classic
Can anyone tell me how to deodex Xperia Z2 6.0.1 firmware step by step? Thanks in advance....
+1
I am also looking for the same. On MM rom, Sony is using symlinks to link odex files.
A step by step guide would be highly appreciated.
Thank you
I'm not gonna go into deep details, but this should help.
- flash MM rom for your device, make sure it is ROOTED as you'll need to use an explorer with root access,it's better if you do this on a clean install, but this is just me
- boot your device and go through the setup process
- once done, install a browser with root access, I recommend MiXplorer, root explorer
- browse into /system folder
- check your /app, /framework, /priv-app, they should have odex files inside them (this was the case for me)
- copy these folders, plus build.prop file into sd card or the phone memory
- connect phone to pc and copy files over
- look up and download SVADeodexerForArtx(32 or 64 based on your system), you also need to have java installed on your machine.
- extract the SVADeodexerForArtxxx to your c: drive, and create a folder named /system insides, and post the files from your phone inside that
- your final folder will look something like this : c:/SVADeodexerForArtxxx/system/ (app, framework,priv-app) and build.prop file
- remember to move the Semcxxx app folder from /framework into /app folder or it won't be deodexed
- run SVADeodexerForArtxxx and point it to your /system folder, it will show you your android version, tick the checkbox for app, framework, priv-app, hit the start button
- it'll run and once done the log file will open and tell you how many were deodexed.
- the deodexed folders will be in the base folder, make sure to return the Semcxxx folder from the /apps to /framework
- create a flashable zip and flash these folders back on your rom
now your rom is deodexed
install Rom eXistenZ MM, rom is rooted and deodex
lokitooxd said:
install Rom eXistenZ MM, rom is rooted and deodex
Click to expand...
Click to collapse
The intention of this post was to learn how to do it. I know there is existenz and ultraslim deodexed roms. Thanks anyway.
@ticktock666
Thanks for the steps.
These steps looks to be from older version. Anybody with 6.0 Sony MM steps?
@ticktock666
There are certain other folders such as odex.app, odex.framework, odex.priv-app...what about these? These folders also contains similar odex files for app, framework and pri-app...
AlanDS said:
These steps looks to be from older version. Anybody with 6.0 Sony MM steps?
Click to expand...
Click to collapse
I deodexed my MM rom about a week ago, so I'm saying this from experience : it is up-to-date.
vikrant7027 said:
@ticktock666
There are certain other folders such as odex.app, odex.framework, odex.priv-app...what about these? These folders also contains similar odex files for app, framework and pri-app...
Click to expand...
Click to collapse
I'm not sure, but here's some of the stuff I noticed during the deodex process :
- I used to get the files using adb pull command directly to pc after a fresh rom install (remember to install a pre-rooted rom), but I did not get any odex files with the apps this way, so deodexing didn't work.
- after pulling the files from the device using a root explorer, each app had the odex files with them inside the correct folders.
- about odex.xxx folders and odex.xxx.sqsh files : they contain an exact duplicate of the odex files, no idea why (you can extract the sqsh files, they're basically special compressed odex file container sort of thing), which means the rom contains 3 versions of the same odex file, makes no sense.....
after deodexing and flashing the deodexed rom/files, I deleted odex.xxx folders and odex.xxx.sqsh files, and my rom works fine, fully rooted and with xposed. My current issue is that now if I browse into /data/app on the root of the drive I'll find an odexed version of every app I have installed, be it a user app or system app, and it's driving me crazy.
ticktock666 said:
I deodexed my MM rom about a week ago, so I'm saying this from experience : it is up-to-date.
I'm not sure, but here's some of the stuff I noticed during the deodex process :
- I used to get the files using adb pull command directly to pc after a fresh rom install (remember to install a pre-rooted rom), but I did not get any odex files with the apps this way, so deodexing didn't work.
- after pulling the files from the device using a root explorer, each app had the odex files with them inside the correct folders.
- about odex.xxx folders and odex.xxx.sqsh files : they contain an exact duplicate of the odex files, no idea why (you can extract the sqsh files, they're basically special compressed odex file container sort of thing), which means the rom contains 3 versions of the same odex file, makes no sense.....
after deodexing and flashing the deodexed rom/files, I deleted odex.xxx folders and odex.xxx.sqsh files, and my rom works fine, fully rooted and with xposed. My current issue is that now if I browse into /data/app on the root of the drive I'll find an odexed version of every app I have installed, be it a user app or system app, and it's driving me crazy.
Click to expand...
Click to collapse
Can u make a deodex rom for Xperia z2 mm rom d6502 indian version and post it on gdrive?? thanku in advance..? @ticktock666
Silverstarjigar said:
Can u make a deodex rom for Xperia z2 mm rom d6502 indian version and post it on gdrive?? thanku in advance..? @ticktock666
Click to expand...
Click to collapse
sorry buddy, but although just the deodexed files from my rom should work perfectly (it's only the apks, no other settings from the rom are included), it is near impossible for me to upload anywhere due to slow & unstable connection and power situation, since none of the hosting services support upload resume on their apps/sites.
ticktock666 said:
sorry buddy, but although just the deodexed files from my rom should work perfectly (it's only the apks, no other settings from the rom are included), it is near impossible for me to upload anywhere due to slow & unstable connection and power situation, since none of the hosting services support upload resume on their apps/sites.
Click to expand...
Click to collapse
Okk.. I will give it a try then!
Is there any script or something that we can flash through recovery ?
do you mean a script to deodex the rom on the phone ? if so then the answer is no
You can try this
ticktock666 said:
I'm not gonna go into deep details, but this should help.
- flash MM rom for your device, make sure it is ROOTED as you'll need to use an explorer with root access,it's better if you do this on a clean install, but this is just me
- boot your device and go through the setup process
- once done, install a browser with root access, I recommend MiXplorer, root explorer
- browse into /system folder
- check your /app, /framework, /priv-app, they should have odex files inside them (this was the case for me)
- copy these folders, plus build.prop file into sd card or the phone memory
- connect phone to pc and copy files over
- look up and download SVADeodexerForArtx(32 or 64 based on your system), you also need to have java installed on your machine.
- extract the SVADeodexerForArtxxx to your c: drive, and create a folder named /system insides, and post the files from your phone inside that
- your final folder will look something like this : c:/SVADeodexerForArtxxx/system/ (app, framework,priv-app) and build.prop file
- remember to move the Semcxxx app folder from /framework into /app folder or it won't be deodexed
- run SVADeodexerForArtxxx and point it to your /system folder, it will show you your android version, tick the checkbox for app, framework, priv-app, hit the start button
- it'll run and once done the log file will open and tell you how many were deodexed.
- the deodexed folders will be in the base folder, make sure to return the Semcxxx folder from the /apps to /framework
- create a flashable zip and flash these folders back on your rom
now your rom is deodexed
Click to expand...
Click to collapse
But with file odex.app.sqsh format...are that no need to extract
Sent from my D6503 using XDA-Developers mobile app
A1nur said:
But with file odex.app.sqsh format...are that no need to extract
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
sorry for the late reply, haven't been checking much recently.
now about those sqsh files, I've tried extracting them, and they seem to contains a 2nd copy of the odex files, not sure how they work, but after deodexing my rom I simply deleted them, and everything worked normally.
ticktock666 said:
sorry for the late reply, haven't been checking much recently.
now about those sqsh files, I've tried extracting them, and they seem to contains a 2nd copy of the odex files, not sure how they work, but after deodexing my rom I simply deleted them, and everything worked normally.
Click to expand...
Click to collapse
In new build fw 291 i try deodex that rom sir, n i do not extract sqsh.file...all normally work but if i delete boot.art n boot.oat it butlop....
How to i delete that sir
A1nur said:
In new build fw 291 i try deodex that rom sir, n i do not extract sqsh.file...all normally work but if i delete boot.art n boot.oat it butlop....
How to i delete that sir
Click to expand...
Click to collapse
I don't have the latest rom yet (not released for 6502), but when you go into your /system/app folder using a root explorer, do you see "arm" folder inside any of the installed apps ? maybe they changed something in 291, and now they only use sqsh files, also what does the log from the app says when you deodex the rom says ? it should say something like "300 apps deodexed, 10 apps already deodexed" or something like that.
ticktock666 said:
I don't have the latest rom yet (not released for 6502), but when you go into your /system/app folder using a root explorer, do you see "arm" folder inside any of the installed apps ? maybe they changed something in 291, and now they only use sqsh files, also what does the log from the app says when you deodex the rom says ? it should say something like "300 apps deodexed, 10 apps already deodexed" or something like that.
Click to expand...
Click to collapse
Thanks sir for your answered...
Sent from my Sony Xperia Z2 using XDA Labs
Hi!
Thanks, for good instructions!
It is also working for Xperia Z3 Compact on MM .291. I failed in the past, cause of forgetting 'semcxxx' in framework.
Greetz, brockn