Anyone found a way to clear the cache like on the tablet or android phone? If not, would individually clearing app cache do the same thing?
Edit: Think I know how to do it. I will try when I get home and report back. Can get to fastboot menu with steps in the user guide. From there I'll have to see.
http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=About_SHIELD.htm
Root cleaner I'm using, but you need rooted and preferred busybox installed but it's working without that too. Busybox apk you can find on Internet.
Sent from my Nokia 3310 using free xda app
LunarHound said:
Anyone found a way to clear the cache like on the tablet or android phone? If not, would individually clearing app cache do the same thing?
Edit: Think I know how to do it. I will try when I get home and report back. Can get to fastboot menu with steps in the user guide. From there I'll have to see.
http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=About_SHIELD.htm
Click to expand...
Click to collapse
Did you ever successfully clear the cache? I can get into the fastboot menu, but when I choose "Continue," it just boots into the Shield operating system (is it supposed to do that?). I can't find any information on what options to choose. I can't find anything on what each menu item means and I know you can do a factory reset from the fastboot menu, so I'm afraid to choose anything.
Can someone explain what each menu item means? I don't want to do anything irreversible.
Continue
Boot recovery kernel
Forced recovery
I don't want to factory reset. I just want to clear the cache. I installed an add-on into SPMC and it was super glitchy, caused my whole system to freeze, even after I uninstalled the add-on, uninstalled SPMC, etc. Multiple reboots. Everything just keeps crashing and freezing over and over and over. I have never had this problem before.
So I figured clearing the cache for the whole system might help. A factory reset would just be crazy.
---------- Post added at 03:46 PM ---------- Previous post was at 03:38 PM ----------
I chose "boot recovery kernel," and it brings to a screen that shoes an Android laying down with his belly open. It says, "No command." I read that I'm supposed to press the power button and wait a few seconds and that will bring me to a screen to clear cache, factory reset, etc. But nothing happens. I press the power button and hold again, still nothing. If I press and hold and wait and wait and wait, eventually, it just exits this screen and goes back to the fastboot menu.
I tried again, and gave up. It just sat on the screen with "No command," and as I typed, it just exited everything and booted into the operating system. What is going on?
Related
I am trying to install Dexter's ElocityMod v1.41, and running into two problems.
The easy and final problem is this: how do I know if the mod was successful or not? How can I verify that the A7 is running ElocityMod v1.41.
The confusing problem and first problem I have is this.
I power the machine up, and use the procedure ElocityMod v1.42 thread to enter the Recovery Menu
I press home and see the menu
I select Wipe/factory reset
BUT
At that point I am presented with the following:
Android system recover <1e>
Confirm wipe of all user data?
THIS CAN NOT BE UNDONE.
No
No
No
No
No
No
No
Yes -- delete all user data
No
No
No
E:recovery.c Can't open /cache/recovery/command
Formatting MISC:...
Click to expand...
Click to collapse
So this confuses me. I have a few questions.
Do I want to wipe the user data? What will I lose by doing so?
I can move up and down selecting each list item. Do I want to press MENU and wipe each one?
Or do I want to wipe only the first item?
Or do I want to wipe only the user data?
And what is that stuff at the bottom about can't open a cache recovery command and formatting MISC:?
And finally, is the Elocity A7 easy to brick, or hard to brick and easy to recover from?
Thanks so much
Jerry
What I did when flashing was wipe data/factory reset, wipe cache partition, and then apply sdcard:update.zip. I did the same thing for 1.41, 1.42 and the xbox controller patch. Wiping should erase all data and programs on your tablet. I am not sure how hard it is to brick this tablet but as long as the files you download from that thread don't get corrupted in the download process you should be fine. And even then I think you should easily be able to just turn it off and get back into recovery to flash again.
Thanks, I deleted the user / data partition, and actually did not apply the update (accidentally) and just rebooted to find that the tablet booted up just fine, looking reinitialized to factory defaults.
So I tried again, and this time applied the update, and it worked just fine.
And success seems to be self-evident, in this case, coming up, being asked to setup a "phone", and signing into a google account, and eventually seeing a lot more apps in the drawer, specifically including the market.
One other tip though, you can't sign into your google account until you setup a wifi channel. The tablet wants you to do it the other way around.
And just a note for google 2 step authentication users, if you do use 2 step authentication, then when signing in to an existing google account on the tablet, you do need to use a google application specific password.
yeah kind of dumb it asks for a google login when you don't even have wifi setup. you can also check the what version you have by going into settings and clicking about.
Hi all,
I have a problem on my HD2 with CyanogenMod 7 (v 2.6)
When installing it on my phone everything was working perfectly.
but now... 4 months later, when i go to the menu, browse to Applications, and pressing Manage Applications or Active Services, the menu fades away, and returning to the Applications menu, there is no way of going into that menu.
Rebooting doesn't give any solution.
Does anyone recognize this issue, or know how to fix it?
Alright, Do you use CWM?
Do a backup.
Wipe Cache,
Under advanced:
Wipe Dalvik-Cache, Fix permissions.
Try again, booting will take longer, explanation by Cyanogen:
When Android starts up, the DalvikVM looks thru all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimize the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimized bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's reoptimized and the cache is updated.
Click to expand...
Click to collapse
Try if it works, if not, reflash the rom (that's why you did the backup), and clear those caches again, and fix permissions.
Good luck
I do have Rom Manager, when i want to backup it asked me to install CWM.
after installation and running the backup tool it rebooted without any messages.
I try get into the recovery mode, but i am failing doing that.
in the aMAGLDR v1.12 i held the Power button for a couple of seconds.
a menu appears.. there are 10 options, but non of them is related to AD Recovery.
what do i wrong?
BTW.. it's funny to see you as living in the same place
oops.. i think i screwed up some things..
In the rom manager menu, i selected the Fix Permissions item.
After a couple of minutes and applying of permissions i had to reboot the phone.
..and now it is in a reboot-loop.
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.
My settings force close and have went through cleared cash, closed apps recent, even went to safe mode and still forces close. Any ideas besides the ones you can dig offline?
I think a simple factory reset and clearing cache partitions will do. Try clearing only cache partitions first see if it works alone if not then factor reset (from recovery menu)
sarsary said:
I think a simple factory reset and clearing cache partitions will do. Try clearing only cache partitions first see if it works alone if not then factor reset (from recovery menu)[/QUOTE.
Found out at one point recently i had applied substratum theme and did a theme. Caused conflicts so i uninstalled but apps it added sometime later caused issues and locked me out. So downloadd a ram booster which let me scan for running apps and seen android symbol by the apps and removed. Walla. Thanks for help. Hate starting phone fresh after swipe or factory reset. There is an answer if ya look. Just couldnt find till now.
So note to any users clean out unused apps and attached files. They can cause issues down road!
Click to expand...
Click to collapse
At first I thought I had downloaded an app that was just being an asshole and wiping my device. But now I think that this head unit has some kind of protection or something. I had downloaded an app to reboot into recovery, but it said it needed administrative permissions so I di ti and as soon as I did it, the device reset into recovery (without me telling it to) and proceeded to wipe itself.
But now, I just tried to mount the system as writeable using /dev/block/platform/soc/11230000.mmc/by-name/ and as soon as I hit enter, the device reset and wiped itself.
Has anyone heard of anything like this? I am about to lose my mind if I have to go through setting this thing up again for it to just wipe itself. Would diabling or enabling Preserve AVB 2.0/dm-verity help this? Does anyone know what is going on here?
Also, I tried to sign up at the 4pda site but I cannot get through the captcha