Database Develop

Help a Captivate brother out?

Can Galaxy S users backup their bootup animations for me? I want to get rid of as much of the AT&T crap as possible.
They are as follows
Startup
/system/etc/PowerOn.wav
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
Thanks

here you go...
View attachment gt-i9000.zip
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother

Thanks! Going to try them out now

Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.

Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?
Sent from my GT-I9000 using XDA App

Didn't they free the brothers back in January 1865?

Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
decepticon said:
Just wanted to add that they work fine, now just to figure out how to flash a different boot image to get rid of the AT&T World Phone logo.
Click to expand...
Click to collapse

KJPDX said:
Why dont you flash with the GT-I9000 rom and say goodbye to At&t everything?p
Click to expand...
Click to collapse
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.

bestwebs said:
Hi,
How did you get these into the right folders?
What commands did you use?
Tried root explorer and su file manager and they won't paste ther files into system/etc or system/media.
adb gives a no access and can't use adb remount to push file.
So I am stuck.
Thanks
Click to expand...
Click to collapse
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
jodue said:
hm.i guess that would not be a good idea as they are not 100% the same. replacing the custom stuff is the easy and secure solution for the time being.
Click to expand...
Click to collapse
This is the reason why, the generic Galaxy S FW does not work with the Captivate.

Hi,
For some reason root explorer wouldn't paste these.
But I did figure out a way with adb.
I copied all 3 files to my sdcard 1st
These are the commands I used in case they are of help to anyone:
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9
mount -o rw,remount -t rfs /dev/block/stl9 /s
# busybox cp /sdcard/PowerOn.wav /system/etc
busybox cp /sdcard/PowerOn.wav /system/etc
and
D:\>adb shell
$ su
su
# mount -o rw,remount -t rfs /dev/block/stl9 /system
mount -o rw,remount -t rfs /dev/block/stl9 /system
# busybox cp /sdcard/bootsamsungloop.qmg /system/med
busybox cp /sdcard/bootsamsungloop.qmg /system/media
# busybox cp /sdcard/bootsamsung.qmg /system/media
busybox cp /sdcard/bootsamsung.qmg /system/media
Thanks
decepticon said:
I used Root Explorer and copied them. You would have to mount the /system folder with RW permissions in ADB or just click the Mount RW button in Root Explorer before copying them over.
This is the reason why, the generic Galaxy S FW does not work with the Captivate.
Click to expand...
Click to collapse

emclondon said:
here you go...
View attachment 368161
from GT-I9000;2.1-u1;JF3;2.6.29;ECLAIR
sorry for the delay, was testing other apps..
enjoy brother
Click to expand...
Click to collapse
Thanks for posting this, exactly what I was looking for!

BusyBoX

I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?

Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.

Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!

Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.

Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)

Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.

Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.

miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!

Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.

[MOD] 4.1.57 deodexed framework and app files (AT&T Only)

Here are the App and Framework system files for 4.1.57 fully deodexed.
You must already have Root access in 4.1.57.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Remember to make a backup of your existing framework and app folders BEFORE you do this.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Again, backup your original system/framework and system/app files BEFORE you do this in case you want to revert back to an odexed system.
Here is the correction:
Put your phone in USB Mass Storage Device mode.
Copy the app and framework directory and their contents from the zip file to the root of your sdcard.
***Verify the copy was successful before you continue.***
Set USB mode back to None.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /dev/block/mmcblk0p12 /system
reboot

Thanks, you beat me to it!

lindsaytheflint said:
Thanks, you beat me to it!
Click to expand...
Click to collapse
I deodexed them last night, but wanted to run through some testing before I packaged them up.
Anyone feel like scripting this, go for it.

I must have done something wrong in shell... soft brick, certain it was my fault.

tl_bull said:
I must have done something wrong in shell... soft brick, certain it was my fault.
Click to expand...
Click to collapse
Not your fault... I found an error in my instructions.
cp /sdcard/frame/* /system/framework/
should be
cp /sdcard/framework/* /system/framework/

rjohnstone said:
Here are the App and Framework system files for 4.1.57 fully deodexed.
Typical disclaimer as always...
USE AT YOUR OWN RISK.
This is for experienced users only please.
Link: Atrix-1.57deodexed IGNORE the instructions in the zip. Updated ones below.
Feel free to mirror.
Note: Photoedit.apk was pulled form the 1.26 Adeo file as the 1.57 version would not deodex properly.
This file did not change from 1.26. to 1.57, so I see no issue with using it.
Been running all day with these files with no issues.
UPDATE: The instructions contained in the zip have an error... oops.
This is why I don't write scripts. I type to fast.
Hopefully some of you guys caught that before entering the commands.
Here is the correction.
Copy the app and framework directory to the root of your sdcard.
Type the following commands via ADB.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Click to expand...
Click to collapse
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system

lpsi2000 said:
Another error with the commands
it should be the following for the mounts command:
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o ro,remount /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Thx. Updated OP.
The mount commands I originally posted did work for me without any issue though.
Sent from my MB860 using XDA App

It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.

Ririal said:
It looks like this isn't complete. There are some files in framework that you did not deodex, installing this on any phone will very likely brick.
Click to expand...
Click to collapse
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App

I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Edit:
Had to use usb port on the rear instead of the front when rooting.

zeyoner said:
I followed every step however when I attempt to run the following command
mount -o rw,remount /dev/block/mmcblk0p12 /system
I'm receiving Permission denied.
Click to expand...
Click to collapse
Sounds like you don't have root access.
Do you see a $ or a # in your command prompt?

i have $ in my root access... i'm getting permission denied at when i type 'su' but im pretty sure i rooted it earlier today
edit fixed i wasnt rooted

rjohnstone said:
What is missing?
Running on mine without any issues at all.
EDIT:
I see what you're talking about and it's a non-issue if you follow the commands to load them.
The 4 files missing from the framework folder were not odexed to begin with, so the originals will remain.
Remember, I'm not having anyone delete the entire contents of the framework folder, only the .odex files AFTER they copy over the deodexed versions first.
rm /system/framework/*.odex
These files are not odexed to begin with, so they are not touched.
blur-res.apk
framework-res.apk
moto-res.apk
android.test.runner.jar
You will also notice that 19 files are missing from the app folder as well... again, I'm not deleting any .apk files in the instructions, only the .odex files.
The 19 .apk files that are not included in my zip file are already present on a 1.57 system in a deodexed state.
I saw no point in adding them.
Make sense now?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yeah I looked it over again, should be fine.
EDIT: Nvm saw you updated.
I'm working on a new method to automate this, I'll post something when I have it working reliably.

looking for another way
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?

Very nice contribution!

Rad ryan said:
Question, possibly a dumb one but anyway it is. . . I couldn't get the script for root on update to work so if I go this route is it the same as getting from moto and is it possible to still have root with it?
Click to expand...
Click to collapse
This won't work without having root access first.
Sent from my MB860 using XDA App

I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.

Immix said:
I am still on 4.1.26 rooted and deodexed. Do I have to update my phone to 4.1.57 before copying the framework and apps folder? I know the script in OP won't work in my case but I can come up with another script. Thanks.
Click to expand...
Click to collapse
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.

shawnbuck said:
Right - this is only for 4.1.57. If you do it on 4.1.26 you'll get a soft brick.
rjohnstone, its always best to do stuff like this under Early USB Enumeration mode. It is possible to get it to stop the automatic rebooting by typing "stop" into the console.
Click to expand...
Click to collapse
Thx for the tip.
I did use the stop command in my process and was able to prevent a reboot.
The process is so quick that I didn't see a single FC during the copy.

I think it should be mentioned in the OP that root is required.

[HOWTO] Root HKTW 2.3.4 - The easier way

I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
Click to expand...
Click to collapse
3. Then, type and press enter:
su
Click to expand...
Click to collapse
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
Click to expand...
Click to collapse
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!

Will try and report if it works or not
Sent from my MB860 using XDA App

Well I know I shouldn't say it here...
But is the HKTW rom blurred or blurless?

Different kind of blur but its still blur
Sent from my MB860 using XDA App

Do you mean Blur 4.5?

I don't know what its called lol
Sent from my MB860 using XDA App

Trying it out now. Will report back.
And this has Blur on it. It's not a custom ROM.

Anyone else experiencing issues getting their phone recognize by adb
Sent from my Atrix 4g Ubl 2.3.4

su is throwing me a permission denied
http://pastebin.com/brXVEYDb

i guess i didn't phrase the instruction clearly. sorry. just edited first post.. reread everything and try again.

had to run it a few times.. but it worked! thx!

Works! 10char

reserved *10chars

su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
having the same issue with SU

Are there any other alternatives to root currently?

jimmer411 said:
su: not found
For some reason USB debugging does not seem to be working properly, even with stay awake checked.
EDIT:
An even easier way.
I decided to run beforeupdate.bat and afterupdate.bat and was able to successfully gain root access on hktw-2.3.4.
Click to expand...
Click to collapse
Can you be more specifically on those files? Where to download and how exactly did you go about running those files?

Do I need the SDK for rooting it?

THIS WORKS ON WINDOWS, OSX, AND LINUX
once you type in adb shell then type dosu instead of su and see if that helps

I get an error at the last part when I put it in cmd
Whenever I type in 'su', I get permission denied - and dosu doesn't work either.

[IDEA][Vivid] Possible Tethered Perma-Temp-Root Solution (Devs only!)

So, I just got this phone.
Not having permanent root is killing me, but I think this should solve the issue of disappearing su and busybox.
The general idea is to move all our root binaries to /data/local/bin, and remount /data to accept suid binaries (the 'su' binary requires sticky bit, aka chmod 4755). After you set that, you bind mount /system/xbin to /data/local/bin. Bind mounts stay in memory, and aren't cleared like mods to /system are.
This won't solve the issue of stuff in /system going away, but it will solve the issue of having your root utilities go away after a short amount of time.
This section would be run from the desktop PC on the first time of 'rooting' the phone:
Code:
adb install superuser.apk
adb push zergRush /data/local/tmp/zergRush
adb shell "chmod 755 /data/local/tmp/zergRush;/data/local/tmp/zergRush"
adb shell "mkdir /data/local/bin"
adb push su /data/local/bin/su
adb push busybox /data/local/bin/busybox
adb push temproot.sh /data/local/tmp/temproot.sh
adb shell "chmod 755 /data/local/tmp/temproot.sh;/data/local/tmp/temproot.sh"
and the 'temproot.sh' file would contain:
Code:
#!/system/bin/sh
mount -o remount,suid /dev/block/mmcblk0p34 /data
chmod 4755 /data/local/bin/su
chmod 755 /data/local/bin/busybox
cat /system/xbin/dexdump > /data/local/bin/dexdump
cat /system/xbin/wireless_modem > /data/local/bin/wireless_modem
/data/local/bin/busybox mount --bind /data/local/bin /system/xbin
on a reboot, all you'd have to run from the desktop PC would be:
Code:
adb push zergRush /data/local/tmp/zergRush
adb shell "chmod 755 /data/local/tmp/zergRush;/data/local/tmp/zergRush"
adb shell "mount -o remount,suid /dev/block/mmcblk0p34 /data"
adb shell "/data/local/bin/busybox mount --bind /data/local/bin /system/xbin"
and you'd be back to working.
let me know what y'all think, hopefully this solves something or isn't something already been done before
Thanks for looking!
EDIT:
upon discussing some other possibilities with a friend, he suggested "why not have this all happen on-device?"
it appears there may be a way to temproot/do the above all on the device without the need for a PC!
(dev details: adbd listens on localhost:5037, run zergrush then take adb client on phone connect to adbd on phone and run the temproot scripts)
exciting stuff here, folks!

This should work. If the device is killing any mods in the system folder just move it to the data folder. Just install superuser in the data/app.
Sent from my Sensation using XDA App

Sounds like an interesting idea. I've played around with moving su to different places with no luck, but I hadn't tried moving everything to /data. I'll try it and see if it helps!
Sent from my HTC PH39100 using XDA App

This works for my phone-- I've rooted it with this method, and rebooted then ran my 'on reboot' script, and the phone is good to go again.
Right now I'm working on a method to do all this on-device and at boot.
The process should work, since the zergRush exploit restarts the adb server as root, so in theory connecting to the adb server from the phone itself should give it root privileges.
Once you've got root privileges, the app can decide whether it's been 'rooted' before or not, and apply the proper script (either install busybox and su, or just re-mount the necessary partitions).
Hopefully this all makes sense, I'll try to make a proof of concept sometime soon... but I'll probably make a windows GUI first.

What about running a script that gives root on each boot
Sent from my Sensation using XDA App

you might talk to the guys that wrote the visionary root app that we used on the G2/desire z. i think it was paul obrien. it was an app that would do this on reboot for you.

Script Manager by devwom
Pirateghost said:
you might talk to the guys that wrote the visionary root app that we used on the G2/desire z. i think it was paul obrien. it was an app that would do this on reboot for you.
Click to expand...
Click to collapse
Sent from my Sensation using XDA App

Pirateghost said:
you might talk to the guys that wrote the visionary root app that we used on the G2/desire z. i think it was paul obrien. it was an app that would do this on reboot for you.
Click to expand...
Click to collapse
Speaking of visionary, has anyone tried that route yet?

malickie said:
Speaking of visionary, has anyone tried that route yet?
Click to expand...
Click to collapse
Tried Visonary no go.

So nice of thecubed to up and leave the revo community and not say anything. Great job thecubed!
I've been Supercharged and Gingervolted!

RootedUser said:
So nice of thecubed to up and leave the revo community and not say anything. Great job thecubed!
I've been Supercharged and Gingervolted!
Click to expand...
Click to collapse
Why you mad 4 bro?
Sent from my HTC PH39100 using xda premium

Not mad at all! "Bro"
I've been Supercharged and Gingervolted!