i try this on the comment prompt while phone running.
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
and it'll say:
rm failed for -f, read only file system
it wont let me write on the system im guessing.
Now i tried doing the same thing but phone mode is on recovery.
I have the nand protection unlocked so when i get to recovery mode
i have already the custom recovery setup showing, i don't run the recovery-windows.bat.
now when i type this on the comment prompt
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
after i hit enter it shows me
#
so im assuming the apk. has been removed
after i exit the comment prompt and i wipe the dalvik-cache
i reboot the phone and all the apps i removed are still there and running still.
help please
1. Prepare a short mp3 and name it android_audio.mp3
2. Put the mp3 under the adb folder
3. Save the following code as !bootaudio.bat (I use this name)
4. Turn your phone into ADB debugging mode
5. run !bootaudio.bat
6. Reboot your phone and have fun!
This should work on almost all G7
Tips: During the boot animation, the volume would change twice. So I suggest insert 1 second before the audio for escaping from the volume changing side-effect.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb shell rm /data/local/android_audio.mp3
adb push android_audio.mp3 /data/local/
adb shell rm /system/customize/resource/android_audio.mp3
adb shell ln -s /data/local/android_audio.mp3 /system/customize/resource/android_audio.mp3
adb shell ls -l --color=never /data/local
adb shell ls -l --color=never /system/customize/resource/
adb pull /system/customize/CID/default.xml
pause
Script description:
Mount the system path to enable writing access.
Remove the original boot sound if it exists.
Push your mp3 into the data/local, where the bootanimation.zip is.
Make a link to data/local/android_audio.mp3
List the two affected pathes for you to confirm the result
Pull the default.xml out from the phone, if you find it not work after reboot, you can check the xml to see what the actural fullpath it is using. And manually change the script to try again.
My current boot sound is attached to the thread.
Hi there, I have an error when trying to link beacause the folder does not exist... may I create it manually?!
What for SuperUser command does exists?
Is there a List?
How can i get the file from
/data/data/com.android.providers.settings/databases/settings.db ?
i used:
adb pull /data/data/com.android.providers.settings/databases/settings.db C:
but it says:
failed to copy '/data/data/com.android.providers.settings/databases/settings.db' to 'C:': Permission denied
any solution?
try typing
Code:
su
or if not try
Code:
adb remount
I dont know much about this stuff yet, but that could help
ilendemli said:
How can i get the file from
/data/data/com.android.providers.settings/databases/settings.db ?
i used:
adb pull /data/data/com.android.providers.settings/databases/settings.db C:
but it says:
failed to copy '/data/data/com.android.providers.settings/databases/settings.db' to 'C:': Permission denied
any solution?
Click to expand...
Click to collapse
are you rooted?
try:
Code:
adb shell "su -c 'cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
this will use su to copy it to the sdcard, then you should be able to pull it from there. Phone may pop up a "Superuser request". Be prepared to allow it.
when i type:
adb shell "su -c '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
It says:
/data/data/com.android.providers.settings/databases/settings.db: permission denied
My Device is rooted, and i gave su permission
You forgot the "cp" between "su -c" and "/data/data/..."
C:\Users\ilendemli>adb shell "su -c '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
/data/data/com.android.providers.settings/databases/settings.db: permission denied
C:\Users\Muhammet ilendemli>adb shell "su -c 'cp /data/data/com.android.provider
s.settings/databases/settings.db /sdcard/'"
cp: not found
My CMD Window, whats wrong?
Hum, that's strange.
Try this : (<Enter> means pressing the Enter key on your keyboard)
adb shell <Enter>
su <Enter> (here you may have to look at your phone to give him the autorisation it needs)
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/ <Enter>
If it says "cp: not found", try this line :
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/ <Enter>
busybox: not found
Try to replace busybox by bb in the command I gave you.
If it doesn't work, well, I'll doubt you did your root well ^^ Cause it should have install BB
Can you explain us what you did to root your phone ?
I used SuperOneClick Root, to root my Phone. it installed the su files and superuser.apk nothing else
EdIT:
I installed busybox manually and rebootet my phone, now when i type:
>adb shell "busybox -c cp '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
it says:
-c: applet not found
EDIT2:
>adb shell
$ busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
cp: can't open '/data/data/com.android.providers.settings/databases/settings.db': Permission denied
$
That's normal, you missed the "su" command in your Edit 2.
So, 2 ways to do it.
Edit 1 version :
adb shell "su -c busybox cp '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
Edit 2 version :
adb shell
su
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
And I thought SuperOneClick did install BB... Well, I thought wrong ^^
Edit 1 version: Didnt worked..
Edit 2 version: WORKED!? i have the database,
now, how can i give these command in java?
anything with exec("..
From adb, you can't execute Java methods (because you're not in a JVM).
And I don't think you can access the DB like that in fact.
You have to make an app that read/write/do what you want on the DB (and it seems you're doing so, refering to the other topic you made )
it's not allowed, to edit databases directly, so my app will copy the database somewhere else, edit it, and copy it back, then it should work.
€: and i don't want to edit databses from the adb, i cant do it, the program cant do it, but java can do it:
Code:
myDB.execSQL("DELETE FROM system WHERE name = 'name1';");
myDB.execSQL("DELETE FROM system WHERE name = 'name2';");
myDB.execSQL("INSERT INTO system (name, value) VALUES ('name1', '"+arr[0]+"');");
myDB.execSQL("INSERT INTO system (name, value) VALUES ('name2', '"+arr[1]+"');");
Yes it should.
Make sure you don't mess with the DB though. It's an easy thing to break
Edit : From adb, apparently you can do something like
sqlite3 settings.db
Then you'll have a DB prompt where you can write SQL commands like SELECT, INSERT, etc.
can busybox delete and replace files?
BB lets you use any Unix command.
So you can use (in your example) the mv command, which will move a file from a directory to another one.
Runtime.getRuntime().exec("busybox mv /sdcard/ /data/data/com.android.providers.settings/databases/settings.db");
this should work
E: Hmm, doesn't work..
E2: should look like this: Runtime.getRuntime().exec("busybox mv /sdcard/settings.db /data/data/com.android.providers.settings/databases/");
will try it.
Yes. But remember you have to be root to do that
Hi there,
I tried if it is possible root on stock ROM 1.82.405.1 on HTC Desire Z. YES, we can!
This is a little "how to" with all previous roots and updates from "1.34.." to actual 1.82.405.1 stock ROM:
Permanent root on HTC ESIRE Z using linux
Software No. 1.34...
Necessary files:
adb (Android SDK)
gfree_02
psneuter
Terminal emulator (Android)
Optional files:
gfree_verify
Settings on Phone:
Menu-Settings-Applications-Development-USB debugging [yop]
USB connected to PC – only charge (card not mounted to PC)
Procedure on PC:
Check your device is properly conneted:
$ ./adb devices
It has to be like this : SH0BFRT00451 device
Than continue:
$ ./adb push su /sdcard/su
$ ./adb push Superuser.apk /sdcard/Superuser.apk
$ ./adb push rage /data/local/tmp/rage
$ ./adb push busybox /data/local/tmp/busybox
$ ./adb push root /data/local/tmp/root
$ ./adb shell chmod 0755 /data/local/tmp/*
On Android:
Launch Terminal Emulator
$ /data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Procedure on PC:
$ ./adb push gfree /data/local
On Android:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
# sync
# /data/local/tmp/root
# sync
there can be some errors with directory create – it is ok.
update to 1.72 via system and do following again:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
Superusere error is patchable by this:
http://forum.xda-developers.com/showthread.php?t=886999
check /sys/devices/system/cpu/cpu0/cpufreq/current_scaling_freq
But do we need to be already on 1.82++ or do we need to downgrade to 1.34++ because I don't really understand what we have to do!
PS: really really thank you!!!!! (all other root methods failed for me, so fingers crossed that this one will work!)
You need to have S-OFF; if you don't you need to go to 1.34 to get it, then upgrade back up the chain...
oh, thanks... I guess I'll have to downgrade then, wouldn't I
I guess so, but should only have to do it once...
Sent from my HTC Vision using XDA App
I rooted my 1.72 device a while ago with this tut: http://forum.xda-developers.com/showthread.php?t=905261
Should I be fine by just executing the latest part off this tut?
Code:
update from 1.72 to 1.82 via system and again root:
./adb push su /sdcard/su
./adb push Superuser.apk /sdcard/Superuser.apk
./adb push busybox /data/local/tmp/busybox
./adb push root /data/local/tmp/root
./adb shell chmod 0755 /data/local/tmp/*
./adb push psneuter /data/local/tmp/psneuter
./adb shell chmod 777 /data/local/tmp/psneuter
./adb shell /data/local/tmp/psneuter
./adb shell
Finally execute this inside the shell you opened with the previous command >adb shell<:
/data/local/tmp/root
restart mobile and you have root....
I got error:
E:signature verification failed
I'm using clockwork recovery 2.5.1.3. I think that's the reason, anyone got a fix for this?
hi, I have desire Z with bootloader 1.82.405.1 , from which stage should I start the rooting process?
Out of the 4 or so times I've successfully rooted the damn thing, I still am not 100% what I am doing right. Since each time I end up with a headache I've written myself a guide which seems to be almost always wrong along somewhere. I'm curious how wrong my latest discovery is. It seems when I use the 2.2.2 Android sbf I can't follow the usual directions listed on the wiki page. I need to run psneuter from another phone's root hack to give me "busybox, psneuter and su. Then I go back to install the bootmenu. Am I missing anything? Cheers:
II.C. Rooting
[EDIT:: It seems for Froyo 2.2.2 ("CEE sbf") you will probably need to follow the psneuter instructions:
http://wiki.cyanogenmod.org/wiki/LG_G2x:_Full_Update_Guide
Then go back and install bootmenu:
http://wiki.cyanogenmod.org/wiki/Motorola_Defy:_Full_Update_Guide ]
Is there anything else?
II.C.1. Connect Defy via USB and set it to "None." Open up terminal and begin pushing the files over:
Code:
$ adb push $PATH/TO/busybox /data/local/
i.e.
Code:
$ adb push /Users/kg/Android/android-sdk-macosx/platform-tools/busybox /data/local/
Push psneuter:
Code:
$ adb push $PATH/TO/psneuter /data/local/
… and su:
Code:
$ dab push $PATH/TO/su /data/local/
Now to change some permissions
Code:
$ adb shell chmod 777 /data/local/busybox
Code:
$ adb shell chmod 777 /data/local/psneuter
Enter into Defy and run psneuter by typing:
Code:
$ adb shell
Code:
$ /data/local/psneuter
Once the command finishes enter:
Code:
$ adb shell
"$" should now be "#."
Code:
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Code:
# mkdir /system/xbin
Should the last command say, "mkdir failed for /system/xbin, File exists" let it be. It tried to create a directory but one with that name already exists. Just move along:
Code:
# /data/local/busybox cp /data/local/su /system/xbin/su
Code:
# chown 0:0 /system/xbin/su
Code:
# chmod 6755 /system/xbin/su
Code:
# ln -s /system/xbin/su /system/bin/su
Code:
# exit
One last push:
Code:
$ adb push $PATH/TO/Superuser.apk /system/app/Superuser.apk
Code:
$ adb reboot
Fin.
II.C.2.To Install the Bootmenu by connecting the Defy via USB, allow memory card access.
Drag and drop the bootmenu folder into the SD card
Rename it "bootmenu"
Eject the SD card and on the Defy set the USB mode to "None."
In Terminal start up adb:
Code:
$ adb shell
Now give it SuperUser permissions, enter the following then unlock the screen on the defy and select "allow":
Code:
$ su
The prompt "$" should now be "#."
Code:
# cp -R /sdcard/bootmenu /data/bootmenu
Code:
# cd /data/bootmenu
Code:
# chmod 755 *
Just let this command run the script to the end (when the user prompt, # is given)
Code:
# ./install.sh
Once finished, don't reboot yet:
Code:
# rm -R /data/bootmenu
Now do so:
Code:
# reboot
If you want to see if it worked, upon the first boot animation/logo watch for the LED to flash blue after a good few seconds. Press Volume-Down upon seeing the light. You should be in the bootmenu!