Database Info

[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] Ployer MOMO2 rk2818 arm9 rooting?

Hi,
quick specs before the tirade:
Brand: Ployer
Model number: MOMO
Firmware version: v2.2.1_00.04-CN *at* 20110625
Kernel version: 2.6.25_(V2.2_3_718DC(E8_R8)_D2_RHJ_A18* at *0728)
Build number: froyo1.00 MASTER.eng.root.20110323.164551
Android version: 2.2.1
CPU: Rockchip 2818, ARM9, 660MHz
Screen: 7.0 inch TFT, Resistive Touch screen, 800*480.
No external hardware buttons for navigation or volume. Only Power button, menu and esc buttons on the top side of the tablet.
* had to replace at symbols because I am obviously sending email addresses or something... *
I'd also love to link the device so people can see what I am referring to if that helps... ployer momo2 should find the ployer.cn web.
--
I am sorry if this does relate to another thread, I am still trying to work out where I am at with this thing, and do not know enough, and I've been searching for days and days putting off posting and hoping it falls into place, but no luck.
I have a Ployer MOMO2 device, which is a cheap Chinese Tabet, no phone, no camera. Here is the URL to the device: .. well i would but cant link.
My problem is I need to get root access to this. I would ultimately like to have a fresh install on it entirely, as everything is in Chinese up until it boots into the os.
There is no Market app on it, and any websites that need flash try to redirect to market: which the device has no idea about. So, I need Market but this is only part of the reason. I cannot uninstall the default Chinese apps, and I cannot use them either.
I also know it has a cramfs filesystem, which is the reason I cannot perm root using z4root. And unfortunately, z4root also fails to temp root the device, failing and then locking up the tablet, or freezing it requiring a cold reboot.
I have tried various version of r4root, having read others have had success. Not so.
I downloaded rageagainstthecage-arm5.bin which is suposed to work with android 2.2.1, and executed it using a terminal app, which proceeded to fork processes and can adb. However, that is where the success ends.
The terminal freezes, as expected, and I force close it. Reopen it to check root, but it won't open. The only way I can access the terminal now is to reboot the device, thus losing any temp root access.
Ugh.
I've tried 1click, as well as other recommended once, but not having the options to boot into recovery/bootloader etc, I cannot complete any instructions on those guides.
I also just wanted to see how I could go about the process of updating the system, using update.img on the sdcard, not intending to do it, but to just gauge the process for now.
It detects the image but says it's corrupt and asks me to delete it.
This was the update.img I got OFF the tablet. It wont even accept it's own? Nah Im doing something fundamentally wrong.
I've been trying so many things, I'm lost.
I simply need to know which direction to attack this issue, and I've seen other rk2818 images out there that have been edited to include root access and market, so for those guys it's possible.
Can someone please offer any advice, keeping in mind I'm not well versed in this, and may require more than cliffs notes...
I really do feel as if I've made complicated something that does not need to be so.
Thanks in advance for any help,
Cheers!

ihave the same tablet u need rktoolupgrade and the firmware from alcordigital website (search on google) .
to install this firmware first open rktoolupgrade ,hold the back key in your tablet and plug usb cable(keep holding back key) windows will find your tablet xp will demand to install drivers(upgrade work only on win xp)choose the driver for xp it is inside rktool folder (driver/86/xp)
open image you will see grren led in rktool then clic upgrade wait when it finish you will see a message (1ok,0fail)
sorry for my bad english i hope it will help you .

[Q] eMatic oem folder

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

[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.

[Q] Root Vivitar XO (Kids tablet)

Hey guys!
First off, any help or info on this is GREATLY APPRECIATED!!
Just wondering if anyone has any info or knows where I can find, how to root this Vivitar XO, children's tablet?
My daughter just won this at preschool. It's ok, I guess, its similar to the other kids tablets with the "kid UI" and the normal Android UI, we see on our phones and tablets. it does have decent specs (below) for a kids tablet, better than most so far, especially in the $150 range..
Hopefully, some kids with hacker parents/siblings gets one soon, so we can really make this thing cool! :fingers-crossed:
If anyone knows anything now, please share the knowledge, a very generous beer/coffee donation's waiting! :highfive:
THANKS!!!!
Technical Specifications
Size: 7.6" x 4.65" x .39"
Screen Size: 7"
Screen Resolution: 1024 x 600
Storage: 8GB
Processor: 1.6GHz dual core
Operating System Android: 4.2 (Jelly Bean)
RAM: 1GB
Wi-Fi: 802.11 b/g/n
Camera: 1.2MP Front-Facing / 2.0MP Rear-Facing
Battery Life: up to 7.5 hours

I'm interested in this too - I hooked up with USB debugging turned on and tried adb, but it couldn't see the device. I'm guessing this is due to a generic adb driver not working, but I suppose there could be other secret sauce (e.g. adb.ini magic numbers) needed too.
I'm eager to try some scans for e.g. the Master Key vulnerability and point the Impactor to it - if I can just get adb to see the device! Please, anyone, let us know if you have success getting adb working - I can't stand having an un-rooted tablet in the house!

Magic numbers for XO Tablet
microwiz said:
I hooked up with USB debugging turned on and tried adb, but it couldn't see the device. I'm guessing this is due to a generic adb driver not working, but I suppose there could be other secret sauce (e.g. adb.ini magic numbers) needed too.
Click to expand...
Click to collapse
Interested too but I found the magic numbers !
If I add following lines to the Google generic USB driver, I could see the XO Tablet from ADB:
;XO Tablet
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8007
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8007&MI_01
Hope that help and you could find a way to root it
Let us know !

Vivitar Camelio Tablet Root Method (no fastboot or bootloader)
I have a Vivitar Camelio tablet for my kids and I have rooted several tablets and phones and understand as a tech myself what to do in most cases...
I want to root and remove bloatware and test some customized JB roms on this basic tablet.
I can connect and see it using PdaNet drivers and I can only backup/restore via adb but when I try to run any fastboot commands I get errors such as fastboot device not detected.
This vivitar stock tablet has a custom 4.1.1 JB rom on it stock. I cannot boot into download mode. However I can boot into its stock recovery with just a few options available such as sideload, wipe cache, factory reset and also reboot. I can see the device from ADB but cannot use fastboot commands without the no device error.
*****
A way to root this tablet and without the bootloader accessibility I cannot do this. I will pay via paypal 10 whole US dollars for the first person that can successfully walk me through this. We can use gotomypc or to video conference or simply you can draft up the steps I need to perform. I am ok with bricking this toy my kid is 3 and the device is a bit much for her at this point so I'll try anything to unlock the bootloader so I can root and rom it.
I was able to gather tablet information but this is all that was displayed via ADB.
DEVICE INFORMATION:
Product Description: Camelio Family Tablet
Device Product: (Blank)
Device Type: PI070H04CA
Firmware Version: 4.1.1
Firmware Build: JRO03H
Firmware Region Code: (Blank)
Bootloader Version: (Blank)
Boot Image Status: Secure
ANY HELP I S GREATLY APPRECIATED!
This tablet is pretty good for the $99 price tag so this should be a question that will be asked again and again by others in the future. Help me on this one and you can post the Vivitar Camelio Root method update and take all the credit for it
Thanks!!!!!!!
Jason

Problem Solved!
Root your device with Kingo. here is the link! Enjoy!
Google Kingo Root and you will find it quick and easy.
Jason
Rooted Camelio Tablet and S4 Mini with Kingo.

lionel911 said:
Interested too but I found the magic numbers !
If I add following lines to the Google generic USB driver, I could see the XO Tablet from ADB:
;XO Tablet
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8007
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8007&MI_01
Hope that help and you could find a way to root it
Let us know !
Click to expand...
Click to collapse
I found another way of waking up adb and getting it to see the "XO Learning Tablet" over USB debugging - I kind of cheated by launching Moborobo :/ but at least I got connected.
Anyhow, after that, I checked with the SRT AppScanner and both existing Master Key vulns were still present on the 4.1.1 build of Android that the tablet ships with. I tried the first option in the Cydia Impactor ("# drop SuperSU su to /system/xbin/su") and had immediate success! Both a shell (which allowed me to su) and activating the Root Explorer in ES File Explorer (after installing SuperSU) worked flawlessly.
Hope this is helpful to folks desiring to root their XO Tablet. Please feel free to ask any other questions you may have!

ReaperMMA said:
Root your device with Kingo. here is the link! Enjoy!
Google Kingo Root and you will find it quick and easy.
Jason
Rooted Camelio Tablet and S4 Mini with Kingo.
Click to expand...
Click to collapse
Kingo root does work on the XO Learning tablet. Also the button combo to get into recovery mode is Vol- & Power at the same time. When it starts up release the power button.

SnoopyII said:
Kingo root does work on the XO Learning tablet. Also the button combo to get into recovery mode is Vol- & Power at the same time. When it starts up release the power button.
Click to expand...
Click to collapse
Kingo Root only worked for me after I ran Moborobo. Before that adb would not find the device, moborobo fixed that.

So I root the Vivitar XO but how would i flash a clean version on android on to it or maybe even sugar.

Camelio F.T ROOT
ReaperMMA said:
I have a Vivitar Camelio tablet for my kids and I have rooted several tablets and phones and understand as a tech myself what to do in most cases...
I want to root and remove bloatware and test some customized JB roms on this basic tablet.
I can connect and see it using PdaNet drivers and I can only backup/restore via adb but when I try to run any fastboot commands I get errors such as fastboot device not detected.
This vivitar stock tablet has a custom 4.1.1 JB rom on it stock. I cannot boot into download mode. However I can boot into its stock recovery with just a few options available such as sideload, wipe cache, factory reset and also reboot. I can see the device from ADB but cannot use fastboot commands without the no device error.
*****
A way to root this tablet and without the bootloader accessibility I cannot do this. I will pay via paypal 10 whole US dollars for the first person that can successfully walk me through this. We can use gotomypc or to video conference or simply you can draft up the steps I need to perform. I am ok with bricking this toy my kid is 3 and the device is a bit much for her at this point so I'll try anything to unlock the bootloader so I can root and rom it.
I was able to gather tablet information but this is all that was displayed via ADB.
DEVICE INFORMATION:
Product Description: Camelio Family Tablet
Device Product: (Blank)
Device Type: PI070H04CA
Firmware Version: 4.1.1
Firmware Build: JRO03H
Firmware Region Code: (Blank)
Bootloader Version: (Blank)
Boot Image Status: Secure
ANY HELP I S GREATLY APPRECIATED!
This tablet is pretty good for the $99 price tag so this should be a question that will be asked again and again by others in the future. Help me on this one and you can post the Vivitar Camelio Root method update and take all the credit for it
Thanks!!!!!!!
Jason
Click to expand...
Click to collapse
Hey Jason, I have the same tablet someone gave it to me. So I've been playing with it seeing what happens but an answer to your question is by Geohot at towelroot DL the file and run it the DL busybox and install it and let it run oh, DL superSU after that try Root Checker from play store you should be rooted. Hope this helps.

After We have Root access, is there a rom We can flash to make this a normal
Tablet?
My kid doesnt like the interface at all.
Just a stock jb 4.1.1?
Thanks much.

Thanks in advance
microwiz said:
I found another way of waking up adb and getting it to see the "XO Learning Tablet" over USB debugging - I kind of cheated by launching Moborobo :/ but at least I got connected.
Anyhow, after that, I checked with the SRT AppScanner and both existing Master Key vulns were still present on the 4.1.1 build of Android that the tablet ships with. I tried the first option in the Cydia Impactor ("# drop SuperSU su to /system/xbin/su") and had immediate success! Both a shell (which allowed me to su) and activating the Root Explorer in ES File Explorer (after installing SuperSU) worked flawlessly.
Hope this is helpful to folks desiring to root their XO Tablet. Please feel free to ask any other questions you may have!
Click to expand...
Click to collapse
...i am very new to android mods.. ive modded xbox1 ,360 ,ps3, jb ipods n iphones but never anything android .. kids got xo tablet for Christmas ..2 kids 2 tablets 1 of which .. my oldest daughter .. 7 .. insist her dad can modify anything lol .. i dont want to brick it and a detailed tutorial or at least point me in the right direction would be greatfully appreciated .. ive looked into it with not many results..if u could walk me through the proper procedure on backing up and reinstalling stock im up to try anything and post results

r2161984 said:
...i am very new to android mods.. ive modded xbox1 ,360 ,ps3, jb ipods n iphones but never anything android .. kids got xo tablet for Christmas ..2 kids 2 tablets 1 of which .. my oldest daughter .. 7 .. insist her dad can modify anything lol .. i dont want to brick it and a detailed tutorial or at least point me in the right direction would be greatfully appreciated .. ive looked into it with not many results..if u could walk me through the proper procedure on backing up and reinstalling stock im up to try anything and post results
Click to expand...
Click to collapse
Did you ever find anything about this? I'm killing myself trying to install cyanogenmod on this tablet after I rooted it.

I'm a little unclear on the appropriate rom to install over the old one. I assume Cyanogenmod, but I can't find the correct version. Any help?

This really needs a root or firmware if you ever intend on repurposing it. Will have to experiment with ADB and see if I can at least clear out the excess media files. My middle-schooler could probably still make use of it as it is (having a restricted "child" mode might still be a good idea), but would like to clean up the cruft that's not needed (like a lot of undeletable sample files). But yes, if it could also be permanently set to "parent" mode, and I could put MS Launcher on it, that would be nice too.
I actually ended up with 4 of them, two or three that aren't charging. I'm going to open the two that don't charge and see if I can fix that, at which point they could be available for dev work. (now that I re-located my bricked Nabi2, I should send that one out for dev work too).

If it's of any use, when it's attached to my Linux box, "lsusb" will report it as this:
Bus 001 Device 013: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug)
"adb devices" shows:
XO8801114002af6
as the device name.
Since I can connect it and am able to navigate through the directories on internal storage, I could pull system information if you tell me what you need.

For something that was supposedly an open-specification device, this tablet is sorely lacking in documentation and other critical information. Wasn't the who purpose of the OLPC project (which was selling this tablet) that it was supposed to be open and customizable? Or was Nicholas Negroponte lying to us?
---------- Post added at 10:29 PM ---------- Previous post was at 09:50 PM ----------
Actually, at this point the tablet is garbage. I can't even force it into a factory reset, because I can't get to the bootloader menu. And somehow it has decided to add a secondary password (after the parental password), so there is ***NO*** way to get into a system menu to do a reset from the settings screen. Short of finding a way to short something on the system board, the only thing to do with this thing is to take a sledgehammer to it.
(yeah, it failed just as harshly as the entire OLPC project did, I guess).

So I still haven't found an answer to what the deal *IS* with the XO Tablet. It has all the pretensions of being part of the OLPC Project, but unlike the laptop itself, which was an OPEN design, fully specced, available for experimentation and customization, this tablet seems to be much the OPPOSITE of that, being pretty-much undocumented, and no one wants to touch the things.
I mean seriously, I'd be willing to pull an image from a fresh factory-reset system so that someone could experiment with it. I'd send it to someone to hack themselves, but really, the device doesn't exude any noxious odors, it doesn't spontaneously spring out poison-laced spikes, at worst it looks kind-of 'meh' as far as design goes. So you don't have to be afraid to touch one.
(for that matter, I'd also send someone my bricked Nabi 2S (was that the name for the later revision?); it does nothing for me sitting unused in a closet)

From what I was able to get from someone who had worked/still works for the OLPC project, this tablet was something some execttive had pushed through without Engineering's knowledge, and therefore it was little more than a sugar UI slapped on top of a proprietary device. Released under their name, but that's about it.
System information from the "Hardware Info" tool shows:
System (Android 4.1.1)
Model XO Learning tablet
Manufacturer XiangDe
Device PI070H08XO
Product PI070H08XO
Brand Vivitar
Android Version 4.1.1 (Jelly Bean)
API Level 16
Build ID JRO03H
Fingerprint Vivitar/PI070H08XO/PI070H08XO:4.1.1/JRO03H/XD-XO-BN-29052013.V010:user/release-keys
Although it will prove to be about as useful as anything else, since the configuration files for it haven't magically sprung out of netherspace.

Yes, you can "root" this tablet (it's pretty much open anyway), but even if you leave it at it's default Android version, the UI is still a serious problem. If you want to repurpose it as a normal tablet and not the dumbed-down kids version, you need to get rid of the built-in launcher. I had thought I found how to disable the launcher in ADB, but it only made it not boot, and I had to wipe to the factory image again. How do you even figure out what it's running for it's launcher so you can disable/remove it at the system level?
I know it must be possible to edit the system image itself (that reloads when you do a factory wipe) because I had at some point managed to delete the on-screen keyboard app (when you factory wipe, you have to plug in a USB keyboard with OTG and eventually re-load a KB device). But Android seems intent upon making the internals of the device incomprehensible. Even with all the cruft Microsoft forces on you with their systems, I'd still think the Windows Mobile devices were probably MORE open than Android.
Since I have two of these (the other is stock) I could factory wipe the other one and pull an image, if there were actually some documentation on how to do that. But with Android, you can never do something for the first time unless you've already done it 10 times previously.