running vegan and i keep getting this message. I think my wife was using it and maybe the battery died? not sure. any thoughts?
thanks
I get this about every 2 weeks. I boot into clockwork, reset to defaults, then restore from backup.
sent from my g-tablet using tapatalk
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Steps
Posting the steps you took might be a little more helpful to anyone reading your thread.....
gpzjack said:
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Click to expand...
Click to collapse
Which data base?
Do you mean perform a clear cache/data?
or are you mentioning the contact database sync from gmail?
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Thank you so much, this worked for me!
gpzjack said:
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Click to expand...
Click to collapse
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
yup the contacts storage got corrupted -> most likely you created an empty contact in the contacts app by mistake. Someone should sticky this - i see one of these threads daily haha. Its a pretty common problem.
many time that error (fc) is due to a contact with blank first and last name as the contact database uses them as index. if you have blanks the probem will keep returning.
thanks for the tip - seems to have helped me out of the
...acore... problem
Mind you, I **Never** touched the contacts app in any
way whatsoever.
The corruption happened "spontaneously"
After playing (it is *only* suitable for play) with android
for a few weeks now, you know what, android is CRAP
Cant get to Manage Apps
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
cassycan said:
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
Click to expand...
Click to collapse
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Norm Minske said:
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
Click to expand...
Click to collapse
I was unable to see the folder described in other peoples solutions, your solution of clearing data through the settings application worked great for me on brilliant corners 1.3.1. Thanks.
simuloid said:
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Click to expand...
Click to collapse
i manage to get tru the issue on adb shell by installing usb deview, n my command bar alrdy shown my device no. after typing adb devices but aft adb shell, came $ and not #, is there any different?
okay i had mine miracle- ly and not realising it done, my force stop no longer appear after downloading the latest busybox apps.=)
Hi - I was getting the acore error too. but I went ahead & did an nvflash. The error is still popping up. Any ideas?
Related
THIS METHOD IS NOW OUTDATED.
For everyone that is starting from scratch with a wiped NookColor, I have made a linux script available that will do everything for you. This includes enabling apk installs on the device, live wallpapers, multitouch, etc. It will also download and install YouTube, Gmail, and the Market. It also changes the Market fingerprint to that of a Droid Eris on Verizon so you can see protected apps. It does not require use of the Android Emulator to generate an AndroidId as this is done automatically thanks to clockworx. All it does require is that you be nootered and have working Superuser.
Thread here:
http://forum.xda-developers.com/showthread.php?t=871210
DISCLAIMER:
These steps are what worked for me and some may not even be required. If this guide needs any clarification, post a reply and I will do my best to update it. I'm 99% certain all the steps are here.
If you have already tried to get the Market or other Gapps working, etc then it is very likely you will have to do a full factory reset before this will work for you. I have no idea why, but if these steps don't work I would try that first.
In my experience the factory reset is two steps:
8 failed boots restores the /system partition. You can easily trigger this reset without 8 failed boots by running this command from a Linux or Mac OSX command line:
echo -n -e "\008\000\000\000" > /tmp/foo; adb push /tmp/foo /rom/devconf/BootCnt; adb reboot
Click to expand...
Click to collapse
Afterwards:
Booting while holding power+volumeup+nook button restores /data
I had to do both of these steps in this order to get a full reset on the device.
Required:
nc_gapps.zip
system.img for AVD
Youtube for Eclaire
Optional:
Root Explorer really speeds this up. If you have it, I recommend using it as this tutorial is written with it in mind.
* Copy nc_gapps.zip onto the 4gb internal partition of the NC, /media/
* Unmount both the internal partition and the SD card (if applicable) from within your OS but leave the USB cable connected.
* Using a command prompt on your OS, navigate to android-sdk/tools (or platform-tools in newer SDK) and type the following:
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system <-----This can be also done by going to /system/ in Root Explorer and clicking "Mount R/W" at the top
cd /media
miniunz -x nc_gapps.zip -d /system/ <-----Overwrite [A]ll if prompted!
echo "ro.config.nocheckin=no" >> /system/build.prop
exit
Click to expand...
Click to collapse
* Leave this command prompt open, we will need it in a minute!
* Install Youtube App. If you have a previous version installed it's best to use Titanium Backup to wipe it's data then uninstall.
* Run Youtube. Press Menu->My Channel. Log in with Gmail account. If you get the authentication error here you can try rebooting and wiping Youtube data again with Titanium Backup.
* Reboot NC
After reboot:
* Using the command prompt on your OS from before, type:
adb pull /data/system/packages.xml
Click to expand...
Click to collapse
*In this file find the string "uid.system". You should find a line that looks like:
<shared-user name="android.uid.system" userId="1000">
Remove the 3 lines beneath this one. They should look similar to:
<sigs count="n">
<cert index="n" />
</sigs>
n is an integer that may be different for everyone. After removing these lines, the line immediately after "<shared-user...>" should be "<perms>"
Save.
* Using the command prompt on your OS:
adb push packages.xml /data/system/
Click to expand...
Click to collapse
Reboot NC and disconnect USB.
Gmail should work but running the Market should load the TOS after which you will get a server error. This is caused by our device not having a valid androidId. Let's generate a valid androidId using the AVD emulator.
Create a new AVD for Android 2.1-API Level 7 using these settings:
SD Card Size: 100M
Skin: Built-in: Default (HVGA)
Hardware Properties:
Abstracted LCD Density: 160
Touch-screen support: yes
Device RAM size: 1024
Once the AVD is in your list, click on it and then click Details on the right hand side. Note the path and move the system.img you downloaded in that directory.
Start the AVD. When prompted, sign in with your existing Gmail credentials. Use CTRL+F11 to slide the keyboard in and out when prompted.
Run this command to get the androidId from the emulator:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Click to expand...
Click to collapse
It's the long number after androidId|, SAVE IT!
Now, connect your NC back to USB.
On the third command below, be sure to replace ANDROID_ID_FROM_EMULATOR with the number I just told you to save.
adb pull /data/data/com.google.android.googleapps/databases/gls.db
sqlite3 gls.db
update meta set intvalue='ANDROID_ID_FROM_EMULATOR' where name='androidId';
.q
adb push gls.db /data/data/com.google.android.googleapps/databases/
Click to expand...
Click to collapse
Reboot NC
Wow, that was quite a bit of work to figure out, to be sure.
Thanks, will give it a try!
Does this also provide the Google account setup capability (Reader, Listen, etc.)?
Thanks for the fix first of all!!!
I used root explorer and copied over all of the files recommended, then installed the youtube app you linked to, but when I tried to go to menu/my channel it flashes a message that there was a problem authenticating.
Any ideas?
Thanks!!!
Never mind...
Before doing the androidID stuff, Gmail is supposed to work? It doesn't. Just flashed for a sec and goes back to home screen
Also, there is no Market icon available. Am I supposed to install Vending.apk after putting it in /system/app?
EDIT: Youtube now doesn't work either...
EDIT2: Youtube works after an uninstall/reinstall, and I can sign in. Gmail still doesn't work and no market icon
bazzly said:
I'm confused....
"Using Root Explorer:
1) copy etc, framework, and lib folders into /system."
Those files are already in the /media/system directory....ohh...you talking the root /system not media/system....correct...?
Click to expand...
Click to collapse
Yes, that is correct.
bbtheory said:
Thanks for the fix first of all!!!
I used root explorer and copied over all of the files recommended, then installed the youtube app you linked to, but when I tried to go to menu/my channel it flashes a message that there was a problem authenticating.
Any ideas?
Thanks!!!
Click to expand...
Click to collapse
Try rebooting first. If that does not fix it then try clearing the data for the youtube app. If all else fails do a complete factory reset and start this from scratch. The youtube authentication issue was my biggest hurdle and I ended up doing a factory reset myself.
Xhorder said:
Before doing the androidID stuff, Gmail is supposed to work? It doesn't. Just flashed for a sec and goes back to home screen
Also, there is no Market icon available. Am I supposed to install Vending.apk after putting it in /system/app?
EDIT: Youtube now doesn't work either...
EDIT2: Youtube works after an uninstall/reinstall, and I can sign in. Gmail still doesn't work and no market icon
Click to expand...
Click to collapse
Same here...
Does the build.prop contain a valid version string which allows market access?
Also, there's a new version of the market going about too
Ok so I got past the youtube and now gmail works and the market gets the server error. However, I cant seem to get started with AVD to get the android ID... are there some more detailed instructions for an AVD noob???
bbtheory said:
Ok so I got past the youtube and now gmail works and the market gets the server error. However, I cant seem to get started with AVD to get the android ID... are there some more detailed instructions for an AVD noob???
Click to expand...
Click to collapse
Were there any variations from the steps above that you made to get gmail working? Not sure why mine is flashing then closing.
norkoastal said:
Were there any variations from the steps above that you made to get gmail working? Not sure why mine is flashing then closing.
Click to expand...
Click to collapse
No variations from the steps above other than fixing the permissions on the files that I copied over... They need to match the permissions of the other files in the respective folders.
Managed to get Gmail, Reader, and Market working. However, every download on the market fails. When I run a logcat i get "authentication failed"
I did replace androidId using the emulator.
Any ideas?
Nice! this works great! just tested out couple free apps from Market and both installed and worked fine. Thanks for figuring this out! finally I don't have to hunt for apk files
-----------
buy the way, AppBrain works fine with Market too.
From my pandigital days I have this question: does enabling google market and other apps prevent your nook color from staying in deep SLEEP?
Sent from my LogicPD Zoom2 using Tapatalk
I had an issue because I had not ever logged into youtube with my gmail account. I went to youtube.com and logged in, then was able to log in using the YouTube app.
Can someone plase post some AVD or emulator instructions??? That would be awesome!!!
For avd, you have to have the Android SDK installed. Then you can run (sdk folder)/tools/android to start the avd manager.
msid said:
For avd, you have to have the Android SDK installed. Then you can run (sdk folder)/tools/android to start the avd manager.
Click to expand...
Click to collapse
When I do that I get this message:
[INFO] Starting Android SDK and AVD Manager
'java' is not recognized as an internal or external command,
operable program or batch file.
bbtheory said:
When I do that I get this message:
[INFO] Starting Android SDK and AVD Manager
'java' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
You need Java. (java.com)
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
Hello,
Here is the short story.
I have Samsung Galaxy ACE which is rooted.
Till y'day I was using CM9 Beta 8 ICS 4.0.4 and it was working well.
I installed CM10 JB for Galaxy Ace alpha1 from "hxxp://maclaw.pl/?page_id=180#comment-3642"
Now the problem is, JB doesn't have File Manager installed and I need to install TB to revert my backups.
Due to some unknown reason I am not able to access internet on my device either through GPRS or 3G connection.
I am desperately looking for a way to access my SDCARD wherein I have all my apk's which I can install however, without File Manager I am not sure how to install an apk.
I did some google search and came across topics about installing apk using Android SDK etc.. however I would not want to work on SDK as I feel its bit tedious job for me.
I also tried Android Injector however that didnt work even if I have enabled USB debugging Mode for adb + apps.
Now, I am hoping that, I can use the Terminal Emulator which is preinstalledo n my phone to install apk present on my sdcard.
However, I am not sure how to do that, It would be really appreciated if anyone can suggest the steps to install apk present on my sdcard from Terminal Emulator available on my phone.
Here are some of the screen captures
http://imageshack.us/photo/my-images/855/screenshot2012072418240.png/
http://imageshack.us/photo/my-images/52/screenshot2012072418234.png/
http://imageshack.us/photo/my-images/822/screenshot2012072418230.png/
Thanks
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
@@
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
Awesome guide !!!! , thanks bro !! :good::fingers-crossed:
Thank you for the guide
it works. thank you
works, thanks
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Really appreciate for the guide man
Sent from my LG-P700 using xda app-developers app
Thanks for the reply... short, to the point, and it works.
DannyShane said:
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Click to expand...
Click to collapse
Hi DannyShane,
Not sure if this is still relevant and you are around here, since it's been a very long time and I stopped using Android
I am not an Android geek but here are my 2 cents...
You need to keep .apk file on the root of the SD CARD instead of a folder. IIRC, I had the same exact error which you had mentioned, I was trying to install .apk which was placed in a folder and it didnt work., then I had to move the .apk file to root and it worked flawlessly.
Extremely sorry for the very late response though. I use my secondary e-mail for this forum and missed replies on this thread.
@ All others who have replied, I am glad that, my little finding helped you guys.
Cheers :angel:
I have a few things to add to hsotnas answer. The insufficent space error seems to be a very generic error on android that can have various causes. Maybe there is something like this in the android source code:
PHP:
try{
installApk();
} catch (Exception ex){
output("Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]");
}
If you understand what I mean
I had this error myself a few days ago and for me it was caused by some left over files in the /data/app-lib directory. It was a self-developed application and I added a library to this directory manually. As I uninstalled the application, it wasn't removed and the reinstall failed with the above mentioned error. So make sure the directories /data/data/app.package.name/ and /data/app-lib/app.package.name/ are empty.
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
PSV_Supporter said:
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
Click to expand...
Click to collapse
Me too same thing happens when I try to install 3.apk
the command used is "pm install apps/*.apk"
Mine are backups of play store
Thankyou for this tutorial... IT WORKS.. Can't believe it.. You made my day. Thankyou :good:
I'm trying to recover an old tablet and need to install a file manager... the touch screen inst working so I thought terminal would do the job... but .APK's dont show when I go to the root of the SD card and type 'ls'
An ideas?
Thanks it works
failed on me ..
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.