I found this
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=715913
and this
http://i-miss-erin.blogspot.com/2009/09/connect-bluetooth-keyboard-in-android.html
and i have the same keyboard, so it will be great to get this working
What i did:
via adb:
adb shell
su
mount -o remount,rw -t yaffs4 /dev/block/mtdblock3 /system
chmod 777 /system/xbin
adb push hidd /system/xbin
failed to copy 'hidd' to '/system/xbin/hidd': out of memory
What is the problem?
Thank you guys!
EDIT: Ok i successfully flashed trough recovery but then i read the whole thread and find out that this thing only works with a non sense rom
Gurdjieff said:
I found this
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=715913
and this
http://i-miss-erin.blogspot.com/2009/09/connect-bluetooth-keyboard-in-android.html
and i have the same keyboard, so it will be great to get this working
What i did:
via adb:
adb shell
su
mount -o remount,rw -t yaffs4 /dev/block/mtdblock3 /system
chmod 777 /system/xbin
adb push hidd /system/xbin
failed to copy 'hidd' to '/system/xbin/hidd': out of memory
What is the problem?
Thank you guys!
Click to expand...
Click to collapse
We don't have /system rw access. Your best bet is to make a flashable zip for it
That solved the problem, but according to the topic, it dont work on a sense rom On my Pulse i have used Bluekeyboard Jp but on wildfire it isnt working too
Sent from my HTC Wildfire using XDA App
HCDR.Jacob said:
We don't have /system rw access. Your best bet is to make a flashable zip for it
Click to expand...
Click to collapse
I think you can write to /system if you first do
Code:
adb reboot recovery[code]
then remount,rw ect....
Ok, with openfire it is working, Bluekeyboard Jp which on sense rom didnt, here it is also working. What is missing from the sense rom?
Related
Hi, I always update ROMs on my rooted g1
and every time the new ROM is flashed i have to type this on terminal
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
mount -o remount,rw /dev/block/mtdblock3 /system
(there is a file on my sd card)
with this my hard keyboard got the german layout. but on every rom update it changes again to the US layout..
is it possible to make it easier then typing all the time this?
thx for uor help
You can try this:
djluis48 said:
You have to manually push the keyboard files using adb....something like this:
Code:
adb remount
adb push c:\usr /system/usr
adb shell reboot
Thats assuming you got the folder usr on the root of your C hard drive....you can get that folder out of CMod, WG or almost any other 1.6 rom here. If you need any more help, just ask
Click to expand...
Click to collapse
In your case, you are going to need the "usr" folder out of a german rom or something, and place it on the root of your C drive.
Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.
Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.
I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.
looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873
YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything
Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse
still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App
mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount
huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]
Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)
ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!
Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr
same thing for me. i get permission denied
DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.
Post deleted.
Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit
I'm trying to copy a Camera.apk from my sdcard into the /system/app/
so far this is what i've come up with and I get an error saying I don't have the permission to Change the original Camera.apk:
su
cp /sdcard/Camera.apk /system/app/
reboot
Can somebody please help me with this? I just switched from Win7 to Linux and I realized that using the terminal emulator might be the fastest way to do this without installing the sdk.
http://forum.xda-developers.com/showpost.php?p=4900207&postcount=1
Use the mount line from this thread:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
that should work..
Thank you
thatdudebill said:
Thank you
Click to expand...
Click to collapse
Assuming it worked?
No problem man, welcome to the rooting world.
Every time i try to mount a directory on my o2x in adb it says this:
Code:
c:\sdk\platform-tools>adb shell mount -o rw,remount /system/framework /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I just can't get to mount anything while using shell in adb
That doesn't work because you're trying to mount a folder in /system as /system
You need to remount all of /system as RW, if you're on a custom ROM then just use adb remount
Rusty! said:
That doesn't work because you're trying to mount a folder in /system as /system
You need to remount all of /system as RW, if you're on a custom ROM then just use adb remount
Click to expand...
Click to collapse
And why wouldn't that work? Works just fine on my HTC Legend
BTW: I was the one trying to push the framework-res (through teamviewer VPN connection) it has always worked on my legend and I have no idea why it doesn't work on the LG.
The LG doesn't have a security lock on the bootloader does it?
thx in advance
JonasDroid said:
And why wouldn't that work? Works just fine on my HTC Legend
BTW: I was the one trying to push the framework-res (through teamviewer VPN connection) it has always worked on my legend and I have no idea why it doesn't work on the LG.
The LG doesn't have a security lock on the bootloader does it?
thx in advance
Click to expand...
Click to collapse
I tried to backup my custom rom but it said can't mount /system xD
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
try: adb shell mount -o remount,rw system
Code:
adb remount
It should do the trick too
gromez said:
Code:
adb remount
It should do the trick too
Click to expand...
Click to collapse
lol, that's shorter indeed
adb remount will only remount an existing mount, it won't create one.
It's not clear what the OP wants.
You don't need rw to deodex a ROM because you certainly don't want to write to system whilst you're doing it.
Also, I thought the stock ROM was deodexed?
To mount system in recovery, which will give you rw access and allow you to pull the files you need you just type:
Code:
mount /system
or
Code:
adb shell mount /system
Because system is included in /proc/mtd
to all: the answer is:
mount -o rw,remount /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
masi0 said:
to all: the answer is:
Click to expand...
Click to collapse
Hello
in my case, what it worked:
mount -o rw,remount /system
Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app
Micronuub said:
Why is this thread in development section, are you that stupid?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I already reported it
In my case except adb nothing is working as i cannot access system folder.
In my case except adb nothing is working as i cannot access system folder.
Can anyone suggest me what to do or what i should do as no flash tool or anything other option is working except adb.
also $ SU is not working please help me its driving crazy.
TheSSJ said:
I already reported it
Click to expand...
Click to collapse
Here's a solution
masi0 said:
Hi,
I want to deodex stock rom myself, so...
what variables in mount command I should use to properly mount /system partition in rw under adb shell?
Cheers
Click to expand...
Click to collapse
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.
helllpppp
rktcool said:
Hi, this seems to work for me:
Open a terminal (Command Prompt).
type adb shell
type su
You should see a # in your prompt.
type mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and Bingo! Your /system is now mounted as r/w. [NOTE: There will be no confirmation message. Your command will simply be printed again, and that means its a success)
The possible error might be that you forgot the su part. I'm making a wild guess that it stands for superuser. The first time I tried this, I didn't know about the 'su' and I wasted a little time because of that.
Hope this helped.
Click to expand...
Click to collapse
i used an app ldc dpi modder n its bricked with black screen n im on cm10 now it want to change chmod to 644 for my lww but i dont know how to do that please help me with step by step guide im new to this things
this worked for me:
mount -o rw,remount /system