ATM7013,gs701b,gl5201 -- with gsl1680 touch processor.(i open it),polaroid rainbow 7" multitouch, midc407 pr005,
After i flash-it with 'action tablet tool product' (icecream_gs701b_q8_rgb.fw,acta.img,actab.img) ,touch doesn't work anymore.
i can root it.i can use MOUSE with OTG adaptor
i try to install another touch driver : insmod---gsl1680.ko and i get (exec format error),isnmod---glsX680-tp.ko is ok,but my touch don't work.
gslX680-tp.ko is in my /system/lib/modules already and i have also /system/usr/idc/gslX680-touch.idc(i try to modify gslX680-touch.idc to gslX680-tp.idc and nothing happen.
in lsmod i get gslX680_touch 0 - Live
getevent
add device 1: /dev/input/event0
name: "gslx680"
i try to flash anothers firmware but is the only one who work,i try 30 firmware,mips.
if i try to flash UPGRADE_FAST.fw , i get black scree and nothing work,even ADFU is not work anymore,i need to press pin 7 and pin 8 from NAND flash,to come in ADFU mode.
so...with linux driver i can extract misc.img and system.img and the flash with Action Tablet Tool Product.
Also i can modify easy misc.img in WinImage for windows.but i can't modify system.img,only i can explore it with ext2explorer.
AND i try maaaany firmwares from TF card.i format it FAT32 and copy inside firmware like...update.zip (don't work),UPGRADE_FAST.fw(don't work)
If someone have the same tablet,and if he want to give me the firmware.
or if someone want to help me
Thanks
EDIT:if is multi-touch i need to install more touch drivers ?like----
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ????
to have in lsmod ---- ft5x_ts 7 - LIVE goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ??
and touch drivers for JB 4.2.2 work also for ICS 4.0.3 ?
polaroid midc704
blad3_sv said:
ATM7013,gs701b,gl5201 -- with gsl1680 touch processor.(i open it),polaroid rainbow 7" multitouch, midc407 pr005,
After i flash-it with 'action tablet tool product' (icecream_gs701b_q8_rgb.fw,acta.img,actab.img) ,touch doesn't work anymore.
i can root it.i can use MOUSE with OTG adaptor
i try to install another touch driver : insmod---gsl1680.ko and i get (exec format error),isnmod---glsX680-tp.ko is ok,but my touch don't work.
gslX680-tp.ko is in my /system/lib/modules already and i have also /system/usr/idc/gslX680-touch.idc(i try to modify gslX680-touch.idc to gslX680-tp.idc and nothing happen.
in lsmod i get gslX680_touch 0 - Live
getevent
add device 1: /dev/input/event0
name: "gslx680"
i try to flash anothers firmware but is the only one who work,i try 30 firmware,mips.
if i try to flash UPGRADE_FAST.fw , i get black scree and nothing work,even ADFU is not work anymore,i need to press pin 7 and pin 8 from NAND flash,to come in ADFU mode.
so...with linux driver i can extract misc.img and system.img and the flash with Action Tablet Tool Product.
Also i can modify easy misc.img in WinImage for windows.but i can't modify system.img,only i can explore it with ext2explorer.
AND i try maaaany firmwares from TF card.i format it FAT32 and copy inside firmware like...update.zip (don't work),UPGRADE_FAST.fw(don't work)
If someone have the same tablet,and if he want to give me the firmware.
or if someone want to help me
Thanks
EDIT:if is multi-touch i need to install more touch drivers ?like----
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ????
to have in lsmod ---- ft5x_ts 7 - LIVE goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ??
and touch drivers for JB 4.2.2 work also for ICS 4.0.3 ?
Click to expand...
Click to collapse
nobody? realy? not any advice ?
Related
I'm sorry it took so long, I got lots of stuff to deal with. Good things are worth waiting for (i heard)
First off: You are responsible for any of your actions! Changes that are needed to boot Ubuntu on your folio will void your warranty!
Special Thanks goes to DerArtem for posting his Kernels, Weeds2000 for eMail support, topogigi for wifi hacking and last but not least the Ubuntu-Touch Team on IRC that made it possible for me to tweak the touchscreen driver.
However, the system you are about to create is not fully functional, there are still things missing (a working sound driver for example). Its nice to play with it anyway
Heres a quick walk-through:
We will flash a kernel to the toshiba folio tablet which makes it possible to boot from an sdcard or USB-stick (You have to choose one, we need at least 2GB, I'd recommend 4GB so you can install fancy stuff like OpenOffice etc.).
We will then create a root filesystem with rootstock, which will hold our Ubuntu system (similar to your hard drive-Ubuntu).
Finally, we have to tweak that filesystem and change passwords, copy wifi driver etc.
Then we're able to boot a beautiful Ubuntu.
Things you will need:
- A Computer running Linux (Debian / Ubuntu would be great. If you're not running Linux on your computer, running it on the folio would make absolutely no sense. Please don't ask, I don't know how to install it in Windows.)
- The files i added to this post
- A SD-Card, 2-4 GB should be fine.
- optional: A second SD-card, 128MB would be enough (for flashing)
- A USB hub (If you want to boot from USB AND use a keyboard.
- Some time... =)
The first thing you should do is flash one of the update.zip files; choose update-sdmmc.zip (this will boot your folio from sdcard) or update-usb.zip (this will boot from a usb pen drive), open it and unpack the content to a sdcard (This has to be a SDcard, we're gonna flash our device from there.)
Backup all your data on your folio (I'm serious! It'll be gone!) and turn it off.
Put the SDcard in its slot and turn the folio back on. Press + hold both power and volume up.
Follow instructions to do a system update (If you've never done this before you shouldn't start now =) )
When it reboots, your folio will show some funny black and white linux text stuff and hang somewhere. Congratulations! You just bricked your tablet. Now lets see how we can fix it... Turn it off (Keep power pressed for about 5 seconds) and take out the sdcard, put it in your PC.
It's getting messy now, so grab a beer and let's go:
Open a Terminal on your linux computer.
Code:
#echo "Hello world!"
If your console says "Hello World" you got it. Awesome! =)
Code:
#sudo apt-get install rootstock gparted
This will install rootstock, the tool we're gonna need to create our filesystem, as well as gparted, a tool for partitioning our flash drive. You can also install rootstock-gtk, the graphical version. Try it if you like:
Code:
#sudo apt-get install rootstock-gtk
I heard that ubuntu-netbook won't work because there are drivers missing, would somebody try that and report please?
If your beer is already empty when this is done, you need a faster computer. Tell your wife the guys at xda-developers told you so
Back to the terminal:
Code:
#sudo rootstock -f MyCoolHostName -l myCoolUserName -p myCoolPassword --seed xubuntu-desktop -i 2G --notarball
This will create our filesystem with a user called "myCoolUserName" and (theoretically) his password "myCoolPassword" and install a basic xubuntu-desktop. I had to change the password manually because it didn't work this way... We'll do that later.
Rootstock will download lots of packages (You could also set it up with "--seed ubuntu-desktop", then youll download even more packages or "--seed ubuntu-minimal" or kubuntu... I still didnt find a list of seeds online :-/
The creating will take quite some time, get another beer.
When this is done, you'll get a file like this : "qemu-armel-201104112120.img". We will now mount this image: (make sure the directory /mnt/ does exist and is empty:
Code:
#ls -la /mnt )
Code:
#sudo su
(its simpler to be root for now)
Code:
#mount -o loop qemu-armel-201104112120.img /mnt/
(You are aware that your filename is different, are you? Try this:
Code:
# mount -o loop qemu-armel-*TAB*
and your terminal will automatically fill in your filename. Awesome linux, huh? =)
)
Code:
#cd /mnt/etc/
#mv fstab fstab.bak
#echo "proc /proc proc defaults 0 0" > fstab
#echo "dev /dev tmpfs rw 0 0" >> fstab
Note that the first time we create a file called fstab (echo asdf > fstab), then we add one line to this file (echo asdfasdf >> fstab)
Now we need to copy our wifi-driver over. Remember I told you to write down the directory you put them in? =)
Code:
#cp /home/YourUserName/Desktop/FolioStuff/firmware /mnt/lib/firmware
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK.
Code:
#cd /
#chroot /mnt/
#passwd myCoolUserName
#passwd
#exit
That's it, we're out of the chroot.
It's now time to prepare the SDcard (The steps are the same for a USB Flash drive, I think you'll figure them out.)
Find out how your SDcard can be accessed (You should still be root):
Code:
# fdisk -l
In my card reader, it's "/dev/mmcblk0", it could also be "/dev/sdb1" in your computer.
Now there are two possibilities:
1. You know what youre doing. Then it's easy: You wipe the only partition (or, if there are more than one, the first partition) on your sdcard and format it with ext3:
Code:
#mkfs.ext3 /dev/mmcblk0p1
Note: The device is called /dev/mmcblk0, the partition itself /dev/mmcblk0p1 (Partition 1)
2. You are not sure about this. No problem, start gparted: (as root!)
Code:
#gparted
In the upper right corner, select your flash drive, delete all partitions and create one formatted with ext3. Close gparted.
Mount your freshly created partition somewhere (i chose /mnt2/):
Code:
#mkdir /mnt2/
Code:
#mount /dev/mmcblk0p1 /mnt2
We can now copy our filesystem over. Make sure you use exactly the same flags (rfp for recursive, force, preserve (attributes))
Code:
#cp -rfp /mnt/* /mnt2/
OK, that could work. Unmount the sdcard:
Code:
#umount /mnt2/
Put it in your folio and cross your fingers.
Wifi drivers will be up soon...
It's recommend to add build-essentials to your rootstock image too..
Because then you can easily build the wireless lan drivers on your devices..
Maybe I'll post a howto this afternoon!
Is this Ubuntu really usable (for daily work) with the folio 100 (touch, response speed, ecc.)?
Thanks.
Yup, it's usable for everyday work. It's quite fast on the Folio 100, I've been pretty impressed when I tested it a few weeks ago.
Thanks ph84
It seems most difficult than expected but, great job !
Only i have 1 question, bricking the tablet sounds dangerous... is possible break out the tablet and get a rock?
Thanksss!!!!!
if ubuntu is installed on sd, does that mean that we can dual boot foliomod from nand and ubuntu from sd/usb?
Hm... I'm using Ubuntu 11.04 and I'm getting this error at the end of the rootfs creation :
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
umount2: Dispositivo o risorsa occupata
umount: /tmp/tmp.zaZ1j1Tgt6/tmpmount/proc: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Dispositivo o risorsa occupata
Click to expand...
Click to collapse
Do you have any idea where I can find the log?
And this procedure will build in the tablet a dual boot? Or dualboot is another procedure?
what is the *.rar????
No it's for singleboot only...
You can only start Ubuntu installed on SD-Card/USB-Stick with this procedure...
I don't know wether the boot-partition is locked when you are booting ubuntu/android..
If not it should be possible to build some applications to flash the boot-partition on the running system to change from ubuntu to android
When I do the rootstock step,I got this error!!!Please help!!!
I: Base system installed successfully.
I: First stage install done
I: Using Chroot for installer
Adding 'local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
Generating locales...
en_GB.UTF-8... done
Generation complete.
Generating locales...
en_US.UTF-8... done
Generation complete.
/bin/installer: line 53: syntax error near unexpected token `+'
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
I: A logfile was saved as //rootstock-201104140706.log
I: Done
Click to expand...
Click to collapse
Could you upload an *.img for us in this forum?
or a databank,etc?
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
sony_tornado said:
what is the *.rar????
Click to expand...
Click to collapse
Nvm, I was talking crap...
schnudergof said:
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
Click to expand...
Click to collapse
Just try rootstock without the parameters on --seed..
Maybe it will work..
You wont have a Desktop Enviroment like Gnome or something but you wont need that for installing the wireless drivers...
And after installing wireless drivers you can install ubuntu-desktop or something with apt-get!
Ok, I have been looking at rootstock, and if you install rootstock-gtk and than click on tasksel there is a whole list of seeds to chose from. I Think im going to try build the netbook build.
On a side note:
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK
Click to expand...
Click to collapse
with chroot your only changing the root of your file system, your not running anything from there.
But its its in no way a complaint to your awesome guide! Thanks and keep up the good work!
shidima_101 said:
with chroot your only changing the root of your file system, your not running anything from there.
Click to expand...
Click to collapse
Thats right but when you change your root shell to the rootstock-fs you can also use sudo apt-get update/install and install it into the rootfs!
ph84 said:
Meanwhile, open another terminal. (This is linux! We're gonna multitask since our computer is capable of handling that!) Go to where you stored the attached files, for example
Code:
#cd /home/YourUserName/Desktop/FolioStuff
and unpack them:
Code:
#rar x *.rar
Click to expand...
Click to collapse
Where/what is the "attached files"?
Thanks
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
°EraZoR° said:
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
Click to expand...
Click to collapse
The files I found are only *.zip for update bootloader. Where is *.rar file?
Thanks
is there a possibility, both the stock Archos firmware to root and also with a boot menu such as OpenAOS to use.
Need to control both the floor on my A70H firmware with root right and as a second OS Debian Linux to the possibility of the software with a panoramic head Papywizard.
The Debian Linux I've done and it works flawlessly under OpenAOS, but unfortunately I have no right under Android Root.
Have also been tested UrukDroid, unfortunately, it works with the boot of an Alternative OS will not therefore have already contacted the developer of UrukDroid, unfortunately without positive result.
Sorry for my bad English.
Best regards
kwalter
Multiboot for OpenAOS works the same as Chulris Root but not for the last FW.
So if you want Root and Linux you have to downgrade the Archos to 2.3.81.
Ich you then boot through the Multiboot menu and select Android, you have root.
fzelle said:
Ich you then boot through the Multiboot menu and select Android, you have root.
Click to expand...
Click to collapse
Doesn't this also work with the latest firmware, because openaos multiboot uses unionfs to create an overlay over the archos firmware to give you read write access, su and superuser.apk.
I didn't upgrade, because of lack of time, it is still on my todo list.
Maurice
Do you think that your Kernel and InitRam is 100% compatible with the new FW?
P.S.: Any news on cm7?
Well there are only minor changes in the kernel from the latest firmware, so I guess it would be no problem to boot the new firmware with the openaos kernel.
However like I said I didn't try it myself yet, so that is why I asked if there are problems.
PS CM7:
For CM7 we have made good progress. However we have to wait until bubu has some time to finish the new unified multiboot menu for gen7 and gen8. In the mean time we are still improving CM7.
To get an impression on the progress just look at closed tickets and the commits on our git.
Maurice
openAOS A70H
hi,
can anyone help me?
i've created a ext4 partition on my A70H 250GB Harddisk with 50GB space.
On this partition i've put the Imagefiles for debian etc., what is the correct entry in menu.lst
to boot debian or other os from openAOS Bootmenu.
On Android over openAOS, fdisk say it is sda2.
When i put the following entry on Menu.lst it will not boot Debian etc. only Android boots correct:
Archos|ARCHOS|ARCHOS|/init|0
Debian|/dev/sda2|/rootfs.debian|/sbin/init|1
Angstrom|/dev/sda2|/rootfs.angstrom|/sbin/init|1
Gingerbread|/dev/sda2|/gingerbread.img|/init|0
or
Archos|ARCHOS|ARCHOS|/init|0
Debian|/dev/block/sda2|/rootfs.debian|/sbin/init|1
Angstrom|/dev/block/sda2|/rootfs.angstrom|/sbin/init|1
Gingerbread|/dev/block/sda2|/gingerbread.img|/init|0
What is the correct path to the second partition on openAOS Boottime??????
Sorry for my bad english.
Best regards
kwalter
It depends how your partition shows up in initramfs. To find out you could try serial debugging.
You can enable serial debugging in the boot menu by going to advanced menu and select Debugging then choose serial.
When your device is connected to your pc you can use minicom to get a shell on initramfs.
This is all explained http://dev.openaos.org/wiki/SettingUpMultiRootGen8#Debugging
In the initramfs shell you can see how your partition shows up by using "df" or looking at /dev etc.
However the way you want it doesn't work, you have to create a partition for each image file and unpack that image file on that partition. Partition booting is meant to get rid of image files.
Maurice
openAOS A70H
Hi,
sorry, but I do not understand.
If the image files I in the storage directory and the menu.lst like this I can change the whole boot without problems:
Archos | Archos | Archos | / init | 0
Debian | | / rootfs.img | / sbin / init | 1
Angstrom | | / angstrom.img | / sbin / init | 1
Gingerbread | | / gingerbread.img | / init | 0
Whether floor Archos firmware, Gingerbread, Angstrom or Debian, everything works 100%.
Unfortunately, I have 4GB but only for my Debian image since FAT file system.
Best Reagards
kwalter
You could change internal storage to ext3 to overcome the filesize problem.
However when you want to boot your image file from a different partition then you don't copy the image file to that partition, but you copy the contents of the image file to that partition. That is why you need a different partition for each image file.
In the multiboot menu we only loop mount image files from internal storage and not from other partitions. From other partitions they will be directly "booted" and not loop mounted first.
So what you can do is on your pc create a folder say /temp/mount/debian
Then you do the following:
Code:
$ sudo mount -o loop (path_to_where_your_archos_is_mounted)/rootfs.img /temp/mount/debian
This will mount your image file on the folder /temp/mount/debian
Then copy everything to your created partition on your archos using -rp option for recursive and preserve rights on the files.
Code:
$ sudo cp -rp /temp/mount/debian/* /(partition_on_your_archos)
After that adjust the menu.lst like you did before.
Maurice
Multiboot and root for A70H - Bluetooth
Hello at all,
so now I've finally managed to boot the Debian from a separate partition with openAOS.
But now comes the next problem, Bluetooth works
not more.
In the image it has worked reasonably clean, but once I
openAOS've installed boot menu does not work anymore.
Both the image and also on the partition, when I try to connect a Bluetooth device, gets out Blutooth.
(Only the devices, thats need a PIN for connection, all other devices are OK.)
Is there a solution?
Hope that someone can help me.
Best regards
kwalter
Hello, xda-developers community! This is my first post here, and and I come to ask for help.
Yesterday, I ****ed out my tablet, I did it trying to install ClockworkMod Recovery from this thread: Clic here. Ok, I entered to my tablet's stock recovery, installed update from zip, selected cwm6028-a13-10part-v2.zip, rebooted my tablet, and here comes the problem. CWM stuck in a bootloop, I can't boot to Android, just CWM, and CWM can't mount /cache, /system, /data, etc... just the /sdcard. I have tried reinstalling the ROM with Livesuit, and Livesuit throws me a error: Upgrade fails : 0x162[random chars here], no matter what rom try putting on, always throws me that error. Ok, next solution: Change the recovery.img via fastbook, ha! my tablet can't enter to fastboot mode. Wipe data/cache: I can't, because /cache is not mounted. Factory reset: same. After hours of research, I figured my tablet partitions were screwed, why? Here is the answer:
Code:
~ # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 nandf ram0
loop1 loop3 loop5 loop7 mmcblk0p1 platform ram1
/dev/block #
There must have more partitions, like nanda, nandb, nandc, nandd, nande, nandf, nandg, nandh, nandi and nandj. I tried every solution, but all fails. Here's some info from the tablet connected to adb (in Recovery mode):
Code:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
~ #
Code:
~ # mount /system
mount /system
mount: mounting /dev/block/nandd on /system failed: No such file or directory
~ #
Code:
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 181028 52 180976 0% /dev
tmpfs 181028 4 181024 0% /tmp
~ #
Code:
~ # cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 59.63
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : sun5i
Revision : a13b
Serial : [Hidden serial, i don't know if may have a problem with that, but hidden anyway.]
~ #
Video:
Link: http://www.youtube.com/watch?v=BjguNxLh-rQ
Btw, my bro has another tablet like this, but fully functional, no CWM, only rooted.
PDT: When installing the CWM, the tablet was still with the stock ROM.
PDT2: I can only access the terminal via ADB.
PDT3: Sorry for my bad English, my native lang is Spanish.
Thanks for all the help.
Bump :/
carl0sra1n said:
Bump :/
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump
carl0sra1n said:
Bump
Click to expand...
Click to collapse
Bump.
exact same problem for me too. Please help. Here is my thread,
http://forum.xda-developers.com/showthread.php?p=45728817#post45728817
me too!
Sounds exactly like what I did!
Except that I have nandf, but as a file not a partition.
I have tried to recreate the partitions with fdisk, but it fails to write the partition table at the end. next reboot i get the same thing. Surely it must be possible to repartition the device, but this is taking me beyond the limits of my linux knowledge.
So annoying because I have each of the partitions backed up on my PC as an image file.
Have the exact same problem.
Anyone found a solution ?
ShironLive said:
Have the exact same problem.
Anyone found a solution ?
Click to expand...
Click to collapse
Bump
here's how i got out that mess.......
ShironLive said:
Bump
Click to expand...
Click to collapse
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Livesuit cant detect
atmolight said:
first of all i've been searching for the solution for 2 weeks now,
-get livesuit v1.11 and faaastjb v2 or v2.5 and flash ur android device :
-after ur done please tell me the progress so we can proceed with geting to fassboot mode
and flashing custom recovery,img via fastboot mode
Click to expand...
Click to collapse
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
same problem have you found solution??
nvenezuela said:
Live suit cant detect my a13....says that NO DEVICE NEEDS UPGRADE
The only way that i can think of to solve this problem is to have someone with an ALLWINNER A13 Tablet which is in stock rom and nothing has been changed could make a back up of his or her tab and upload it here for us to recover in our restore option in the cwm recovery boot loop....
Click to expand...
Click to collapse
same problem have you fix it ?
same problem too
Anyone have a stock rom ?
thanks
@ everyone i am discontinuing myKIT_BATCH and replacing it with a standalone batch script / shell script for rooting & the tethered recovery launcher ; with Intel Tablets increasing in use i feel this is the best course of action and will make it easier for new users . . .
The new thread is up but its still very much under construction : Intel Android Devices Root / Temp CWM Session
[TOOL KIT] myKIT_BATCHV1.1.x :
social-design-concepts : said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression myKIT wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
myKIT_BATCH TOOLv1.1.2 : "and Yet Another Generic Android Tool Kit "
any issues using this tool kit please use :
Code:
@social-design-concepts : myKIT_BATCHv1.1.2 ISSUE
DOWNLOAD / SETUP myKIT_BATCHv1.1.x
save the download somewhere on your computer using 7-zip , right click on the file and select extract here
myKIT_BATCHv1.1.2 : myKIT_BATCHv1.1.x.7z
Additional Downloads :
download any additional _ASSETKIT's / _ROOTKIT's needed for your device save the downloads in folder :
mykit-downloads
located in the top of the myKIT_BATCHv1.1.x directory where the run-me.bat file is located.
note : do not extract the files or rename them each time myKIT_BATCHv1.1.x is started it searches for .7z files with specific name endings and automatically extracts them to the correct location. . .
_PATCHKIT's :
place _PATCHKIT in mykit-downloads start myKIT_BATCH after patch is applied you'll need to close and restart myKIT_BATCH
myKIT_BATCHv1.1.2d_PATCHKIT.7z
change log :
Fix DERP in ADB Driver for Dell Venue 7 / Acer A1-830
Make ADB backup Quick Restore select-able instead of typing the full backup name
Prep For Flash Tool
Other Misc Corrections
_ROOTKIT'S :
10/06/2014 TRIAL2 : SDC_INTEL2_ROOTKIT Jellybean 4.1.2 - KitKat 4.4.x
note : This _ROOTKIT does not require the device specific _ASSETKIT that were needed before , should work on the :
Dell Venue 7 3730 / 8 3830 Clovertrail Plus , Acer Iconia A1-830 , Acer Iconia B1-730HD ,
Possibly other Intel Android Devices that have a method of starting the adbd service via fastboot oem command . . .
SDC_INTEL2_ROOTKIT.7z
OLDER _ROOTKIT'S : Recommend using the _ROOTKIT above
Jellybean 4.2.2 - Jellybean 4.3 note : this _ROOTKIT is already loaded in myKIT_BATCHv1.1.x there is no real need to download this . . .
jb4.2.2-jb4.3_ROOTKIT.7z
supported devices :
Dell Venue 7 3730 / Venue 8 3830 US Wifi / US 3G jb4.2.2 - jb4.3
Acer Iconia A1-830 jb4.2.2
Kitkat 4.4.2 note : requires device specific _ASSETKIT
DELL VENUE 7 Model 3730 US NoModem / VENUE 8 Model 3830 US NoModem WiFI Only
Kitkat 4.4.2 Dell SW v1.33 DellVenue-kk4.4.2v1.33_WiFi_ROOTKIT.7z
ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.2014062.120901:user/release-keys
ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.build.20140624.115655:user/release-keys
DELL VENUE 7 Model 3730 US 3G / VENUE 8 Model 3830 US 3G
IMPORTANT NOTICE : THERE WAS A MISTAKE IN THE ORIGINAL _ROOTKIT FOR DELL VENUE 7 3G DEVICE THAT BRAKES OTA COMPATIBILITY . . .
IF YOU ROOTED YOUR DEVICE WITH THE OLD ROOT KIT PLEASE RE-ROOT WITH THIS ONE TO RESTORE YOU ABILITY TO INSTALL DELL OTA UPDATES. . .
YOU CAN TELL IF THE OLD _ROOTKIT IS LOADED BY LOOKING AT THE NAME IN myKIT_BATCH THE NEW _ROOTKIT SAYS "KK ROOT TOOL Dell Venue 7 / 8 US 3G SW v1.33 date : 9-01-2014"
Kitkat 4.4.2 Dell SW v1.33 DellVenue-kk4.4.2v1.33_3G_ROOTKIT.7z
ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.20140624.122423:user/release-keys
ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.XYX.20140624.150615:user/release-keys
_ASSETKIT'S :
DELL VENUE 7 Model 3730 US WiFI : DeviceWIFI-Venue7_ASSETKIT.7z
DELL VENUE 8 Model 3830 US WiFI : DeviceWIFI-Venue8_ASSETKIT.7z
DELL VENUE 7 Model 3730 US 3G : Device3G-Venue7_ASSETKIT.7z
DELL VENUE 8 Model 3830 US 3G : Device3G-Venue8_ASSETKIT.7z
_PKGKIT'S :
coming soon . . .
ROOTING INSTRUCTIONS :
please make sure to disconnect all other device besides the device your working on. . . do not disconnect your device during rooting process . . .
open up the myKIT_BATCHv1.1.x folder and double click the run-me.bat to launch myKIT_BATCHv1.1.x
at the initial disclaimer screen type " ACCEPT " case sensitive without the quotes to continue
next on initial menu screen choose option 1 to update the driver ( update the driver more than likely the driver you have installed doesn't have all the modes included with it.
note : instructions for unsigned driver installation if running windows 8 or 8.1
Unsigned Driver Installation Windows 8
Unsigned Driver Installation Windows 8.1
Click to expand...
Click to collapse
after the driver installation is complete follow the instructions on the screen
once at the main menu , verify that your device is visible and showing " DEVICE STATUS: ADB-ONLINE "
next choose option A1 ROOT KITS to view the ROOT KIT MENU
at the ROOT KIT MENU select the appropriate ROOT KIT
note : the ROOT KIT MENU is dynamic and the menu option will change depending on the number of root kits found
please be sure to select the correct ROOT KIT for your Device / Software version. . .
Click to expand...
Click to collapse
next select the su / supersuer installation
next type " ACCEPT "
device will reboot and rooting / su installation will start after windows installs additional drivers if needed . . .
Click to expand...
Click to collapse
Driver Installations Language Error :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you are getting the above language error when trying to install the driver please see this link for editing dpinst.xml for your language:
The current language is not supported by the device Driver Installation Wizard
the driver is located in the myKIT_BATCHv1.1.xmykitsdriverKITADB
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
XDA:DevDB Information
[TOOL KIT] myKIT_BATCHV1.1.x, ROM for the Dell Venue
Contributors
social-design-concepts
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-05-28
Last Updated 2016-05-27
Downloads :
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Stock Image Downloads :
Note : do not extract the <file name>.system.img.gz contained with in the 7zip file .img.gz is the correct format for flashing through fastboot for intel. . .
Acer
A1-830_WW_GEN1 :
JB4.2.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.2.2/JDQ39/eng.svnadmin.20140620.161423:user/release-keys
Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.4.2/KOT49H/241:user/release-keys
Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG.7z
Dell
Venue 7 WiFi 3730 :
JB4.2.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.2.2/JDQ39/eng.XYX.20131114.170109:user/release-keys
Venue_7_WiFi_JB4.2.2v1.42_FLASHPKG.7z
JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140226.114853:user/release-keys
Venue_7_WiFi_JB4.3v1.25_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.2014062.120901:user/release-keys
Venue_7_WiFi_KK4.4.2v1.33_FLASHPKG.7z
Venue 7 HSPA+ 3730 :
JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140111.111157:user/release-keys
Venue_7_3G_JB4.3v1.22_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.20140624.122423:user/release-keys
Venue_7_3G_KK4.4.2v1.33_FLASHPKG.7z
Venue 8 WiFi 3830 :
JB4.2.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.2.2/JDQ39/eng.DYY.20131114.160805:user/release-keys
Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG.7z
JB4.3 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.3/JSS15Q/eng.XYX.20140226.115029:user/release-keys
Venue_8_WiFi_JB4.3v1.25_FLASHPKG.7z
KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.build.20140624.115655:user/release-keys
Venue_8_WiFi_KK4.4.2v1.33_FLASHPKG.7z
Venue 8 HSPA+ 3830 :
KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.XYX.20140624.150615:user/release-keys
Venue_8_3G_KK4.4.2v1.33_FLASHPKG.7z
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Tethered CWM Recovery Trial 11/5/14
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
Tethered CWM Recovery Trial :
Note : This is a Trial CWM Recovery for some Intel Devices with locked boot loaders , it still has a few bugs . . .
WARNING : This is Tethered CWM Recovery is for some Intel Devices with locked boot loaders , it is not intended for installing custom roms as if the devices has a locked boot loader the device will fail to boot the unsigned images
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
Tethered CWM Recovery Trial 11/5/14 : INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z
Launch the recovery by placing it in the mykit-downloads folder the start myKIT_BATCHv1.1.x from the main menu select option A2 then select the tethered recovery program.
See this post for latest version : http://forum.xda-developers.com/showpost.php?p=57227753&postcount=2310
Note : WORKING
adb root shell
backing up to external storage
unsigned .zip installation
you tell me
Note : KNOWN BUGS
backing up to internal storage is currently broken
installing using adb side-loading of zips doesn't work and breaks adb
you tell me
CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
I just wrote a PM to Chainfire. Let`s see if he`ll respond.
If this thing is flawless....
Then I would understand Dell for locking the boot loader.. But I am very very mad at Dell. This piece of device IS piece of junk with Android 4.3. Almost all appLications at some point in time will locked up and froze and for you to get back to it, you would have to press the power button momentarily, i.e turn off the display and turn it back on. Too bad I did not play with it very hard w/in 21 days of owning it. Now I don't know if it is worth talking to dell of repairing (AND/or REPLACING IT.)
Dell you can PM me. I will be actively watching this V8 (i GOT A 32 GIG v8) on www-facebook-com-DellHomeUS.
Thanks,
Tik
tikblang said:
Then I would understand Dell for locking the boot loader.. But I am very very mad at Dell. This piece of device IS piece of junk with Android 4.3. Almost all appLications at some point in time will locked up and froze and for you to get back to it, you would have to press the power button momentarily, i.e turn off the display and turn it back on. Too bad I did not play with it very hard w/in 21 days of owning it. Now I don't know if it is worth talking to dell of repairing (AND/or REPLACING IT.)
Dell you can PM me. I will be actively watching this V8 (i GOT A 32 GIG v8) on www-facebook-com-DellHomeUS.
Thanks,
Tik
Click to expand...
Click to collapse
Tik, while i under stand your frustration, I started this thread to move the devices out of the low activity section and for discussing and sharing any information that may lead to root method and aid in future development of these devices not to complain about Dell or the device..
if you wish to address to Dell your frustration with the device i urge you to post a commit to the facebook post:
Dell Venue 7/8 Intel Unlock Request
if you have a general question about the device please feel free to post in the new QA thread:
Dell Venue 7 & Venue 8 Intel General Q&A
or search in the original dell thread:
Original 2013 Dell Venue Tablet - root progress
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
wowbro said:
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
Click to expand...
Click to collapse
I think that social-design-concepts has them.
wowbro said:
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
Click to expand...
Click to collapse
Tell me what you want, jcase rooted 1 Venue 8 on 4.3 but the exploit was never made public, but that user allowed me access so i have, extracted boot, recovery, droidboot, kernel and ramdisk only no real images, and the rooted system.img, also took cat /proc/kallsyms from the rooted device, but have since figured out how to get kallsyms from a non rooted device, i probably have most everything you just tell me what you need.
i hope to have everything i have up by the end of the weekend, till then list what your wanting and ill post what i can provide.
social-design-concepts said:
boot.img, root.img, droidboot.img, kernel and ramdisk only no real images, and the rooted system.img, also took cat /proc/kallsyms from the rooted device.
Click to expand...
Click to collapse
Quick couple questions, how are you getting into fastboot? I can't get it. Have you tried using fastboot to flash the rooted system image?
adb reboot-bootloader even works powered off as the device use a charging os mode, or from powered off hold down vol down and the power key to boot to droidboot.
No I have the V7 not the V8, flashing a fake data.img to data I've had issues flash any img larger than 100mb or sparse images. Dell hasn't released a full restore firmware yet so I've not risked flashing system.img.
By the end of the weekend I should have everything I know up. The flashing a prerooted system image does seem to be a common root for Intel devices but with out a factory restore firmware / full-install.zip that's a huge risk knowing if it doesn't work dell won't warranty the device. So you'd be stuck with a soft brick until Dell released a full-install.zip and i don't think dells done that for any device they have ever released. Knowing that the device can be rooted with out flashing a prerooted system.img this should be a last option.
Sent from my XT907 using xda app-developers app
I am just wondering, can we dump partitions without root? If yes, then we could dump them, try to flash this rooted img`s and in case of any errors we could go back by flashing dumped files via fastboot.
social-design-concepts said:
adb reboot-bootloader even works powered off as the device use a charging os mode, or from powered off hold down vol down and the power key to boot to droidboot.
No I have the V7 not the V8, flashing a fake data.img to data I've had issues flash any img larger than 100mb or sparse images. Dell hasn't released a full restore firmware yet so I've not risked flashing system.img.
By the end of the weekend I should have everything I know up. The flashing a prerooted system image does seem to be a common root for Intel devices but with out a factory restore firmware / full-install.zip that's a huge risk knowing if it doesn't work dell won't warranty the device. So you'd be stuck with a soft brick until Dell released a full-install.zip and i don't think dells done that for any device they have ever released. Knowing that the device can be rooted with out flashing a prerooted system.img this should be a last option.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
OK. I don't know how much side chat anyone has has with jcase. He literally says the root method on his webpage i think he has registered in his xda profile. We also know he required Linux with the one and only root on the current dell ROM. He also posts on his site the basic method which he explains pretty clearly. Looks to have adb waiting for a device during the boot process to; I'm sure quickly mount something RW and script out a copy and execute a root. So, I know Linux treats hardware different and it may require less time to initiate communication with devices. Windows may not be showing you all the hardware/hardware ID's this thing reports it is so quickly during boot. It may not be possible to apply his method in a Windows environment. That said have you tried to get all the different types off hardware this thing reports that it is running on Linux and attempted a adb wait then immediate adb root method while its booting/rebooting?
I was never able to get it to work on the dell venue, I actually discovered it independent of jcase, he wasn't gonna publish it but I leak it, mine is down at the moment, when I get my new one i'all try it again.
Sent from my XT907 using xda app-developers app
deansouth8 said:
OK. I don't know how much side chat anyone has has with jcase. He literally says the root method on his webpage i think he has registered in his xda profile. We also know he required Linux with the one and only root on the current dell ROM. He also posts on his site the basic method which he explains pretty clearly. Looks to have adb waiting for a device during the boot process to; I'm sure quickly mount something RW and script out a copy and execute a root. So, I know Linux treats hardware different and it may require less time to initiate communication with devices. Windows may not be showing you all the hardware/hardware ID's this thing reports it is so quickly during boot. It may not be possible to apply his method in a Windows environment. That said have you tried to get all the different types off hardware this thing reports that it is running on Linux and attempted a adb wait then immediate adb root method while its booting/rebooting?
Click to expand...
Click to collapse
how it is in the HP 1800la
init.debug.rc:
....
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered
mkdir /data/logs 0755 system system
mkdir /data/logs/modemcrash 0775 system system
mkdir /data/logs/stats 0775 system system
mkdir /data/logs/gps 0775 system system
mkdir /data/logs/aplogs 0775 system log
setprop persist.service.apklogfs.enable 1
setprop sys.usb.config adb
setprop ro.debuggable 1
how it is on the venue 8 JB-4.2.2
init.debug.rc:
....
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
# mount data partition for get charger log
#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered
mkdir /data/logs/modemcrash 0775 system system
mkdir /data/logs/stats 0775 system system
mkdir /data/logs/gps 0775 system system
mkdir /data/logs/aplogs 0775 system log
setprop persist.service.apklogfs.enable 1
setprop sys.usb.config iadb
setprop ro.debuggable 1
how it is on the venue 8 JB-4.3
init.debug.rc:
....
on charger
on charger
# basic networking for "adb root"
ifup lo
hostname localhost
domainname localdomain
mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered
mkdir /logs/modemcrash 0775 system system
mkdir /logs/aplogs 0775 system log
setprop sys.usb.config iadb
Do you have an uncompressed boot.img off the 4.3 ? I'd like to try enabling ADB and making system mount rw. That was how we got root on the Le Pan S originally.
kairnage said:
Do you have an uncompressed boot.img off the 4.3 ? I'd like to try enabling ADB and making system mount rw. That was how we got root on the Le Pan S originally.
Click to expand...
Click to collapse
All files we have are here:
https://www.dropbox.com/sh/tqx1j2cpi155v2n/hPZPEnsZfi
maxld said:
All files we have are here:
https://www.dropbox.com/sh/tqx1j2cpi155v2n/hPZPEnsZfi
Click to expand...
Click to collapse
Right, unpacked, I would like the original boot.img.
kairnage said:
Right, unpacked, I would like the original boot.img.
Click to expand...
Click to collapse
Sorry, I misread that. I think that Social-design-concepts has them. I will try to contact him, cheers.
maxld said:
Sorry, I misread that. I think that Social-design-concepts has them. I will try to contact him, cheers.
Click to expand...
Click to collapse
Thanks, If I try to pack it and fastboot can't boot it I won't know if it's the edit or the method I used to pack it. With the original image I can try to boot it first, and make sure that the system will even allow it. Then I will be certain I am a screw up if my version doesn;t work. :doh:
How can i root my oblio min 8x8i tablet ? The programs like "odin" does not see it ?
most of oblio tablets came pre-rooted, you must be have root permissions when write "su" in any terminal emulator I just researched but I cannot find it's chipset but cpu is cortex A8 so its must be a allwinner a10 so you can even boot arm linux from sd card most of oblio tablets(such as oblio mint plus 7 just google this magical words "sunxi linux")
kingoroot working usually
reinstalling factory image = use livesuit with proper .img file
installing roms @xda we have jelly bean and if you google for a10 devices you gonna see marshmallow even possible (psst some of roms need a little modifications)
final trick: changing boot screen(not bootanimation just logo)
1-)adb devices
2-)adb shell
3-)mkdir /sdcard/nanda
4-)mount -t vfat /dev/block/nanda > /sdcard/nanda
5-) exit
6-) adb push ./linux.bmp /sdcard/nanda/linux/linux.bmp
linux.bmp must be a 32bit depth bmp file original resolution 120x120(in my tablet) but 480x480 is fine
-----
ps = I know this is a very old topic but maybe someone in somewhere finds this info and maybe help