Well I was wondering if there was a way to get the original Swype Keyboard on a MIUI ROM. My friend told me about flashing it but I dont know how and where to get the file for it. Please help me, the Swype Keyboard BETA has issues and I want the original keyboard. Please post links..
If you got a nand back up you can use swype restorer
Or get one of the stock roms un zip it and take out the swype.apk and libswypecore.so and push them into the phone
I'll make it easy for ya:
adb shell
su
mount -o rw,remount /system
mv /sdcard/Swype.apk /system/app \\NOTE: use "cp" instead of "mv" if you want to keep the file on your sdcard as a backup for future use or whatever
chmod 644 /system/app/Swype.apk
mv /sdcard/libSwypeCore.so /system/lib \\NOTE: use "cp" instead of "mv" if you want to keep the file on your sdcard as a backup for future use or whatever
chmod 644 /system/lib/libSwypeCore.so
reboot
Click to expand...
Click to collapse
after your reboot, go to your language&keyboard settings, Swype should be available now.
EDIT: cleanup
pmcqueen said:
I'll make it easy for ya:
download attached files and push them to /sdcard/
(NOTE: before you move the libSwypeCore.so.zip, rename it to just libSwypeCore.so - I had to add .zip to be able to attach it here)
then run the following commands from ADB (or terminal emulator, you just don't need the adb shell command in that case):
after your reboot, go to your language&keyboard settings, Swype should be available now.
Click to expand...
Click to collapse
After " mv /sdcard/libSwypeCore.so /system/lib" I get the error " mv: can't rename '/sdcard/libSwypeCore.so': No such file or directory "
Please help!
I AM VS4 said:
After " mv /sdcard/libSwypeCore.so /system/lib" I get the error " mv: can't rename '/sdcard/libSwypeCore.so': No such file or directory "
Please help!
Click to expand...
Click to collapse
before moving libSwypeCore.so.zip from your PC to your phone, did you remove the .zip? sounds like it still thinks it's a zip to me.
how do I do that when it wont let me open the zip folder?
EDIT: cleanup
Thanks alot! It worked!! ;P
But the thing is that this Swype wont work! Everytime I swype a word a blue box flashes around it! Please help with this issue too!
did you reboot?
if so and it's still doing it, try clearing Swype data and rebooting again. if you're still having issues after that, let me know and I'll find a different apk for you to try.
yo im all for help and all but your really not allowed to distribute swype, its in the form rules, even if the phone had it, you would have to get it from your own phone, or as said get it from a stock rom,
Thanks for this post. My question no longer really has anything to do with Swype. Now its personal!! lol
When I copy and paste the
mount -o rw,remount /system
command, it comes up showing the options for mount instead of executing the command. Is there by chance a syntax error in the typing or am I missing something?
Thanks
look in the market there is a app called remount you can use that to mount the system to read or read/write
Thank you!!!
Strange. Tried Remount app, no dice. Tried mount command, yet it still gives me a cross-link error when I try to run the "mv" command. I read that this error is due to the fact that it isn't mounted properly (I'm a complete noob at this stuff). The thing that puzzles me is I type
mount -o rw,remount /system and it always comes back with
Usage: mount [-r] [-w] [-o options] [-t type] device directory
which leads me to think there's some kind of syntax error.
It's to the point now that I just want to know why it isn't working as described in the post.
ok try this
mount -o remount,rw /dev/block/mtdblock3 /system
Thanks for the advice. I used the command you posted and it allowed me r/w access. But (there always seems to be a but...) when I tried to move files with the mv command I got a cross link error.
I ended up simply using the move function from root explorer (once I figured out what I was trying to do). Worked well.
ilostchild said:
yo im all for help and all but your really not allowed to distribute swype, its in the form rules, even if the phone had it, you would have to get it from your own phone, or as said get it from a stock rom,
Click to expand...
Click to collapse
Guess you didn't read the rules to well. If a custom rom is made for a device that has swype it can be included in rom
Just get swype from the website
Sent from my T-Mobile G2 using XDA Premium App
Spastic909 said:
Guess you didn't read the rules to well. If a custom rom is made for a device that has swype it can be included in rom
Just get swype from the website
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
That's if them rom itself came from the stock kernal, not from asop kernal, think why cyanogen doesn't include it in his roms? But we are allowed to bring it back from our back up that has it,
Related
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
ifiweresolucky said:
I moved from an HD2 to the Evo this week (no more TMobile, woot!). I am very familiar with custom WMO ROMS, Hard SPL, blah blah...
I have nearly zero Android development, custom ROM knowledge, etc, however.
I'd like to flash a custom ROM based on the factory, without all the Sprint programs preloaded.
Clearly I need to root; I am on steady ground with that knowledge. After that? Not so clear. There doesn't seem to be a thread with the steps I need to proceed.
Any info would be invaluable, thanks!
(PS - side question: why does Android launch all sort of processes in the background seemingly at random?)
Click to expand...
Click to collapse
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
I started Toasts root directions, placing PC36IMG.zip on the base directory of the SD card. Shut down, loaded with the Vol Down and Power buttons. The bootloader checked the file on the SD card but then stopped on the white screen.
It seems it was supposed to proceed automatically? But I am dropped off with options on the white screen: FASTBOOT, RECOVERY, CLEAR STORAGE, SIMLOCK, and HBOOT USB.
Directions show Vol Up and Down for previous and next and Power for select.
Alright, I resolved this issue. I recopied the file to the SD card and made sure to eject drive before shutting the device down. Seemed to make all the difference! Proceeding with the remainder of Toast's directions now...
p-slim said:
any reason adb remount isn't working for me? I do adb devices and my devices is there but when i type adb remount i get "remount faild: Invalid argument"
Click to expand...
Click to collapse
I'm running in to the same issue...
rgordon3091 said:
I'm running in to the same issue...
Click to expand...
Click to collapse
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
That's Linux trying to protect you. Essentially the rm command by default just removes one file at a time.
Try...
rm -r NameOfFolder
...to delete recursively.
Sent from my EVO 4G using Tapatalk
Go see the thread in the apps sub-forum about this. I have a post (#28, I believe) with the exact code to remove the bloatware. You can just copy any paste.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
nick325i said:
Getting error trying to remove nascar..
Code:
rm Sprint_NASCAR.apk
rm failed for Sprint_NASCAR.apk, Directory not empty
Any ideas?
Click to expand...
Click to collapse
you shouldn't have a problem deleting the apk, because an apk is not a directory.
i deleted it without the same message.
p-slim said:
i fixed it. you have to do this.
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
ls
Click to expand...
Click to collapse
'
hmmm i put im adb shell then i got a "#" so i put in "mount /dev/block/mtdblock4 /system"
and i got mount:mounting /dev/block/mtdblock4 /system failed: No such file or directory
so what did i do wrong?
Found the issue. Thanks all
Jus10o said:
This should be in Q & A.. But unless someone creates a rom with the apps removed. Its easier to just do it yourself.
If you did toasts method of rooting. Boot into recovery and type this
adb remount
adb shell
cd /system/app
ls
This displays all apps on the phone. Do this to delete them.
rm NameOfApp.apk
rm NameOfApp.odex
It is caps sensitive and make sure you type the apk exactly as its written.
Click to expand...
Click to collapse
By the way, when I "cd /system/app" and then "ls" I see only NamesOfApps.apk. There are displayed no *.odex files. Is that normal?
thread dead?
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
I was just about to say something similar. I had uninstalled Nascar using Titanium Backup, and the found out that I cant do the 2.2 OTA unless its there. TB didn't have the ability to restore it for some reason, so I got an APK from XDA, and put it in the system/app folder via Root Explorer. Then, I had to reset the permissions to match the other APK's, and it showed up and launched perfectly. Even did an update. Much easier than all that adb stuff, I think.
I used system app uninstaller for a buck on the market.. Easy and all there with the icons for easy to find and delete sprint and gapps.
Sent from my PC36100 using XDA App
scottspa74 said:
IDK if this threads still monitored by anyone, but here's my question: I don't use adb, but I just rused root explorer to locate sprint crap, and added a .bak to the end of all of them to essentially 'disable' them. Is this a safe method? Will Android system waste energy looking for them anymore (they no longer show in app tray, but are they still using resources) ? Thanks much.
Click to expand...
Click to collapse
Thats a good way.. If something goes wrong just have to rename.
Sent from my PC36100 using XDA App
Flash this zip and it should remove most of the Sprint apps. It will back them up to /sdx on your SD card so if anything is removed that you want, it will still be there. It's signed to work with RA.
http://grathwohl.me/uploads/android/evo/Sprint-Apps-Remover-signed.zip
I've seen a few people reference my post, but my post was really just trying to ask if anyone knew if, now that I've renamed them, and they don't run, they shouldn't be using up resources? Right, is that correct, or am I wrong in thinkin this?
And thanks cosine83, that's a really helpful post for a lot of people.
There's a really simple way to prevent CyanogenMod from overwriting your custom /system changes during an update. Create the file '/system/etc/custom_backup_list.txt' with a list of files within /system that you don't want to be overwritten.
For example, to prevent CM from wiping out Swype, open adb shell and type this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
cd /
mount -o remount,ro /system
If you use teferi's custom keymap, do this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
echo usr/keylayout/vision-keypad.kl >>custom_backup_list.txt
echo usr/keychars/vision-keypad.kcm.bin >>custom_backup_list.txt
cd /
mount -o remount,ro /system
Then the next time you flash CM, your changes to /system will still be there. If you want to see why this works, take a look at /system/bin/backuptool.sh
Hope this helps
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
CM probably needs to overwrite build.prop but I've been changing the LCD density in this file. Is there a way to use a seperate file to override the lcd density so that i can let CM overwrite build.prop but still maintain lcd density after a flash?
Whatever commands you put in /data/local/userinit.sh will run at boot. So in adb shell, type this for a density of 215:
Code:
cd /data/local
echo setprop qemu.sf.lcd_density 215 >userinit.sh
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Thank you!
This may be the long lost solution to my Swype and Cyan Problems. The new Release Candidates are destroying my swype and not liking it's return after installing the new Cyan. So, if this can basically help me update without losing much, it's a god send. Especially the LCD density.
You're a genius.
Thank you.
Hmm, seems the issue is still persistent. Thanks though.
Should userinit.sh and custom_backup_list.txt survive the upgrade or should they both be included in the backup list file?
Sent from my HTC Vision using XDA App
If you look at the actual script, it seems that it ignores the backuptool if .installscript exists, and in practice, I've noticed that nothing gets saved when flashing via ROM Manager. Is this, in fact, what's happening, and is there a way around it?
sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
You can put the following in /data/local/userinit.sh:
mount -o rw,remount /system
for apk in ADWLauncher.apk MS-HTCVISION-KNT20-02.apk
do
rm -f /system/app/$apk
done
for package in com.android.launcher
do
pm uninstall $package
done
mount -o ro,remount /system
exit 0
Click to expand...
Click to collapse
I haven't tried this for removing the Wifi Calling app, so ymmv. I remove a much larger set of apps myself (facebook, email, live wallpapers, amazon mp3 store, DSPManager, FileManager, Browser). http://wiki.cyanogenmod.com/index.php?title=Barebones has a list of apps that can be removed safely.
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Rc4 has the trackpad wake fm radio and speaker led fixed its workng very smooth better than rc3
Sent from my HTC Vision using XDA App
sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
Just delete them from the cmupdate.zip before flashing. Cwm recovery doesn't require sig so u don't have to worry about resigning it.
OP: nice find, I'm sure ill use it at some point.
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
I need that apk
Sent from my HTC Vision using XDA App
Used this method to when going from stock to CM 6.1.1 and could not get it to work. I had to push/install manually from ADB.
Anyone had any luck? I did what the OP said then flashed. Was I supposed to do anything after flashing wiping and then flashing (CM & gapps)?
rraxda said:
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
Click to expand...
Click to collapse
Make sure you have root in the shell by typing su.
cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
IConrad01 said:
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Click to expand...
Click to collapse
chubb16 said:
I need that apk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I am also interested in that apk
How can I backup progress on Angry Birds? Drives me nuts starting back over when I reflash CM
Titanium backup. You can use it to restore the app and the data. Usually i just restore the data to a fresh install.
I've recently rooted my Desire Z and flashed Virtuous G-lite on it. One thing I really miss is an FM Radio app like the one of HTC Sense. I'm really searching for an app that receives FM, and not streams it over the internet.
I've searched the market but I haven't found anything, XDA forums had lots of hits but nothing that resolved my issue.Then I got a suggestion someone might be able to make an APK out of the Sense FM Radio.
So basically my question: Is there an app which alows me to receive FM Radio in the market? Or could anyone please wrap up an .apk from stock HTC Sense so I could try that out?
take a look at Spirit FM Radio
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Awesome, I like this radio more the CM's.
Sent from my T-Mobile G2 using XDA Premium App
pmcqueen said:
here is the fm.apk from cyanogen. I assume it works on other aosp roms, but I've been wrong (many a time) before.
Click to expand...
Click to collapse
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
mprost said:
take a look at Spirit FM Radio
Click to expand...
Click to collapse
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Puffballofdoom said:
Thanks for posting! Installing works fine, but the app FC's on launch, even after reboot, might need some work before it works on G-lite
Thanks for the heads up, app installs and launches, but after selecting an FM frequency there is no sound or any sign of receving anything.
Click to expand...
Click to collapse
poo. make sure permissions are correct.
I don't ever use the FM radio so I'm not really familiar with how it works or if it relies on files outside of the apk to work. I do know that it requires bluetooth & headphones (headphones are used as antenna).
let me do some digging and I'll post back if I find anything.
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Puffballofdoom said:
I haven't got Root Explorer, but ROM Manager had a button Fix Permissions that should fix it too. After that I rebooted (ROM Manager suggested that), I enabled bluetooth, plugged in my headphones and still get instant FC when launching the app.
I will get back to it tomorrow, thanks for helping!
Click to expand...
Click to collapse
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
adb shell
su
mount -o rw,remount /system/app
mv /sdcard/FM.apk /system/app/
chmod 644 /system/app/FM.apk
reboot
Click to expand...
Click to collapse
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Why don't you just use tune in radio? It gets a ridiculous amount of stations and doesn't need headphones for an antenna. Try it!
Sent from my HTC Vision using XDA App
Tune In streams from internet, since I have a 1GB/month datalimit I really need FM to keep my data usage under 1GB/month.
Pmcqueen: I will try that first thing in the morning!
Sent from my T-Mobile G2 using XDA App
pmcqueen said:
yes, rom mgr fix permissions works as well. I just hate using it because most of the time I only need to fix permissions for one or two apps at a time, and in that case it's easier to just know the chmod command (see below).
how did you "install" the app? did you place it on your sdcard and install it that way? or did you push it to /system/app (or /data/app)?
here's what I would do with it (I will test with g-lite when I get home tonight and let you know if it worked for me):
I would take the FM.apk attached and place it on my sdcard, then run the following commands from command prompt (you can do this from terminal emulator as well, just skip "adb shell"):
in your case, my first step would be to find wherever FM.apk put itself (probably /data/app depending on what you did to install it), delete it, and start from scratch.
Click to expand...
Click to collapse
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Puffballofdoom said:
If I try mount -o rw,remount /system/app I just get feedback Usage: mount [-r] [-w] [-o] [-t] device directory. As far as I can tell the comma shouldn't be in the command, but what the command should be then I don't know
(My terminal has Superuser rights)
Click to expand...
Click to collapse
try just
mount -o rw,remount /system
(no /app, but since it is a subdirectory it will inherit the r/w access)
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Puffballofdoom said:
Still the same message, I know for sure the terminal has SU because the $ changes to # after I type 'SU'.
Thanks for helping once again
Click to expand...
Click to collapse
well darn it.
mount -o remount,rw /dev/block/mtdblock3 /system
^^ should get system mounted as read/write.
if not, do you have root explorer? we can do it that way as well, it's just faster to use terminal emulator/adb if it's not being tempremental.
So back at home once again, I tried the same commands from CMD and I'm getting the same message. I really don't know what's going on, it seems like the command isn't correct because it returns the possible options. Google hasn't come up with any suggestions too..
EDIT: Lol you posted at the time I was making this post, I will try what you said. I don't have root explorer, yet, let's see if your suggestion works, else I will need to find myself a copy of that root explorer
# su
su
# mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/FM.apk /system/app/
mv /sdcard/FM.apk /system/app/
failed on '/sdcard/FM.apk' - Cross-device link
#
Seems like your suggestion worked, but then moving the FM.apk failed. Any hints on that? Google tells me something about unmounted devices, but I can't find any solutions..
try just copying it instead. I saw this come up once before and I know a [very lengthy] workaround, but since it doesn't hurt to have a backup on your sdcard in the first place, might as well just copy...
just replace "mv" in the command with "cp"
let me know if that works or not.
edit: also, try adding busybox to the beginning of your command... ie:
busybox cp /sdcard/FM.apk /system/app
or
busybox mv /sdcard/FM.apk /system/app
Thanks, the busybox command did the trick. All commands execute perfectly now, but the FM radio still ain't working. Instant FC on launch (Bluetooth turned on and headset plugged in)
i also flashed virtous g-lite, but psx4droid can not load game with this rom. so i have to back to cm now. do you use psx4droid? how about its performance? pls let me kown.thanks.
Well I got Root Explorer, it looks usefull and I have used it with pleasure already. But moving/copying the FM.apk, it still doesn't work.
Anyone any thoughts?
Rooted with this method completely stock kernel...
Ok I am new to Samsung but not new to rooting and using adb. I have been searching and maybe I missed something but I can not get adb working properly on my phone and pc. adb remount does not work so I can not push any files over. I have tried all the methods with mount -o rw,remount -t yaffs2 ... etc...
I can get su permissions on the phone but it will not allow me to transfer any files over at all. I even tried to r/w permission with Root Explorer while connected to phone through cmd window and nada. I am not running CWM so I would like to push files over if I can. I have done it the root explorer way of copy and paste its just that way seems so sloppy to me.
Any help would be appreciated since I cant seem to find a method on the web that works for me
Thanks guys
How are you typing the push command? Remember there are 2 sdcards on this phone.
For the internal sdcard
Code:
adb push c:\this\place /sdcard
for the external sdcard
Code:
adb push c:\this\place /sdcard/external_sd
You *shouldn't* have to use mnt/sdcard/external_sd but give it a shot just to be sure.
Doesn't this phone have to be on for ADB to work? I thought I read that. Obviously that seems a bit odd since most have to be in recovery. Or am I wrong about the on part?
Lastly, if you can run 'adb shell' then use the 'cp' or 'mv' commands to get the files on there.
EDIT: Ok, I completely just misread your post. You're trying to write to the /system? Try mount -o remount,rw /system
I don't know why everyone uses the yaffs, mmcblk, and all the other craziness. You still mount /system just with more typing. Let me know if it works.
KCRic said:
How are you typing the push command? Remember there are 2 sdcards on this phone.
For the internal sdcard
Code:
adb push c:\this\place /sdcard
for the external sdcard
Code:
adb push c:\this\place /sdcard/external_sd
You *shouldn't* have to use mnt/sdcard/external_sd but give it a shot just to be sure.
Doesn't this phone have to be on for ADB to work? I thought I read that. Obviously that seems a bit odd since most have to be in recovery. Or am I wrong about the on part?
Lastly, if you can run 'adb shell' then use the 'cp' or 'mv' commands to get the files on there.
Click to expand...
Click to collapse
tried cp and mv still gave me problems moving file. I forget the error message I got. Also I know the proper push commands I used to do it with my Evo all the time. Its just that this phone wont let me mount system. What do you mean be on ADB?
playya said:
tried cp and mv still gave me problems moving file. I forget the error message I got. Also I know the proper push commands I used to do it with my Evo all the time. Its just that this phone wont let me mount system. What do you mean be on ADB?
Click to expand...
Click to collapse
I meant the phone needs to be on (with debugging selected) in order to use ADB and write to it. At least that's what I think I remember seeing. Could be wrong since I haven't used ADB with this phone yet.
KCRic said:
I meant the phone needs to be on (with debugging selected) in order to use ADB and write to it. At least that's what I think I remember seeing. Could be wrong since I haven't used ADB with this phone yet.
Click to expand...
Click to collapse
correct all that has been done... all the basics you can think of have been done but it just keeps failing on adb remount
adb shell
$ su
#
no problem now, at first yes but I still cant mount system... driving me nuts since I dont use Clockwork right now I want to push files over... and my software on my pc AndroidCommander says NORoot has been obtained....
I'm probably as new to this phone as you are. Mostly just dealt with HTC. Past this point I have no idea what's going on. I can write to my /system - no problem. Hopefully one of the more seasoned guys will jump in here soon. Sorry I'm not much more of a help.
KCRic said:
I'm probably as new to this phone as you are. Mostly just dealt with HTC. Past this point I have no idea what's going on. I can write to my /system - no problem. Hopefully one of the more seasoned guys will jump in here soon. Sorry I'm not much more of a help.
Click to expand...
Click to collapse
what method did you use to root with... Is it the same as what I used the deoxeded stock method I posted above
Did u try with the Odin method? way easier.
Sent from my Galaxy SII √Epic4G Touch
skykc0401 said:
Did u try with the Odin method? way easier.
Sent from my Galaxy SII √Epic4G Touch
Click to expand...
Click to collapse
Odin method to do what? root? If so that is how I rooted thanks
I downloaded an app on the market that fix it.. thanks guys
After rooting my Galaxy Nexus with Wug's Root Toolkit and sim unlocking with the Docomo hack, and then restoring my apps/data (can't recall if I restored from GN Toolkit or Root Toolkit), my camera app was messed up--could snap pix but they didn't save; and video always fc'ed. The solution turns out to be to rename or delete the DCIM folder. I couldn't delete--so I renamed. Now I am trying to delete that DCIM.old folder and contents (eating up 1+G on my storage), but cannot delete either individual files or the folder. I'm sure there is a simple solution, but I can't find it. Help (even with a condescending attitude ) much appreciated!
zzcat
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
You could also try the following Apps:
- Rootexplorer (paid)
- Astro File Manager
familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...
familyguy59 said:
If you use a file explorer, that has it's standard directory at / then all you need to do is navigate to /mnt/sdcard/ then make sure it's mounted as R/W and not R/O, if all that is the way I said it, you shouldn't have problems deleting anything, if so, use the ADB and type:
Code:
adb shell rm /mnt/sdcard/<Folder>
That should then do the trick
Click to expand...
Click to collapse
Update: solved
boot into recovery mode
mount /data
adb shell
rm, rmdir etc. all work as expected from here, no need to chown or chmod anything
zz
I see you've solved this, but i thought i would throw this in anyway...
The easy way is to delete the files from /data/media
The sdcard directory is a symlink, so go to the true folder and you should have more success...
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Thanks for this and other suggestions--my solution was trial and error, thrashing around in the dark (my unix command line chops are really, really rusty), and these are far more elegant. It's good to understand the underlying problem, your wisdom is appreciated.
Yes, permissions were messed up after rooting and applying a sim unlock hack, wiping and restoring from pre-unlock backup set. I see it so clearly now...
Problem can somebody help me?
Hello. I have a problem with my motorola defy+ running on gb 2.3.6 and is not ROOTED. Still he has an annoyng problem. After installing an aplication (not from the market) i saw that it didn't save data on the sd card. I uninstalled it and after a data factory reset i install apps such as temple run and Brother in Arms 2. At temple run it gave me this mesage
"File Access Problem Caution, unable to write files. This means your game progress can't be saved! Reason: Access to the path "/mnt/sdcard/Android/data/com.imangi.templerun/files/spaceholder.dat" is denied."
Also at Brother in Arms 2 the game didn't save. I rest the phone abouat 7-8 times.I changed the sd card. Note that the card was a 16 gb kingmax class 6 and put the 2 gb card that came with the phone. It all work smoothly. So what is the problem the sd card or the phone's software. Please answer i'm desparate and tired of wasting time.
This thread is about the Samsung Galaxy Nexus which has no external SD and uses a very different storage structure. I'm afraid we can't really help you here. Try the Defy forum.
Sent from my Galaxy Nexus using Tapatalk 2
zzcat said:
FamilyGuy, thanks for the suggestion, the problem seems to be bad permissions and I can't figure out how to fix them. Tried the "fix permissions" from recovery, as well as when booted, to no avail.
Typing
adb shell rm -rf /[directory]
gives me "permission denied"
So tried
chmod 666 /sdcard/.../*
but get an "operation not permitted" message.
So I'm really stuck here...
Click to expand...
Click to collapse
Before chmod the folder, you needed to be root by entering 'su' after 'adb shell' .
It worked from cwm, because cwm gives root access.
Linux/Android are all about permissions.
Sent from my i9250
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277
rocketero said:
I tried your theory, and it didn't work, still get the message" unable to change ownership permission denied, in recovery mode.
we are still trying to find a solution, here is the discussion: http://www.slatedroid.com/topic/32434-i-got-my-smartq-t20/page__st__260 on Post # 277
Click to expand...
Click to collapse
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.
cmstlist said:
Sorry to hear that. It sounds like the problem you are having is with a completely different device, so I can't really say why this may be occurring - I don't know how your device's file system is structured. This advice is specifically for the Galaxy Nexus. If a version of CWM exists for your smartQme device, I can't speak to whether it works properly and interprets commands the same way ours does.
Click to expand...
Click to collapse
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.
rocketero said:
it's a 9.8 inches tablet branded named called "LePanII'. it has ICS now, before we had Honeycomb 3.2.1.
The manufacture of this tablet did such a bad partitioning that the /system partition was left only with merely 4MB of free space in it.
Click to expand...
Click to collapse
Good luck with your issue. I doubt it's related to the one we were having on the GNex though.
cmstlist said:
Sometimes the file ownerships get messed up after a cycle of recovering the OS and restoring files.
http://forum.xda-developers.com/showthread.php?t=1515291&page=2
If you have any other directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
This fixed it for me and others.
Click to expand...
Click to collapse
Sorry if my question is dumb.
Does this command solve the problem for all the folders and sub-folders in sdcard? Thank you for your help!
Sent from my Galaxy Nexus
/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-R Recurse
-h Affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Don't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?
Jar3112 said:
/data/media # chown -R media_rw.media_rw*
BusyBox v1.20.2-jb static (2012-10-25 21:29 +0100) multi-call binary.
Usage: chown [-RhLHP]... OWNER[<.|:>[GROUP]] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP
-RRecurse
-hAffect symlinks instead of symlink targets
-LTraverse all symlinks to directories
-HTraverse symlinks on command line only
-PDon't traverse symlinks (default)
I got this after giving the commands from recovery in adb shell.
What does that mean?
Click to expand...
Click to collapse
OK solved, I forgot the space before the *!
Worked like a charm!!
Sent from my Galaxy Nexus