Here is what happened: I uninstalled the Latin Input Method (via ROM Toolbox) as I was sure it was necessary, so I neither created a backup. After I rebooted my phone, each time a text input possibility acures, for an example I try to write a text message, google sth and etc, I get the following warning message: The application Android keyboard (process com.android.inputmethod.latin) has stopped unexpectedly. Please try again. Can I reinstall the application without the reinstallation of the whole CM7 I am using? I looked for similar threads, but didn't find any.
I'm pretty sure you can resolve this problem without reinstalling the whole rom by pushing the missing file through adb (if you are unfamiliar with adb and the process try copying the file through QtADB (just google it)) to the destination folder i.e. in system/app/.... After that I'd just reboot phone and the problem should be gone...
And if you are wondering the file you are missing can be extracted from any cm7 rom .zip file which can be downloaded from their site... obviously it's in the same directory >system/app/LatinIME.apk
Related
Hi.
I have some apps i want to install.
I have uninstalled the weather app along with the weatherSyncProvider and WeatherProvider.
So all the posts say "copy to system/app, clear dalvik-cahce, and reboot" to install a system app.
But thats not working. So after rebooting, i went into Root Explorer and installed the Weather app. It installed successfully.
On the other hand, the WeatherSyncProvider and WeatherProvider app didnt install giving the "Application not installed" message.
I tried using adb to install it, and it gave me an error (forgot what the error said exactly) but it gave the meaning that the error was got to do with the sharedID
which is com.htc.uid.rosie. I've tired way too much, but cant get it to install.
Do i have to change anything in the AndroidManifest.xml file?
---- OH and same thing happens to HtcMusic.apk, but this gives the DEXOPT error, and the .apk had no .dex file but has a .odex file and im running a stock 2.3.3 rooted odex ROM
Root is not enough to make persistant changes to the system directory, you need S-OFF.
Oh and you should use a deodexed ROM, it will save you the hassle of deleting the odex files.
yea, i have radio and eng s-off.
i've been to many posts, read MANY solutions, but none work.
I like the odex ROMs, mostly because its more stock'ish' and i like the challenge! , but as you can see i've hit a little bump with the error that adb is giving me (DEXOPT and SHARED ID).
And if you could please...
When i get an app that is DEXed, will using the 'dexopt-wrapper' command always work to make a .odex file? -- because i used it with the sense 3.0 lockscreen and it worked but with
com.htc.framework.jar (in /system/framework/)
it didnt. -- it wouldnt even load the bootanimation, just hanged on the HTC splash screen.
Could you tell me the importance of the com.htc.framework.jar file?
Sorry if its too much questions! ... any help would be greatly appreciated!
A similar issue happened to me just a few days back. While trying to apply a Rosie patch, i just used Root Explorer to copy the new apk to /data/app_s, but for some reason that did not work.
So i then tried pushing the apk via adb, and it worked. I'm not really sure what difference this makes, but it seemed to work for me.
So maybe you could give this a try. Instead of copy-pasting, try to do a push.
i've tried both ... still not working
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Not sure where you got your flashtool from, but obviously not the page in the dev section. Try flashing with the latest flashtool and report back. I take it your boot loader isn't unlocked?
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
issak42 said:
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
Click to expand...
Click to collapse
If that works it would be great. I have tried to get into recovery mode but with no luck..... however that could be the keypress combo i was using. Have found talk of lots of different ways, not necessarily saying what handset its for.
What is the confirmed keypress combo / method for the arc s?
which flashtool works with the latest generic firmware, as i thought i got this but it wouldn't work
mattshaw4 said:
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Click to expand...
Click to collapse
OK, this worked for me when I did something very similar...
start up the phone, and plug it into the computer.
After a while the light on the phone comes on, and the boot animation keeps looping...
The thing is that adb works now so you can install your launcher through adb!
to do this you type in this command on the windows command prompt
Code:
adb install Trebuchet.apk
some notes: -
you may need to type in the path to your copy of adb.exe if you get a "Command not recognised" error.
I used the launcher from CM10 - Trebuchet in the code snippet. You can extract your launcher's apk file from the rom (look in "system/apk"). Then use your launcher's apk name when you type out the command
Good Luck
An update guys.... spent a couple of hours on this only to find a very simple fix......
Using Flashtool in flashmode (?green light)..... noticed the icon for "install apk".... so found a free launcher apk, hit the button & my phone sprung back into life, text messages & all!!!!
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
liran corleone said:
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
Click to expand...
Click to collapse
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
MartCLEANRFr said:
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
Click to expand...
Click to collapse
well, at this point - i just want to make the device work...
D855 running blisspop 2.2 (5.0.1)
As above, I had an issue with my G3 losing the home button at the bottom after 5 mins of switching on so I decided to Fix permissions in TWRP
My G3 is stuck in the blisspop boot animation and stupidly I don't have a nandroid backup :crying: . I have then tried to reboot into TWRP and make a nadroid backup of the bootlooping rom so I could try to get data off it, I'm mainly trying to get my SMS and call history data off the bootlooping rom as all my pictures e.c.t are still on the phone. I have dirty flashed the same version of Blisspop 2.2 I had running but no apps or data show up.
I have tried to used Nandroid manager to try getting the SMS and call log off the old rom, but It says file not found.
Can someone please help me, I just want to get my SMS's off the phone
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
redduc900 said:
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Click to expand...
Click to collapse
I tried doing so, however I seem to have not to have "/data/data/com.android.providers.telephony/databases/mmssms.db" file or the "com.android.providers.telephony" folder in general
I also checked this in TWRP file manager and I don't have the folder let alone the file, it seems other com.android folders are missing too such as dialer, cell broadcast receiver, nfc e.c.t
I've dirtyflashed the same version of the ROM again to see if this also had files missing, however this has "/data/data/com.android.providers.telephony/databases/mmssms.db" and other folders present when I check in TWRP's file explorer and I can use adb pull to get the mmssms file off from the new rom.
Did "Fixing permissions" really cause me to lose all these com.android files?
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
Just my 2 cents worth, but I've never been a fan of toolkits. They work great sometimes, but then again they don't at times. I think it's better to learn adb/fastboot on your own. I would recommend fastbooting the factory image again, without the -w, and see if that resolves your problem. Then leave well enough alone. And uninstall the toolkit app as well if that's what it is :good:
groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
What were you trying/wanting to do when "checking out" the toolkit? I agree with Badger about installing the factory image, but I would go one step further and leave the -w in place just running the flash-all as is. At some point when you have done some normal work on the phone, you can run it again without the -w so you can start to understand what is not deleted as well as how to re-root since you will need to do it every month. From your description, it sounds like you have deleted some stuff on the user side that would not be restored without the -w.
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
jd1639 said:
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly what jd said. Running flash-all with no modifications will essentially do a factory restore of that build. Removing the -w (for wipe) from the batch file leaves the non-system files/settings, etc in place and you will then need to fastboot boot TWRP.img and install Magisk. As both of us mentioned, it may be best to get over the pain of a full image instead of seeing what issues remain without the -w in place in the batch. I think the real lesson here is that the folks who make these toolkits do a lot of hard work but it is still better/safer (especially on this device) to understand doing things manually.
I reflashed without the -w and everything seems to be fine. Thanks for the help!