I am new to android (and thus adb) but I keep getting this error:
failed to copy 'Email.apk' to '/system/app/Email.apk': Read-only file system

How do I launch adb as root?

(I'm trying to use this 1.4.1 method with the 1.4.0 rooting)

Originally Posted by mfleigle

I am new to android (and thus adb) but I keep getting this error:
failed to copy 'Email.apk' to '/system/app/Email.apk': Read-only file system

How do I launch adb as root?

(I'm trying to use this 1.4.1 method with the 1.4.0 rooting)

if you are rooted try command adb remount before adb push Email.apk /system/app/ command
Here is a little tutorial to introduce you to adb commands created by me: http://forum.xda-developers.com/show...23&postcount=4

Originally Posted by lavero.burgos

if you are rooted try command adb remount before adb push Email.apk /system/app/ command

I must of unrooted myself. I will restore to 1.4.0 and try again. I was on 1.4.1, and everything seemed to be working fine, except adb wasn't allowing me to launch root commands. I was able to use the market, use root apps (like SuperUser) I have no clue if it was something I did after I finished the instructions or if there is a flaw in the method.

Originally Posted by mfleigle

I must of unrooted myself. I will restore to 1.4.0 and try again. I was on 1.4.1, and everything seemed to be working fine, except adb wasn't allowing me to launch root commands. I was able to use the market, use root apps (like SuperUser) I have no clue if it was something I did after I finished the instructions or if there is a flaw in the method.

So you were/are rooted, uhmm did you get a code like this after run adb devices command?



if not then most likely is a problem with drivers

Originally Posted by lavero.burgos

So you were/are rooted, uhmm did you get a code like this after run adb devices command?

I think I did right after updating to 1.4.1, but I have already restored to 1.4.0

Originally Posted by mfleigle

I think I did right after updating to 1.4.1, but I have already restored to 1.4.0

ok then you can sideload as normal no need of adb. Good luck

Originally Posted by lavero.burgos

ok then you can sideload as normal no need of adb. Good luck

Thanks. I'm still going to trying to get 1.4.1 with root. There is no harm in restoring the device as many times as I want?

Originally Posted by mfleigle

Thanks. I'm still going to trying to get 1.4.1 with root. There is no harm in restoring the device as many times as I want?

Let me know if you succeed with the 1.4.1 root and android market method. Wouldn't be a problem restoring many times if you do carefully and following steps correctly but i would't recommend also to be messing up with that device too much as off the weird issues i've seen so far, so go ahead try the 1.4.1 root method and if it doesn't work as you expect then restore back to 1.4.0 root, block OTA then stick with that for now.

Which steps preserve specifically save the su for 1.4.1? I tried a slightly different method (Since I wanted to use the 1.4.0's rooting apps), and now I am on .1 with no su. I follow the method the first time and had root for a time but then lost it

Don't make assumptions ...

---

Originally Posted by mfleigle

Which steps preserve specifically save the su for 1.4.1? I tried a slightly different method (Since I wanted to use the 1.4.0's rooting apps), and now I am on .1 with no su. I follow the method the first time and had root for a time but then lost it

Just because ADB doesn't AUTOMATICALLY go into root, doesn't mean you've lost it. You can still invoke "su" after "adb shell" to get to root. "SuperUser", "adbWireless", and other applications that need root all do this (in effect), and you have to, too (unless you want to steadily drain the battery to ZERO if not charging).

1. Steps 5.2 and (especially) 5.3 make it automatically go into root when you invoke ADB.
2. Step 7.2 removes the "automatic root" when you invoke ADB. However, you are still rooted.

If you don't do step 7.2, your device will not sleep and you will steadily drain the battery to ZERO if not charging.