well one my friend have problem with his HTC Tattoo while he was trying to delete a font from font folder he accidentally deleted the FONT FOLDER now his phone is not working...
is there anyway to fix this problem ?
I suppose that usb connection works, so he can push them to device via adb.
Here is the fonts folder.
Or he can use Android commander: http://forum.xda-developers.com/showthread.php?t=628138 to push them in system with an easier way.
can u pls explain how i can do it via ADB ?
Sorry, I'm not a linux expert and I don't know exactly which commands you must give. For this I suggested Android commander, cause you can drag & drop the folder to device's system folder like you do in windows file explorer.
You can also push the folder along with files with the Android SDK... It's easier as it is GUI based...
rre_za said:
can u pls explain how i can do it via ADB ?
Click to expand...
Click to collapse
1. Unpack the zip file into a folder
2. Connect Tattoo via USB, start recovery, open a terminal and type adb start-server
3. cd into the fontfolder: cd fontfolder
3. PATH\TO\adb push . /system/fonts (please note the DOT!!!! sign)
You're done.
What prob with my tattoo?
I used root1click tool
And I installed Enable Market >>>>> My phone's rooted
but when I try to push font in /system/fonts
ADB say : Permission Denied
Please Help
You need to remount the filesystem with the read-write permission.
Before typing "PATH\TO\adb push . /system/fonts" you need to execute "PATH\TO\adb remount"
I tried
adb remount
adb say:
remount failed: operation not permitted
what prob?
If you type
adb shell
Do you see a # or a $ ? (if you see a $ something has gone wrong with the root)
I believe you cannot remount via adb with stock (didn't try)...install Root Explorer and then try to remount from phone side (there is a button on the upper side saying: Mount RW)
Else do it manually and open adb shell and type:
1. su
2. insmod /data/local/bin/tattoo-hack.ko
3. mount -o rw,remount /dev/block/mtdblock5 /data
4. mount -o rw,remount /dev/block/mtdblock3 /system
Related
Hello folks, i have a quick question... i have cyan mod 4.1.99 installed on my phone which im sure comes equipped with busybox. I am trying to find the commands that i would type into terminal emulator to push .apk files without having to use adb.. my pc went up and all i have is my g1 phone now. Is it possible to do what adb does like install, push, and pull files through terminal emulator and busybox? If so what are the commands, or is there a thread with a list of commands? Thanks in advance
to install an app
busybox install <path to apk>
there may be an arguement im missing.....but it should still work (if you put in a random argument or do -h or -help, it should give you the lists. i dont remember what they are though)
for moving files, use the mv and cp commands (mv = move, cp = copy paste)
ie
cp /sdcard/app/heroled.apk /system/sd/app
Click to expand...
Click to collapse
Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system
Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system
bbbblack said:
Im trying to copy a file to system/app/ but it says " read only file system"
So i type in a command i found " mount -o rw, remount -t yaffs2 /dev/black/mtdblock3 /system"
But then after i put in the command it stills says read only. Is there a non pc method to remount the system as read/write ? Or should that code work? Another thread said it should change the system
Click to expand...
Click to collapse
its block, not black
that should mount as rw
Ladies and Gents:
Please help me out.
I am trying to install a "Japanese IME" that sir JMaurice has kindly provided through one of the forums.
Did everything (I think) required in order to get my N1 connected and recognized by my laptop. Then used SuperOneClickv1.5.5-ShortFuse to gain root. Started on the IME installation and got the following.
>adb devices
List of devices attached
HTxxxPxxxxxx device
>adb kill-server
* server not running *
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
So I decided to confirm root.
>adb shell
$ su
su
# exit
exit
$ exit
exit
I couldn't start the "adb push" sequence due to the errors above. What am I doing wrong?
Did you reboot after executing SuperOneClick? Try that.
Jack_R1 said:
Did you reboot after executing SuperOneClick? Try that.
Click to expand...
Click to collapse
Believe I rebooted. Rebooted again just in case. Still gives me the following:
>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds
>adb remount
remount failed: Operation not permitted
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Jack_R1 said:
Weird, but already seen on the forum not a long time ago, I think. I'm not sure what can be done in this situation. "adb remount" can be easily substituted by shell commands, root shell you're still achieving by "su", but how to solve this - I have no idea. Might be permissions thing.
Click to expand...
Click to collapse
Thanks for your replies. Am searching the forums for a similar post; still no luck. Hopefully someone will chime in with an answer.
Thanks again.
You have root, you just don't have an insecure boot.img
Rusty! said:
You have root, you just don't have an insecure boot.img
Click to expand...
Click to collapse
Please clarify. Where possible, detailed explanation/instructions would be most appreciated.
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Rusty! said:
You have root, that's all fine.
To use the command adb remount, you need an insecure bootloader, as you don't have this (due to using the stock boot.img) you have to mount /system as RW in a different way:
su
mount -o remount,rw /dev/mtdblock3 /system
Click to expand...
Click to collapse
What I am trying to achieve after adb remount is:
adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
adb push iWnnIME/libnjubase2.so /system/lib/
adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
adb install iWnnIME/iWnnIME.apk
This will actaully be the first time for me to use su. Could you confirm whether the following sequence of commands are correct?
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /data
# exit
$ exit
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
>adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Please let me know if I am missing anything.
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Jack_R1 said:
Wrong. You don't need to remount data, it's always writeable, and the command is erroneous - you're mounting system partition and calling it "data". You need to just push the apps to /data, as shown below:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
> adb push iWnnIME/[email protected]@[email protected] /data/dalvik-cache/
> adb shell
$ su
# mount -o remount,rw /dev/mtdblock3 /system
# exit
$ exit
> adb push iWnnIME/libiwnn.so /system/lib/
.
.
.
> adb push iWnnIME/libnjubase2.so /system/lib/
> adb push iWnnIME/DroidSansJapanese.ttf /system/fonts/
> adb install iWnnIME/iWnnIME.apk
Click to expand...
Click to collapse
I think I am starting to understand this. I punched in the first adb push sequence and got the following:
> adb push iWnnIME/jp.co.omronsoft.iwnnime /data/data/
push: iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a -> /data/data/dicset/master/njuserphone.a
failed to copy 'iWnnIME/jp.co.omronsoft.iwnnime/dicset/master/njuserphone.a' to '/data/data/dicset/master/njuserphone.a': No such file or directory
Checked in tools directory and the appropriate directory/file combination was there. Does this indicate that I have to create the appropriate directory in my phone?
Someone? Anyone?
Or is it possible to execute the same adb sequence in shell as su?
I must admit, I've never pushed more that a single file at a time over, given you appear to be trying to push an entire directory tree, perhaps you might be better off copying it over to the SD card in Windows, and using busybox to get it where you need it.
Exactly as Rusty suggested above me. Otherwise you need to create all the directories manually, through adb shell mkdir <your_directory_that_is_not_on_the_phone> .
I have searched but haven't been able to find a solution to my problem.
I am on the latest CM9 nightly and I have installed ADB on my Windows 7 64bit computer and it seems to be working but when I try and use the 'push' command, I get this "C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system"
I have tried the 'Remount' command, but that just throws back "Remount failed: Operation not permitted"
Any help is much appreciated.
You need to change permissions on the system folder
C:\android-sdk-windows\platform-tools>adb remount
then
C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
Didn't see that you had tried this !!
if you have root explorer or such navigate to system directory and change permissions to r/w...
otherwise...
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
Thank you for the help, however it still isn't working. I used the commands;
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
and it didn't throw me an error, but then when I tried to push the Trebuchet.apk it says the say as before. "failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system" "
Try
adb root
It could also be your version of busybox...
running out of ideas but one more...
Actually try this reboot into recovery (I presume you have some type installed), if you have an option to 'mount system' select it and then push the file...
Sent using my fingers and some technology from my HD2
Thank for your help! In the end it was my bad.
I didn't realise that on CM9 nightlies you have to go to Settings > Developer Options > Root Access > Apps and ADB.
Bling
Firstly what i would like to say is this is not a one click root like update.zip or superoneclick you will need to have some basic knowledge of adb and ubuntu and a little bit working mind which can follow the provided steps.
Requirements:-
*cwm recovery already flashed (if not refer here)
* Working linux distro (ubuntu, mint, kubuntu etc.) with atleast sudo rights
* adb setted-up (if not refer here, may not need to follow the usb drivers steps)
* must know how to use adb
* superuser package from here
Click to expand...
Click to collapse
So we are now ready to start
STEPS:-
1. Extract all file (su, busybox) from the downloaded package to the folder where you have adb setted-up
2. open a terminal
3. cd to the directory where you have placed adb and files
4. boot your phone into cwm recovery mode (home power) connect through usb
5. type "sudo chown root:shell /path to su"
6. type "sudo chmod 06755 /path to su"
7. type " sudo chmod 04755 /path to busybox"
8. type " adb devices" if you will see anything attached you are good to go
9. type " adb remount" if you get remount succedd then you can do below steps if not you are doing something wrong do again
10. type "adb push su /system/xbin"
11. type "adb push busybox /system/xbin
12. type adb push supersu.apk ( or what it is called) /system/app
13. now type "adb shell"
14. type su if accepted then you are rooted
15. now type "reboot"
Click to expand...
Click to collapse
you are successfully rooted
enjoy your phone
awesome guide buddy very useful for n0obs
First of all great guide! But please correct these:
You have to mount the system partition manually. Adb remount won't do it!
adb shell
# mount -rw -t rfs /dev/block/stl12 /system
Do chmod/chown in adb. It isn't enough to set it before copying.
# chown root:shell /system/xbin/*
# chmod 06755 /system/xbin/su
# chmod 04755 /system/xbin/busybox
# chmod 04755 /system/xbin/sqlite3
# chmod 04755 /system/xbin/ssh
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
and thanks for chown part
dheeraj (dhlalit11) said:
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
Click to expand...
Click to collapse
Hi!
For me, adb remount didn't work. It exited with an error code. I don't remember the exact error code... (cwm couldn't mount too)
When I experienced "operation not permitted" while chmoding, the partition was mounted as vfat! Because if you do "mount /dev/... /system" without switches, it automatically mounts it as vfat. In vfat you can't set setuid, setgid permissions.
I think it was just a coincidence that i could rooted with ubuntu. But it worked, so better to use linux (better adb perhaps?).
Rooting is a bit strange in this new firmware. For example when you do "adb shell" while the phone is in cwm, you have root access. So you have to do those things manually while you have temporary root access.
how can you mount rfs file system as vfat i dont think it can be done
dheeraj (dhlalit11) said:
how can you mount rfs file system as vfat i dont think it can be done
Click to expand...
Click to collapse
Yes it's really strange. I don't know how this thing possible too...
But I checked multiple times with "cat /proc/mounts" , and mounting without "-t rfs" it was mounted as vfat.
a bit of googling:
"You can mount as rfs as Fat in ubuntu and read/copy the files
editing them wont work at all ."
So maybe it is possible.
Enjoying my galaxy gear but a bit upset that there isn't an easy way to add custom ringtone sounds or notification sounds to the smartwatch. Has anyone figured out a way to add custom sounds to the gear for notifications? Would love to be able to do this myself. Thanks in advance!
yes, there is a way...but unfortunately it requires the device to be rooted first
you can push any custom ringtones using adb commands
adb remount
adb push *.ogg /system/media/audio/alarms/
adb push *.ogg /system/media/audio/notifications/
adb push *.ogg /system/media/audio/ringtones/
adb push *.ogg /system/media/audio/ui
adb remount didnt work for me, i couldn't run adb as root in a production build. i also needed to remount / & /system as rw
so what i did:
mount -ro remount,rw /
mount -ro remount,rw /system
mkdir /tmp1 (temp staging folder)
then push my files to the /tmp1 dir:
adb push filename.ogg /tmp1
(using wildcard on adb command line didnt work for me)
then in a root shell
cp /tmp1/* /system/media/audio/notifications etc whatever dir you want.
to copy all ogg files to the folder.
once you've copied all the files, type in reboot in a shell and the ringtone & notification list in settings will update. viola!
and remember, if you want your ringtone to loop: use your favourite tag editor (I used foobar2000 on Windows), add a tag/field called “ANDROID_LOOP”, and set it to “true”.
without this tag it will not loop.