Database Users

Problems with adb push

I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.

I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please

su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox

fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system

n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.

fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)

`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!

I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!

LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?

I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.

post baleeted

[SOLVED] Uninstall Swype?

I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it

I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App

There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App

I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App

yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?

I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.

kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)

dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer

kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]

Backing up Swype/QuickOffice; restoring on custom ROM [UPDATED 11/13]

OK so I installed the latest CM6.1 Nightly and was able to backup and then restore both QuickOffice and Swype. NOTE: I am NOT providing any apks for backup purposes or if you somehow lost yours. These are merely directions for how to get Swype/QuickOffice off your phone and back on.
BACKUP:
(In a terminal w/ ADB)
Code:
adb pull /system/app/Swype.apk .
adb pull /system/app/Quickoffice.apk .
adb pull /system/lib/libSwypeCore.so .
After installing a custom ROM....
Code:
adb install Quickoffice.apk
adb push libSwypeCore.so /system/lib
adb install Swype.apk

tuzonghua said:
I was wondering if it is possible to pull the Swype/QuickOffice .apk's from my G2 (currently stock ROM), flash a custom ROM (say, Desire Z or CM6), and then re-install those .apk's. I figure it will throw some kind of error (e.g., Swype will say it's not configured for my device) because of different ROMs but just thought I'd ask.
I know how to pull, push, and install apk's from ADB so I'm not asking for how to do it. Just if it is possible.
Click to expand...
Click to collapse
I would love to know this as well. If you figure it out would you mind PMing me the details on how to do it?

Once a more stable version of CM6 or some other ROM comes out, I'll be trying it myself. Just as a reference, the ADB commands for doing this are:
Code:
C:\>adb pull /system/app/Swype.apk
C:\>adb pull /system/app/Quickoffice.apk
then after installing a custom ROM...
Code:
C:\>adb install Swype.apk
C:\>adb install Quickoffice.apk

I was able to use ES File Explorer and press menu>manager>app manager> then long press the Quick office app to back it up to the SD card, still trying to find the Swype apk though, going to do some digging with SUFBS (another file manager) and see if I can't get a hold of the Swype apk

This would be pretty awesome once we figure this out. Using Swype is the main reason why I'm still on the stock ROM. I tried out Sense and if it can come with Swype, I'll be one happy camper.
Did anyone try the above poster's method on pulling the apk?
Sent from my T-Mobile G2 using XDA App

tuzonghua said:
Once a more stable version of CM6 or some other ROM comes out, I'll be trying it myself. Just as a reference, the ADB commands for doing this are:
Code:
C:\>adb pull /system/app/Swype.apk
C:\>adb pull /system/app/Quickoffice.apk
then after installing a custom ROM...
Code:
C:\>adb install Swype.apk
C:\>adb install Quickoffice.apk
Click to expand...
Click to collapse
Quickoffice will work, but Swype will not. Swype has some libraries that you have to copy as well. Beyond that, I've not tested it. Find those Swype specific libs in the stock ROM and copy them as well, and maybe you might be ok.

Any chances you guys can send me the original Swype.apk that pre-installed on the G2? I stupidly deleted it off while doing Titanium things. Thanks.

See the post above from Dyndragon. I don't know what specific libs also go with Swype so the apk alone won't be enough.
Sent from my T-Mobile G2 using XDA App

tuzonghua said:
BUGS:
- Cannot use voice input with Swype after restoring to custom ROM
Click to expand...
Click to collapse
This is working fine for me on the CM 12 nightly. I used the same steps as you so try it with that?

Is there a way to get these files from a backup without having to back up the CM rom and then restore the stock, grab the stuff, and then go back to cm rom?
Sent from my T-Mobile G2 using XDA App

Popokrew,
No, AFAIK, and I cannot provide them here.

root file explorer
/system/app long click and copy what u wanna backup.
Sent from my T-Mobile G2 using XDA App

tuzonghua said:
Popokrew,
No, AFAIK, and I cannot provide them here.
Click to expand...
Click to collapse
No worries. Ill restore the backup, grab it, and go back to cm once the RC comes out. I noticed the google apps are also missing and I know cm can't provide those so I'm sure there is a backup procedure for them.
Sent from my T-Mobile G2 using XDA App

Hey guys, I was able to back everything up and while I was able to install the swype apk, whenever I go to copy the libswypecore.so file I have issues. Both through adb and root explorer. Any ideas? I'm going to attempt to do it through an update.zip + clockwork recovery now

tuzonghua said:
OK so I installed the latest CM6.1 Nightly and was able to backup and then restore both QuickOffice and Swype. NOTE: I am NOT providing any apks for backup purposes or if you somehow lost yours. These are merely directions for how to get Swype/QuickOffice off your phone and back on.
BACKUP:
(In a terminal w/ ADB)
Code:
adb pull /system/app/Swype.apk .
adb pull /system/app/Quickoffice.apk .
adb pull /system/lib/libSwypeCore.so .
After installing a custom ROM....
Code:
adb install Quickoffice.apk
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Click to expand...
Click to collapse
Ok, I got it, I'm not sure if everyone has to do this or if it was just an oddity for me but
A. For those that quickly jumped on the rom band wagon without thinking about backing up swype. You can just open any g2 stock rom as an archive and get the files from it.
B. This is what I had to do to install it.
Turn it from Read-Only to Read/Write
Code:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you have acess to the system folder to copy the swype lib file so...
Code:
adb install Quickoffice.apk
adb push libSwypeCore.so /system/lib
adb install Swype.apk
[/QUOTE]
Then close that access up
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
And your good to go.
REMEMBER SWYPE WILL NOT FUNCTION WITHOUT THAT LIB FILE!

If you are already on the custom rom and don't have the files, you can grab the files from the stock rom posted in this forum.
Sent from my T-Mobile G2 using XDA App

adb wont let me adb push libSwypeCore.so /system/lib . Says it is read only. I just installed cm6.1 and would like to have swype back.
Thanks for any help.

popokrew said:
If you are already on the custom rom and don't have the files, you can grab the files from the stock rom posted in this forum.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
And where is this located?

i got this to install. but when i go to use swype it says something about i cant use this version of swype with this phone.... do anyone know anything about this? if you do post some info. thanks!
i'm using the g2 with sense ui.

shaneleelevin said:
Ok, I got it, I'm not sure if everyone has to do this or if it was just an oddity for me but
A. For those that quickly jumped on the rom band wagon without thinking about backing up swype. You can just open any g2 stock rom as an archive and get the files from it.
B. This is what I had to do to install it.
Turn it from Read-Only to Read/Write
Code:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you have acess to the system folder to copy the swype lib file so...
Code:
adb install Quickoffice.apk
adb push libSwypeCore.so /system/lib
adb install Swype.apk
Click to expand...
Click to collapse
Then close that access up
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
And your good to go.
REMEMBER SWYPE WILL NOT FUNCTION WITHOUT THAT LIB FILE![/QUOTE]
Just FYI, you don't need all the extra stuff when you're remounting /system, you can just say
Code:
mount -o remount,rw /system
It already knows where it's mounted from and what it is, neh?
Also, I have a Swype Beta login, so I wanted to install the newest beta, and before you can install with the Swype Installer, you have to delete /system/app/Swype.apk and /system/lib/libSwypeCore.so both before the new beta runs right (if you leave the library it just FCs as soon as you enable it).

Rooting Help

Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve

stevefxp said:
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
Click to expand...
Click to collapse
what version of Android you have?

I am running VZW stock 2.2.1 but the problem seems to lie in the fact I cannot keep USB debugging on, even though it is enabled on the phone.
Has anyone seen this?

Root your phone without your computer - This would be the path someone on a Mac could take or someone without access to a computer.
This works for the DX and D2 phone, won't work for the D1
Visit the market and get the free Android Terminal Emulator installed.
Visit the market and make sure you have Astro installed.
Grab rageagainsthecage.zip with your phone http://www.droidforums.net/forum/at...s-root-them-unroot-them-rageagainsthecage.zip
Use Astro to navigate to the /sdcard/download folder
Long press on the rageagainstthecage.zip file and "extract to this directory"
The 4 files, from the zip file should now be in the /sdcard/download folder (rageagainstthecage-arm5.bin, su, superuser.apk and busybox.
What are we going to do?
Steps 1- 5: Change to the /tmp folder on your phone, copy the file to the tmp directory, change its permissions. run it, and wait.
Step 6: make sure we can proceed
Steps 7 - 14: make system read-writable, copy the superuser. su and busybox files to where they need to go, use chmode to change their permissions, then make the system folder read-only, and exit Terminal Emulator.
If you want to know more about the commands being used here: cd, cp, chmod, mount, and exit are all Linux commands you can look up on your favorite search engine.
Okay, let's do it - type the blue parts in Terminal Emulator
cd /tmp
cp /sdcard/download/rage*.bin /tmp/
chmod 777 rage*.bin
./rage*.bin
This will take some time, just wait for the $ to show up so you know it is done.
Go to Settings > Applications > Manage Applications > Terminal Emulator > and Force Stop the application
Sanity check - Go into Terminal Emulator again and make sure you have a # symbol as a prompt. If so you are ready to proceed.
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/download/Superuser.apk /system/app/Superuser.apk
cp /sdcard/download/su /system/bin/su
cp /sdcard/download/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit

For USB debugging, it might be your usb connection type. Try changing it to computer, mass storage, etc, until you find what's stable. I used Z4root when I did mine. Took like 2 minutes, and no computer, no terminal commands, true one-click root. Don't have the APK anymore, since I've moved on to the Bolt, sorry. But a google search should pull it up.

Thanks to all. I am now rooted. Woo hoo!

Weak Flipout mobile network signal

I've debranded a UK Orange Flipout and unlocked to use on Vodafone UK.
The mobile signal is terribly weak and spends more time with no bars that with. It makes the phone useless as a phone however great the design is.
Sitting next to another android phone on the same network the bars are almost full on the other phone - when showing nothing on the Flipout.
Does anyone else have this problem? Is there something I can do to re-configure the phone and make it work as a phone? I've had all the data settings from Vodafone reset for MMS and data etc.
If no answer it will have to go back to stock ROM and back to the shop.
Thanks.

Hey, I got the same problem. Had me temporarily switch back to Milestone 'cause Flipout wasn't able to even connect to the service..no signal at all. I noticed that Flipout has slow network acquiration compare to Milestone. But, I have to point out that I flashed it from stock to UK ROM without BLUR so it's more likely possible that something just went wrong. For now I blame the basebands and try to solve it that way..somehow. let me know if any news
Sent from my Milestone using XDA App

ok, it was the baseband.. i changed it from what it was to this (attachment) and everything's fine.
you have to be rooted, and remount system as r/w
the original baseband files are located in /system/etc/motorola/bp_nvm_default
basically you need to replace this folder with the new one and set the same permissions as the original files had. i don't know if you know how so just for sure, here's the how-to
i suggest you doing this:
0]if you are not rooted, install Universal Androot and press Go Root, then reboot your phone
1]unrar the attachment to your phone's sdcard
2]boot up the phone, switch to airplane mode
3a]if you have Root Explorer, navigate to /system/etc and push remount as r/w
3b]if you don't have that, install Root Toolbox go to Mount-System Mount Options-Mount System R/W
4]fire up Terminal Emulator
5]enter those commands: (enter after each line)
Code:
su
cd /system/etc/motorola
cp -R /sdcard/bp_nvm_default bp_nvm_default_nw
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
chmod 755 bp_nvm_default_nw
chown root.root bp_nvm_default_nw
cd bp_nvm_default_nw
chmod 644 *
chown root.root *
cd ..
rm -R bp_nvm_default
mv bp_nvm_default_nw bp_nvm_default
reboot
6]after the reboot, turn off flight mode, let the phone get registered to network and see what happens.. hope this will fix your problem.
it's a bit tricky, i actually had to reboot after mounting system to R/W and giving Superuser permissions and mount again because somehow it didn't work for the first time.. anyway, let me know if anything goes wrong

Thanks, that looks a bit technical but ill give it a go... thanks for info.
Sent from my Transformer TF101 using Tapatalk

Well I gave this a go - and I kept getting permission denied. sounds like problem you had with the system RW refusing to allow a copy.
Anyhow I am hoping I might have fixed it by using this link
http://dext3r.komodin.org/
And there is a radio file you can install under Quick FAQ with different country baseband radio files. Might help someone else ...

it didnt work
well, i did everything as written except i used ES File Manager to mount the /system as R/W and when it came to:
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
it said "cp: can't create symlink '/sdcard....': Operation not permitted" for every file so i just did it manually with ES File Manager... that is only a backup anyway and shouldnt affect anything.
it just doesnt work.
and why cant i just drop the baseband files in there with copy and paste? that didnt work either.
i need baseband files for T-Mobile on the US network for the Flipout. does anyone have any others i could try?
thanks!