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
Related
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
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 ?
How can i root simmtronics xpad mini
Specification :
Processor 1 GHz Quad Core
PLATFORM:
Operating System--Android 4.2.2 (Jelly Bean)
Sensors--3 Axle Load Sensors, G-Sensor
MEMORY:
RAM 1 GB DDR3
STORAGE
Internal Storage 8 GB
Expandable Storage Capacity 32 GB
DISPLAY
Display Type 7.85 inch HD Capacitive Touchscreen with 1024 x 768 pixels
Other Display Features IPS Display
Please Suggest me a process to root the phone ,Back up firmware ..
Any Questions about requirement of more specification/details of Device are welcome
CWM Port
Hi,
This tablet is already rooted just download SuperSU app from Play store.
I am porting custom recovery to Simmtronics XPad Mini but unfortunately I have not taken backup of stock recovery.
If anyone have the tablet, I just need you to run following command in android terminal and send me the recovery.img & boot.img files. Before running the command give root access to terminal through superSU app
Code:
su
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
m.swastik said:
Hi,
This tablet is already rooted just download SuperSU app from Play store.
I am porting custom recovery to Simmtronics XPad Mini but unfortunately I have not taken backup of stock recovery.
If anyone have the tablet, I just need you to run following command in android terminal and send me the recovery.img & boot.img files. Before running the command give root access to terminal through superSU app
Code:
su
dd if=/dev/block/nandg of=/sdcard/recovery.img
dd if=/dev/block/nandc of=/sdcard/boot.img
Click to expand...
Click to collapse
Hey, maybe i can help i am not sure but still...I also own Simmtronics tablet but i own Simmtronics Xpad Freedom...It has the same specs as Simmtronics Xpad Mini..Only thing that Xpad Mini doesn't have is Sim Slots while with Xpad Freedom you have the ability to insert sim and call..Otherwise everything is same..Same screen res,same ram.....I have the boot.img and recovery.img file but it is extracted from Simmtronics Xpad Freedom not from Xpad Mini...If that be of some help to you i can upload it here..:good:
UPDATE: 11/21/2014 Ok @#$% bluestacks .. spam adware ... after a few days its like buy or download this other stupid game ... @$%^ that... ill get ARM working and post the image...for it to be 'open source' android is a pain inthe ass when it comes to play store and games/root on AVD
UPDATE: 11/14/2014 I am just going to use bluestacks ....this is a cluster #@$% to many moving parts ... and I looked at bluestacks root and all the post are old ... I took the su busybox and superuser apk and tried to use them and I get error in superuser apk that says su is not installed ... busybox and su both work find from the shell ...
I also tried 4.4.2 and 4.2.2 with all kinds of apks for google play .. never could get it fooled and the right combo is g / google games / build file / play store / google play services the closest I got was starting the game in ARM mode and not being able to sync with google for the game because google services was out of date ...
here are some notes:
* binary files like su busybox need to match the system env ... IE arm su binary doe syou no good with HAX etc ....
* I used about 100 different su and busybox combos and could not get it to work with HAX ...
* I also tried to get emulator to run all cores with no luck using 64 bit java and 64bit SDK ...every time I tried to mount system.img it would just be black screen ..
emulator -verbose -cpu-delay 0 -no-boot-anim -avd JB -qemu -nand system,size=0x1f400000,file=C:\Users\admin\.android\avd\JB.avd\system.img
* android versoin / cpu emu / apks / bins for su busybox / google play stuff and apks / build and store hax to fool into different phone .... ALL HAVE TO BE working right for this to work right ...
example tcpdump: ELF 32-bit LSB shared object, Intel 80386
* its no wonder this is hard for me as bluestacks and apps like stupid 'jar of beans' were heavy dev to keep everything current etc ...
My best case is ARM emu on ONE core with root etc working but a jacked up store you have to force download apks some place else ... the store working is not that big of a deal untill you want to sync the games with gms google games sync or whatever... there also million apks for that too.
You could install what ever version on a real phone and get the right APKS but then if root bins and superuser is not working its pointless or well 1/2 working in my eyes ...
UPDATE: 11/11/2014 So turns out its the CPU Intel HAXM (using Intel Virtualization Technology) all the bins are Intel 80386 below example tcpdump works on the image... so I guess I just need su bin for ANDROID but build inder Intel 80386/linux (even tho the host is WINDOWS .. its emulating x86/linux ... ... ill update later .. im just working with regular ARM cpu now ...ill try to find su for linux ...for android .. or whatever im lost ..
Code:
busybox: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
busybox_ANDROID: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
su: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped
tcpdump: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
WOW REALLY !?!?
1) I been @#$^ing with emulator for the past 6hrs trying to get different apks to work and load up all the games in playstore
2) is there a way I can just take a NAND backup or maybe some .img file and load it up in the emu ?? ( IE a non @#%^ing restarted AVD )
3) maybe pull my personal apks for GoogleServicesFramework and Vending GSF / Playstore / services ?????
4) I have done a sideload of the game and it errors out saying to reinstall from play store ? what do I need to set to trick the app ?
5) I guess I can try this markethelper ...but dont think that will help the problem..
6) apparently I can't even get SU to work http://forum.xda-developers.com/showthread.php?t=821742 think I got it http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
7) is there some kind of guide for EMU working with carriers specific market play and root etc ... I would liek 4.2.2 but any guide would be fine still can't get superuser working..
All I want to do is get "clash of clans" to install along with some other apps I am poking with ;/
http://blog.apkudo.com/2012/08/08/run-google-play-on-an-emulator-and-pretend-to-be-any-device/
http://forum.xda-developers.com/showthread.php?t=1580827
http://www.howtogeek.com/138500/the...g-incompatible-android-apps-from-google-play/
http://forum.xda-developers.com/showthread.php?t=821742
for the love of god BUMP
can i put kali on my device??
if so, how?
@AlfredoAAA, The answer is NO . This is the matter of particularity , even If you did meet all of the requirements I would explain later . I am using the sequel of this Popular continuation of Backtrack 5 R3 on my Multi-Boot system for penetration testing and still got problem with my medium custom made bulid ( specially GPU for all injection and compiling \/ coding/scanning/etc etc,,,) Now imagine how on earth this Debian development based going to work on your even most powerful Nexus/Galaxy Note ,,,,,,
Requirements :
- At least 7 GB free on your internal SD card
- Kali Linux custom ARM image dedicated for your device infrastructure >>
Kali Linux has ARM repositories integrated with the mainline distribution so tools for ARM will be updated in conjunction with the rest of the distribution. Kali is currently available for the following ARM devices :
rk3306 mk/ss808
Raspberry Pi
ODROID U2/X2
Samsung Chromebook
EfikaMX
Beaglebone Black
CuBox
Galaxy Note 10.1
- Custom made recovery image for your device form the developer site
- Custom kernel patched for injection in case of wireless assessments for example.
This is quite off topic though , but I am going to share some practical method for medium to powerful devices such as Nexus line ( might be [email protected] related section though,, didn't check it) , which does not require physical installation of Canonical production line.
With the help of the attached app ( released by the same company ) , you can get your Dual boot inside your Android phone ( i,e: Nexus 7/5/,,,,,) .
We’ll need to use the Linux distribution Ubuntu to get this to work, however you won’t need to install it.
Requirements : 3 GB of free space on your device , as it needs this much to actually download and run the OS.
Instructions :
1. Create a live Disc >> Ubuntu website;download the latest desktop OS ( comes with ISO file ); Create your USB stick boot able device with the help of UNetbootin or any device you do prefer though.
2. Boot into Ubuntu >> you know the drill >> Boot your PC with USB attached; Bios choose to boot from your stick USB > After selecting , choose Try Ubuntu. It will boot into it straight from USB without installing anything literally.
3. Put the attached file into Home Folder in the File system . Open up Terminal ( assuming you have rudimentary knowledge of command line in Linux )
Type :
Code:
$ chmod +x dualboot.sh
4. We need to install Correct ADB and dependencies over company's portal through our terminal, which is included in one piece of software.
Type:
Code:
$ sudo apt-get install phablet-tools
and choose "Y" in following scene
5.Connect your Device to your PC; USB Debugging enabled through your settings>Developer. In the terminal from earlier session,
Type to install the app:
Code:
$ ./dualboot.sh
Device will be rebooted couple of times i guess upon completion
6. Ignore anything about loosing root and just press the power button once to reboot.
Once you are back into Android , open your brand new Ubuntu Dual Boot app.
7. Now we need a super fast internet and lots of patient to get through 3GB download .
From within the app, press the greyed out 'Choose which channel to install' to bring up the options. Check 'bootstrap' and scroll down to 'utopic' so you get the recommended
version of the OS. Press install.
8. During installation you'll have to grant SU permission and after a while you will be done. Press 'Reboot to Ubuntu' ( grayed out option) and your device will be booted into Ubuntu Touch OS. ( again ignore any Android identifiers while booting ).
9. Now lets Return to Android : ( Tip :Using Power button to turn it off and on again will allow you to always boot back into Android) and with the reboot button on the app you can get back into OS Touch . please pay attention in this method your Android OS will not be wiped in the process.
As usual , I am not responsible for any kind of device meltdown, possible Bricking ,, etc etc ,, All credits goes to Ubuntu developer team.