Related
This is a new ipad2 imitation, i'm interested but need community support please:
it is on HSN, these are the specs :
Specs
Model #:
i10-h
Operating System:
Google Android 2.2
Processor:
Samsung A8 Cortex 1GHz
Display:
9.7"; 1024 x 768 resolution; 4:3 aspect ratio
Dynamic RAM:
512MB DDR
Memory Storage:
4GB built-in
Memory Expansion:
microSD card slot
Wireless Networking:
802.11b/g/n
Bluetooth 2.1
Ports:
(1) HDMI output
(2) USB 2.0
(1) 3.5mm earphone jack
Battery:
Lithium-ion 6800 mAh
Measurements:
Approx. 9.64"L x 7.55"W x 0.47"H
Weight:
Approx. 0.8 lb.
Listing:
UL
Country of Origin:
China
I can not vouch for other methods but I have rooted this tablet with SuperOneClick ver. 2.1.1. If you leave "Exploit" on "auto" and click "root" you will be pleasantly surprised. Took me two tries, but if you turn on usb debugging in settings and leave the screen timeout on 30min your golden. Happy rooting.... I'm also uploading a google apps zip file. I unzipped it and installed all the files in the corresponding places to get a working Android Market. I used Android Commander to move the files & install apk's. *NOTE* You need to install the apps in the "/sysem/app" folder in this order...
1. GoogleServicesFramework.apk
2. OneTimeInitializer.apk
3. SetupWizard.apk
4. Talk.apk
5. Vending.apk
6. Gmail.apk
7. Maps.apk
After... Restart, Connect to wifi, and launch Market. You will be prompted to sign in to google. Then you will see Market License blah blah blah...
*Use the attached zip not the one at the following link* But use this link as a guide if you need it... http://forum.xda-developers.com/showthread.php?t=827209
Have fun.
*Zip File Link*
http://www.mediafire.com/download/d85zjeb9b43j9do/gapps-hdpi-20100817-Impression_10.zip
****THIS METHOD WORKED FOR MY IMPRESSION 10 MODEL # i10-50, but UNTESTED by me on other models****
***EDIT*** Sorry guys... you were unlucky because I forgot something crucial.... THE DARN ADB DRIVER.... You will need to go into the device manager and right click the "Android" device with exclamation mark & click update driver. Search for the driver and point the installer to this folder should work on 32 & 64 bit if my edits are correct... Tested on 64 bit Windows 7.
DRIVER
http://www.mediafire.com/?lzrwj65da0c5c63
Also when you install those "/system/app" files above use Android Commanders "Installer" and install them one at a time in the order above. AND AFTER YOU RESTART USE LAUNCHER AND NOT SETUP OR YOU CAN'T ACTIVATE YOUR WIFI.
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
wonkastocks said:
I tried both methods,
SuperOneClick and Gingerbreak both did not work.
The table is running android 2.3.1.
Click to expand...
Click to collapse
Do you have usb debugging turned on, and did you use the latest version of SuperOneClick. For me it stalled when my screen timeout was to short and locked me out of my tablet when the screen cut off. Second time around it looked like it was going to fail, stalled and then prompted me to ok the install of busybox... etc etc. I am also running android 2.3.1 and it worked for me. Just have to keep trying till you get it.
PIC's...
http://img148.imageshack.us/img148/5624/44983779.jpg
http://img225.imageshack.us/img225/3019/68779107.jpg
http://img32.imageshack.us/img32/7827/42856323.jpg
http://img198.imageshack.us/img198/3149/44013908.jpg
Remember i'm running a i10-50, but the pictures speak for themselves. SU, Market...
Fails
I've also tried this on my husband's Impression 10 - same model i10-50. Can you give some details of how you rooted? What programs did you use besides Android Commander and SuperOneClick 2.2.1? Any help would be appreciated.
i just got an impression 10 as well. i10-50 model with android 2.3.1. im interested in more in depth info on rooting it as well. i tried updating firmware from the page it gives from the box. instructions to download the system.img file from the impression site. but i am not sure how long it takes? when i loaded the file on sd card and restarted (power+vol-) one time it stayed on the blue screen with the white status bar for like over a half hour. i thought it froze and restarted. when i tried it another few times the blue screen disapeared and i got a screen full of multi colored lines all down it. when i reseted.you could still faintly see those lines even when its running normaly. its faintly in background and you can see it more on certain pages or folders u open. my first tablet and i wish there was more info on it. any clue what im doing wrong?
dude i do customer suport forthis tablet, as u may know by now............it sux
leader Impression I10-50 firmware update
In order for the firmware update to be completed successfully, u need to first format your sd card via sd card reader or your tablet as follows:
Plug in the tablet via usb to your PC or load your card reader with sd card
Then select and left click whatever removable disk drive your tablet shows up
Select format and make sure the file system is set at FAT32
Select start, your sd card should begin formating.
Once complete, then u follow the 13 steps, but since you have already started step 1-13, just press your -volume and power buttons at the same time (steps 11 and 12 again) and it should update your tab. Be sure to do it twice as far as the volume and power button go so the update completes successfully.
I cannot seem to get this thing to root....tried the above with the external sd unmounted and then removed. Followed the instruction on the gtab post. All I can see is the external sd card. It did install superuser. Without the sd it gets stuck at Step 6.
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
edit: nevermind
StephenMC said:
It took awhile....but switched to EZ File Explorer. And I was able to see the internal sd and copy the files Then was able to install the market! Life is good!
Click to expand...
Click to collapse
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
TC93 said:
Do you know if the root is reversible in case you need to put it back to the factory default? Would installing the image file on the Impression website reset the tablet back to stock firmware?
Click to expand...
Click to collapse
Yes, SuperOneClick has a unroot option as well.
StephenMC said:
Yes, SuperOneClick has a unroot option as well.
Click to expand...
Click to collapse
Thanks for the reply. About that file program you used, the only one I can find with a similar name is "ES File explorer". Is that the one you used?
I can't get it to copy the files over in the system directory, it acts like its write protected and fails the copy. I must be doing something wrong.
Oops yes ES File Explorer...
Need go to settings.... Open menu, choose Settings Check Root explorer and mount file system...
I'll probably just give up on this. This still isn't wanting to write/copy the files. This is the whole reason I returned my Nook Color before because of the hassle it takes to do this.
edit: it copies a few files, but then some files it says it failed.. like the "maps.apk" file.
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
StephenMC said:
Had a few apk's not move as well. I think map was one of them. Just followed the install order and did those from the external sd.....all worked out.
Click to expand...
Click to collapse
Thank you for your help. I finally got it working, I spent hours on this.
But I decided to try that original posts recommendation of using the program "Android Commander". I had to search to find it, but its a Windows program that makes it much easier to copy files over to the root directory. (although I had to change a setting it in so that it auto closes the log window after it copies, otherwise you can't close the log window, or do anything else until its closed).
I wasn't able to copy the maps with that either though, it gave the error that there wasn't enough space. But it seems to be working fine now.
Impression i10-50
I bought the i10-50 and actually love the tablet. With google market installed (update firmware first), I have full access to the market and no problems installing apps. The only con about the tab is no gps. To install the market, I only downloaded the google apps file and installed the apks in the correct order and that was it. No need to root. I am truly enjoying this tab now.
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
ttttttttttttttttt said:
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
Click to expand...
Click to collapse
You can try use adb from Android SDK but this method needs root
We did initially try adb but it was inconsistent during the restore phase. Sometimes it would just stop in the middle and never complete. Didn’t try it on a rooted device. So maybe that would have helped…
Anyhow I found the solution to my immediate problem. Figured out what our MDM vendor refers to as the UDID is really the Android_ID. So by deleting that row from the settings database in our master backup image it’ll generate a new one the first time the OS starts after restoring with CWM.
I’m still a little concerned we’re going to find other issues cause by this cloning method later on but I guess we’ll just have to roll with the punches as they come.
In case someone else ever needs to clone devices like this and in the interest of sharing here’s the basic steps we’re following.
1.) Setup the master device as you like with all the apps and settings.
2.) Install Clockworkmod Recovery on to the master device
3.) Boot into CWM Recovery
4.) Mount /data and connect to adb
5.) Delete /data/nvram/RestoreFlag (this step prevents duplication of MAC address)
6.) Using sqlite open the database (this prevents duplication of Android_ID): \data\data\com.android.providers.settings\databases\settings.db
execute: delete from secure where name='android_id';
7.) unmount /data
8.) Create a backup
9.) Boot the device back in to normal mode and copy the clockworkmod folder to your computer. This the backup image you’ll restore on the other devices.
10.) [OPTIONAL] I deleted the system and cache backup files from this folder and also removed them from the nandroid file. There didn’t seem to be anything in these we cared about so removing those speeds up the restore process.
Once you have the backup image here’s how to restore it on the other devices:
1.) Install CWM Recovery
2.) Copy the clockworkmod folder from your computer on to the device
3.) Boot in to CWM Recovery
4.) Restore the backup
5.) Reboot the device back in to normal mode
6.) [OPTIONAL] Complete MDM enrollment
Sorry for the thread grave dig, but thanks for posting info on how to do this. I have attempted cloning in the past and ran into similar issues. My question - is this process the same for Android Lollipop 5.0/5.1? I have some Lenovo K3 Notes I'd like to deploy and cloning would save a lot of time.
Haven’t had the need to do any devices running 5.x versions so can’t say for sure. I would imagine a similar process would work.
But I will provide a bit of an update. Our initial deployment of 11,000 Lenovo A1000 devices have been out in the field since February/March of 2014 and no trouble has come to light using this cloning method. These devices run 4.1.2
Sometime around May 2014 we did another round that was about 300 Lenovo A3000 devices. Don’t have one of these handy and I don’t remember the exact Android version but it was 4.x something.
Then starting in October 2014 we put out another 9000 or so Lenovo A3500 devices. These run 4.4.2
All around so far so good.
For the A3000 and A3500 there were two changes to the process. For step 5 in creating the backup I had to clear the entire nvram directory instead of just the one file. I don’t remember what exactly but there was something undesirable getting copied over. The result of clearing this directory is the first boot after the restore takes a little longer as each app runs through the “update” process at startup. The second change was I could not get CWM to backup and restore to/from the internal memory so instead did it from a micro-sd card. This ended up speeding up the restore process since we didn’t have to copy the backup to each device and instead just moved the sd card with the files already there.
this should be pinned in android dev
also sorry for grave digging? except this should be a maintained topic. why isnt this an ongoing thread?
Hi all,
I need your help with the following tablet 9" GT90H with Allview A23 CPU/ chipset and android 4.2. I want to backup the ROM, to perform few modifications and to upload the modified image to the tablet, but I am stuck on the first phase (cannot dump the rom).
I tried several ways to do it (actually that I found) to dump/ backup the stock ROM but I was stuck on all of them. First I tried using the clockwork way, but unfortunately my tablet is not supported (and I could not find supported MOD). Then I tried with romdump, but unfortunately I was stuck because the tablet does not have /proc/mnt file. Finally I found a way using the rkdump method but I had non recognize image error (although I am not sure if I found the correct partition to back up - /dev/block/by-name/recovery ). I have doubts if this is the correct partition, because I did a binary copy using dd to a file, which ended up with size around 32 MB (which I found too small for a recovery image).
So that is why I decided to seek help from more advance users (this is my first tablet, and first android experience) and I believe this forum is the right place for that.
My first request is could someone guide how to make a proper ROM backup, that I would be able to restore later?
In addition I want to ask is it possible, once I backed up the ROM, to modify for example the home page (because on the current ROM the home page for all browsers that I install is http://www.baidu.com)?
Moreover I would like to to install the ROM on external memory card and to run the tablet from there (because the internal memory of this table is too low - 8GB but for the system partition I have only 500 mb, which are all occupied with pre installed software). Is this something that I can achieve (android as far as I know is *unix system, and in theory this should be possible)?
Thank you in advance.
For increase space you can use Terminal Emulator for market and must have root on tablet.
Open terminal , and run the commands :
pm get-install-location (this will show you where apps are installing in this moment)
Auto device install is 0 (the tablet chose auto where to install apps,usuale is chosing to internal memory,your 500mb )
internal memory is 1 (Tablet memory - your 500mb )
External memory is 2 this is where you want to instal apps - (your 8GB )
After run the comand and see the sistem is set to AUTO (0) you will run this :
pm set-install-location 2 - This will force apps to instal in your 8gb
to check if is ok , run again : pm-get-install-location
exit terminal emulator
Good luck ! Hope it help you
Problem with my GT90H
Hey Guys,
I have a Problem with my GT90H. It stops to boot at the screen: Tablet PC - Keep Moving Forward.
If i go in the recovery mode. I can reboot the system, but it stops at the same screen like I explained in my first sentence.
The Factory Reset doesn't work. So I read in some communitys that Tablets can be flashed with a new ROM (Android System) over the USB Port from the Computer.
So can anybody send me the Android 4.2.2 Image for my GT90H ?
It's very important. So thanks.
Thanks for your help.
Greetings from
TheGuardianTX
Hi,
so now I have an Firmware as an Image-File at my computer, but I don't know how I can flash my tablet via ADB.
So can someone help me ?
Thanks a lot.
Greetings
TheGuardianTX
As in another thread, I just complete bricked my TS but with help from cheahcl and Lokifish Marz I come back a alive! With more and more people receiving their TS, I feel the need to summarize what I experienced so others wont need to go through all those sh*t. I didn't create any of the tools/step here... All things belongs to the great DEVs of XDA. I just summarize as my personal experiences for your convenience~
<A little background: I am on the 4th list of 1/8/2100>
First of all: Do a backup immediately after you got your TS!
===========================================================
MTK based system is actually very difficult to become brick (almost impossible) as long as YOU HAVE THE F/W SPECIFIC to your TS! The problem is that it seems OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in of the 3rd or earlier 1/8/2100. At least from F/W's point of view. Thus, any F/W that are posted on XDA is NOT guaranteed to compatible with YOUR TS, unless you are lucky!
Since there is NO official/complete deposit of "stock F/W". Once you modified what in your watch, there is no guarantee you will get same version of F/W and it's very possible that your watch will never return to stock!
Part I --- back up the F/W
============================================================
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
*if above link doesn't work, I have a mirror in end of this post.
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. After Step D), you will have a backup of your F/W which 100% compatible with your TS!
Part II --- back up the IMEI and NVRAM
============================================================
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
Tools:
============================================================
Currently I mirror "All tools" here https://www.dropbox.com/sh/tsa2jottw...uIEpOyyDiYWFva until it's shutdown by Dropbox for too much traffic. (Any one can provide me a better place?)
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this version of TS. It ONLY works if your original build version is "20140513.103530". If NOT, DON'T TRY IT. It will just waist your time! You had been warned!
After you played with your TS, maybe you will come to an end that your TS is no longer turn on! Fear NOT! It's just the fan part of playing with your TS!
Return to Stock Steps (F/W and IMEI, NVRAM)
======================================
1. If your TS still can start in system, then just simply follow the excellent guild prepared by MasterZen88 at http://forum.xda-developers.com/showthread.php?t=2641261
2. The only difference is you must use the F/W you backup yourself DO NOT DOWNLOAD THE F/W list in that page!
3. If your TS no longer powers on, or cannot enter the system, please do:
a. Disconnect your TS from PC
b. Still follow the steps on above link to prepare your PC to install the MTK USB driver, read in the "Scatter file" from your backup
c. The only difference is Step 11. Since your TS won't power on, you need to pull the battery, than re-install the battery than connect to the PC.
d. After you did this, You should see the MTK SP Flash Tool start flashing your TS!
4. After restore system, please follow http://forum.xda-developers.com/showthread.php?t=2631953 "Restoring Your IMEI After A Full Firmware Flash" to restore your IMEI and NVRAM or you will not able to make phone call!
Trouble Shooting (common error message from SP Flash Tool)
=======================================================
1. "S_FT_ENABLE_DRAM_FAIL (4032)"
The F/W you try to flash is NOT compatible with your TS. If the F/W is not backup by yourself, downloaded from XDA or anywhere, there is a 99% chance it won't work on your TS!
Sometimes it also indicate you have a bad connection between TS and PC, maybe a bad cable or cradle...
2. "S_FT_READBACK_FAIL(4009)"
I don't really know what caused this... I experienced twice but I just pull the battery again and it's go like normal
3. "S_COM_PORT_OPEN FAIL(1013)"
a. The MTK USB VCOM driver is not properly installed, or
b. Your connection between PC and TS is not good (bad cable?)
c. Due to previous error, you NEED to pull the battery out of TS and put in the battery than link to PC again! The TS will go offline once any failure during flashing process.
I hope this small guide will save someone from the panic time I had....
How to install Play store and (super)SU?
Installation Play Store
====================================================================
It's really easy... just forget code like *#*#2013.... Doesn't work on newer batch! (I only confirmed this on 4th list of 1/8/2100 developer version)
1. Download Google play here: http://www.xda-developers.com/andro...densities-and-the-rest-of-this-weeks-updates/
2. Make sure on TS you enabled the "Setting/Device/Security/Unknown Sources"
2. transfer the file into the internal SD of TS
3. Use the TS' built in file explorer to locate the apk, than just click the apk to start installation.
4. Profit!
Install (super)SU
====================================================================
Just follow the steps below (I only confirmed this on 4th list of 1/8/2100 developer version) , I saw this somewhere in XDA but forget where... credit to the original poster!
1. Launch MTKDroid Tools (please configure it as the steps in OP)
2. Connect TS to PC
3. Click on "root, backup, recovery" tab
4. Push the SuperSU button then choose which version of SU you want (I use SuperSU)
5. After success installation, go to your TS (TS must have access to internet) and launch SuperSU. SuperSU will prompt to update SU binary
6. Profit!
Great Guide. Following your guide I've backed up all the necessary files to go back to stock for AW-420
:good::good::good::highfive::highfive::highfive:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Actually I been to this before... However I don't remember what exactly I did to resolve this....
Basically this tool relie on ADB to get access to this watch. It seems your watch is not communicate correctly via ADB. Maybe reinstall the ADB driver from the All in one tool I linked in OP (even your ADB works)
Sent from my HTC_One_max using XDA Premium HD app
New link to "All Tools"?
Since Loki removed his files, is there another link to "All Tools"? Can't download it at link above.
Thanks!
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Lokifish Marz said:
Sorry about that. Bad part is older firmware and root/patch methods are causing serious issues due to Omate changing the hardware yet again.
Click to expand...
Click to collapse
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Without the "All tools" I worry when people run into trouble, there would be even harder for them to go back.... (not only need to get correct FW but also need to get correct tools). There are so many version on the internet which is at best too old as not working, at worst infested by something...
Currently I put this "All tools" here https://www.dropbox.com/sh/tsa2jottw6f1f72/AAAgDEcvmo7uIEpOyyDiYWFva until it's shutdown by Dropbox for big traffic.
I also add a FW backup for "4h list 1/8/2100", which ONLY work with this verion of TS. if anyone need it...
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
tshoulihane said:
I have a problem making backups - both the nvram and full system backups fail. I suspect it is not finding an md5 application since files.md5 is zero bytes but the filesystem seems to have been copied OK. (with a fairly clean Win8.1 64 install, just android dev tools installed, this is my gaming machine...)
Code:
--->>> Connect to device <<<---
--- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.bin
--- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxxxxxx59988_nvram_140522-194022.tar
Click to expand...
Click to collapse
Did you run the tool as administrator to make the backups?
Stu| said:
Did you run the tool as administrator to make the backups?
Click to expand...
Click to collapse
Yes, tried that. I'm quite happy with my adb access, managed to root my HTC M8, and get shell access on the TS fine (it now has SU working).
I've installed cygwin (overnight!) in the hope that will provide the missing exe that the tool was seeming to want.
lssong99 said:
(Dear Lokifish, please PM me if you have concern of my hosting of "All tool".)
Click to expand...
Click to collapse
It's all good. I'm fine with it. Seeing that folks are now looking at almost 10 different HW versions to deal with, AllTools is going to become really popular.
lssong99 said:
However, the "All Tools" is still working and a valuable piece for everyone here! Could you please at least keep that?
Click to expand...
Click to collapse
I have also uploaded the zip to gdrive as another mirror. https://drive.google.com/file/d/0B099RU3-XRVgVW5HeEpqUXZPMGs/edit?usp=sharing
Fixed my issue. As per the MTKDroidtools log file:
Code:
23/05/14 11:40:34 --- NVRAM Bin Region is write to the file: : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmart_86xxxx
xxxx59988_nvram_140523-114031.bin
23/05/14 11:40:34 /system/bin/sh: tar: not found
23/05/14 11:40:34 --- ERROR during copying file between phone and PC : C:\omate\tools\All Tools (14-2-8)\1 MtkDroidTools v252\BackupNVRAM\TrueSmar
t_86xxxxxxxx59988_nvram_140523-114031.tar
the issue was with missing functions running _on_the_watch_ Installed busybox, and good to go. Now, this does leave a problem for anyone wishing to do a backup before making mods.My original backup extracted the system partition (as a dos copy of the filesystem, which must be incomplete for permissions etc) but when done with tar on the device I get proper img files.
I suspect it is possible to manually 'mount -remount,rw /system' then adb push busybox, as it happens I've already installed su so just installed from playstore.
lssong99 said:
1. Download "All Tools"
Click to expand...
Click to collapse
Where is the all tools?
sorry i have find it in GDrive!
xs4all said:
FYI:
Just as Lokifish Marz said, looks like omate changed hardware for the 4th EU patch of deliveries.
The latest EU batch from the 4th list has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140513.103530_V2.0
My TS was from the 3rd EU batch which has the following firmware:
Baseband: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
Kernel: 3.4.5
OUI: 2.1
Build: Omate_TrueSmart_20140328.182336_V2.0
Out of curiosity, I was already in Unified Rom, I tried to flash "Build: Omate_TrueSmart_20140513.103530_V2.0" for my TS.
I bricked my device! lucky I had made all the relevant backups, and got my TS back to factory ROM that came from the 3rd list batch.
Then Unified it again.
Click to expand...
Click to collapse
My TS was from the 2nd EU batch and it have the same firmware as yours.
There are two backup folders for TrueSmart in the location of "backups"
I just tried to backup my TrueSmart and everything went quite smoothly until I was meant to prepare blocks for Flash Tool. I could find 2 separate backups for TrueSmart with different time stamps on them. I downloaded the AllTools.zip that was hosted in this thread in Google Drive. Is that someone elses backup or what? I have to just choose the later backup, correct?
EDIT: Went with the latest because the earlier already had !FilesForFlashTool folder in it.
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
soulcrusher said:
How can I actually use SuperSU? When a root request pops up, there aren't any buttons visible except for ask again. I cannot scroll. How do you do this?
Click to expand...
Click to collapse
That happened to me as well. It turned out that if you change the font size in Settings - Display - Font size to Small it will work just fine and show the buttons. Your welcome.