So, my Acer is rooted and I've been running the Virtuous Galaxy 1.0.5 ROM for awhile with no issues. I decided to purchase the Titanium Backup Pro app to make a backup of my phone and tablet to Dropbox. They both backed up fine. Then all of a sudden my tablet just froze. When I reboot it just goes to the Acer screen.
I have tried a reset with the pinhole, and then going into CWM and wiping data, cache and dalvik cache. When I try to load new ROMs or even the one I was running, it just hangs. Sometimes I'll get a random offset and then it will hang, and other times I get a message like: "E:\error in /sdcard/update.zip" Installation aborted.
Any ideas? I believe stock for my tablet was Android 3.1 Kernel 2.6.36.3 Build Acer_A500_4.010.13_com_gen2.
Also, when I wipe Dalvik cache I get the message "E:unknown volume for path [/sd-ext]" If I continue and say yes, it does say that the cache has been wiped.
All help is appreciated.
Related
I flashed to the latest Overcome Kernel + Rom (2.1.2 and 1.4.2 respectively), after running fine on 1.4.0 for several days. I choose not to backup my apps as I don't have many and I wanted a clean start.
However, after doing wipe data/factory reset, then wipe cache, then davik wipe (not sure of the spelling), then proceeding to install the 1.4.0 ROM then 1.4.2 update, my apps were still on my Tab when I rebooted.
Why is this?
Now I am getting errors with every app.
"The application xxx (process com. ) has stopped unexpectedly. Please try again
I have tried to factory reset and reinstall the ROM multiple times, but it doesn't seem to help. How can I get rid of everything and start from scratch with this ROM?
scoperz0r said:
I flashed to the latest Overcome Kernel + Rom (2.1.2 and 1.4.2 respectively), after running fine on 1.4.0 for several days. I choose not to backup my apps as I don't have many and I wanted a clean start.
However, after doing wipe data/factory reset, then wipe cache, then davik wipe (not sure of the spelling), then proceeding to install the 1.4.0 ROM then 1.4.2 update, my apps were still on my Tab when I rebooted.
Why is this?
Now I am getting errors with every app.
"The application xxx (process com. ) has stopped unexpectedly. Please try again
I have tried to factory reset and reinstall the ROM multiple times, but it doesn't seem to help. How can I get rid of everything and start from scratch with this ROM?
Click to expand...
Click to collapse
I had the exact same issue with my T-Mobile US Tab, and it wound up needing repair from Samsung. I sent it in, and they replaced a component on the board. When I got it back, it was back to the factory fresh load which is what I expected when I tried to wipe it to begin with. The process took almost 3 weeks, which includes the free *ground* shipping to and from the Samsung repair center in Plano, TX. Awesome.
Acer Iconia A500 keeps force closing when booted (the home screen wont even load , its just black with that force close pop up) and when i try to factory data reset it gets some error saying something about gameloaf.com or something when i try to reset data from CWM. I was currently running Thor latest from for A500 what I must do to solve this issue ?
Wipe system, apps, cache, dalvik-cache, and then flash a stock rooted ROM using CWM.
epiphany9x said:
Wipe system, apps, cache, dalvik-cache, and then flash a stock rooted ROM using CWM.
Click to expand...
Click to collapse
Yep, that'll do it.
But, considering they may install the same rom again, they may get by with just Cache and Dalvik, while saving user data.
At least I'd go that route first, and if it doesn't fix it, then nuke it all.
My word prediction are broken. The only thing that every appears are words I've previously typed and punctuation. Under samsung keyboard settings Predictive text is on, and auto complete and spell correction are both checked under the Predictive Text settings. Does anyone know a fix? I'm rooted using http://forum.xda-developers.com/showthread.php?t=1756885 with the STOCK rooted, not stripped version. Anyone know of a fix or is experiencing a similar issue? Is it not able to connect with the spell check server because of root?
jasondhsd said:
My word prediction are broken. The only thing that every appears are words I've previously typed and punctuation. Under samsung keyboard settings Predictive text is on, and auto complete and spell correction are both checked under the Predictive Text settings. Does anyone know a fix? I'm rooted using http://forum.xda-developers.com/showthread.php?t=1756885 with the STOCK rooted, not stripped version. Anyone know of a fix or is experiencing a similar issue? Is it not able to connect with the spell check server because of root?
Click to expand...
Click to collapse
I'm having the same issue. I'm on the GS3 SCH-i535 and had initially flashed the stripped version. I did attempt to flash the deodexed stock version which also experienced the same autocorrect/spellcheck symptoms. Additionally, my T9Keyboard draws the lines but does not generate input.
Each time I have restored, or flashed a new ROM, I wipe the cache, wipe the dalvik cache, and fix permissions.
I also installed ROM manager and used that to re-flash CWM. After I flashed CWM from ROM manager I am unable to mount the external SD card which is mounted in /mnt/extSdCard. When I select Advanced -> wipe dalvik cache on the yes screen I receive an error "E: unknown volume for path [/sd-ext]", however, when I reboot I receive a screen: "Android is upgrading X of 61" leading me to believe that the dalvik cache has been wiped.
Interestingly, when I create a backup in CWM it defaults to a date of 1970-01-03.<Current Time>, if I start the backup from ROM manager it defaults to the current date/time.
I did remove my SD card and perform a factory reset (on the stripped version), then wiped cache, dalvik cache, and fixed permissions, when the phone boots, messaging just crashes. attempting to open messaging, the app starts to open, hangs for a few seconds, and then crashes presenting the error "Unfortunately, messaging has crashed". Restoring from backup fixes the crashing messaging. Odd that a factory reset causes messaging to crash.
three18ti said:
I'm having the same issue. I'm on the GS3 SCH-i535 and had initially flashed the stripped version. I did attempt to flash the deodexed stock version which also experienced the same autocorrect/spellcheck symptoms. Additionally, my T9Keyboard draws the lines but does not generate input.
Each time I have restored, or flashed a new ROM, I wipe the cache, wipe the dalvik cache, and fix permissions.
I also installed ROM manager and used that to re-flash CWM. After I flashed CWM from ROM manager I am unable to mount the external SD card which is mounted in /mnt/extSdCard. When I select Advanced -> wipe dalvik cache on the yes screen I receive an error "E: unknown volume for path [/sd-ext]", however, when I reboot I receive a screen: "Android is upgrading X of 61" leading me to believe that the dalvik cache has been wiped.
Interestingly, when I create a backup in CWM it defaults to a date of 1970-01-03.<Current Time>, if I start the backup from ROM manager it defaults to the current date/time.
I did remove my SD card and perform a factory reset (on the stripped version), then wiped cache, dalvik cache, and fixed permissions, when the phone boots, messaging just crashes. attempting to open messaging, the app starts to open, hangs for a few seconds, and then crashes presenting the error "Unfortunately, messaging has crashed". Restoring from backup fixes the crashing messaging. Odd that a factory reset causes messaging to crash.
Click to expand...
Click to collapse
Did some digging and found mention of these issues here: http://forum.xda-developers.com/showthread.php?p=28682782#post28682782 (Post number 421...) Seems the "root66" rom fixes the issue?
----------------------
Ok, I did flash the root66 ROM and it does fix the dictionary problem, but you'll have to install root manager and strip out the bloat manually (unless someone has a better recommendation)
Hi,
Hopefully someone has a solution for me.
This morning I switched on my TF101 and when I tried to go home from Gmail the button lit up but did nothing. I was convinced it didn't work. So I treid a few reboots and still nothing. I tried some other launchers and still nothing.
On further inspection I realised that when turning on slide unlock that also didn't work. Changing to pin, pattern or password still shows no unlock.
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Lethe6 said:
Are you running stock or a custom ROM?
Are you running stock recovery or a custom one?
I'd try to wipe the cache and dalvik, it fixes lots of weird software issues.
Click to expand...
Click to collapse
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
I managed to clear dalvik through terminal emulator. Optimised apps and rebooted but the problem persists.
Sent from my Transformer TF101 using Tapatalk 2
Reaper1242 said:
It's the stock ROM rooted with debugfs.
I know how to wipe the cache but how do I wipe the dalvik. I remember doing it once a couple of years ago on another device but for the life of me now can't remember.
I was going to try clearing the davlik with Terminal Emulator and typed "su" followed by "ls" and all it showed is "recovery". Does this mean it's somehow landed in recovery mode? If so, how do I get out of it?
Click to expand...
Click to collapse
If you have CWM, go to advanced, wipe Davlik.
frederuco said:
If you have CWM, go to advanced, wipe Davlik.
Click to expand...
Click to collapse
Thanks, now I remember I used CWM.
I thought I'd report back on this in case the information might help someone else down the line.
I tried the cache/davlik clear method and that did nothing for me. I stuck with it for a few days and eventually resorted to button saviour. I also realised that not only was the home button and any lock screen not working, but when using the ASUS quick settings in notifications it didn't show all settings.
This lead me to believe something in the system itself had gotten warped.
Today I did a Titanium backup, factory reset and restored all apps, data and system data. Initially it was fixed but on restart the problem casme back. I knew I'd restored whatever had caused the issue. My next step was to do another factory reset. Since it takes minutes to manually get the system back I only restored apps and data.
This time, after restore the issue was gone. So clearly the issue was in a system setting.
So for anyone else having this issue. Backup with Titanium, factory reset and only restore apps+data.
Just upgrade my 16g Nexus 7 to CM10.1 M2. After restart everything is fine but the device keeps on showing "upgrading" on every bounce as if the dalvik cache is getting cleared.
It only takes a few seconds but am noticing that SU shows messages about apps granted root...
Also I noticed my background will from time to time reset to default and my notification icons in status bar don't always show.
Tried to uninstall ti backup, wipe the cache again to no avail.
Upgraded to the latest nightly... Still no luck.
Trying to avoid having to do a full wipe. Any ideas?
samw52000 said:
Just upgrade my 16g Nexus 7 to CM10.1 M2. After restart everything is fine but the device keeps on showing "upgrading" on every bounce as if the dalvik cache is getting cleared.
It only takes a few seconds but am noticing that SU shows messages about apps granted root...
Also I noticed my background will from time to time reset to default and my notification icons in status bar don't always show.
Tried to uninstall ti backup, wipe the cache again to no avail.
Upgraded to the latest nightly... Still no luck.
Trying to avoid having to do a full wipe. Any ideas?
Click to expand...
Click to collapse
Wipe and reflash.
Whenever flashers have odd things happen, it is a common mindset to wipe and reflash. Just be sure you wipe system and factory reset before flashing.
Just seems to be just so much work for what this actually do... Device otherwise works fine.
Trying a different supersu package... Will probably give it a few more days before doing anything since its just so minor...