[Q] eMatic oem folder - General Questions and Answers

Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.

Ematic: What is the browser?
What is the browser that is install from factory.. on Ematic devices ..as it is not "Chrome" [It almost looks like Dolphin], when I tried to do a regular .apk install of "Chrome" from the Google store it dies which almost tells me that it need to be pushed into the device. So am I correct that I need to find a downloadable .apk of "Chrome" for Android 4.0.3 ?

bfrench1990 said:
Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.
Click to expand...
Click to collapse
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)

fsuinnc said:
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)
Click to expand...
Click to collapse
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.

bfrench1990 said:
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.
Click to expand...
Click to collapse
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)

fsuinnc said:
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)
Click to expand...
Click to collapse
I'll bet that you can get it rooted. You may have to edit those drivers though since I don't think my girlfriend's tablet isn't the same as the one you mentioned.
If the drivers I posted don't work for you, then open up "android_winusb.inf" from that zip file in your favorite text editor.
Somewhere under the "[Google.NTx86]" and "[Google.NTamd64]" sections, add this:
;eMatic egs005
Remember where you put those, cause what goes under those entries is the hardware ID of your tablet. You can get that by going under device manager and right clicking on your tablet, if it is unrecognized it should have a yellow triangle on it or something like that. Go to properties and go to the details tab, then from the drop down menu, select hardware IDs. In my case, two came up. Just pick one. If that one ends up not working later, use the one you didn't try.
Now, your entries should look like this:
;eMatic egs005
%CompositeAdbInterface% = USB_Install, (your hardware ID)
Next, try to update the drivers on your tablet via device manager. Right click on your tablet like we did last time, and click properties. Go to the driver tab, and hit the update driver button. You'll have to manually navigate to where your drivers are. Select the folder where you extracted the zip to (make sure you have the edited file in there!) and follow the procedure to update the driver.
Next, open up an adb window and type in adb devices. If you have something showing up, congrats! You should be able to try the root tool now. As always, be careful!

eglide pro ll xl
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z

Livinbad said:
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z
Click to expand...
Click to collapse
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.

bfrench1990 said:
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.
Click to expand...
Click to collapse
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.

Livinbad said:
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.
Click to expand...
Click to collapse
Check if there's fastboot for this tablet. There's a fastboot command to boot into the recovery. If not, then I would just not flash a Rom

Related

[old guide] moderators please unsticky and replace with the new guide

THIS GUIDE HAS BEEN REDONE. PLEASE VISIT THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=761819
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Rad_Fishy said:
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Click to expand...
Click to collapse
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
nbs11 said:
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
Click to expand...
Click to collapse
I Fixed it
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Rad_Fishy said:
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Click to expand...
Click to collapse
Thanks! I fixed all those errors but I'm not gonna upload the new version just yet because I will keep finding more errors so it just seems wasteful. I did not actually write most of the guide myself I just formatted it so there may be some mistakes I didn't pick up on.
i used this guide today and it delivered.
orlandoxpolice said:
i used this guide today and it delivered.
Click to expand...
Click to collapse
If there was anything you found difficult or anything you would like to change just tell me and I will add it to tonight's update.
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
ask_j said:
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
Click to expand...
Click to collapse
The SD card is simply the root directory of your phone. You do not need to open a folder, it is the highest folder you can place it in. Hope that helps
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
ask_j said:
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
Click to expand...
Click to collapse
I did not write the PC instructions, so I can not help you (I only have a Mac). But the person who did can probably help you his username is systoxity.
Because not enough errors were found to make it worthwhile to update the PDF i will wait till tomorrow to fix the minor errors.
Good source of information
Thank you for putting this together. I am going to sticky this for the time being.
For installing the latest version of busy box, you should include that before the instructions for running titanium backup...the latest version of busybox installed from the market will work with titanium backup so theres no need to have to click the "problems" button...this way you wont have to do the busybox download step twice...should also save a few megs since titanium backup wont have its own copy of busybox installed BTW nice guide
You can also just mount the phone memory using windows explorer and move the file over. I was never able to get droid explorer to transfer the file. It always said it went but then was never there.
Anyway all I did was connected just as I was going to connect to kies but then when windows asked me what I wanted to do I clicked on open file view and dropped updated.zip on my phone.
Only issue that I had with rooting was I accidentally opened the file in windows(winrar). After I moved the file over it found it and attempted to install it but then exited with an error(do not remember exact error), but had to do with mounting. Anyway I re-downloaded file and saw file size was different. After I moved the file over again everything went great. I still haven't removed bloat-ware and such but thats next on the agenda.
Also I was on windows 7 64 bit, saw some other users in other threads saying they had issues connecting the phone. Everything so far has worked great for me
Thank you very much for this handy pdf file!
Somelinks aren't working
First of all I have to say very good guide for noobs!
1. when I downloaded the update.zip folder I didn't work I guess because the name of Samsung captivate is not in the folder or something. So I just downloaded the other file from the forums.
2. Link to CPU optimization doesn't work.
3. I downloaded the droid explorer. It connected to my phone but I was unable to transfer anything. So I just tapped on the USB connected in the notification bar and mounted the phone. This allowed me to use windows explorer to transfer files. I believe one can transfer files by selecting the option of Samsung Kies under USB settings.
I got all your feedback. It will all be corrected by tomorrow night.
Cool guide however the rumor is the GPS only gets turned on when pulling up an App that uses it, so that step in the "battery saving" section might not be necessary.
Also you may want to replace Market Enabler with Market Access. It's a rehash of Market Enabler but also has a Set on Boot option that keeps it persistent versus being reset each time.
You also Might want to add a Tips/Tricks Section..
Here You can put some cool tips like the one i found out about backlight control.
(found here: http://forum.xda-developers.com/showthread.php?t=735394 )

[Q] help with IDeaUSA 7" tablet

Hi, everyone
I hope that I am in the right part for posting? I am new to this android thing.
I am trying to find a how to root idea usa 7" tablet from fry's for $77.00. Their is a lot of rooting programs but I have not been able to find anything on this model.
Also what would be a good rom to flash it with? I tried finding out if uberoid and cyanogenmod would work but I could not find any info on this model.
Not to sure what model I have that I would be able to flashing this rom with, either uberoid or CM7? Help
Model: MID, sv7206 v1.4, kernel 2.6.35.7-infotm
processor armv6 rev5,
hardware imapx200,
android 2.3.3,
brand infotmic,
display gri40,
release codename REL
bootloader unknown
I don't know if this is the right model IDea USA IUMID-0071 because the spec's are off. Http ://ideausa.us/produects.html but similar. I am looking for rom that is more update/modern. any potters?
Does anyone have the original rom for this or know how to make a backup this rom?
Well I am thinking that is might be this model but not to sure wm8650,SV7206 v1.4 or IDea USA IUMID-0071.
It's not flytouch
The screen is very slow on this model. Unless you use a pen then is works better.
Also hoping to be able to flash this to ics 4
Thanks
I just bought one, too. What a pos? it works but the screen is almost unusable, lots of mis-fires.
I did figure-out the real OEM web-page,
http://www.sinovideo.com.cn/Products/indexshow.asp?lang=EN&SortID=61&ID=85
This correctly identifies the installed 2.3 OS and reveals that it's some kind of 1 GHz processor. The real performance problem, however, is the 256 MB of memory, ouch!
I have not had any luck finding any updated ROMs. Actually, I suspect the installed ROM is tweaked to work around the defective screen (I think it's configured to ignore any 'touch' lasting less than 0.5 second?) so I'm not going to change it.
---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------
FYI - I found another site that has lots of discussion about the "M7206" tablet
http://www.techknow.t0xic.nl/forum/index.php?board=51.0
Here's some more info. (Yes, I have continued to investigate even though I bad-mouthed it )
- This tablet is also sold as the "infotmic m7206"
- the screen works MUCH better if you use a stylus
Currently, my tablet seems to be getting about 24 hr standby battery-life, and the battery-usage report says "Cell standby" is using 75%, even though there's no cell radio? Some of the discussion on the techknow forum seems to be about this same issue but all the solutions seem to involve rolling your own ROM, which I'm not prepared to do. For now I just plan on leaving the tablet plugged-in overnight.
Rooting Idea USA Tablet
Oh my, what a mess...
This post is in regards to the Idea USA Tablet (Unable to Root)
My specs:
- Idea USA Tablet (Made in China)
- Model Number: MID (Unknown)
- Android Version: 2.3
- Kernel Version: 2.6.35.7
- Build Number: MID-userdebug 2.3 GRH55 (ENG)
Issues:
Whelp, I have tried the basics and I can't get this thing to root for anything. I was able to get it to hook into the PC through USB. There are 2 usb slots on the side of the tablet. I believe one is for HOST and the other usb is for OTG (Charging). Once I figured out the host port, then I had to download the drivers for this poorly made tablet...But, what drivers? You go to the Idea US website and you get no helpful information. So, there are no drivers made specifically for this $100 dollar generic tablet from FRY's. Ok... No big deal... So, I download the default "Android USB Drivers".
Peachy, it worked! Now, I can transfer files back and forth between the card(s). Wonderful, first step down, next step was to root. So, I read up on how to root with Super One Click.
Ok, so now, I set the tablet to "USB Storage" and "Host"...Then I download and run Super One Click.
Ok, I run the "Super One Click v.2.3.3"; by clicking the root button and then all I get is a frozen screen that reads:
Code:
Killing ADB Server.... Kill Server 0.11s
Starting ADB Server.... StartServer 4.09s * daemon not running. starting it now on port 5037* *daemon started successfully*
And then it just freezes the program. So, now I'm completely stuck. I mean I learned a great deal, that I can hook up a keyboard, mouse, etc to this thing, but, obviously Super One Click was not designed for these generic tablets. I have read other articles which have suggested that the .inf driver for the default "Android USB Drivers" needs to be edited for your specific tablet model and you must enter the specific CODE# for it to recognize for rooting with Super One Click... But, god forbid, I haven't found any useful information on where that might be. Also, someone suggested to install the Android SDK and edit those files along with the .inf files to make this work. But, that didn't work either. I did everything right. I turned off USB debugging and then I would wait for super one click to come up with waiting for device...but that never happened. I even tried it with USB debugging on... still nothing.
Has anyone created a generic batch program to root these types of devices? What am I doing wrong here?
Rooting Idea USA Tablet
Well, this took me all night to read and learn about how to root this basic tablet from Fry's.
First off, I tried many different things and it just didn't work. Using super one click is definitely out of the question for this particular tablet.
I read all night and thankfully found the forum article on how to solve this issue on xdadevelopers own forum.
As per quoted quotes below:
.....You can use gingerbreak to root this. Run it once and let it reboot, then use supermanager free from market to rename the su symlink from /bin/ to "old" or something, and reboot again.
You should now have root ........ It might take a couple of trys but it works.
You need to download supermanager from the market. Enable root in supermanager settings and click yes when superuser pops up.
Then use the file explorer within supermanager to navigate to the /bin/ directory and you will find a sysmlink called su
You need to rename this su symlink to old - completely take out the name su.
Just to be safe run gingerbreak again and then you can install busybox from market.
pablo11
Click to expand...
Click to collapse
Thank you so much Pablo11. The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts. Nothing will run right. Things will break and it will be a complete mess. It will however, install superuser apk. However, it will not work. You can download the Root Checker from the market and you will notice it is NOT rooted. So...thanks to pablo11, you will want to download supermanager from the google play market. Install it.
Next go into the supermanager settings and click on ROOT. Make sure root is enabled and checked marked in the settings. When you enable root in the settings, it will prompt you with "allow root?" Click on Yes. This will give you the access you need.
But, your not done, once again as per Pablo11, go to the super managers file manager section. Get to the root directory by clicking up, and then find the folder "bin". Look for the file "SU" and rename this to "old".
Now, you will be able install busybox and any thing else thats root.
By the way, restart your tablet again, and I "personally" recommend that you go into your settings> Privacy> Check mark both (Backup my data and Automatic Restore) and then click on Factory data reset. Start the tablet from like it was brand new. Don't worry it will keep the root that you did intact. You will just have to re-register the tablet with your existing gmail that you originally used with that tablet.
Lastly, use the root checker from the market and you will see that it is successfully rooted.
Okay... Now, my next step. To crack open this tablet and put in a bigger SD Card as the 2G SDCARD is way too small, especially if you want to use new roms and install a linux operating system onto it....

[Q] FileMate Clear 7" T720 tablet

Does anyone know if Z4Root will work on this tablet? Thanks!
I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!
I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)
I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...
I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.
How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.
jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]
ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.
cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk
Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.
Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.

Broke my New phone Installing Gapps??

I just bought a Chinese phablet and was excited about the good deal I got for $250. The phone (Ginwave G503) arrived on Monday and I was disappointed to learn that the retailer did not install google apps as they do for some of their chinese phones. I figured I would just look around the internet and just install them myself. This proved to be much harder than I thought. I came across a German forum for Chinese phones and installed the google apps package that one user had uploaded to my system/app/ folder and it didn't work. I was told in the forum that It might not fork because I used some old files for Android 2.3. So they pointed me to a thread with a newer version and I deleted everything I had copied into the system/app/ folder and then replaced them with the new files. Then even less worked. My phone didn't ring anymore, sound didnt work, and the play store wouldn't even start at all anymore (it gave me a download manager stopped error or something like that). So then I figured out that those files were probably for Android 4.1 and my phone has Android 4.0.4. So then I found a package on rootzwiki for 4.0.4. I again deleted all the stuff i had put in the system/app/ folder and did a factory reset.
When I restarted the phone I was not able to install my ES File Explorer from my SD Card again. When I click on it it asked me if I want to install to phone or SD card, no matter what i select it says "X Application not installed". So I went into the chinese app store that was on the phone (called 360 followed by some chinese symbols) and actually found ES File Explorer on there. But when I tried to install it from ther, it downloaded and then gave me the same error. No matter what apps I try to install, I get this error now. What can I do? Did I break my phone?
If I did end up breaking the Rom and can't find a replacement rom for this phone online is there like a universal android version that can be installed on any phone? Would there be any way I could somehow play a new Android on my phone without having to know how to program something
Wow.. This forum is extraordinarily worthless
u should think before bought a phone/tablet from china,dude...
agstwn21 said:
u should think before bought a phone/tablet from china,dude...
Click to expand...
Click to collapse
At this point, it's not where he bought it from, it's what he did to it. Sorry to say OP, but you're very far up ****'s creek.
If you can't get ahold of the factory ROM and no one has made an aftermarket ROM for your device, you're going to have to learn to compile yourself. I wouldn't advise you do that, however. Based on your original post, you don't do any research before mindlessly flashing any old thing from the internet to your device.
If I'm coming off as a ****, that's because you want to call xda worthless when you clearly have your head up your ass. Someone might've tried helping you before you insulted the forums.
The only thing I can suggest now is using recovery mode to factory reset your device. This might only work if you still have your factory recovery; you never mentioned that you flashed a new one and I can't imagine you flashed anything to your phone without a custom one... But again, reading your OP it sounds like you just flash things all willy-nilly.
BTW, your device didn't have gapps because it's probably not approved by Google to access the play store. No access to play store = no gapps.
stefan0325 said:
I just bought a Chinese phablet and was excited about the good deal I got for $250. The phone (Ginwave G503) arrived on Monday and I was disappointed to learn that the retailer did not install google apps as they do for some of their chinese phones. I figured I would just look around the internet and just install them myself. This proved to be much harder than I thought. I came across a German forum for Chinese phones and installed the google apps package that one user had uploaded to my system/app/ folder and it didn't work. I was told in the forum that It might not fork because I used some old files for Android 2.3. So they pointed me to a thread with a newer version and I deleted everything I had copied into the system/app/ folder and then replaced them with the new files. Then even less worked. My phone didn't ring anymore, sound didnt work, and the play store wouldn't even start at all anymore (it gave me a download manager stopped error or something like that). So then I figured out that those files were probably for Android 4.1 and my phone has Android 4.0.4. So then I found a package on rootzwiki for 4.0.4. I again deleted all the stuff i had put in the system/app/ folder and did a factory reset.
When I restarted the phone I was not able to install my ES File Explorer from my SD Card again. When I click on it it asked me if I want to install to phone or SD card, no matter what i select it says "X Application not installed". So I went into the chinese app store that was on the phone (called 360 followed by some chinese symbols) and actually found ES File Explorer on there. But when I tried to install it from ther, it downloaded and then gave me the same error. No matter what apps I try to install, I get this error now. What can I do? Did I break my phone?
Click to expand...
Click to collapse
Before anyone ever uses a new device thee shall make a Rom Backup; just in case... (at least i would do this).
Anyway; i don't understand why you've put the *.apk file inside the \System\apps folder...
You should try (have tried) to install Android SDK (If you've not installed already); and install the *.apk through adb.
Check these:
http://www.xda-developers.com/xda-tv-2/pro-tip-number-4-installing-applications-using-adb-xda-tv/
[and]
http://forum.xda-developers.com/showthread.php?t=879701
I don't believe that the operating system blocks "Google Apps / Play Store". Either way i'm not going to say that it is impossible. But it doesn't make much sense.
But like "rockingondrums" said; If your device doesn't have have "gapps"; it's probably because it's not approved by Google to access the play store.
No access to Play Store = No "gapps"...
(Never seen that happening though)
Also you didn't need to root your device for that. "Play Store" doesn't require Root Permissions...
In order to help you (and help yourself up); I've done research for you (just because i understand your situation).
1st of all you shouldn't insult XDA Forum. This Forum has loads of information scattered around. Just dig like everyone else... There's probably the info you need. Yes it may take hours, day or months if you have no idea of what you're messing with. If the info is there, just don't expect people to do the research for you...
But, XDA is far from being "worthless". I've lost the count of how many times it helped me; and what i've learned is priceless. (And i still don't know everything i want to know ^^)
2nd; [Get your Device Working]
If you haven't messed up much... (Like flashing a wrong Rom)
Use "Recovery Mode" to "Factory Reset" your device.
I'm not sure if the method i'm about to show, works for every device or for your device; but it's a good example.
On my device i would do:
- Turn off the device;
- Press and hold in the following order: Camera Button; Then Volume - and then Power Button; let it vibrate 3 times; and then release the buttons.
In other words; this will "Reinstall / Reset" your system. You'll see in your screen if it works. Just dont turn off your device in any way while it's executing that operation.
Note: It may be different on your device. If it is... You have to search for a different method that will work for you.
Search this forum, Google, or Ginwave Website (if it has one...)
After this; i recommend you to do some search and learn on how to backup & restore your device.
Search XDA Forum. Grab some examples, compare the info you've got; then backup that device.
3rd; If you've flashed a wrong Rom; then you really have to compile your own, as i also couldn't find a Stock or Custom Rom for your device.
Note: If you (ever) find a Rom for your device; remember that it has to be A ROM FOR YOUR DEVICE! AND NOT SOME OTHER. Otherwise you'll probably end with a dead device...
And that would be sad and wasted money.
Here's a good example on how to flash a Rom and a good place to start with:
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Do some more reasearch; and now don't ever say that XDA is worthless.
P.S - Experienced People aren't here every day and every hour just for you... Sometimes you've got to wait and pray for a god answer (lol - so true...).
I hope this helps solving your problem.
Best Regards;
stefan0325 said:
If I did end up breaking the Rom and can't find a replacement rom for this phone online is there like a universal android version that can be installed on any phone? Would there be any way I could somehow play a new Android on my phone without having to know how to program something
Click to expand...
Click to collapse
Hi,Did you have chance to find ROM-replacement? D you have any ROM image for this Ginwave GnoteM?

[Q] Exchange the whole UI stack on Android

Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Nick Hill said:
Hi
I am new to hacking android. I have built linux distros in the past, and have worked with Linux for 15 years,
I have just rooted a ZTE V965. It doesn't come pre-installed with Play store, and has all sorts of ZTE-specific Chinese apps. It has a good baseband circuit, a good screen, reasonable camera and I think is a great value phone, apart from the awful UI.
It is an android phone, although heavily customised. It has an MTK6589 processor coupled with 4Gb ROM and 512Mb RAM.
I have other phones which operate a much more "Vanilla" android. For example, the Guophone 9105 which also uses an MTK6589. This has a troubling tendency to reboot every random interval. Approx 6 times a week.
I have had success in the past running Linux systems built for much earlier kernels on later kernels. This suggests the ABI (application binary interface) for the Linux kernel changes rather slowly.
I am wondering how well the userland apps are separated from the kernel and drivers on Android.
Specifically, is it feasible to dump all the UI stuff from one phone onto another then change the init to launch the other UI?
Would this risk bricking the phone, or would the shell commands and ADB infrastructure still likely operate?
I guess I should change the bootloader to one that supports fastboot first, right? Is ther a how-to on achieveing this from the root shell?
Thanks for any thoughts
Nick.
Click to expand...
Click to collapse
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
I really need to get google play working in this phone, read a lot of stuff, tried many things, but I havent succeeded yet. Please let me know if you make any progress.
In China they are flashing this phone, found some ROMs even, but I am not sure how they manage and google translate isn't much help there.
http://www.romjd.com/Device/zte-v965/hot/all/1
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Byte_Me said:
Hmmm my V965 is having some issues now
After a factory reset, the setup wizard keeps crashing. Even after another resest. So I can't get in the phone anymore.
Any chance you can send me the USB drivers that are on the phone? My phone isnt deteceted anymore, so I can't access the drivers, which I want to reinstall. And of course they are not on the ZTE website.
Click to expand...
Click to collapse
Hi
You can temporarily download the ZTE v965 USB drivers from
www dot nickhill dot co dot uk forward slash ztev965usb dot zip
Byte_Me said:
Hi Nick, I have the same phone. I'm also very new to android, last phone was iOS and before that windows. I managed to root the V965 using Vroot. I also managed to install SuperSU and CWM. However, the CWM is not fully functional, I can only do a factory reset, not install any packages or roms. Probably the phone has a locked bootloader. I can't check, because the USB driver with the phone doesnt support fastboot.
Click to expand...
Click to collapse
Fastboot and ADB appear to be standard protocols, at least on my Ubuntu, which don't need special drivers. However, it does appear that the stock boot loaader on the v965 does fail to incorporate the fastboot option.
If you remove the battery, replace it then turn on holding the volume down, you will get a menu, but fastboot is not there.
I don't know for a fact, but I do suspect that if you have access to the running android system as root, then you could in principle change any of the internal flash data. Therefore, in principle, I guess you could replace the boot loader or anything else in the running android system. Anyone please correct me if I am wrong, or confirm if I am right.
The feature set of this phone seems to be the same as the feature set of my Guophone. MTK6589, dual SIM, etc. So this image may be a good place to start if considering a transplant.
If you have ROMs, then perhaps it is possible to flash the ROM from a root terminal. I'm thinking add the uncompressed ROM to the Micro SD card, then using the dd command, block copy it to the appropriate image area on the internal ROM, reboot, reset to factory defaults.
If anyone more experienced than me with the nuts and bolts of Android can confirm or deny this will work, or where it should be put, please let me know.
An important factor is that the NAND is not locked on the ZTE V965. So if you have a root shell on the phone, you can issue the following command:
mount -o remount,rw /[email protected] /system/
Once you have done this, you will have read/write access to the system partition.
The only thing I then need to know is what should I avoid changing that may break the ADB bridge/root console?
And is all the UI stuff kept together, if so, where?
Shuffle it around a bit, make a new ROM
Thanks for the driver!
Unfortuntely it doesn't help
I found out the culprit, I tried to install gapps (google apps package) to the system app folder. I thought these changes would be reversed with a factory reset, but they are not. Setupwizard.apk keeps crashing and is preventing me from accessing my phone, so I must find a way to remove it from the system app folder. However, since this error occurred, I am not able to contact the phone in any way from the PC. Adb toolkit does not detect it, even when I reinstalled your driver. It's quite puzzling, I dont understand why in recovery mode I cannot connect adb-toolkit anymore.
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
I'm convinced it's possible to flash the phone, it seems they do it a lot in China.
I found a website with a couple of custom ROMs specific for the V965:
http://www.romjd.com/Rom/Detail/17086
And what I suspect is a rooting & flashing tool. Rooting works, I haven't figured out flashing yet.
http://dl.vmall.com/c0xa12brvo
I've also tried flashing from the settings - update menu in the phone, but it never finds the ROM (update.zip)
I did find another problem, I can't be reached on my phone, it always goes to voicemail. Same SIM in another phone works fine. No idea what's causing this.
Byte_Me said:
Got my V965 working again, but it was a lot of hassle with shell access. Still not fully functional, no drives detected when i connect to USB, which is quite annoying, but not more than that. If you ever make any progress with google apps or flashing, please keep me informed, that would make this phone much more useable. I'll also keep hacking away at it, but without a bootloader unlock (I still think this is the problem), I don't think it will be possible.
Click to expand...
Click to collapse
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
You should be able to write this back to your phone using flashtool.exe.
I don't know for sure if this will work, so entirely at your own risk! Just trying to help. If unsure, ask around.
I am new to this forum, so please remember to click the thanks button if you find anything I have done helpful!
Meanwhile, the MTK droid root and tools has a function to remove much of the chinese stuff (once the system has been installed) and there is always the cyanogenmod gapps package. This may be worth investigating.
Nick Hill said:
Hi
I might be able to help you with the problem.
I have a mint, unused ZTE v965. I have used MTK Droid root and tools to extract a backup of the entire new phone. It is currently uploading to www dot nickhill dot co dot uk forward slash ZTE-V965_new_backup.zip
Click to expand...
Click to collapse
The file size should be 635,972,093 bytes and should finish uploading at 04:00 GMT
md5sum 17ecfdd1040d5dbfab70a3adbc24e07a
Thanks for the ROM, i'll give it a go. I will try to install it using the update option in the settings, that seems the safest.
Be careful with gapps. setupwizard.apk + factory reset = a lot of problems (if you install in system app folder)
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Byte_Me said:
OMG that tool is awesome. created CWM boot, installed your ROM, then installed a clean ROM, then installed gapps, all working!!!
Click to expand...
Click to collapse
Firstly, I'm glad it's working for you.
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Which clean ROM did you then install, and how did you install it?
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it.
I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
Thanks, me too
Secondly, which tools did you use? Did you unpack the zip, open flashtools, select the scatter file then program the phone, or did you use some other method?
Click to expand...
Click to collapse
I used MTK tools as described in that topic, rooted, made backup, installed CWM
Which clean ROM did you then install, and how did you install it?
Click to expand...
Click to collapse
I used the update tool from CWM to flash this ROM:
http://www.romjd.com/Rom/Detail/17086
That ROM is not very clean though, You might as well clean your own ROM
Did you then use MobileUncle to install CWM then use the cyanogenmod 10.1 gapps, or did you do something different?
Click to expand...
Click to collapse
CWM is installed using MTK Droid Root and Tools:
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
This gapps version I installed: gapps-jb-20121011-signed
It's installed using CWM bootloader: install .zip package
It is useful to remember that MTKdroidtools has a useful function to remove chinese stuff. I think if more people contributed to the list of Chinese files that are safe to remove, that would be blade.
Click to expand...
Click to collapse
I used the delete China function, but it didnt catch very much. But with all the functions available now, it's quite easy to clean manually.
A detailed step-by-step guide might be helpful for anyone else with the same problem. One of the general problems I find is that there are plenty of guides around referring to this program, or that program, but few are detailed enough for someone who doesn't already know about those programs to use.
Click to expand...
Click to collapse
Yes, I plan to make a topic for this phone, but at the moment I am still testing many things.
I pretty much bricked a Lenovo A766 yesterday, and it took several hours to learn about the tools to eventually unbrick it. I would have rather spent my time understanding what is really going on, rather than spending my time learning vaguely what tool achieves what end result. If I understood more about the Android system, and built that knowledge on my understanding of Linux, I reckon I could achieve much more.
Click to expand...
Click to collapse
I know how you feel, I was ready to toss this phone in the trash
One thing I notice is that tablets and smartphones are actually replacing desktops and laptops. February this year, windows machines were down 7% YOY. I use Ubuntu for my main computer. Using these tools on Windows led me to significant frustration! This has led me to understand why there is a move. Maybe the tools provided for windows need to eventually move to android. We could then potentially use USB OTG to service other android devices. MTKdroidtools and flashtools runnng as a host on a separate Android system would be cool.
Click to expand...
Click to collapse
I have no idea about the possibilities there. I'm not a programmer, just someone who is good with computers and knows a little bit of everything.
PS. I could also use some thanks as well, maybe get some respect around here
Nick Hill said:
...
Click to expand...
Click to collapse
Did you give it a try yet? Another user did and google apps are working for him, so thats 2 for 2.
Are you still on your original ROM? If so, I have a question for you. Do you get notification badges on your icons, for instance, when you have a missed call, is there a red box with a 1 on the phone icon? Also, do your contacts get ID-ed when they call you? I have some problems with that, caused by the country code prefix. I am still running that ROM I downlaoded from the Chinese forum, but if your ROM doent have these issues, I will switch back ASAP.
Nick Hill said:
Firstly, I'm glad it's working for you.
Click to expand...
Click to collapse
as you are a Lenovo a766 owner, may you help me with this?
http://forum.xda-developers.com/showthread.php?p=49076877#post49076877
Where are configuration settings stored accross factory resets?
I have come to the (perhaps erroneous) conclusion that the user interface and what the user will experience is governed primarily from:
the APKs in
/system/app/
/system/vendor/operator/app/
and the configuration files pertaining to the installed apps, which is located at:
/data/user/0/
I guess that when the android device is factory reset, the /data partition is completely cleared, right?
Is there a set of standard configurations which are unpacked from somewhere into /data/user/0/ after a factory reset, or is it normal for all configurations to be stored in their respective APKs?

Categories

Resources