Related
Sony Tablet S 3.2.1 (release2) Kernal Version: 2.6.3.6 [email protected] #1 Build number THMASOO124OOO can i root this? if so can you point me to the right direction? not tell me how to do it but where i can find a tutorial because i don't wanna mess it up you know thanks much appreciated
hey
as far as I know, only build #10 devices are not root able
if you want to root your tablet, enable USB-Debugging in your options,
after you have done that, go to this post, install the usb drivers, if you want to test if adb is working, start the batch file, which is located in the folder of the drivers, than type in the batch file, "adb devices", without" ", if it found devices, proceed to the next step
got to this post, download the AoI tool by condi, extract the tool, start the tool
type in "1" than press enter, wait till it's finished, exit.
congrats your tablet is rooted
I would recommend you, to also install the rescue-backdoor.
I hope that I could help you with my confusing tutorial
cheers
Lyxath said:
hey
as far as I know, only build #10 devices are not root able
if you want to root your tablet, enable USB-Debugging in your options,
after you have done that, go to this post, install the usb drivers, if you want to test if adb is working, start the batch file, which is located in the folder of the drivers, than type in the batch file, "adb devices", without" ", if it found devices, proceed to the next step
got to this post, download the AoI tool by condi, extract the tool, start the tool
type in "1" than press enter, wait till it's finished, exit.
congrats your tablet is rooted
I would recommend you, to also install the rescue-backdoor.
I hope that I could help you with my confusing tutorial
cheers
Click to expand...
Click to collapse
k i understand all this but that last part when you said install resuce backdoor, do you mean after i rooted? correct? awesome deal mane i appreciate your time and effort
Update: also i googled this but i dont' quite understand the concept of rooting, i know its admin previlages but does that mean i could run apps that aren't for the tablet S in market like say ORDER AND CHOAS MMO ? ? ?
biggyhead said:
k i understand all this but that last part when you said install resuce backdoor, do you mean after i rooted? correct? awesome deal mane i appreciate your time and effort
Update: also i googled this but i dont' quite understand the concept of rooting, i know its admin previlages but does that mean i could run apps that aren't for the tablet S in market like say ORDER AND CHOAS MMO ? ? ?
Click to expand...
Click to collapse
yes u can only do install rescue backdoor after the tab is rooted.
rooting in android means gaining root access. Market aka PlayShop is a place where all androids apps/games are hosted. Weather u can play on Sony Tab or other android devices are purely base on the Android version (eg: 2.3.5(GB), 3.2.1(HC), 4.0(ICS) ).
if u ever come across apps like Titanium Backup, CPU Tuner... u will need root previlages to run it because it is meddling with the Android system settings which default the tab is mainly run as a normal user. Also, with rooted android devices, u can change the wifi binary to support adhoc wifi which again, by default it is not enabled. It seems that ICS does support it thou base on the adhoc wifi functions i see.
hope this info gives u a better picture about android rooting. for apple devices u jailbreak to install free apps or freely distributed IPA files.
zerod78 said:
yes u can only do install rescue backdoor after the tab is rooted.
rooting in android means gaining root access. Market aka PlayShop is a place where all androids apps/games are hosted. Weather u can play on Sony Tab or other android devices are purely base on the Android version (eg: 2.3.5(GB), 3.2.1(HC), 4.0(ICS) ).
if u ever come across apps like Titanium Backup, CPU Tuner... u will need root previlages to run it because it is meddling with the Android system settings which default the tab is mainly run as a normal user. Also, with rooted android devices, u can change the wifi binary to support adhoc wifi which again, by default it is not enabled. It seems that ICS does support it thou base on the adhoc wifi functions i see.
hope this info gives u a better picture about android rooting. for apple devices u jailbreak to install free apps or freely distributed IPA files.
Click to expand...
Click to collapse
oh so same general idea DUDE AWESOME THANKS SO MUCH i really appreciate your time mane i have decided to take the risk after more reading on rooting thanks so much i really appreciate this i can't wait!
biggyhead said:
oh so same general idea DUDE AWESOME THANKS SO MUCH i really appreciate your time mane i have decided to take the risk after more reading on rooting thanks so much i really appreciate this i can't wait!
Click to expand...
Click to collapse
np.. we should all thank Condi and bunch for their efforts to make root possible on sony tab...
have fun!
zerod78 said:
np.. we should all thank Condi and bunch for their efforts to make root possible on sony tab...
have fun!
Click to expand...
Click to collapse
ran into a problem i did everything but it says error can't find path, says like mtp something i don't have it?
UPDATE: that one doesn't work with the other adb you gota use the one given by him http://forum.xda-developers.com/showthread.php?t=1488822 or you get an error so second part doesn't work , which in term scared the **** OUT OF ME when the program turned red but it works now with dj's style ROOTED WHOOO i think iono how to tell xD
biggyhead said:
does that mean i could run apps that aren't for the tablet S in market like say ORDER AND CHOAS MMO ? ? ?
Click to expand...
Click to collapse
Absolutely my good man!
go to this thread to change you build.prop (makes it/the market think it's a different device)
I've been known to pull out my sony tab at work on lunch, crank the wifi hot spot on my phone and smash out a few minutes of questing lol It's truly the best
biggyhead said:
Sony Tablet S 3.2.1 (release2) Kernal Version: 2.6.3.6 [email protected] #1 Build number THMASOO124OOO can i root this? if so can you point me to the right direction? not tell me how to do it but where i can find a tutorial because i don't wanna mess it up you know thanks much appreciated
Click to expand...
Click to collapse
I rooted my Sony s and the only # that change from urs r the THMAS#
DreadPirateDan said:
Absolutely my good man!
go to this thread to change you build.prop (makes it/the market think it's a different device)
I've been known to pull out my sony tab at work on lunch, crank the wifi hot spot on my phone and smash out a few minutes of questing lol It's truly the best
Click to expand...
Click to collapse
im so glad i read this sick wit it!!!
Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly
Hi all,
I am working in a school and we have ordered some tables for students to use. The problem I am faced with is that the systems needs to be very secure (the students can't change settings, install/uninstall apps) and i need to be able to apply the restrictions and software to many tablets with relative ease or to apply it to them simultaneously.
Sumvision provides software to flash an image to the tablet and will flash multiple tablets at once (8 if i remember correctly). It would be very handy if I could easily create my own image with a few apps and things configured so it can flash the tablet ready to use, however i have never created a ROM before and am inexperienced in programming.
Another option is to set up one tablet and use CWM to backup/restore to all the other devices, however I am unable to find any way of doing this, or any actual recovery.img files to download for this model. Does anyone know of any?
Any help would be appreciated, as at the moment my plan is to upgrade the tablets 8(?) at a time to 4.2.2 and use titanium backup to restore apps and settings to each tablet.
The tablets are Sumvision Cyclone Voyager 10.1" BT tablets.
Thanks in advanced,
tylergard702
CWM recovery for Sumvision Cyclone Voyager BT
tylergard702 said:
Hi all,
Another option is to set up one tablet and use CWM to backup/restore to all the other devices, however I am unable to find any way of doing this, or any actual recovery.img files to download for this model. Does anyone know of any?
tylergard702
Click to expand...
Click to collapse
Disclaimer: The following worked for me. Any one else is trying it at there own risk.
Here are roughly edited notes on how I got ClockworkMod recovery onto Sumvison Cyclone Voyager BT (Bluetooth edition)
Hope it's helpful, it comes from bits and pieces of other folks work found on the net, to all of whom I'm grateful.
After you go through this process on all tablets you could make a NAND backup, of a tablet suitably set-up for your own requirements, to micro-SD card and flash it to all remaining tablets
Getting into Recovery Mode
From a terminal program in fully booted system
#su#reboot recovery
or from Power Off
From Power OFF (NO Cables Connected)
Hold Vol+ while plugging in Power, release Vol+ when splash screen appears
How I installed CWM-based Recovery for Rockchip Sumvison Cyclone Voyager BT
Recovery image used was:
RECOVERY Image for v10_BT_recovery_fun_13-02-13.rar (Google it)
(Generic rockchip recovery image from CWM.zip did not work, but I used the flash_image utility from that archive. Again search Google for CWM recovery images for rockchip 3066)
In XP with tablet fully booted and power and USB cable plugged in (don’t know if power in required, as far as I remember adb driver is fine without power, but no harm to have it plugged in. When flashing firmware from SCV's rockchip software utilities power must be plugged in. Also if you have the choice, prefer USB2 over USB3, although unlikely to make a difference. (Note: since got adb working on Ubuntu Linux also, but that's another story )
1. Extracted flash_image from CWM.zip
2. Extracted recovery.img from v10_BT_recovery_fun_13-02-13.rar
3. Copied both files to /dev on tablet
adb push flash_image /dev/ adb push recovery.img /dev/4. Started shell
adb shell5.Set flash_image utility executable
chmod 755 /dev/flash_image6. Flashed the recovery.img
/dev/flash_image recovery /dev/recovery.img
Hope that helps
Thanks
Ah, thank you
This has quite possibly saved me hours of time reformatting the tablets. I take it that this can be installed relentless of the ROM that is on the tablet? I will try this as soon as the tablets arrive
Thanks again,
tylergard702
PS:
I don't suppose that sumvision's flash utility will flash the recovery.img to the tablet successfully? I currently don't have a linux workstation at work, and adb confuses me :S
Recovery Img?
Thankyou for all of you help John,
Ignore my previous post, i dived in with adb and got quite well acquainted with it
The only problem i have now is that the rar file for the recovery .img you told me to Google for yields no results. Is there another place i can download it? i can't find any :S.
Or if you have a copy of it would you be able to email it to me? (I can PM you my email)
Thanks in advanced,
tylergard702
Flashing recovery image with RK tools
tylergard702 said:
Ah, thank you
I don't suppose that sumvision's flash utility will flash the recovery.img to the tablet successfully? I currently don't have a linux workstation at work, and adb confuses me :S
Click to expand...
Click to collapse
Disclaimer: things can go wrong. You are responsible for whatever you do to your tablet!
I think that the rockchip tools should flash the recovery image for you, I haven't used the Sumvision utility in a while so don't know. The rockchip tools will provide you with a Windows user interface. Make sure you only flash recovery, and leave the rest unmarked. Put the recovery image in the same directory where the tool executable resides (or it may need to be in a sub-folder named ROM). I think the app will tell what path it is looking at for images.
Download from the Sumvision support page (I'm not allowed to post links yet, but find your tablet on Sumvision and go to support page)
Look for: Download Link for RKAndroid tool "cleanup tool" REQUIRED on that page.
Good luck!
---------- Post added at 11:40 AM ---------- Previous post was at 11:29 AM ----------
tylergard702 said:
Or if you have a copy of it would you be able to email it to me? (I can PM you my email)
tylergard702
Click to expand...
Click to collapse
Okay, PM your email and I'll send you a dropbox link to the recovery image previously mentioned.
(I discovered that the CWM recovery for generic rk3066 that didn't work for me, was an incomplete download and likely the reason it didn't work for me. I haven't retried it because the v10_BT_recovery_fun_13-02-13 recovery image works fine, so just left that alone).
Worked a treat
Thank you very much John,
The fun_ package worked perfectly.
The generic package lead to a broken recovery, it wasn't just your download, however the specific package soon fixed that.
Can't tell you how much easier you have made my work, i can now prepare about 4 tablets in 30 minutes for the students to use, which will come in very handy when they get their hands on them and start to find ways around our security measures.
Thanks for everything,
tylergard702
John Hoyne said:
Disclaimer: things can go wrong. You are responsible for whatever you do to your tablet!
I think that the rockchip tools should flash the recovery image for you, I haven't used the Sumvision utility in a while so don't know. The rockchip tools will provide you with a Windows user interface. Make sure you only flash recovery, and leave the rest unmarked. Put the recovery image in the same directory where the tool executable resides (or it may need to be in a sub-folder named ROM). I think the app will tell what path it is looking at for images.
Download from the Sumvision support page (I'm not allowed to post links yet, but find your tablet on Sumvision and go to support page)
Look for: Download Link for RKAndroid tool "cleanup tool" REQUIRED on that page.
Good luck!
---------- Post added at 11:40 AM ---------- Previous post was at 11:29 AM ----------
cheers.
Okay, PM your email and I'll send you a dropbox link to the recovery image previously mentioned.
(I discovered that the CWM recovery for generic rk3066 that didn't work for me, was an incomplete download and likely the reason it didn't work for me. I haven't retried it because the v10_BT_recovery_fun_13-02-13 recovery image works fine, so just left that alone).
Click to expand...
Click to collapse
Any chance i can have a copy of that file to flash recovery to my 10.1 BT?
Sumvision Cyclone Voyager 10.1 BT Recovery Image
jtheg said:
Any chance i can have a copy of that file to flash recovery to my 10.1 BT?
Click to expand...
Click to collapse
Hey jtheg,
Of course I can If you PM me your email I will send you a zip containing the flash_image file, the recovery10.img file (I renamed it for batch purpose, but it works all the same). The zip also contains adb and a batch script I wrote that should do it for you. If you don't want to use the script, you can refer to the instructions above or ask for help
Just make sure all the drivers for your tablet are installed before you start.
I used a program called "moborobo" It detects the device and installs all the drivers for you. It installs junk on your device but you can uninstall it right after
I would also like to point out that although this has worked for me with 16 of these tablets, It may not work for you due to subtle differences between the tablets or human error, and I cannot accept liability for your device. I can, however, say it has worked treat for me and wish you the best of luck experimenting with your device As soon as I get to work in about 20~30 minutes I'll check back and email you if I can
all cwm for cylone voyager can be found on the flashmyandroid forum
Hello,
THBK1-10 is a cheap dual system (Android 4.2.2 /Windows 8.1) tablet based on Bay Trail (Intel Atom Z3740D). More details http://www.thomsoncomputing.eu/dualboot.html
I'm trying to hack it, and especially get root and use non-signed zip in recovery. Basically i'm stuck at theses points, and i'm requesting directions to continue the work.
I have posted in W8 section, but obviously, this is no longer the place
General
------------
* i can use a work-around to write system (/system, /data) partitions
* i can flash signed updates via recovery
* google apps are working flawesly. Only thing is to keep original files (stock keyboard and layout)
-> i would like to flash non-signed zip via recovery, but i guess i have to build a custom recovery, or can i exploit something else ?
Root:
-------
* no auto root is working (z4root, towelRoot). Regarding towelRoot, i tryed each 8 common parameters, and i don't really know how to do others. I have also heard this is only working in 4.4.2+
* pushing su is not working. When i'm launching it, let's say from terminal, i have a code 255 return (-1). Tested with both arm and x86 version (i'm still wondering why arm su is also returning -1, i would have expect a non valid binary. Or perhaps my x86 version is bad ?
-> i'm still trying to dig this issue, and idea on how i could do ? i believe running SU was enough... but it seems not. Any idea ?
Many thanks !
Bump. the way it is booting is based on ramdisk images (one for normal android boot, one for android recovery).
I have acces to theses img, and i can, with hexedit (perhaps mounting them directly at a filesystem), view the whole init sequence.
My question is : what triggers the root invalidation ? AFAIK, everything is done as root (mounting FS, updating permissions, etc....). Basically i can't really figure how it is handled.
Thank you !
Solved !
Graveen said:
Solved !
Click to expand...
Click to collapse
Woaw ! I'm very happy to see that somebody tried and succeed to root the THBK1 ! Please can you share your method in a tutorial when you'll have time ? :laugh:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Yes ! I confirm ! Graveen has installed GAPPS on Thomoson THBK1 / Danew Dualboot tablet with sucess ! I'm not familiarised with linux environnement and realize it, but it requires some knowledges of linux command (coLinux especially)
Graveen is the only one users identified that it can put GAPPS on android environnement concerning this tablet.
Big thanks to him !
Graveen said:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Click to expand...
Click to collapse
7600
I own a Cube U100GT and it's one of the many Chinese brothers of your THBK1-10. But mine came only with W 8.1.
I just start looking for a dual boot solution and I'm happy to know that it's is possible.
I don't need root for while, just play some games and apps.
So the original Android "ROM" of the tablet can do the job.
My version have 64Gb SSD and I've already resize the Win partition to make room for a new system.
Where can I look for a dual boot tuto and find this Android version?
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: http://www.danew.com/support-pilotes-manuels.php?type=218&produit=219 but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Graveen said:
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Click to expand...
Click to collapse
The partition list is the standard for a windows installation (but no windows image on the end):
1: 300 Mb (Windows RE)
2: 100 Mb (System)
3: The rest (Windows). My SSD is 64Gb.
My tablet already comes with a dedicated keyboard cover, so I have full access to to UEFI Bios.
There's a lot of numbers:
Aptio Setup Utility Version 2.16.1242
Vendor - AMI
Core Version - 5.008
Project Version - 3BAGR 0.03
EC FW Version - 201401101A
Intel GOP driver - 7.0.1029
Sec RC Version - 00.05.00.00
TXE FW Version - 01.00.02.1060
I found the drivers pack for windows 8 and so I could install my PT-BR edition of W81. And reserve 20Gb at the end for another OS.
It's my first UEFI machine and I'm completely lost. There's a lot of options and I can't understand a quarter of that.
On the Tabletrepublic forum someone said that my bios recuse everything except a Windows pendrive. If is true, there's no way to put Android but changing/patching the UEFI.
Android x86 is for desktops right? And the Intel site, can I find Android images there?
Thank you. What i'll do is to check if my bios is identical to yours, because there are effectively numerous options. Then, i could finsh to dump my android partitions and let you play with them.
Honestly, the trick is the OS selection system, which is bring by the EFI bootloader (and certainly a dedicated partition). Once selection is done, another EFI bootloader (windows only) is called.
let's continue here: http://forum.xda-developers.com/showthread.php?t=2799404
Q&A for Intel Android Devices Root / Temp CWM Session
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Intel Android Devices Root / Temp CWM Session. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will this root method work with ASUS devices?
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
usenametaken said:
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
Click to expand...
Click to collapse
It should work I've tested it on Medfield, Clovertrail, and Baytrail devices, from the Asus fastboot.imgs I've looked at trigger 2 and 3 should work.
the apk you refer to i believe actually uses a function Asus only seems to of built into thier droidboot binary on the Asus when you start droidboot it looks at /factory for a file called .addon and then triggers it Asus uses it for automating things under droidboot I believe and several recoverys have been built to take advantage of it.
As for the exploit the exploit is the the script the binarys are nothing really special just responsible for setting up and starting the recovery session. recovery.trigger is a simple daemon to launch recovery.launcher and recovery.launcher is basically a small subset of cwm recovery its self.
Sent from my XT907 using XDA Free mobile app
Hi,
this worked on an odys intellitab 7, now i got finnaly root . BIG THX!
Btw I trird trigger 2 and 3 and both worked for me
How can i see if the bootloader is locked on my device?
Another possible device
Hello,
in Czech forum where I compiled a native-language short guide how to use your tethered CWM recovery to root Op3n Dott (I see that somebody confirmed that both T2 and T3 triggers work] one Slovak user reported that he was able to use the tool to root Prestigio MultiPad Thunder 7.0i http://www.prestigio.sk/catalogue/M...NDER_7.0i#/product-specs?article=PMT3377_WI_C. I sent him a question concerning which trigger did he use so if he replies I will send more info. Sorry for the Q&A thread, but I got kicked here because of the low post count.
Succesfully rooted Tesla L7 Tablet
Using the method described successfully rooted Tesla L7 tablet. The method used is T3 and supersu used is UPDATE-SuperSU-v2.40
Is the recovery built from source?
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
pm-cz said:
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
Click to expand...
Click to collapse
The actual recovery is built by @vampirefo but i am very interested in adding that feature in and was actually going to ask you about that.
Also have you looked at any of the older update_osip source?
Can you please tell me an easier to understand method.
Because even though i understand what you're talking about, i don't know where to put the files. I understand flashing the session and all but coukd you pleeease explain how to root. Because this the first time i'm rooting a device
Thanks
rooting without voiding warranty
Can you please tell me how to root my dwll venue 8 3830 without voiding the warranty?
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/android/software-hacking/mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Getting Windows 7/8 to Recognize Dell Venue 3740
Fajfie said:
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Click to expand...
Click to collapse
Thanks to Social Design Concepts for the great work. It is appreciated!
Fajfie, thanks for posting. That's awesome. If you used Windows, how did you get Device Manager to identify the Dell Venue 3740? I've downloaded all recommended driver files in this and the previous thread and I can't get Windows to identify the device. When I run launcher.bat I get DEVICE: UNKNOWN.
Any ideas?
Another rooted
Great work, this worked to gain root on Medion (Lenovo) Lifetab S10346 tablet.
Intel Z3735F cpu
2GB ram, 32 GB storage.
I used trigger T3 and it went through smoothly, a Great bit of work.
Works perfectly on the Asus Padfone X Mini. I referenced this thread over in the device specific forum. I used the T3 command in step 3.
Thanks!!!
Worked on my ASUS Padfone X mini (TOOS) used T3 option.
Thanks!
Thanks you. The procedure works with method 3 to GoClever Insignia 700 PRO , Android 4.4.2.
I just installed IntelAndroidDrvSetup 1.5.0 with the drivers for my pc.
hi im having the same problem as GeeKerGurL
" Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help! "
i have a Acer Iconia A1830
Problems with the update surpeuser zip
I followed your guide to rooting Acer iconia tab 8 A1-840FHD with intel chip, (Wich is great by the way thanks) and evrything goes to plan until, i get to Install Zip. I get, E:Can't mount /sdcard/ Update-superSu-v2.40(1).zip Installation aborted. I've downloaded the zip from your link by desk top (windows 7) and transferred it over. Also downloaded from the tablet and just used a file manager to move it over to sd. Same msg for each. I used the T3 option. any ideas how to get the zip to install?
Zip copy to folder on your tablet (download,...) and install from recovery install. zip.
Send from my Samsung Galaxy S2 - RR Lollipop v. 5.2.7
Verified with Acer Iconia A1-830
Firstly, big thanks to the dev, social-design-concepts for making this thing work on Intel device. Thumb up~
It works wonders with my Acer Iconia A1-830 android 4.4.2.
I used option T1 and it works without any problem.
Thanks again.
P/s: Hope this will work on the latest Intel devices like Asus Zenfone 2 ;p