I have bricked my device when I tried to copy framework-res.apk to the system folder. I renamed the old framework-res.apk to framework-res.apk.bak but before I could paste the new one the phone freaked out and rebooted and now I'm stuck at the ATT white screen. I have adb access though so I'm hoping I can just push the framework-res file using adb. Every time I try this though I get an error saying file system is read only. I know all I probably need to do is get the computer to mount system as read/write. I just don't know how to do this. Is there anyone out there who can help me out?
Modified from:
http://forum.xda-developers.com/showthread.php?p=41339365
You may need to do:
mount -o remount,rw /system
chmod 777 /system/framework
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
jack_slapped said:
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Click to expand...
Click to collapse
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
jack_slapped said:
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
Click to expand...
Click to collapse
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
alacrify said:
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
Click to expand...
Click to collapse
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
jack_slapped said:
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
Click to expand...
Click to collapse
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
gwbard said:
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
Click to expand...
Click to collapse
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Aou said:
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
Click to expand...
Click to collapse
Yea I posted that last one before I saw his instructions. They were right on point. Thanks guys!
jack_slapped said:
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Click to expand...
Click to collapse
When you click "start" and type "cmd", you're starting a shell. They're command interpreters that extend functionality in specific ways. like "dir" for the Windows/DOS command shell, and "su" or "mount" for adb. Lots of good writeups on that around too
Related
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.
Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.
Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.
romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.
Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.
back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic
Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices
im on to the command prompt thingy and im a little confused......
do i put the whole command in? because when i do it says faild bla bla?
do i type it in just how it shows? cuz i wont work for me, but if i put in
JUST..."abd shell mount" it show alot of writing like it worked but im not putting in the WHOLE command???
can anyone tell me what it is supposed to say after each command??????????
omg i just want it to work. i got a new phone from verizon because i downloaded the leak, when all i wanted was a custom rom for wireless tether
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you might want to hit up in the irc chat, you can get real time help there. irc.wastate.net i believe or irc.zifnab06.net chat room either erisroothelp or droideris
where is that? those links diddnt work
those werent links, they were the servers for the irc chats. you need a irc chat client to get on there. if you want to use a web based chat client, the direct link to there is chat.andirc.net
whooohoooo!
you dont remember how the command prompt works? im just wondering if you put the whole command in or just the first part....sorry if im coming off a little stupid and pushy
how about posting the error?
ok i get in to my tools directory(this is what i see)
*C:\AndroidSDK\AndroidSDK\tools>
i put in (adb shell mount -o rw,remount /dev/block/mtdblock3 /system)
this is what it says "mount: Operation not permitted"
Why not use this:
http://forum.xda-developers.com/showthread.php?t=661413
what does that do? is it an app to get around the command prompt?
Does your phone have root access? (did you flash the rooted PB00IMG.zip?)
yes i did all the steps leading up to this now im stuck on the command prompt
do i type in all of the command? when i do it says "mount: Operation not permitted" on the first command
*Sigh*
- Open up command prompt (either type in cmd in the windows search bar or dig deep into your computer to find that sexy thang.
- Direct it to the folder of your choosing. In this case, the tools subfolder of android sdk. There are several ways to do this, the easiest would be as follows:
Say you're trying to get to C:\AndroidSDK\tools
Type:
cd C:\AndroidSDK\tools
or
cd C:\
cd AndroidSDK
cd tools
- From here, you shouldn't have a problem with adb. Make sure your device is plugged in and type:
adb devices
and you should see your device. Copy and paste the commands and you should be good to go.
ok so i put in adb devices (wasnt in the walkthrough)
and it showed
"list of devices attached"
HT9CTHG01052 device
im assuming that this is my device! yay.....or so i thought
i copied and pasted the command...and i also tried to type it out
it said the same thing!?
"mount: operation not permitted"
im sure its something im doing wrong...i just need someone to take a couple minutes to help a brutha
i typed in "cmd" in front of each command and it showed
microsoft windows [version bla bla]
copyright bla bla
untill i got to the last command..... it said 'ecovery.img' is not recognized as an internal or external command, operable program or bach file (yes it did say " 'ecovery.img' ") i looked all over a i found no file mis labled as "ecovery.img"
when it says all that stuff about windows does that mean that it took the command?
Why are you typing in "cmd" infront of everything?
IDK im just trying to figure it all out? am i wrong?
thanks for helping btw
i wish someone knew what it is supposed to say after each command....or even a video showing someone doing these commands so you can see them typing them
Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
you type the adb commands in exactly like they are shown. you dont type anything in front of adb.
Someone please tell me what I'm doing wrong:
C:\Users\[my name]> cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb devices
List of devices attached
HT9ADHG05719 device
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# adb push recovery-ra-eris.img /sdcard
adb push recovery-ra-eris.img /sdcard
adb: not found
#
I had to enter adb shell and hit enter before inputting the rest of that command just to get past that step. I tried doing the same with the next step and entering adb push separately but I got this:
# adb push
adb push
adb: not found
#
Does anyone know what I'm doing wrong or leaving out? I have the recovery and flash saved to the tools folder of my sdk.
you cant use adb push from inside a shell
That's what the "how to root" instructions are telling me to do.
joshw0000 said:
That's what the "how to root" instructions are telling me to do.
Click to expand...
Click to collapse
looks like you are "separating" steps...
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
(Taken from this thread: http://forum.xda-developers.com/showthread.php?t=647707)
your command is "adb shell" (which is going to shell... in which, anonomouse is correct, you cannot "adb" inside a shell). instead, type 1 command like this:
- adb shell mount -o rw,remount /dev/block/mtdblock3 /system
re-read the thread (link i posted) again... you're close
from your post... you'd have to exit shell... then get back to a DOS prompt... then do the "adb push" command
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Linux or windows
Nevermind.... i reread your post. Sorry.
joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
Make sure your sdcard is not mounted, it should be in charge only mode. Also make sure USB Debugging is on.
My phone was in charge mode and USB debugging was enabled, thanx.
joshw0000 said:
My phone was in charge mode and USB debugging was enabled, thanx.
Click to expand...
Click to collapse
You can use the application in this thread to help ease the process. They automated the commands through scripts to help in these situations. Plus, ECLIPS3 and Jamezelle do great work!
http://forum.xda-developers.com/showthread.php?t=661413
joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
First the solution and then the explanation; note that I have included the command prompts here:
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
So, here's what is happening.
When you "break up the command", by making the first part the single line
Code:
adb shell
What you are getting is an interactive shell running on the phone. That shell does not terminate immediately; you can type an unlimited number of commands into it, one after another.
When you issue a command (from the PC's command window) which looks like this:
Code:
adb shell programname arg1 arg2 arg3 arg4
something a little different happens than in the first example: the program "programname" is launched on the phone, with the arguments "arg1", "arg2", et cetera - and the "shell" on the phone terminates as soon as "programname" is finished running
Note that the command prompt changed!
C:\android-sdk-windows\tools>
vs
#
So what happened? "adb" is a program on the PC, and NOT ON THE PHONE. When you typed "adb blah blah blah" into the interactive shell on the phone - guess what? you see "command not found".
If you insist on "splitting up the command", then go ahead (although I really don't see any reason why it wouldn't work in it's original format); just bear in mind you are typing commands into an interactive "command prompt" that is running on the phone. When it comes time to run other "adb" commands - you need to be at the PC's command prompt
bftb0
Thanks for the info. You were right. I had just screwed something up when I typed it in the first time. Explaining the steps really helped me to understand what I was doing. I entered the commands as you had them in the tutorial and it worked perfect. So after that I created a backup and attempted to flash a custom rom:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
It turns out I was just having another newbie moment. I did a wipe and reflashed the rom and it worked perfectly.
Hey guys. I've done commands in adb many times. I'm still new to it, but I never remember having this issue.
I've ran CM6 for months, and nightly's as well. I'm running a custom compiled CM6 right now though.
adb remount I get
remount failed, operation not permitted.. and in default.prop ro.secure is set to 1. I changed to 0 but still can't do remount. Any other suggestions?
Thanks!
For a workaround, try remounting through shell - mount -o rw,remount /system, or the full command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
is that a temporary fix, or for good. or just a work around?
Just a workaround. It's a command in OS itself that does the same job as "adb remount" - which is, remounts.
I just can't think of anything that would cause adb remount to fail, so I have no suggestions for you to try. But in case you want to be able to do something without getting stuck, and wait for the solution without being in a hurry - I've posted the workaround.
I don't have a solution to solve it once and for all, but every time you want to remount, use
PHP:
adb root
before your commands
excellent.
adb root
adbd is being restarted
adb remount succeeded .
Thanks dude! that will work for now til cooker fixes that. lol
Jack_R1 said:
For a workaround, try remounting through shell - mount -o rw,remount /system, or the full command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Click to expand...
Click to collapse
Tried this and it appeared to succeed but I didn't get the results I wanted.
After doing this I tried push c:\com.amazon.mp3.apk \system\app\ and it repeated it back to me, but when I look in that directory, it's not there. What am I doing wrong?
Wrong direction of slashes:
push c:\com.amazon.mp3.apk /system/app/
And you shouldn't be doing it from the ADB shell. The remount is done in the shell, the push is done outside of it.
Jack_R1 said:
Wrong direction of slashes:
push c:\com.amazon.mp3.apk /system/app/
Click to expand...
Click to collapse
Ahhhh, I was wondering about that! Thank you!!
And you shouldn't be doing it from the ADB shell. The remount is done in the shell, the push is done outside of it.
Click to expand...
Click to collapse
So once I perform the remount I exit out of the shell?
operation not permitted.
"adb push" gets you "not permitted"?
try "adb root" first, as suggested above.
Jack_R1 said:
"adb push" gets you "not permitted"?
try "adb root" first, as suggested above.
Click to expand...
Click to collapse
adb root gets me something along the lines of "not supported on a stock build."
EDIT
ok...
adb shell
su
mount -o rw,remount /system
then i get this:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So it appears it's not actually registering the command?
Then I try
push c:\com.amazon.mp3.apk /system/app/
and I get: failed to copy 'c:\com.amazon.mp3.apk' to '/system/app/com.amazon.mp3.apk' : Read-only file system.
You need to use the full command, since you're running sh, not bash.
Look for the full command in my post.
Yes, currently it doesn't do a thing.
Jack_R1 said:
You need to use the full command, since you're running sh, not bash.
Look for the full command in my post.
Yes, currently it doesn't do a thing.
Click to expand...
Click to collapse
So I tried the full command and exited out to "dos" command prompt and tried again. This time I got "failed to copy.... ....permission denied."
Ok, try without exiting. I'm not sure it'll do anything useful, though.
There is some problem with either your ADB setup or the ROM you're using. Or you're just not rooted.
Jack_R1 said:
Ok, try without exiting. I'm not sure it'll do anything useful, though.
There is some problem with either your ADB setup or the ROM you're using. Or you're just not rooted.
Click to expand...
Click to collapse
Found another thread on another board. I just flashed amon ra's recovery and booted up from there, and it appeared to let me copy!
But then it wouldn't let me cd to system/app. It let me cd to system, but not to app. Weird... I booted back up and there's no evidence of the "copied" apk, anywhere.
What...
the...
****.
Thanks to all for your patience with my super-noobish ass, I'm hoping you're not as frustrated with me as I am with this.
When you're in the recovery, your system isn't mounted. You need to mount it first.
Use almost the same command as for remount, but leave out the "remount" option. Just "-o rw".
Your copy went to void.
Jack_R1 said:
When you're in the recovery, your system isn't mounted. You need to mount it first.
Use almost the same command as for remount, but leave out the "remount" option. Just "-o rw".
Your copy went to void.
Click to expand...
Click to collapse
lol, awesome, thanks. I'll fiddle with it some more in the morning.
Why isn't there a link somewhere to a simple instruction manual? It would be so much easier if I could read up on this myself without bugging all of you guys.
Of course there is. My sig has it in bold, and you can find everything there. It's just that people tend to rush asking questions instead of reading
Jack_R1 said:
Of course there is. My sig has it in bold, and you can find everything there. It's just that people tend to rush asking questions instead of reading
Click to expand...
Click to collapse
I've seen a couple of the basic noob guides to adb and I've seen the google definition of adb functions but it doesn't include instructions on how to do the stuff you're walking me through.
Will take a look at those links shortly. Btw, I'm on a MT3G though I don't think that makes a difference at this level.
First of I had no idea where to post this as it's not "device specific"
I'd been undertaking framewokr-res changes fine up until yesterday when I started to recieve an Invalid Argument error in ADB shell.
The command that I am using with ADB is;
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod644 /system/framework/framework-res.apk
sync
start
Click to expand...
Click to collapse
But after "cp /sdcard/framework-res.apk /system/framework/framework-res.apk" I'm now recieving, "cannot remove /system/framework/framework-res.apk Invalid Argument"
Where's that come from, I've never had it before, any ideas please?
I'm no noob btw, I've searched google and the forums here to no avail.
Regards.
SWFlyerUK said:
First of I had no idea where to post this as it's not "device specific"
I'd been undertaking framewokr-res changes fine up until yesterday when I started to recieve an Invalid Argument error in ADB shell.
The command that I am using with ADB is;
But after "cp /sdcard/framework-res.apk /system/framework/framework-res.apk" I'm now recieving, "cannot remove /system/framework/framework-res.apk Invalid Argument"
Where's that come from, I've never had it before, any ideas please?
I'm no noob btw, I've searched google and the forums here to no avail.
Regards.
Click to expand...
Click to collapse
My first guess is that the system partition is mounted read-only, but that seems like an odd message.
Is this on a different device than you normally use, or one that has worked before in the past?
Yep just that device, just tried on my Nexus S and it's still working on, but not on my Archos 70. Is there anyway I can mount as r/w with ADB to ensure its read and write?
Thanks for the response, appreciated.
SWFlyerUK said:
Yep just that device, just tried on my Nexus S and it's still working on, but not on my Archos 70. Is there anyway I can mount as r/w with ADB to ensure its read and write?
Thanks for the response, appreciated.
Click to expand...
Click to collapse
I don't know anything about the device, but if it is rooted, busybox mount has a remount option:
Code:
busybox mount -o remount,rw /system
Sorry where do I enter that, just the CMD in the Android SDK? I've not used Busy Box commands before.
on the command line just like your other commands above.
I'm doing something wrong as this is what I'm getting;
No, as part of the commands you are running on the device via adb shell:
Code:
su
stop
[COLOR="Red"]busybox mount -o remount,rw /system[/COLOR]
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod644 /system/framework/framework-res.apk
sync
start
Yet another error;
mount: can't find /system in /proc/mounts
May aswell give up at this rate
Apparently that device uses some other mounting format that standard android.
Ok cheers, champ, I'm sure I'll find a solution, like I said, it worked before, but after a full reformat last night thats no the error that I'm getting.