Related
I am not responsible for any damage your nook suffers.
Officially supported by The Nooter Project for Nook Simple Touch
http://code.google.com/p/nooter/
MinimalTouch 1.1beta5
Information:
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox and sqlite3
All zips install ADW launcher + NookColorTools + MinimalisticBlack theme + Minimalistic Text Widget + Button Savior with eink friendly skins.
Bugs:
Two step method (necessary to avoid the 1+ day wait time on market).
Future updates:(In order of priority)
Block automatic updates (Accidentally taken off on last update).
Officially make it compatible with 1.1.2
Check /system version and proceed install, if not force update to 1.1.2
Make a 1 step process.
Automatically backup and zip /factory to SDcard, to avoid having to make a full backup before rooting, and to use in conjunction with Touch-Formatter
Minimal zips install my stripped down repack of Gapps.
Fulltouch zips include the complete package of Gapps.
All W zips install ADB wireless Uramdisk.
All U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need.
All X zips include NookTouchTools + Xorzone's mods, for more details on this, read (http://forum.xda-developers.com/showthread.php?t=1289894).
All beta5 in conjunction with Unroot.zip include a way to backup and restore the original files modified by the rooting process, and delete all apps installed after rooting.
Unroot restores the original files modified and deletes all installed programs after or during the rooting process (only use with beta5).
Files that get Modified:
/boot/uRamdisk - enables ADB over wifi or usb
/system/build.prop - enables google check-in service and fakes signature, to enable protected apps on market
/data/system/packages.xml - enables Gapps to work correctly once installed
/system/framework/framework.jar - generates Android ID
/data/data/com.android.providers.settings/databases/settings.db - enables Non-Market Installs
Also on X files:
/system/framework/services.jar
/system/framework/android.policy.jar
User manual:
Things you will need before rooting:
Update your NST to 1.1 (http://nooter.googlecode.com/files/nook_1_1_update.zip)
CWM: Thread: http://forum.xda-developers.com/showthread.php?t=1360994
Direct download links:
http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399
http://forum.xda-developers.com/attachment.php?attachmentid=806434&d=1323121315
Download it and burn it to an sd-card, (windows users use this to burn the image https://launchpad.net/win32-image-writer/+download)
(If the last version dosn't work, try the first).
You must have an external microSDCard reader to burn CWM, not the NST.
Understand the button layout of CWM:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Download 2 zips from one of the different releases listed underneath:You can choose what first part to use on each folder, which can be the original MinimalTouch (coreGapps+launcher,etc), or the Fulltouch(fullGapps+launcher,etc).
The second part zip is obligatory.
Select the package version to use:
NW files include Normal + adb Wifi zips.
(Download one of the "START" zips and the "END" one).
NWFullTouchPART-1-START
NWMinimalTouch-PART-1-START.zip
XWU-NWU-MFTouch-PART-2-END-1.zip
NU files include Normal + adb Usb zips.
(Download one of the "START" zips and the "END" one).
NUFullTouch-PART-1-START.zip
NUMinimalTouch-PART-1-START.zip
XWU-NWU-MFTouch-PART-2-END-1.zip
XW files include Normal + Xorzone's mods + adb Wifi zips.
(Download one of the "START" zips and the "END" one).
XWFullTouch-PART-1-START
XWMinimalTouch-PART-1-START
XWU-NWU-MFTouch-PART-2-END-1.zip
XU files include Normal + Xorzone's mods + adb Usb zips.
(Download one of the "START" zips and the "END" one).
XUFullTouch-PART-1-START
XUMinimalTouch-PART-1-START
XWU-NWU-MFTouch-PART-2-END-1.zip
beta5 folder has the most popular zips above, with an extra security layer for those who forget to make a backup. Beta5 backups all the used files to /data/backup.
(Download one of the "START" zips and the "END" one).
beta5-2 XUFullTouch-PART-1-START
beta5-2 XWFullTouch-PART-1-START
beta5-1 XWUMFTouch-PART-2-END
Unroot(only for beta5) You can revert back to the original state by flashing Deletebeta5-1.zip through CWM, let it run then pull the SD and reboot. Beta5 files also have the progress bar fixed.(testing)
beta5-4Unroot
Installing instructions:
Copy the zips onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select Choose install from zip, choose zip from sdcard, MinimalTouch-PART-1-START.zip, click yes and wait 1+ minute, (or FullTouch-PART-1-START.zip)
Go back, eject the sd card, and click reboot.
If you selected the extended package with Touchnooter apps:
At the Android Welcome Screen skip Sign In
Enable Location Services when given the option.
Select ADW launcher as default.
Log in on YouTube, by clicking options, my channel, add acount, use a complete Gmail account not just the username, accept the messages, open Gmail but dont add any account to it, just click options and force sync it, force sync it until it fails to sync and closes (FC), it may take some tryes and time, dont desist, then open market and it will fail to sync, DO IT, dont skip this steps as they are necessary for building correctly the databases.
Easy steps from here on.
Shut down your Nook.
Insert the sdcard on your nook, and boot it.
On CWM select Choose install from zip, choose zip from sdcard, MinimalTouch-PART-2-END.zip, click yes and wait.
Go back remove the SD-card, reboot.
The system will load, open Gmail let it sync, wait a bit, if it dosn't, force it to sync, it will work.
Open market, accept policies, and you are ready to go .
File list:
All the available files are listed here:
http://code.google.com/p/nooter/downloads/list
or
http://bit.ly/uqxM99
Index
Automatic Methods:
[NST]MinimalTouch 1.1beta5
[NST]Touch-Formatter
Manual Tutos:
Skip registration (OOBE)
Making the manual process LESS PAINFULL
Setting up adb manually on the nook touch
Setting up root access on NST through adb and installing busybox
Improve battery life(testing)
Backup bookmarks and annotations(testing)
Enable non market app installs
Installing XorZone's B&N button modifier
Change the powered off screen image
Blocking OTA updates
Installing new fonts for your nook (testing)
Installing Gapps (+launcher, etc)
Totally uninstall Gapps (my repack), unrooting, erasing and restoring
Interesting or useful specific apps or hacks for Nook Simple Touch
nook 1.1 update
Thanks to:
GabrialDestruir for his hard work, making easy to root the NST creating the Touchnooter (http://forum.xda-developers.com/showthread.php?t=1343143) (http://forum.xda-developers.com/showthread.php?t=1132693)
ros87 for the update on uramdisk and the how to modify boot/charging images and usb drivers. (http://forum.xda-developers.com/showthread.php?t=1337653) (http://forum.xda-developers.com/showpost.php?p=17882146&postcount=11) (http://forum.xda-developers.com/showpost.php?p=19342931&postcount=12)
XorZone for NookTouchTools and his jars, book button menu and the orientation Switch (http://forum.xda-developers.com/showthread.php?t=1289894)
nookdevs for noogie and making all this possible (http://nookdevs.com/NookColor_Rooting)
mali100 for the update on framework. (http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352)
xboxexpert for the working market. (http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51)
Kralik for his findings. (http://www.mobileread.com/forums/showthread.php?t=156539)
jerryfan2000 for Button savior (http://forum.xda-developers.com/showthread.php?t=865525)
OMGWTF_BBQ for the Button Savior eink friendly mod (http://forum.xda-developers.com/showthread.php?t=1250278)
met67 for the permissions and ownership on Gapps (http://forum.xda-developers.com/showpost.php?p=19658259&postcount=109)
mali100 for portin CWM to NST (http://forum.xda-developers.com/showthread.php?t=1360994)
salsichad2 for pointing out that the X files where corrupt and his adw theme config (http://forum.xda-developers.com/showpost.php?p=19720053&postcount=139)
kneeldug for sugesting extra steps on the automatic tuto.
bisbal for helping me beta test.
dobbing for the copy of the 1.1 update.
Hi,
thanks for the guide. I have a dumb question. Could you please provide the correct sqlite3 url to use for the download?
Thanks.
Eded,
All I can say is that I am truly sorry. The nooter didn't work because I was dumb enough not to read instructions properly. Now I added the uramdisk to the nooter/boot directory, not root directory!!!!!!!!!!!
Now it worked, and I restored the apps I downloaded with titanium backup pro.
Thing is: market (with vending.apk installed over original market) doesn't reach the server properly when I press "my apps", and I am still not able to find my device on the android market in my computer.
On the rest, it works! Thanks for everyone who gave tips!!!
I already rooted my nook with touchnooter for 1.1 can I use the instructions to just install market or do I have to start from scratch.
Dopedangel said:
I already rooted my nook with touchnooter for 1.1 can I use the instructions to just install market or do I have to start from scratch.
Click to expand...
Click to collapse
You have no need to start from scratch
You can use this method to install gapps.
Just remember to delete the other apps as launcher, etc, that you have allready installed from the package I posted.
apeine said:
Eded,
All I can say is that I am truly sorry. The nooter didn't work because I was dumb enough not to read instructions properly. Now I added the uramdisk to the nooter/boot directory, not root directory!!!!!!!!!!!
Now it worked, and I restored the apps I downloaded with titanium backup pro.
Thing is: market (with vending.apk installed over original market) doesn't reach the server properly when I press "my apps", and I am still not able to find my device on the android market in my computer.
On the rest, it works! Thanks for everyone who gave tips!!!
Click to expand...
Click to collapse
Dont worry, **** happens It's easy to mess up if you are in a hurry, it happens to me alot.
Can you still search and install from market, even if it dosnt appear en the pc?
beber75 said:
Hi,
thanks for the guide. I have a dumb question. Could you please provide the correct sqlite3 url to use for the download?
Thanks.
Click to expand...
Click to collapse
I will when I get home.
Is it possible to modify the partition to enlarge the 250mb partition? I heard that 750 mb is reserved to b&n contents and i find it a waste of space.
user4242 said:
Is it possible to modify the partition to enlarge the 250mb partition? I heard that 750 mb is reserved to b&n contents and i find it a waste of space.
Click to expand...
Click to collapse
Not sure what you mean?
Nook partition (6) is 252MB and Data partition (8) is 841MB
There's no partition "reserved" for B&N contents, it uses both and so can you.
Code:
Number Start End Size Type File system Flags
1 16.4kB 79.7MB 79.7MB primary fat32 boot, lba
2 79.7MB 96.5MB 16.8MB primary fat32 lba
3 96.5MB 296MB 199MB primary ext2
4 296MB 1942MB 1646MB extended
5 296MB 598MB 302MB logical ext2
6 598MB 849MB 252MB logical fat16 lba
7 849MB 1101MB 252MB logical ext3
8 1101MB 1942MB 841MB logical ext3
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
user4242 said:
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
Click to expand...
Click to collapse
Sure you can, but only the Nook partition is auto mounted trough USB.
If you want to put files in /data/media you can use adb or some filemanager app.
thanks Ros87, thats just another reason to nooter my NST.
I'm still on 1.0 and my plan is to:
1. backup 1.0 with the help of the link in your sig.
2. upgrade to 1.1. from B&N servers
3. Follow the guide in this thread and nooter it manually...
Smart? or do you have any tips for me?
Thanks a lot for the root.
Just got my nook touch and I'm eager to root it.
Quick question, what's the difference between this root and touchnooter.
Thanks.
dark_hawk said:
Quick question, what's the difference between this root and touchnooter.
Click to expand...
Click to collapse
This root is manual bút it adds android Market. Touchnooter does this all with a script, so its automatic BUT it doesnt add Android Market because it can't.
tomic22 said:
This root is manual bút it adds android Market. Touchnooter does this all with a script, so its automatic BUT it doesnt add Android Market because it can't.
Click to expand...
Click to collapse
Can you use touchnooter to root and then use the part of this guide to add market and apps?
Can you use touchnooter to root and then use the part of this guide to add market and apps?
Click to expand...
Click to collapse
Of course
user4242 said:
Yes but i can't put my files on the b&n reserved partition.
So if i want to put only my contents on the nook i have only 250 mb.
Right?
Click to expand...
Click to collapse
If you still want to resize the Nook partition, here's a Linux way:
As always, make sure you backup your Nook before fiddling with stuff like this
Prerequisites:
1: NST booted with Noogie
2: USB attached and recognized in Linux (usually /dev/sdb)
Make a copy of Nook and Data files (ignore socket warnings)
Code:
#mkdir tmpnook tmpdata
#mount /dev/sdb6 tmpnook
#mount /dev/sdb8 tmpdata
#tar cf tmpnook.tar tmpnook
#tar cf tmpdata.tar tmpdata
#umount tmpnook
#umount tmpdata
Delete existing and create new partitions:
Code:
# fdisk /dev/sdb
Command (m for help): d
Partition number (1-8): 8
Command (m for help): d
Partition number (1-7): 7
Command (m for help): d
Partition number (1-6): 6
Command (m for help): n
First cylinder (286-926, default 286):
Using default value 286
Last cylinder, +cylinders or +size{K,M,G} (286-926, default 926): +840M
Command (m for help): n
First cylinder (707-926, default 707):
Using default value 707
Last cylinder, +cylinders or +size{K,M,G} (707-926, default 926): +252M
Command (m for help): n
First cylinder (834-926, default 834):
Using default value 834
Last cylinder, +cylinders or +size{K,M,G} (834-926, default 926):
Using default value 926
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Create filesystems:
Code:
# mkfs.vfat -F 16 -n Nook /dev/sdb6
# mkfs.ext3 /dev/sdb7
# mkfs.ext3 /dev/sdb8
Write back your data:
Code:
# mount /dev/sdb6 tmpnook
# mount /dev/sdb8 tmpdata
# tar xf tmpdata.tar tmpdata
# tar xf tmpnook.tar tmpnook
tar: tmpnook: implausibly old time stamp 1970-01-01 01:00:00 (just ignore)
# umount tmpnook
# umount tmpdata
Remove sdcard and reboot
Eded,
Even though I am unable to download through my computer, I can perfectly download from Nook. A few weeks ago, I lost that capacity on 1.0.1, and that is why I was so interested in running the 1.1.0 rooted.
Once again, thank you all (Gabrial, Eded, Xorzone - great nooktouchtools comeback, Ros, and everyone else that helped me).
eded333 said:
[*]When the NST reboots select go launcher as your predefined launcher, skip google registration and try first to open and register on Youtube (Youtube may fail, dont worry) then GMail and then Market, if Gmail fails, dont panic, reboot and try again, dont start all the proces agian, just power cycle, allways use the same google account.
Click to expand...
Click to collapse
I was able to register on YouTube, but I keep getting the register your google account screens with both Gmail and Market over and over again. I've rebooted and tried registering about a dozen times, no success.
I followed directions exactly, could there be something I'm missing?
Hi,
If I well remember, this is a know issue I already faced off on my notion ink adam. You have to delete your registered account in your settings.
Power off then power on again your device.
Register again.
beber75 said:
Hi,
If I well remember, this is a know issue I already faced off on my notion ink adam. You have to delete your registered account in your settings.
Power off then power on again your device.
Register again.
Click to expand...
Click to collapse
Thank you for the suggestion. I tried to do this but got a message "Barnes and Noble failed to deregister device" or something. Then I tried to return to the launcher and my Button savior failed.
Restoring with nookRestore.img and starting from scratch.
Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recoveryYou can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install itSDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used romsThese roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom romsCustom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official romDownload official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based romsInstall modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support.
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse
Change symlinks/bindsTrevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADBADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing SuperchargerSupercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful linksSome link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide
3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.
I meant to edit first post... well, this works as 4th reserved then.
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app
help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:
Hi,
I would like to make an image of my currect archos install to push to 59 other tablets used for education.
Could anyone explain me how to fetch/create the current install so it can be pushed to the other devices using adb?
thanks
Chuanse said:
Hi,
I would like to make an image of my currect archos install to push to 59 other tablets used for education.
Could anyone explain me how to fetch/create the current install so it can be pushed to the other devices using adb?
thanks
Click to expand...
Click to collapse
Hi!
As I spoke, you need a PC with linux !
The most simply way is :
- copy from your device /data/media/archos.ext4 on your linux PC !
On your PC :
> mkdir data
> sudo mount -o loop archos.ext4 data
( now modify data/ how you want in /data/system/ you have all android system ! )
...repack archos.ext4 by command :
> sudo umount data
Now you have archos.ext4 with your stuff added in !
Good luck ! :good:
Dear Surdu,
If I understand correctly you are showing me how to fetch archus.ext4 file (which is archus.ext4.update on my device since I use your rom)
Then mount it in linux to make changes and unmount it again and then push to the new device
But the archos.ext4.update is your file and it does not contain alle things I configured on my archos?
like:
- wallpaper
- apps
- wifi settings and password
- custom icons on homescreen
- google account login/pw
-...
I think I need an exact clone of the configured tablet to copy and boot with on another :/
Is there a way to do that?
or am I completly wrong and what you say is perfectly doing the stuff I need?
(God I like Clockworkmod/rom manager; but that seems to be pretty complicated on Archos)
PS: I am installing the linux android sdk on my debian system, maybe I can do more with it... I was using a windows sdk
Chuanse said:
Dear Surdu,
If I understand correctly you are showing me how to fetch archus.ext4 file (which is archus.ext4.update on my device since I use your rom)
Then mount it in linux to make changes and unmount it again and then push to the new device
But the archos.ext4.update is your file and it does not contain alle things I configured on my archos?
like:
- wallpaper
- apps
- wifi settings and password
- custom icons on homescreen
- google account login/pw
-...
I think I need an exact clone of the configured tablet to copy and boot with on another :/
Is there a way to do that?
or am I completly wrong and what you say is perfectly doing the stuff I need?
(God I like Clockworkmod/rom manager; but that seems to be pretty complicated on Archos)
Click to expand...
Click to collapse
Hi There , For an exact clone of android you also need to grab the /data directory, which is the mount point for /dev/block/mmcblk0p4 ( on the SD Versions ) that's where you'll find the databases which hold account data amongst other things.
Thanks
Hello,
I'm the proud owner of an hybrid monster, called THBK1-10.
This is basically an affordable tablet, running both Windows 8 and Android 4.2.2.
10.1 display, running x86 Atom 4cores, 2Gb RAM, 32Gb eMMC, USB host enabled. It is shipped with an external keyboard/touchpad (no port, no battery, no extended storage on it). More informations: http://www.thomsoncomputing.eu/dualboot.html
Windows 8 comes in x86 flavor...
The boot process let you choose Windows or Android.
There is no play store. My main goal actually is:
- (ok) rooting Android part
- (ok) installing Play Store
- (ok) increasing space
- (nok) installing a recovery (CWM/TWRP) allowing you to flash non-signed updates
- (nok) running Linux from an external USB drive
Partition layout: http://forum.xda-developers.com/showpost.php?p=54095052&postcount=8
Rooting / play store guide: http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
Known clones: http://forum.xda-developers.com/showpost.php?p=54282229&postcount=10
Increasing space with external SD: http://forum.xda-developers.com/showpost.php?p=54914759&postcount=17
Timezone issue Android/Windows: http://forum.xda-developers.com/showpost.php?p=54945950&postcount=19
BIOS default (SlateDroid): http://www.slatedroid.com/topic/106594-thbk110-default-bios-values/
Have fun !
I know there are EXT2 drivers for Windows, and EXT3 is just EXT2 + Journaling (the journaling is an important feature, but it's not part of the security model). However, I'm not sure if any of those drivers can modify file permissions. Alternatively, one could of course hex-edit the Android partition and try to tweak the file permissions that way, but that would require much more understanding of the EXT filesystem than I have. The source code is all open, though...
Thank you. Here is what i did:
a) trying to handle EXT3 fs from Windows
-> with Ext2Fsd, i have accesses to all the partitions, including /system and /data, but unfortunatly, permissions are not correct
-> i trying with other tool (Explore2Fs) not luck
-> ltools seems to provide a lattr util that could do it, but i'm unable to see the files (certainly because of the GPT partition
b) trying to use VirtualBox with raw disk access for handling, with a linux guest, permissions:
-> up to partition 7, this seems correct
-> from partition 8 (/system), i can mount it in RO but it crashes in RW
c) trying to boot to any linux supporting EFI32 and GPT
-> thanks to paperwastage, i could achieve it (thread here: http://forum.xda-developers.com/showthread.php?t=2500078 )
-> i have strange troubles: the system only detect mmcblk0 to mmcblk7, and is throwing an error (error -110 + unknow command)
-> both, in clonezilla and ubuntu
d) tryed to use so android local tricks to force change mode, but once, i'm stuck with no eXecute flag. I dig around the local.prop or any stuff that would help me to achieve this goal. The recovery is not available (nor i found it) and the only thing i can do is factory reset.
It really seems only Windows got the proper drivers for this eMMC. This could explain why i had hard time to dump it (and, actually, i would not try to restore b/c i'm not sure everything is backuped correctly and don't want to brick my tablet), and why i could only write from Windows and why it cuts at partition7 (i have at least 12 partitions. NTFS windows main is the #11 iirc)
What i could try actually:
-> double check with newer ubuntu (when i started "install to disk", it seems it could detect the whole disk, have to look again)
-> double check with local THBK install (copy 3 apks bundled with the tablet, but perhaps a command script is available to be executed ?)
-> double check with virtual box & raw disk acces (i focused on /system, but perhaps /data is ok ?)
-> recompile Ext2Fsd to have different default properties
-> dig the hardware to see if a real recovery boot is not available, or change the recovery to something more usefull than factory reset
Thank you if you have more and more ideas
Quick notes:
- THBK1 does NOT connect to PC/MAC
- THBK1 does NOT have USB Debug activated. The micro-usb is aimed to put a (normal) cable, not an OTG one nor a charging cable. You can reach ADB only over Wireless.
-> Currently trying TowelRoot with different parameters, but for now not successfull. Basically this is a 4.2.2 kernel so i could expect a low resistance at exploits, it worths to be tested
Good news, i was able to boot from an USB stick (with EFI), and while the MMC is not accessible, i found a trick to change permissions.
I have now full R/W support on EXT3 partition.
But sadly SU is not enough to gain root accesses.... damn.
Anyone able to find doc or explain how root access is triggered ?
I found an update, and i'm now able to flash the whole system partition. Sadly, i could not flash another update.zip, so i guess this is signed (and sadly it is).
I have also tryed z4root, towelRoot exploits, not working.
Basically i could somehow bypass the sign system in applying myself the content of the update.zip (as long as it deals with /data and /system files & perms). I'll try that for at least google apps.
edit: ok i have now play store and the whole google suite is working after a big playstore update (talkback, vocal syntgetisis and so on). Only google+ is FCing but it should only be a matter of installation. I should remove it and reinstall it from the market.
Only thing missing is root
Status on Android forum side: http://forum.xda-developers.com/android/help/hacking-thbk1-10-getting-root-t2804631/post53896017
As today, the tablet is now rooted. It works flawlessly.
Next step is the handling of recovery to flash non-signed zip files. It would ease the process of installing GAPPS or rooting the tablet.
But i'll take a break before
TODO list, from top to crazy:
- recovery
- test and deploy various system tweaker sur as Xposed framework
- bugfix vibrator (only working when you hit Windows button, not in apps)
- new rom, new kernel
Here is the actual partition layout:
Code:
Model: MMC BIWIN (sd/mmc)
Disk /dev/mmcblk0: 30.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat16 ANDROID!bootloader boot, hidden, legacy_boot
2 269MB 337MB 67.1MB ANDROID!panic
3 337MB 873MB 537MB ext4 ANDROID!factory
4 873MB 2484MB 1611MB ANDROID!fake
5 2484MB 2618MB 134MB ext4 ANDROID!config
6 2618MB 4229MB 1611MB ext4 ANDROID!cache
7 4229MB 5303MB 1074MB ext4 ANDROID!logs
8 5303MB 7450MB 2147MB ext4 ANDROID!system
9 7450MB 11.7GB 4295MB ext4 ANDROID!data
10 11.7GB 11.7GB 1049kB ANDROID!misc
11 11.7GB 11.8GB 33.6MB ANDROID!boot
12 11.8GB 11.9GB 134MB ANDROID!recovery
13 11.9GB 11.9GB 33.6MB ANDROID!droidboot
14 11.9GB 12.3GB 315MB ntfs Basic data partition diag
15 12.3GB 12.5GB 273MB fat32 EFI system partition boot
16 12.5GB 12.7GB 134MB Microsoft reserved partition msftres
17 12.7GB 30.9GB 18.3GB ntfs Basic data partition msftdata
I'm not able to read the partition w/o filesystem (2, 4, 10, 11, 12, 13).
I tryed with yaffs2, but i'm not able to see them (and since it is not MTD...)
I'm working on dd image of the 32Gb MMC.
In example, hexdump of partition 12 shows it is a kernel. Certainly the recovery kernel directly flash, i should dig this.
Guide: installing Google Apps and Rooting the tablet
THIS POST IS DEPRECATED. See http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
:good: /!\ Please click thanks or offer me a coffee with donate if it was usefull for you /!\ :good:
This is rather technical, but i can help if you are stuck. Thank you for your comments.
Here is how you could install Google App suite to the THBK1-10 and certainly many ones based on Inside H2O bios, board name: CARD_B (see above for detailled specs)
Basically, to install some stuff, the concept is to get rid of all the caveats (special MMC drivers, EFI 32 bits with GPT, etc...) through actual Windows 8.1 installation. Everything takes place through classic Windows desktop. For convenience, personnally worked with TeamViewer, doing this with the dock/touchpad is pain in the ass. You can void your warranty and break the android part of your tablet, so operate carefully, i'm not responsible of what you do !
This leads to 3 phases:
a) accessing EXT4 Android partitions
b) transfer files from Windows to Android
c) change permissions
a) Accessing EXT4. I used coLinux to access and handle Android EXT4 partitions:
- download and install coLinux http://sourceforge.net/projects/colinux/files/latest/download?source=files. At the 'Choose components' screen, uncheck 'Root filesystem image Download', and accept everything (including TAP drivers)
- download and unzip Debian Squeeze image in coLinux folder (c:\program files\colinux). Warning, this leads to a 2Gb file, ensure you have proper space. You could unzip it in your external SDcard, but you would have to change the path to rootfs and swap in above squeeze.conf
http://sourceforge.net/projects/col... 6.0 Squeeze/Debian-6.0.1-squeeze.7z/download
- test it: click on the squeeze.bat file into c:\program files\colinux (if you have an error co-slirp, simply close colinux and restart it). Once you have the 'debian login:' prompt simply type root then enter. You are now under coLinux.
First, install your local keyboard (if needed)
Code:
apt-get update
apt-get install console-setup locales console-data
In case you miss the point for the keyboard:
(choose select keyboard from full list / pc azerty or whatever...)
Code:
dpkg-reconfigure console-data
- you should now update your /etc/apt/sources.list file:
Code:
nano /etc/apt/sources.list
- fill with the following lines (remove all before)
Code:
deb http://ftp.fr.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
- update your apt repository:
Code:
apt-get update
- you would like to sync the clock from Linux with Windows: edit /etc/default/rcS and change UTC=yes to UTC=no
Code:
nano /etc/default/rcS
You can exit coLinux, we have things to tweak now.You can then download the attached Squeeze.conf, and put it into your colinux folder, replacing the old. Remember, if you have changed the path for rootfs and swap, you must change them to reflect your current installation.
Squeeze.conf:
Code:
kernel=vmlinux
cobd0="c:\program files\coLinux\rootfs_2gb.img"
cobd1="c:\program files\coLinux\\swap_128mb.img"
cofs0="C:\share"
cobd8=\Device\HarddiskVolume8
root=/dev/cobd0 ro
initrd=initrd.gz
mem=256
eth0=slirp
b) transfer files from Windows to coLinux
We would create a share folder at the root of C:\.
You must have C:\share folder.
- Create a directory in /mnt
Code:
mkdir /mnt/win
- then mount the folder into your coLinux
Code:
mount -t cofs cofs0 /mnt/win
FOLLOW THE ABOVE ONLY FOR GAPPS:
- You must now download the google apps files. The operation is done under Windows:
download Android 4.2.2 ones: http://goo.im/gapps/gapps-jb-20130812-signed.zip and extract all the file into C:\share
This folder must contains the whole gapps (you 'll see folders named: system, META-INF, optional...).
You must directly DELETE 3 files and 1 folder:
file system\app\GooglePlus.apk
file system\app\LatinImeDictionary.apk
file system\lib\libjni_latinime.so
fodler system\tts
If everything is ok, browsing /mnt/win/ from coLinux (not windows)
Code:
ls /mnt/win
should show the share directory content (META-INF,system,optional,...).
FOLLOW THIS ONLY IF ROOT:
- You must now copy su binary to your tablet: download attached files, unzip, copy it to your windows desktop shared folder
Nota: this file is extracted from Koush' superuser APK. This is the x86 su binary. Feel free to replace with newest version if available or if you fear something
FOLLOW THIS IF ROOT & GAPPS
c) access to Android partition
- create a system folder in /mnt
Code:
mkdir /mnt/system
- mount android to system
Code:
mount /dev/cobd8 /mnt/system
- check you are ok with
Code:
ls /mnt/system
You must see app, bin, usr, etc .... folders.
*** at this point, /mnt/system contains ALL your android system. NO MISTAKE ! ***
FOLLOW THIS ONLY IF GAPPS
- part 1: removing files. Browse to /mnt/system/app and CAREFULLY delete the 8 files (some could be missing, don't bother):
Code:
cd /mnt/system/app
rm Provider.apk
rm Provider.odex
rm QuickSearchBox.apk
rm QuickSearchBox.odex
rm SetupWizard.apk
rm SetupWizard.odex
- part2: copy. Copy the files from Windows to Android - it could take up to 2 minutes -
Code:
cp -rp /mnt/win/system/* /mnt/system
- then fix the permissions:
Code:
chmod -R 755 /mnt/system/addon.d
chmod 755 /mnt/system/app/*
sync
At this point, this is over. You can exit from colinux, reboot to Android, and come back to windows uninstalling coLinux, if anything is ok
The whole GAPPS are installed. Enjoy !
FOLLOW THIS ONLY IF ROOT
- copy attached x86 su binary to android
Code:
cp -p /mnt/win/su /mnt/system/bin
- then fix the permissions:
Code:
chmod 755 /mnt/system/bin/su
chmod u+s /mnt/system/bin/su
ln -s /mnt/system/bin/su /mnt/system/xbin/su
sync
At this point, this is over. Reboot, you can now download and install superuser https://f-droid.org/repository/browse/?fdfilter=superuser&fdid=com.koushikdutta.superuser
Your tablet is now rooted. Enjoy !
Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)
Graveen said:
Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)
Click to expand...
Click to collapse
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.
StridAst said:
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.
Click to expand...
Click to collapse
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.
Graveen said:
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.
Click to expand...
Click to collapse
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.
StridAst said:
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.
Click to expand...
Click to collapse
Like a windows. The 'dock' is allowing light computer use, and Office 2013 home is shipped for free with the tablet. But yeah, Windows legacy is the key when dealing with windows
Hey mate,
I have one of these - http://www.ebay.co.uk/itm/390900023783?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
are you implying that I should be able to get it to dual boot Windows and Android following your guide?
Thanks
Karl
Hello Karl,
Yes it should be possible if strictly identical.
Increase data space with Link2SD
You can dedicate a part of external SD to increase /data size. Link2SD is ok for this, and will, in the free version, allows you to move APK to external partition.
Your tablet MUST be rooted !
1) ensure you have a FAT32 partition (primary, 1st position)
2) ensure you have an EXT2 or EXT4 partition (primary, 2nd position)
3) install Link2SD https://play.google.com/store/apps/details?id=com.buak.Link2SD
You can now use Link2SD which 'll create links and move your APKs to your new EXT partition.
Personnaly, i have a 32Gb SD with 24Gb FAT + 8Gb EXT4 partition.
Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)
Time is changing between windows and Android
You can simply set timezone to GMT+0 and disable network time.
On Debian, you set UTC to YES, but need to seek where it takes place in Android.
bu3304 said:
Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)
Click to expand...
Click to collapse
carrefour or conforama.
thomson carrefour and /danew in conforama.
even saw on internet that MSI is also having this tablet and just sticking there logo on it. atleast looked like this tablet.
---------- Post added at 12:05 AM ---------- Previous post was at 12:01 AM ----------
hum. i think i will go for the new asus transformer book t100 with atom z3775 processor.
i like the battery life of the asus.
but prefer the acer switch 10 in terms of look and the magnetic dock
but yeah choice of 11 hours of battery or 8. makes a difference
and the new 3775 or 3745. cpu
Asus T100-TA Magic Stick
{
"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"
}
Since development and hacking for the Asus T100 tablet has been rather slow these past few months, due to the many problems that plagued the kernel and missing drivers, I decided to make a simple-to-use toolchain that works well on the device out-of-the-box. Thus, I have bundled a fully working Ubuntu live CD image and an Android-x86 build into a single usb stick format (I call it the "Magic Stick"), to allow easy testing, booting and updating stuff on the tablet. You can also use it to recover your device and perform maintenance activities without the usual hassle. And you can use it for showing off to your friends and co-workers by triple booting your tablet.
T100 Magic Stick Features:
Dual-boot directly from USB stick into Android or Ubuntu!
Test and play with both systems to see if you like them
Ubuntu 15.04 Live:
Updated 4.0 kernel (thanks to Kirill Belyaev for the kernel build)
No more internal HDD errors (no more rpmb issues)
Suspend working!
Installer working with grub installation! Finally!!
microSD Card working correctly
Wi-Fi working stable since boot
Battery reporting
Hardware buttons
Additional tools by default (gparted, mc, uefi, efibootmgr, grub2)
Android CM13.0.2-rc1 Live:
No more internal HDD errors (no more rpmb issues)
Wi-Fi working
Bluetooth working
Battery reporting
Hardware buttons working
Google Services! (Play Store etc.)
Pre-rooted!
Writable system partition
Persistent data saving on stick (1GB internal storage)
Rotation sensor working
Shrink and change partition layouts
Install and repair bootloaders, grub2 and UEFI
Install, repair, debug and update any operating system
Download and Install:
The installation procedure is extremely simple:
Download the Magic Stick zip file from here: T100 Magic Stick download
Extract the ZIP file
Copy the contents of the extracted folder to a USB stick (at least 3GB free space required)
Disable secure boot in the UEFI firmware configuration (tap F2 at startup to enter configuration)
Boot from the USB stick (tap F2 at startup and choose the stick as boot device from the menus)
Thanks and credits:
Kirill Belyaev, Povilas Staniulis, rbg, Chih-Wei Huang, Brain WrecK, pstglia for their work and contribution + their dedication and their builds.
The whole Asus T100 Ubuntu Google+ Community (chck us out!);
The whole Android-x86 Google Group (check us out!);
Everyone else who contributed patches, fixes, ideas and suggestions!
Download:
v2.0-beta1: Download
Cheers,
C.
Changelog:
v1.5: Ubuntu: no changes or improvements, sorry...
v1.5: Android: microSD card support
v1.5: Android: no more FC bugs at boot...
v1.5: Android: display driver improvements (some games and apps which didn't work will start working now)
v1.5: Android: better overall performance (+2500 points in Antutu than previous version)
v1.5: Android: better browser support (chrome, firefox etc.)
v1.5: Android: streaming support less buggy
v1.5: Android: latest 4.4.2-r3 build included (much more stable)
v1.5: Android: improved bluetooth support (some issues still reported, though)
v1.4: Ubuntu: added bluetooth support (seems unreliable)
v1.4: Ubuntu: updated packages to latest versions
v1.4: Ubuntu: fixed Software Center problems
v1.4: Android: data is saved to the stick (1GB internal storage only!)
v1.4: Android: added bluetooth support (tethering not working, yet)
v1.4: Android: added accelerometer sensor support
v1.4: Android: added rotation sensor support
v1.3: Ubuntu installer does not crash anymore!
v1.3: Added suspend support in Ubuntu
v1.3: Updated to Ubuntu 15.04
v1.3: Added sound for Ubuntu
v1.2: Initial release
Known Issues:
Ubuntu: suspend doesn't work as it should, no bluetooth, no rotation, no camera, no microphone;
Android: suspend doesn't work as it should, no bluetooth, no rotation, no microSD, no camera, no microphone;
Android: at boot, Google text-to-speech will FC a couple of times. This is fixed once you log into google play and update the GApps;
[*]Android: sometimes the keyboard dock is not enabled at boot. This is caused by a race condition at boot and I won't fix it. If you run into it, reboot and try again; (didn't encounter it anymore)
You tell me...
Frequent Questions:
Can I remove the stick after boot?
Answer: No. This works like a live CD.
Will my data be saved?
Answer: In Ubuntu no. This works like a live CD. In Android yes, you can store up to 1GB of data (due to popular request).
Can I install Ubuntu?
Answer: Yes. This works like a live CD.
Can I install Android?
Answer: Yes, but not using the built-in installer.
How can I install Android-x86?
Answer: Manually, but it's easy. Maybe I will create a step-by-step guide later...
Will Android work with ART (before or after install)?
Answer: No.
Can I install xposed framework?
Answer: Yes, but not on the live version, you must install Android locally first.
How can I update the Android-x86 version on the stick?
Answer: Replace the files in the "x86" folder on the stick.
How can I update the Ubuntu version on the stick?
Answer: You can't (not easily anyway).
Windows Tools:
I recommend you download these and save them onto the USB stick you create yourself, to always have them on hand. I did not include them on the stick as they are licensed separately (even if "free") and all credits go to their respective authors. I also recommend downloading the Windows 8.1 drivers for the T100 and saving them to the same stick, just in case you have to re-install Windows. Just make a separate folder on the stick and save whatever you want there. It won't break any functionality.
EasyUEFI - Download
A tool which helps you manage UEFI boot entries, paths and configuration for booting with ease
Ext2Fsd - Download
A tool which helps you mount ro/rw the Android/Linux partitions in windows as regular drives
unsqashfs 4.0 - Download
A tool to extract the ".sfs" and ".squashfs" images to regular ".img" files (to make system.img writable, mountable etc.)
Advanced reboot script - Download
A Windows batch file that reboots the system so you can select the boot device using your touchscreen (boot in Android/Ubuntu directly without the dock attached etc.)
Linux how-to resources:
Unsquash FS: http://unix.stackexchange.com/questions/80305/mounting-a-squashfs-filesystem-in-read-write
Update grub: http://askubuntu.com/questions/281119/how-do-you-run-update-grub
Grub install to separate partition: http://askubuntu.com/questions/472669/install-grub-on-a-different-partition-on-triple-boot-system
Make IMG files: http://ubuntuhak.blogspot.ro/2012/10/how-to-create-format-and-mount-img-files.html
More grub: https://docs.oracle.com/cd/E26502_01/html/E28983/gkvif.html
Even more grub: http://superuser.com/questions/376470/how-to-reinstall-grub2-efi
Android How-to / guides section:
This section contains a set of guides to help you with some basic tasks and activities to easily manage your own installation(s) of Android. This is the part where the Magic Stick itself will prove to be useful and how you can use it to customize and repair or update anything. The Ubuntu related stuff is not documented here, as documentation and forums are available on the internet.
WARNING: These guides are not extremely detailed and include only the activities which have to be performed. Each configuration is different and you need to understand what you are doing to make sure you don't break anything. Worst case scenario is that you will lose all your data. However, you will still be able to boot the Magic Stick to repair or re-install everything (thank me later!)
DISCLAIMER: I am not responsible for any loss of data and you are at your own risk while using the tools, guides and information provided here. Back up your data and do not play around with systems that you use on a daily basis. Only follow these guides if you feel comfortable with the instructions and completely understand what you need to do at each step.
Make the Android system partition writable
When you download an Android-x86 release, you will find in the ZIP or ISO a bunch of files, including a file called "system.sfs" or "system.img".
If you have a file called "system.img" you can stop now, your Android system partition is writable and you can skip to the final step.
If you have a file called "system.sfs", then use the unsquashfs command to convert it into a writable format:
If you are using Windows, download the unsqashfs tool above and extract the zip. Drag and drop the "system.sfs" file on top of the unsqashfs executable to extract the system.img (you can find it inside the generated folder)
If you are using Linux, make sure squashfs-tools are installed and run this command from the folder containing the "system.sfs" file:
Code:
unsquashfs ./system.sfs
That's it, now you can mount the system.img file generated under linux using this command:
Code:
mount -o loop ./system.img /path/to/destination/
Resize the system partition
Usually, the system partition of Android-x86 is made as small as possible (you don't want to download "free space", right?) so if you want to add gapps or other packages to the system partition there will be no space left. Here's how to increase the size of the system partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Browse to the folder containing the system.img file (using 'cd' or 'mc')
Extend the system.img file by 200MB. Replace 200 with the amount of MB you want to add:
Code:
dd if=/dev/zero bs=1M count=200 >> ./system.img
Run gparted to also extend the partition inside the file:
Code:
sudo gparted system.img
In gparted, right click on the partition and select the option to shrink it down by only one MB (so it registers a change) and apply the changes
Close gparted. You're done.
Make space to install Android
Creating a new partition onto which to install Android usually requires shrinking an existing partition. If you want to install Android on the tablet (not the dock base) you will have to shrink the Windows system partition. Here's how to do it in a reasonably safe way:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Run gparted as root:
Code:
sudo gparted
In gparted, right click on the Windows system partition and select the option to shrink it down by at least 2GB. Make sure the partition actually has 2GB of free space, otherwise the process will not work.
Right click the free space and create a new partition and select to format it as ext4. It's important to make it ext4, so keep this in mind. Also give it a name such as "android".
Apply the changes and wait for the partition to be created.
Close gparted. You're done.
To have the partition available in Ubuntu Live, you have to mount it manually or just reboot (to have it mounted at boot automatically)
Install Android locally
Make sure you have the system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have an ext4 partition mounted. The Android-x86 installation is in fact a simple process of copying the ISO/ZIP files onto the destination partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice
That's it, Android-x86 is installed (but not yet bootable!)
Enable data saving for Android
To enable data saving for Android-x86, you have many choices. However, the simplest one is to use an ext4 partition and create a dedicated "data" folder for android. Make sure Android-x86 is installed onto an ext4 partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Navigate to the root of the partition (the mount point folder)
Create a folder called "data":
Code:
mkdir -p data
You're done, Android will save data persistently across reboots.
Note that this only works for ext4 partitions.
Note that using ext2 or ext3 will output errors for Google Play if you use Lollipop builds.
You have been warned.
Install the grub2 boot loader
Resizing partitions and copying (read installing ) Android is a very simple process. However, the bootloader installation is a much more complicated business (usually!). Here's how to make sure everything is installed correctly:
In progress...
Add the Android menuentry to grub2
Once we have grub2 installed and ready to go, it's time to make Adroid-x86 bootable as easily as possible:
In progress...
Update Android with new releases
Once Android is set up and ready to go, all you need to do to update it properly is to overwrite the existing files and reboot. Make sure you have the updated system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have the Android ext4 partition mounted:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice, overwriting the existing ones
That's it, Android-x86 is updated
Cheers,
C.
Reserved....
I am having some problems with this. Granted I am trying to use it for install on the Dell Venue 8 Pro. This tablet is a bay trail base, with most of the same hardware, minus the wireless/bt card. This works fantastic as a live cd, but when I install it I get problems. Is the ubuntu image only i386? When I was trying to change the kernel from the G+ group I kept getting the architecture mismatch (Kernel.deb file is amd64 and system is i386). Also the bootloader is kind of weird. All of the grub settings are correct, but if I want to boot ubuntu from the mmc I have to enter the advanced menu, then boot recovery mode. When recovery mode boots, I hit resume boot and then I am magically loaded into my installed system. Am I doing something wrong here?
The live image is i386 only. For the grub boot loader, try copying the entry contents into the stick boot menu and see if it works as intended. The menuentry file on the stick is in ./boot/grub/grub.conf.
I'll be releasing a new version of the stick with Ubuntu 15.04 (i386) and some additional sound fixes in the next few hours as well.
Cheers,
C.
Ok, v1.3 with new updates and fixes has been posted. Let me know of any improvements and/or problems.
Cheers,
C.
Thank you for great work! One promise: please, fix bug for HP Omni 10. My tablet can't boot in Ubuntu (but works perfectly with Android). Here is a link to the G+ posts with bug disc.
https://plus.google.com/105824122847813147186/posts/4G1BQgD5LNQ
https://plus.google.com/105824122847813147186/posts/gxqsVsNNJoq
The HP omni problem comes from the kernel, which I did not build and I do not maintain. Also, I don't have a HP omni, so I can't test it out.
The bottom line is that I can not promise to make it work, but I will update the kernel when possible. Keep in mind that this is a Asus T100 tool. Follow the thread and when an update for the kernel is posted, try the new version.
Cheers,
C.
Everything runs perfectly. Flawless Android and I'm still testing around Ubuntu. You've helped revitalize my T100! thanks!
Now I just need to figure out how to install the bootloader. Seems simple enough but your instructions say it may be a bit complicated so maybe I'm missing something
For some reason, after Ubuntu installed coulnd open the software manager and didnt have synaptics, also is there a way to turn of the white led,
second do i copy all the android files into the Ubuntu drive or i need to partition the ssd for another partition for android( what are the chances of 5.0/5.1)
thanks for the files and works good, only issue, not home dev but Linux/Ubuntu, that is not finger scroll friendly, and click and hold for right click(context menu) beside chromium that scroll with out having to hold the scroll bar like the rest of the system
It will be great, if you fix it. Thanks for reply!
""Login failed, impossible to establish a reliable connection to the server. This could be a temporary problem or your Android device may not be suitable for data services. If the problem persists, contact customer service. ""
Gives me this error every time I try to log in with my google account. Solutions?
Installation on hdd
I have installed ubuntu on my t100 on the hdd. It works great so manu thanks for that but I have on issue, I need to let the usb stick in on boot in order to make it boot. If I don't grub is in rescue mode saying that : "error : no such device : 25dc1ad7-c268…"
Is there any way to get touch screen working on a Toshiba Encore 2 Write? I know this thread is for the Asus T100, but I tried this flash drive image out on my device and it ran, minus touchscreen. It booted up fine and everything. If anyone is able to help me out, it would be greatly appreciated! I think the issue stems from the device having a Wacom touchscreen, but I can give any information needed!
@feduss: The connection problem did not appear in my tests and I am able to log into Google Services without any problems. Skip the account creation during the initial setup wizard and create it later and see if it works.
@alphaeagle777: try installing plasma-active. You can see it in action here: https://www.youtube.com/watch?v=mOMmp8iEaqY
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
@FiendFyre: The stick will never have Encore 2 support unless one of the kernel developers include it in the configuration. I am not building the kernels myself, so it is best to ask the Android-x86 group for more info.
Cheers,
C.
I tried already to login later...maybe i'll solve the problem creating a new account
cheatman said:
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
Cheers,
C.
Click to expand...
Click to collapse
Thanks for the reply. It was the correct issue, I didn't pay attention during installation. To solve the problem I juste reinstall grub at the right place.
edit : I speak to fast. Just reboot work, not after a shut down.
edit2 : after reinstalling ubuntu with grub at the rigth place, it still doesn't work. Can you explaim me how to install grub correctly ?
Grub entry
Hi cheatman, thanks for your great work and nice tutorials. Now I am trying to figured out, how to edit grub to add entry for android. It is situated in /dev/mmcblk0p5 in folder android. I have alrready installed ubuntu on keyboard HDD. Thanks.