I have successfully rooted my HTC Wildfire S but now I am trying to reinstall HTC Mail after deleting it in error!
I am using the adb command to copy files from my sd card to the system folder on the ROM e.g. adb push/sdcard/Mail.* /system/app. However, when I press the enter key I just get a list of the adb commands and switches and it doesn't copy the files across.
Any ideas as to why this may be happening? My Android Debug version is 1.0.26
If I could just download the HTC Mail app and install as usual that would of course be preferable but I think it's only available as a factory install. I've tried the K9 mail app but I have a feeling there is a connection timeout bug that means it doesn't disconnect from the POP mail server for ages after it's 'pulled' messages. I've had many senders complain they have message failed errors when they try to send to me but they haven't had them since I uninstalled K9 and started using HTC Mail. And in case you're wondering, I started using K9 because the old version of HTC mail would not save my SMTP settings but the new version is OK.
Thanks for any help.
Marnhullman said:
Any ideas as to why this may be happening?
Click to expand...
Click to collapse
Looks like you've used the wrong command.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
Obviously swap framework-res for your apps name.
adb command fails
Thanks XperienceD. Will try your syntax later.
adb command fails
XperienceD
The syntax you suggest is not compatible with the adb I'm running i.e. dd is not a vaild switch. I'm trying to use adb to reinstall an app to an HTC Wildfire S.
From what I've read elsewhere the syntax I used should work but doesn't...
Marnhullman said:
XperienceD
The syntax you suggest is not compatible with the adb I'm running i.e. dd is not a vaild switch. I'm trying to use adb to reinstall an app to an HTC Wildfire S.
From what I've read elsewhere the syntax I used should work but doesn't...
Click to expand...
Click to collapse
Did you start by mounting the system - adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system ?
Related
I'm sure i'm not the only one that has noticed that you can't update terminal emulator with modded firmware, i did a mild look through the searches, and didn't find what i was looking for, is there a means to update this, i've tried takeing it out of white list and then updating, but no go... Not that its a big deal TE works, its just an annoying knawing thing in the back of my mind, knowing there is an update on the market, and i can't have it
Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market
card13 said:
Delete the terminal app in terminal by
su
cd /system/app
ls
them find the app that starts with com. something
type rm -> name of the app
update it in market
Click to expand...
Click to collapse
gives me a read only error, i have to chmod it first right? have no clue how to do that right now, have to look it up. Thanks for pointing me to the proper file though
It'd probably be best to use adb.exe (available in the android SDK) to remove terminal emulator rather than using terminal emulator.
Also, in order to change anything in the /system partition, you need to remount it as read/write.
With adb this is easy:
Make sure your android has debug mode enabled (which I think is by default in all JF releases)
Hook it up to your computer with the USB cable
Open up a command prompt in windows (or whatever other OS you're using that has the Android SDK) and go to the tools directory in the SDK
Type "adb devices" to make sure adb sees your phone, if it doesn't, well uh...it's not working right, and you'll have to figure out why
Type "adb remount" to remount the /system partition as read-write
Type "adb shell" this will give you shell access to your G1, from there you can delete stuff from the /system partition. I think you might also be able to use "adb uninstall" but I don't know if that works for the /system/app folder.
thanks for the info TM will play with the sdk tools and see what i can do, they have been giving me a headache on linux, but then i haven't played with linux in about 6 years.. its come along way. Thanks again for the info wait 2 secs to reload the image
I've noticed that, too. I don't see a reason why I need to update TE, the one I have works just fine.
here your answer in the link below
this will allow you to remove the terminal and install the new one from market
http://forum.xda-developers.com/showthread.php?p=3287558
Download this attachment:
http://forum.xda-developers.com/showpost.php?p=3838743&postcount=8
Then:
in windows:
adb pull /system/usr/keychars/trout-keypad-v3.kcm.bin trout-keypad-v3.kcm.bin
This backups your existing keylayout.
Then: (you must have the downloaded (unzipped!) file on C: !!)
cd C:\
adb remount
adb push trout-keypad-v3.kcm.bin /sdcard/trout-keypad-v3.kcm.bin
adb shell
cd /sdcard
dd if=trout-keypad-v3.kcm.bin of=/system/usr/keychars/trout-keypad-v3.kcm.bin
reboot
Your device should reboot now and TADA you have fully working QWERTZ!
Please correct my commands if they are wrong.
Disclaimer:
You know this..
can you give me codes to work with the terminal (I don't use sdk -ADB)
And , does it fixes all other stuff to like + - :.... or just swap Z and Y.
(I need that fix so much)
Thanks
Copy the file to your sdcard then:
su
mount -o rw,remount /system
cp /sdcard/trout-keypad-v3.kcm.bin /system/usr/keychars
i think it fixes all including + etc..
ok did it, typing reboot....
g1 htc booting
waiting.....
OMG thanks a million....... close this thread or just move it to (make one with USEFULL THINGS).... will help other people in europe.
Thanks again.
maxisma said:
Your device should reboot now and TADA you have fully working QWERTZ!
Click to expand...
Click to collapse
Hi!
This only works reliably with ROMs with the Google virtual keyboard. With the HTC one (which function-wise is better), the hardkeyboard eventually switches back and forth from qwertz to qwerty and back.
Is there a solution for that issue?
Greets
It's because of the Hardwarekeyboardcorrection.
You can try to deactivate it in Settings/Locale Settings/Touch Input/...
maxisma said:
It's because of the Hardwarekeyboardcorrection.
You can try to deactivate it in Settings/Locale Settings/Touch Input/...
Click to expand...
Click to collapse
Yeah, that's my experience as well that it is due to the hardware keyboard correction.
However, even when I switch that off (correction and completion switched off), this strange behavior of switching back and forth continues :-(.
Is there a solution to this?
Or alternatively how can I install the Google IME on a HTC build as a workaround?
Just pushing GoogleIME.apk doesn't help unfortunately.
I have looked and cannot find a solution.
I am a newb when it comes to this stuff.
Is their anyway to remove the HTC keyboard or touch input and use the standard android keyboard. I like the keyboard but it is too laggy.
I would prefer an .apk of the standard keyboard, But I am sure it won't let you install, but rather open up the HTC keyboard.
I think I can plug in and enable USB debugging, and then adb shell, rm touch input,
reboot?
Can someone please help me through this.
Partially correct.
it would be
adb remount
adb shell
cd system
cd app
rm HTC_IME.apk
rm Clicker.apk
reboot
thanks for the hep, really appreciate it, Is their anyway to reinstall the HTC ime touch input apk. that would basically reinstall the htc keyboard over the android one, if I wanted to?
Yes, there is.
Before you do the command I posted above, do this:
adb remount
adb pull /system/app/HTC_IME.apk C:\HTC_IME.apk
adb pull /system/app/Clicker.apk C:\Clicker.apk
That will backup those files to your C:\ directory.
http://www.mediafire.com/?qjymjydmw0m
flash from recovery then after boot long press an input field and change the input method. it will install 2 "android keyboard"s one is stock one is with voice
Make sure you do what andyriot posted above before removing the HTC keyboard... otherwise you'll be keyboardless until you get the new one flashed
mrinehart93 said:
Yes, there is.
Before you do the command I posted above, do this:
adb remount
adb pull /system/app/HTC_IME.apk C:\HTC_IME.apk
adb pull /system/app/Clicker.apk C:\Clicker.apk
That will backup those files to your C:\ directory.
Click to expand...
Click to collapse
andyriot http://www.mediafire.com/?qjymjydmw0m
flash from recovery then after boot long press an input field and change the input method. it will install 2 "android keyboard"s one is stock one is with voice
thanks guys
I know there are a few threads seemingly related but please bare with me. There's nothing wrong with my rom at all. I'm looking for a way to mount my sdcard as a usb disk on the computer to play with the files. Because JB 4.2 only allows mtp, this can't be done anymore. I figured if I mounted the sdcard in twrp, I should be ok. However, the button is unclickable. The reason I want to play with it is because I've flashed CM10 a couple of times and each time, it has moved all of my files into a subfolder called zero as per this page. I can't seem to get TiBu to properly restore because of this so I wanted to move them all back to the root folder as they should be and it would be fine because I did it before I switched to 4.2. So, any ideas as to why I can't click it?
Edit. Im using twrp 2.3.1.1
You can do the same thing from terminal.
Code:
su
cd /data/media/0/0
mv * ../
cd ../
rm -rf 0
No idea why you can't click the button though.
You can do the same thing from terminal.
Click to expand...
Click to collapse
Wow I never thought of that. It failed though because a directory wasn't empty.
It probably failed because there was a directory with the same name when you moved it.
I guess to be sure you could do something like...
Code:
su
cd /data/media/0/0
cp -R * ../
cd ../
rm -rf 0
but before you rm -rf make sure the CP worked. I know android commands sometimes don't have the normal options that linux commands do, so the "cp -R" part may not have worked.
Worst case, you can "adb pull" the files to your computer, remove everything then adb push them back.
Lethe6 said:
It probably failed because there was a directory with the same name when you moved it.
I guess to be sure you could do something like...
Code:
su
cd /data/media/0/0
cp -R * ../
cd ../
rm -rf 0
but before you rm -rf make sure the CP worked. I know android commands sometimes don't have the normal options that linux commands do, so the "cp -R" part may not have worked.
Worst case, you can "adb pull" the files to your computer, remove everything then adb push them back.
Click to expand...
Click to collapse
I'll give it a shot. I wish I could just use my computer dammit.
Edit. Still fails with that original error.
Edit 2: I tried using adb and it fails too. Says adb is in "/usr/bin" but not thats not included in $PATH environment variable.
adb will only be in $PATH if you added it, otherwise you need to manually run the full path or from the directory.
Something like:
adb pull /data/media/0/0 .
Then with adb shell you can cd to that directory:
adb shell
cd /data/media/0/
and remove 0
rm -rf 0
I thought i had gone into the adb folder and just ran ./adb pull yada yada. Im off to work now so ill have to try again laterm
Sent from my HTC One XL using Tapatalk 2
If you did I'm wondering what the $PATH issue is then? On the device itself, cp and rm will be in $PATH unless maybe you forgot to su?
I'm not entirely sure. I was using my laptop to run the adb command. Or am I doing it wrong? I could've forgotten. Anyway this thing's really got me confused. This morning I flashed back to JB 4.1.2 to see if I could fix it using usb. Well I rebooted to recovery to flash gapps and another kernel but I couldn't find the files on my sdcard anywhere. So I tried to reboot and it wouldn't get past the CyanogenMod loading screen (their logo). I've flashed JB 4.2 again and got it back up. This thing is really freaking confusing. I'm gonna try to flash back once again and see what happens.
Edit: Apparently I was wrong in thinking that 4.1 still had the ability to use USM
Using your laptop for adb was correct. It happened to me a few times until I got TWRP installed that I had to flash a couple of times for things to work properly, not sure why but I've seen other people report the same here. Once it was installed most the issues went away.
So I've got 4.1.2 back on it and still can't get USM to work. I thought it was removed in 4.2? I'm using the same rom I had used back in December which can be found here
Ok so yes, I had forgotten to run as root on my laptop. It tells me that it can't find the device though.
Edit: Updating the SDK, making sure I have everything I need.
Edit 2: Ok I've updated the SDK but it's still not detecting the tablet. When I run adb devices, it comes up blank. I set the rules using this page. I'm wondering is this something like having to run modprobe or maybe a reboot to initialize it?
Edit 3: I forgot to enable debugging. Now it says the remote file does not exist.
Kreuger said:
I know there are a few threads seemingly related but please bare with me. There's nothing wrong with my rom at all. I'm looking for a way to mount my sdcard as a usb disk on the computer to play with the files. Because JB 4.2 only allows mtp, this can't be done anymore. I figured if I mounted the sdcard in twrp, I should be ok. However, the button is unclickable. The reason I want to play with it is because I've flashed CM10 a couple of times and each time, it has moved all of my files into a subfolder called zero as per this page. I can't seem to get TiBu to properly restore because of this so I wanted to move them all back to the root folder as they should be and it would be fine because I did it before I switched to 4.2. So, any ideas as to why I can't click it?
Edit. Im using twrp 2.3.1.1
Click to expand...
Click to collapse
You need to update to twrp 2.3.2.3 for proper flashing of 4.2 roms. If you don't you will get the nested 0/0/0 directory copies each time you flash.
Sent from my SGH-I997 using xda premium
I have updated now. Ive gone back to ics to correct it. I may just stick with it to keep ums support.
Sent from my HTC One XL using Tapatalk 2
I did a superwipe and installed cm10 but i have no sound.
Sent from my Transformer using Tapatalk 2
Hi. As title says I need a fix for KitKatDS rom. I tried to post in that thread but it won't let me. I saw this fix in the thread but I don't know where you do this or if it works:
FYI - found a fix. If anyone is having issues sending/receiving MMS, do this:
(load up adb shell)
su
mount -o rw,remount /system
rm /system/bin/ip
ln -s /system/xbin/ip /system/bin/ip
IP on /bin errors out so the device is unable to route a connection to the MMS servers. the IP in /xbin works just fine
Can someone give a noob a walkthrough of how to do this? Thanks
Set up adb on PC and turn debugging on on phone, if you aren't sure how to do this a quick Google search will give you many guides.
Once this is working open a terminal/cmd and type
adb devices
If you a see a serial number than you are good, if not see the guide on setting up adb or ask question here if still stuck
Once all is working type
adb shell
Then type the exact commands you linked from above
Now for safe measure type
exit
adb reboot
You should be good (granted I'm not using this ROM currently and have not needed to attempt this fix, but looking at it, it makes sense and could work. Having said that always make a backup of current ROM in recovery before trying new things you don't fully understand)
Best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
As I mentioned in the KK thread itself, I was able to run the fix without having to PC attach and adb shell. Just used the included terminal program with SU permissions, and the fix has held since day 1. I've sent & received plenty of MMS messages.