Database Info

Droid 2 Bootanimation

OK so i put this in and it works like a charm...... i am running CM6-RC1 with BF Kernel and again it works like a charm....
i did not make this...... just felt like i should share the love....
Steps i took to put this in...
adb pull bootanimation.zip
deleted it from the adb tool folder
adb push this back to /system/media...
adb reboot and enjoy......
if anybody knows how to put the mp3 in and make it work let me
know i have it.....
Ps... i would like to have the sound in it but cant get it to work
if you know how to do it please let me know.......

This looks awesome thenx 4 sharing

cool.... let me know if it worked for you.....

Np..ill do it in like 10 min

not working on 9/1 nightly for me hmm this might make me flash rc1 to test

xII v EnFamouz 2 IIx said:
not working on 9/1 nightly for me hmm this might make me flash rc1 to test
Click to expand...
Click to collapse
What do you get your old one or solid black screen...
Sent from my HERO200 using XDA App

i got it i just needed to reboot...probably sumthing with my phone

Yeah I had to do the same.... now If I can only figure out how to put the sound it would be great...
Sent from my HERO200 using XDA App

Big-O-Devil said:
Yeah I had to do the same.... now If I can only figure out how to put the sound it would be great...
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
This might help? http://forum.xda-developers.com/showthread.php?t=747145

yeah so i think i have tried almost all the ways that i can fine... and still no luck.... so again if anybody out there knows how to add sound to this please show me the way to salvation......please........

Thanks for the bootscreen.

Works great (no sound, which I prefer)!
Thanks!

read-only file system
even after setting my android-sdk-windows to have the read only box unchecked I still get an error in the cmd prompt saying i have a read-only system

Vandelay007 said:
even after setting my android-sdk-windows to have the read only box unchecked I still get an error in the cmd prompt saying i have a read-only system
Click to expand...
Click to collapse
yeah i got that to.....you have to exit and keep on trying... like i said it happened to me to and on the second try i got it....

do you mean to keep re-trying the command prompt or keep retrying setting the folder so its not read-only

Vandelay007 said:
do you mean to keep re-trying the command prompt or keep retrying setting the folder so its not read-only
Click to expand...
Click to collapse
i think the problem is the whole adb thing.... exit out of your command prompt and try again.... it should go....

Being so new at this - only a month with a rooted hero - I didn't think to change my folder permissions on the phone level - so I went into Root Explorer and changed it to R/W - and it gets further than I had before - but no file transfer takes place
This is what I'm typing into cmd
adb push c:\bootanimation.zip \system\media
then I get: 950kb/s - (0 byes in ###s)

adb push bootanimation.zip /system/media

when I do that I get 'no such file or directory' which folder should I have the .zip in to make this easiest ? I just have it in c: right now

Vandelay007 said:
when I do that I get 'no such file or directory' which folder should I have the .zip in to make this easiest ? I just have it in c: right now
Click to expand...
Click to collapse
Go to you c :/ drive then into your sdk folder then into your tools folder and put it in there...
Sent from my HERO200 using XDA App

[Q] CWM feeling like a newb

I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?

BGVampire said:
I downloaded everything in the cwm final
I used file manager to overwrite the old files and when I boot into recovery I still get the old recovery and not cwm
There is also nowhere for me to instal from update.zip
I have done this on my evo and it was easy but I'm clearly missing something with my galaxy 4g would someone be so kind as to give step by step instructions?
Click to expand...
Click to collapse
reinstall packages

krylon360 said:
reinstall packages
Click to expand...
Click to collapse
No fair you beat me to it.....duh winning..
Sent from my SGH-T959V using XDA Premium App

krylon360 said:
reinstall packages
Click to expand...
Click to collapse
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card

wrecless said:
and yes you must reinstall packages every time you want to re-enter CWM so you must leave the update.zip on you SD card
Click to expand...
Click to collapse
Thank you for your post. Common knowledge I know but a great reminder!
Sent from my Galaxy s 4g

can't flash CWM recovery
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?

sarfrazhc said:
everytime i boot into recovery, i selected reinstall packages, then i get error : signature verification failed!
am I missing something? I have EVO too, it wasn't that difficult to install CWM.
anybody can help me by pointing to things I might have missed?
Click to expand...
Click to collapse
recovery.bin probably isn't being overwritten correctly. At first I downloaded the file with Dolphin Browser and had the same problems. Try downloading the file with firefox and then try pushing it to /system/bin again.

probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.

sarfrazhc said:
probably recovery file is not being copied in system/bin folder. i can see it has only read permission for group and write permission. i tried rom manager permission fix, that didn't change permission of recovery. i tried changing from terminal using chmod +w & chmod 755. but that didn't help change the permission on recovery file.
Click to expand...
Click to collapse
Rom Manager isn't working for the Galaxy S 4G yet.
What application are you using to copy recovery to /system/bin?

typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.

sarfrazhc said:
typically i use ES explorer but i tried File Expert too.
one typo on my prev post: i don't have write permission on recovery, only got read permission.
Click to expand...
Click to collapse
ES won't work. File Expert should work. Just make sure you have R/W permissions. Don't do anything with Rom Manager. That won't help.

yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!

sarfrazhc said:
yea it should work as they say but it does not. I tried changing permission using File expert,it click OK and then i check file permission on recovery right away, the write permission is not checked. even chmod 755 failed to change the write permission!
Click to expand...
Click to collapse
I don't think you have any problems with R/W. I just don't think the recovery file was overwritten. Look in /system/bin in File Expert. Do you see recovery and recovery.bin? Or just recovery?

/system/bin/recovery file exists and i have been trying to change its permission.

sarfrazhc said:
/system/bin/recovery file exists and i have been trying to change its permission.
Click to expand...
Click to collapse
You don't need to change the permission of recovery. Copy the recovery file and navigate to /system/bin in file expert. When you get there you want to hit menu then more then mount. It will give you two options. Pick mount as read write. Then paste the recovery file.
Read through this thread again. It should help.
http://forum.xda-developers.com/showthread.php?t=1099374

mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...

sarfrazhc said:
mounted with read/write and now i could boot into recovery.
Thanks a lot for taking time to answer my questions. First backup is in progress...
Click to expand...
Click to collapse
No problem man.

Deodexing (FOR ALL GB ROMS) Most simplest & in detailed explained

Its not a repost guys. I created this thred only for quick view for new android users.
1. You must have java runtime enviornment installed on your computer.
2. You must have a rooted froyo or gingerbread firmware.
3. When we use xultimate 2.2 we must have our phone into USB debugging mode.
4. First u do xutimate procedure as kkrazzy has said.
-Run option 1. After option 1 is done, run option 2.
-Now these well take a while. Run option 3.
-IMPORTANT: After you have run option 3
-Now run option 4, and wait.
-Exit xUltimate, and put the phone in USB mass storage.
-Go back into the xUltimate folder and copy "done_frame", and "done_app",
and move them to the root of the internal sdcard not in the external sd.
-Now again connect phone into usb debugging mode.
5. I suggest that if anybody dont have SDK on their system then dont worry. Insted of SDK simply use adb.exe file which is in the superoneclick folder.
Go into SuperOneClick-->ADB folder. There u will get adb.exe file.
6. Take that whole adb folder & copy it to C drive path (U can keep it anywhere) including other files inside that folder.
Means u will get path of adb file as C:\adb\adb.exe
7. Now enter into command promp.
8. There u will see a path like C:\document and settings> (This path may be different for someone else. Thats not important)
9. This is very impotant step. Simply write there as
cd C:\adb\
Then in next line write adb shell.
You will see a msg on screen demon started successfully.
10. Thats it. You have entered into adb command mode.
11. Now remember by default # sign is always there at start of each line when u enter into adb command mode. Dont write it again in any command command...!!!
12. Now one by one run command
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
13. You will observe that after writing second command # stop your device will get hang. It will not at all respond. If that happens then u r going in right direction. Phone will hang till end of command.
14. Last command # reboot will restar ur device. But sometimes it will not. U will see a msg on computer screen as reboot returned. Dont worry. Simply Disconnect & restart phone.
15. Thats it guys. U will get a deodexed phone.
16. To check whether it is deodexed or not simply go into system->app folder. There u will see only .apk files. U will not at all observe .odex files there.
THIS IS SIMPLEST WAY I HAVE EXPLAINED. HOPE NOW NO ONE WILL FACE DIFFICULTIES IN DEODEXING.
PRESS THANKS IF THIS IS HELPFUL FOR YOU

Good job! But about XXKB3 fw you are wrong. Deodexing can be with any fw. We need only rooted phone

what the problem with the cmd???
i dont know why my cmd cant run ><
not recognized as an internal or external command, operable program or batch file
....

Dude why you have made a similar thread

falex007 said:
Good job! But about XXKB3 fw you are wrong. Deodexing can be with any fw. We need only rooted phone
Click to expand...
Click to collapse
Yep thats right, better update your post vishal.

please dont post similar threads..

updated post

vishal24387 said:
updated post
Click to expand...
Click to collapse
Thanx buddy for your valuable explanation..

Tbh, this does have what kkrraazzyy's thread lacked

Misledz said:
Tbh, this does have what kkrraazzyy's thread lacked
Click to expand...
Click to collapse
Sure yes! It is a lot more simpler for noobs ( like me ) to understand....I did it through kkrraaxxyy's post...But it helped ma friend thouhg

kkrraazzyy said:
Dude why you have made a similar thread
Click to expand...
Click to collapse
sorry kkrazy. I dont wanted to post this as saperate thread. Actually I wanted to post this in ur thread but I thought people will feel difficult to find a particular post through lots of pages. Hope u will understand my intention.

dude, thanks for the info about the adb.exe.. never thought of that before.. i went through hell downloading the needed files when yet there was a simple method.. thanks alot.! Liked the OP bdw..

ephraim033 said:
dude, thanks for the info about the adb.exe.. never thought of that before.. i went through hell downloading the needed files when yet there was a simple method.. thanks alot.! Liked the OP bdw..
Click to expand...
Click to collapse
Its my pleasre to help u. Actually I was also facing problem related to adb.exe. I also dont like to download big files. what about OP bro? I dont understand.

vishal24387 said:
Its my pleasre to help u. Actually I was also facing problem related to adb.exe. I also dont like to download big files. what about OP bro? I dont understand.
Click to expand...
Click to collapse
OP means original post bro.. .. i already pressed the thanks button

Oh...I really dont know about OP. Anyway thanx bro for telling me.

vishal24387 said:
Oh...I really dont know about OP. Anyway thanx bro for telling me.
Click to expand...
Click to collapse
no problem dude.. glad to help

vishal24387 said:
5. I suggest that if anybody dont have SDK on their system then dont worry. Insted of SDK simply use adb.exe file which is in the superoneclick folder.
Go into SuperOneClick-->ADB folder. there u will get adb.exe file.
6. Take that adb.exe file & keep in C drive path (U can keep it anywhere). I will tell u that make a new folder. Give it name as 'adb folder'. Then in this folder keep your adb.exe file.
Means u will get path of adb file as as C:\adb folder\adb.exe
Click to expand...
Click to collapse
Bro, i suggest you edit your post.. tell them to copy the whole adb folder not just the adb.exe.. the .exe needs the other program to work.. just my opinion.. i tried just copying the .exe but to no avail.. once i copied the whole folder it works..

ya I think u r rite bro. I will quickly update my post. Thanks bro.

vishal24387 said:
ya I think u r rite bro. I will quickly update my post. Thanks bro.
Click to expand...
Click to collapse
No problem dude

I updated post bro. Check it plz. If there is any problem in post plz inform me.

[ASK] (MOD)(PORT)Beats Audio&Xloud

Hi Guys...
i found an interesting thread..
_http://forum.xda-developers.com/showthread.php?t=1525226
is that work for stock ROOM ?
i use samsung galaxy ace GT-S5830 2.3.6 and have installed CWM recovery
but when i try to install zip from sd card, the error appears..
what should i do ?
thanks..

androidrealsteel said:
What is the error?
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Hi androidrealsteel, thx for your response..
the installer says :
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/allandroid.zip
(status 0)
installation aborted.
anything wrong ?

Did you try the 'Samsung only' package in that thread?
Also: 'If it doesnt flash you can use root explorer and put the files in the right place till i make a flashable zip'

juzz86 said:
Did you try the 'Samsung only' package in that thread?
Also: 'If it doesnt flash you can use root explorer and put the files in the right place till i make a flashable zip'
Click to expand...
Click to collapse
Yes I did..but it doesn't work too..
where is the 'right place' ? can you tell me the detail, please..
ups..got it
1.download zip
2.unzip using root explorer
3.multi select files
4.go into system and paste were they exp system/bin-system/etc-system/libs
5.reboot phone fix permission in recovery

dix.cloud9 said:
Yes I did..but it doesn't work too..
where is the 'right place' ? can you tell me the detail, please..
ups..got it
1.download zip
2.unzip using root explorer
3.multi select files
4.go into system and paste were they exp system/bin-system/etc-system/libs
5.reboot phone fix permission in recovery
Click to expand...
Click to collapse
That's it! You beat me to it! Just extract the zip and copy/paste the files onto your device in the exact folders they appear in the zip

Thank You
juzz86 said:
That's it! You beat me to it! Just extract the zip and copy/paste the files onto your device in the exact folders they appear in the zip
Click to expand...
Click to collapse
Thx 4 your help juzz86..
i'll try it and hope everything is well

Glad to be of service, hope it all works out for you!

[TUT] V6 SuperCharger & Kickass Kerneliser Scripts & init.d Tutorial [All Devices]

[TUT] V6 SuperCharger & Kickass Kerneliser Scripts & init.d Tutorial [All Devices]
For Tipo/Dual/miro/J/E
Hi all just wanted to share this because i dint see any threads on it. old android users like me will no what these are but for new users these scripts will install new tweaks and performance enhancements to stock rom & kernel. you have to install script manager from google play to run these scripts. all thanks go to the original author Zepp make sure you thank them.
init.d Tutorial
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel.
5. Root Explorer or any other similar app.
Instructions:
1. Download the zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as r.w.e, r.x.e, r.x.e
OR
b. If the file install-recovery.sh is already here, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip i've repacked it to work it flashes to xperia j don't know about Tipo/Dule/Miro
if it doesn't extrack and push the files to there relevant places in /system.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
All credits for this tutorial go to iridaki & Doomlord. i just copied and pasted for new users & people who don't like searching to make it easier to find.
Original Thread: http://forum.xda-developers.com/showthread.php?t=1422061
First Time SuperCharge Tutorial
First of all downloads go here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 and download V6 supercharger update9 rc12, kickass kerneliser update 3 rc11 & the supercharger starter kit Rc12 zip and move them to the root of your sd card. then download & install script manager from google play.
Applying SuperCharger Starterkit
Next extract supercharger starterkit.zip to the root of your sd card (the easyest way would be with root explorer). Then open script manager and click browse as root then select ok. next navigate to sdcard and click StartMeUp.sh that was extracted from the zip (it will prepare your rom and install the features from the zip at onece) click the su icon (This is superuser) then click run grant the superuser prompt and follow any on screen instructions. after script has finished exit out by clicking the X icon in the top lefthand corner. You should be using the new RC12 this one gives you the option to install which features you want if your on jb all you need is the zipaline binary the bussybox and the su binary is for a fault in ics also if your USING SUPER SU DO NOT INSTALL THE SU BINARY AS SUPER SU USES A DIFFARENT BINARY!!!
Running V6 SuperCharger & KaK Scripts
Note if you have init.d do not follow the run at boot part. as the 99supercharger.sh & 98kickasskernel.sh scripts will run as shell scripts at boot.
In script manager navigate to where you saved V6 superCharger then select it then use the same prosses click the su icon then run follow all on screen instruction and choose which options you would like. do the same for the kak script. after you have ran both scripts in script manager navigate to the file v6 supercharger wich will have been created in the internel sdcard. Find 99supercharger.sh we want to run this scrip at boot so select it press su and this time the boot icon then run grant superuser prompt if requsted then let the script finish following any instructions then exit out. Do the same for 98kickasskernel.sh. then reboot. you should now be supercharged.
init.d is 100% recommended so follow that first
This is what i have done and has worked for me. Follow At Your Own Risk I Am Not Reponsable For Any Damage Your Device Suffers
V6 SuperCharger Original Thread: http://forum.xda-developers.com/showthread.php?p=16635544#post16635544
New V8 SuperCharger Is In Alpha Stage So Use At Your Own Risk
V8 SuperCharger Original Thread:http://forum.xda-developers.com/showthread.php?t=1250276

For tipo only or evry phone
Sent from my ST21i using xda app-developers app

tusharkulkarni008 said:
For tipo only or evry phone
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
For every android device mate

Re: V6 SuperCharger & Kickass Kerneliser Scripts. + New V8 Supercharger
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app

tusharkulkarni008 said:
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
Do you mean v6 starterkit

Re: V6 SuperCharger & Kickass Kerneliser Scripts. + New V8 Supercharger
+1
Sent from my GT-I9000 using Tapatalk 2

tusharkulkarni008 said:
Is it ok to manually replace the files from startup pakage
Sent from my ST21i using xda app-developers app
Click to expand...
Click to collapse
sorry im not to sure about that. backup and have a try

What is the purpose of this? Sorry for the noob question. And will this work on cm10?

exelion04 said:
What is the purpose of this? Sorry for the noob question. And will this work on cm10?
Click to expand...
Click to collapse
the main purpose ive used it for is to stableise stock xperia roms ive used it since my xperia x8 from 2010 it even helped minicm 7 on it. the slight modifications to the rom kernel and 3g network is defiantly apparent. if u want to run it on cm10 then make sure u download the jb script the main thing i use it for is the home screen redrawing but when rom is 100% SuperCharged thats a thing of the past im not an expert with these scripts but there useful thats why ive shared the links.

Not Working.
When ever I try to run the StartMeUp.sh it with the root access it carries on running for infinity time . Dont know whats wrong with me.

RounakCreationz said:
When ever I try to run the StartMeUp.sh it with the root access it carries on running for infinity time . Dont know whats wrong with me.
Click to expand...
Click to collapse
Is it showing any errors when its running.

Added
init.d tutorial added

Re: V6 SuperCharger & Kickass Kerneliser Scripts & init.d Tutorial
Startmeup.sh runs towards singularity dosent stop
noob and learning

tusharkulkarni008 said:
Startmeup.sh runs towards singularity dosent stop
noob and learning
Click to expand...
Click to collapse
Ive never heard of that happening before I will look into it when im home from work

I installed supercharger 6 with Die hard launcher...the system works very well but I don't if is coincidence but I see that battery drains faster than without supercharger :S is it normal?

ercea said:
I installed supercharger 6 with Die hard launcher...the system works very well but I don't if is coincidence but I see that battery drains faster than without supercharger :S is it normal?
Click to expand...
Click to collapse
yes if the battery tweaks are not installed did you install them

gavster26 said:
yes if the battery tweaks are not installed did you install them
Click to expand...
Click to collapse
Are you referring the Die Hard battery calibrator script? I installed but I don't know if I did it well. The steps that I did was:
- Charge battery up 100%
- Run Die hard calibrator and execute the "wait 20 mins" option
After that, system restarts... but I didn't see any success/error messages and I don't know if it's working. If the steps are incorrect, please, can you say me the correct process??
Regards!

ercea said:
Are you referring the Die Hard battery calibrator script? I installed but I don't know if I did it well. The steps that I did was:
- Charge battery up 100%
- Run Die hard calibrator and execute the "wait 20 mins" option
After that, system restarts... but I didn't see any success/error messages and I don't know if it's working. If the steps are incorrect, please, can you say me the correct process??
Regards!
Click to expand...
Click to collapse
wich script of v6 supercharger are you using it should be update9 Rc11. im not finding that option you should be using that one. you will get abit more battery drain more performance = more power.

tusharkulkarni008 said:
Startmeup.sh runs towards singularity dosent stop
noob and learning
Click to expand...
Click to collapse
hi ive trawlled the web i have not found anyone ever having that problem. you can try reinstalling script manager and installing busybox from google play. i no startmeup.sh installs busybox 1.19.4 withdrawu but it will help sorry if this is not much help as i say in tutorial i did not create it i just shared it. if problem persists then your device may not be properly rooted. if all else fails go to v6 original thread and ask zepprinox

gavster26 said:
hi ive trawlled the web i have not found anyone ever having that problem. you can try reinstalling script manager and installing busybox from google play. i no startmeup.sh installs busybox 1.19.4 withdrawu but it will help sorry if this is not much help as i say in tutorial i did not create it i just shared it. if problem persists then your device may not be properly rooted. if all else fails go to v6 original thread and ask zepprinox
Click to expand...
Click to collapse
it can be made flashable just a suggestion