Develop Bugs

[Links Included] Android Eclair 2.1 Beta Releases on i8000 by Almar and his dev team

FROYO IS OUT NOW!!! SEE HERE
FEATURES
Supported features in latest public beta release:
HARDWARE
Display & Touch screen
Hardware keys
Internal & External storage
Vibrator
FM radio
Sound & Audio output via 3.5mm jack
Proximity and Light sensors
Orientation (Accelometer), Magnetic (Compass) and Temperature sensors
CONNECTIVITY
Phone & messaging
Wifi
GSM data (GPRS/2G/3G/..)
USB (ADB)
GPS
SOFTWARE
Android 2.1 (Eclair)
Android market
Rooting
2D/3D acceleration (libs are not included due to legal issues)
Open-source patches: I8000 B7610 M715&M8400
OTHER FEATURES
Battery driver/charging
Brightness control/backlight
COMPATIBILITY ON OTHER PHONES
Omnia pro (B7610): wifi not working
Omnia pro (B7610): hardware keyboard not working fixed
Omnia pro (B7610): some hardware buttons not working fixed
Omnia pro (B7610): vibration not working fixed
T*Omnia II (M715): not working when not connected to USB fixed
T*Omnia II (M715): headphone plug problem fixed
T*Omnia II (M715): some hardware buttons not working fixed
T*Omnia II (M715): phone not working (>rev??)
Show Omnia (M8400): wifi not working fixed
Show Omnia (M8400): USB/headphone plug/hardware buttons problems fixed
Verizon Omnia II (I920): not working
FEATURES UNDER ACTIVE DEVELOPMENT
Camera's
Proximity sensor (only kernel support yet)
Light sensor (only kernel support yet)
Bluetooth (only kernel support yet)
I920: Beta support
FEATURES UNDER DEVELOPMENT
Android 2.2 (Froyo) {sleep bug}
Android 2.3 (Gingerbread) {slooooow and some Eclair features broken}
POSSIBLE FUTURE FEATURES
Android kernel and image build from github.com
TV-Out
B7610: wifi driver
I920: CDMA phone part
___________________________________________________________________
TUTORIALS, MODS, ADD-ONS
BETA 1 INSTALLATION TUTORIAL By Me, l3ong91, XDA
1. Backup the files on your microSD first.
2. Go to Start>Settings>Memory Settings>Storage Card and click Format.
3. Download any one of the files provided on http://o2droid.phj.hu/index_en.php file section.(you can download either 512 partition image or 1GB partition image)
4. Extract the files and put it in My Storage. (Attention: Copy only "o2Beta" folder and default.txt, ext2.tar, haret.exe, log.txt, and zImage to the root of my Storage) Look at attachments.
5. Open "o2Beta" Folder and run haret.exe
6. Wait for it to load and until it say something like reboot, the device will auto reboot so just leave it there.
7. It will boot up Windows Mobile again.
8. Then go to My Storage and click on haret.exe
9. This time it will boot again and after awhile you will see Android logo on the bootscreen.
10. After the Android 2.1 was booted, hold on the "Lock" button for 3-4 sec and
turn off the device. (It will boot up Windows Mobile again, or sometimes you will have to do it manually to turn on the device)
10. Now download and copy http://rapidshare.com/#!download|482l33|443140910|o2bupdate.tar.gz|1480 and http://87.229.73.80/zImage file to root of My Storage and overwrite it.
11. Then run the haret.exe from My Storage (not inside o2Beta folder).
12. This time it will bootup faster than the first time.
13. Yes...Android's dream come true on Omnia i8000
BETA 2 INSTALLATION TUTORIAL By Kapica, MoDaCo
1. Clean SD card of beta1
a) Clean format with SD Formatter, or
Use EASEUS Partition Master and format the EXT2 partition on SD card
2. Rename o2b2filesys.tar.gz to ext2.tar.gz
3. Copy ext2.tar.gz and new zImage to My Storage and overwrite
4. Go to O2Beta directory and run haret.exe
And thats it, u get beta2 installed, rest as usual...
To add 2D/3D rename tar.gz to o2b2update as devs said...
If you experience reboots I think its to lack od 2d/3d, open the 2d/3d o2update.tar.gz and copy system directory into ext2.tar with Total Commander, save archive, copy to My Storage, and try to install now.
BETA 2 INSTALLATION TUTORIAL (EASY ALTERNATIVE) By Me, l3ong91, XDA
1. Download the latest installation package as of 11/2/2011
2. Format SD Card again using Samsung Settings>Format.
3. Delete all the Beta 1 Folder and Beta 1 files in My Storage.(if you have previously installed Beta 1 on your phone)
4. Extract and copy all the files in Beta2 installation package to My Storage.
5. Download one of the 2D/3D driver links below and rename as o2b2update.tar.gz
6. Put it in My Storage.
7. As usual, run haret.exe from o2Beta folder.
8.Then after reboot, run haret.exe from root of My Storage.
2D/3D DRIVER DOWNLOADS
For Beta1 Installation
Download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
For Beta2 Installation
Rename as o2b2update.tar.gz
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
TO ROOT BETA2 by turnado1979, MoDaCo
Download this and put it in root of My Storage
TO PREVENT PHONE FROM SLEEPING DEATH By slmz, MoDaCo
Settings>Wireless &network settings>Mobile networks> Tick "Use only 2G networks"
- 4% last for about 9 hs
BUTTON FIXES AND REMAPPING
Button fixes:
To wake up the phone with Hang up and Lock buttons only - by Rapid81
Menu button unlock policy fix - by ult_nrg
DUAL BOOT WIN-MO AND ANDROID ON OMNIA 2
1. Get Gen.Y DualBOOT from megaupload (http://www.megaupload.com/?d=HRPO9CC7)
2. Only use "Gen.Y DualBOOT WVGA v1.0.6.0 - Storage Card.cab" and delete other cabs.
3. Install cab on "Device Storage" (otherwise doesn't work)
4. Copy/move Haret.exe ,default.txt, zimage to root of SD card.
**If you want fastboot (no pushing OK in Haret) rename default.txt to startup.txt
GET LIVEWALLPAPER WORKING By Aafi-rocks, MoDaCo
1. Boot to windows and Connect your phone to PC in Mass Storage mode
2. Open ext2.tar.gz using 7-zip
3. Then go to below path ext2.tar.gz\ext2.tar\system\lib\
4.unzip the attached lib.zip file and copy all the 3 files here..
5.Then go to below path ext2.tar.gz\ext2.tar\system\app
6. Unzip the attached app.zip file and copy all the files here.. (you can also copy any other APK files for games and apps here, if you want to pre-install them)
7. Now close 7-zip and it will ask you if you want to update the archive.. click yes..
8. Now re-install Android..
Once Android is booted. On the home screen try changing the wallpaper and there you see the live Wallpaper option...Select the Live wallpaper of your choice and Njoy...!!
You can also do this without re-installing Android..
1. Explore your phone using Droid Explorer then navigate to system/lib and copy the files from the attached 'lib.zip' here..
2. Then using droid explorer install the APK files from the attached 'App.zip' file..
ADB INSTALLATION AND TUTORIAL By Rapid81, MoDaCo
1. First af all, you need to set the ports under Android.
To do that, write this to the phone: *#7284#
Then you need to select the followings:
UART -> Modem
USB -> PDA
After this, go to the Settings\Applications\Development and check the USB Debugging if it not checked already.
2. Download the Android SDK from here. Install (if you downloaded the installer) or unzip to a location where you'll easly found it. For example C:\android-sdk-windows.
3. Download Samsung KIES. Install it. It contains 2 of the 3 necessary drivers.
4. Download the SamsungADB.zip and unzip it somewhere, where you'll easly found it.
5. If the Android did not went to sleep after it started, then unplug from USB (if it plugged) and put to sleep with the Hangup button. After that, plug onto the USB. The Windows will install 2 of the 3 drivers automatically. The 3rd one will not be found. This will be the ADB driver. Go to the Device Manager and browse the driver (not just add the path to the search root, you need to select the driver yourself!!!) what you extracted from the SamsungADB.zip. Choose one of the followings:
Samsung Android Composite ADB Interface or ADB testing interface and install it.
If the Windows ask for a confirmation to install a not trusted driver, then say yes.
6. Press Windows+R and type into "cmd".
In the upcoming windows, navigate to the unzipped or installed Android SDK directory with the following command:
For example: "cd c:\android-sdk-windows"
In there, navigate to the "platform-tools" directory with this command:
"cd platform-tools"
7. This is where the party started.
Commands you can use:
adb devices -> If you see your device here, you did a good job.
adb shell -> console
In the console:
logcat -> List all android events/errors
cat /proc/kmsg -> kernel log
adb push filename folder -> Send file from Windows to android, to the specified folder
adb pull filename -> Receive file from Android to Windows
Backup all installed applications (rooting is necessary):
tar czvf /storage/App_backup.tzg /data/app* -> Backup
tar xzvf /storage/App_backup.tzg -> Restore
ADB Installation Guide on Omnia2Droid Google Source Code Page
http://code.google.com/p/omnia2droid/wiki/InstallAppsADB
___________________________________________________________________
EXTERNAL SITES, LINKS, AND PAGES
Beta Release Official Download Page: http://o2droid.phj.hu/index_en.php
Beta Release Source Code Page: http://o2droid.phj.hu/trac
Omnia2Droid Official Source Code Page: http://code.google.com/p/omnia2droid/
Almar's Twitter Account (INB2ENSECURITY): http://twitter.com/#!/INB2ENSECURITY
MoDaCo "Android on Omnia 2" Thread: http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/
YouTube "Android 2.1 Eclair on Omnia 2" Video: http://www.youtube.com/watch?v=8khXDEOO96Y&feature=player_embedded
Source Code Repository Browser: http://o2droid.phj.hu/trac/browser
Omnia Pro B7610 Discussion Forum:http://www.modaco.com/content/b7610.../331432/android-tutorials-and-known-problems/
Verizon Omnia II(I920) Discussion Forum:http://www.modaco.com/index.php?showtopic=330325&view=getnewpost
___________________________________________________________________
LATEST NEWS & UPDATES
18/1/2011
Beta 1 (Minor Fix) Link: http://o2droid.phj.hu/index_en.php
19/1/2011
New Kernel (zImage) Sleep Issue Fixed Link: http://87.229.73.80/zImage
27/1/2011
Battery charge corrected, missing interface for redio signal level, powerstate,etc. was fixed. Put in root of My Storage and overwrite it. http://o2droid.phj.hu/o2droid.zip
30/1/2011
Script included for apps that needs ROOTED Android device: http://o2droid.phj.hu/suupdate.zip
31/1/2011
Working GSM data network. The o2droid.zip file contain the latest kernel,modules, patches and applications from Rapid and Voyteckst su correction.http://o2droid.phj.hu/o2droid.zip
9/2/2011
Sleep problem solved, Alarm function working, battery drain and percentage correction, upgrading from C4 to D1 the 6500 framework, more powerfull dalvik machine (Linpack 5.x) and all the usable corrections published. There are two version, a simple upgrade to the beta: o2bupdate.zip (just unzip to My Storage) and a new filesystem including all changes and rearranged file structure: o2b2filesys.zip (contains the filesystem as tar.gz and the kernel, must unpack and copy manually - no automatic install). The later one is the beta2 (this will be commiting to the SVN); there are some changes in the automatic updates when using the beta2 image to avoid the mistakes : the new automatic filenames are o2b2update.[tar.gz][sh]. Neither version contains the EGL libraries!http://o2droid.phj.hu/index_en.php
10/2/2011
Bugfix: the init dont allowed the GSM network to get DNS, dalvik vm problems. update it with o2b2update.tar.gz ( for beta2, if you use just the corrected beta, please rename it to o2bupdate.tar.gz). There is a strange error: within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
11/2/2011
We have prepared Beta2 SD card installer (1024mb only). It includes latest update (2011-02-10). Download it http://87.229.73.80/beta2_1024.zip (it will wipe Your current installation). As always it doesn't contain 2D/3D libraries from Samsung (if You found them somewhere on the web put it before first boot to My Storage as o2b2update.tar.gz).
Note: There is still error, when within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
3/3/2011
Updated kernel and modules with support for accelerometer, compass and light sensor, keylayout files for new kernel. Download it here . Install as always: replace zImage, put o2b2update.tar.gz, o2b2update.sh to My Storage. It will work on second boot (because old init.rc is executed first).
So now working things are:
Phone
WiFi
GPS
FM Radio
Market
Data connections (GPRS)
Sensors (only proximity sensor not yet)
2D/3D (Samsung not allowed to us to distribute the 2D/3D library binaries, so they are not included in the image).
Things which are working (low level tests), but without android support for now:
Bluetooth
Camera (there are some works to be done)
8/3/2011
To enable the automatic time update from the GSM there is a simple update script. The timeupdate.zip contains both o2update.sh and o2b2update.sh, copy the proper version (in the case of beta2 image: o2b2update.sh) to the root of the My Storage and haret... At first boot just updating the system database to use the telephone network time, so must reboot again to really use this setting and show the correct time.
9/3/2011
There was a rare condition when the SD card appeared sooner than the internal flash at boot - resulting the "No init found" error in kernel. The reason that the sdhci interfaces was not stricly assigned to an mmc device - the first sdhci was the mmc0. This is corrected now, so the s3c-sdhci.1 is the mmc0, .2 is the mmc1 and so on. The corresponding kernel ( svn version 100): zImage
19/3/2011
New kernel and modules (+ keylayout for those who didn't update it yet). Main changes are: fixes for SDHCI/MMC (ported from 2.6.32, external sd is much faster now), new battery profile (now percentage is more like in WM), compass calibration bugfix. Download here: kernel_19032011.zip.
___________________________________________________________________
UNOFFICIAL RELEASES
There is an ISO file, which was compiled by Mishatir, a MoDaCo member whom is dev team related, I think. I know this is a bit late....I'm sorry because I am unaware of this unofficial release too until recently read the comment on MoDaCo.
Alright to saves time, this is what it does. This ISO is a all-in-one package where it contains the updates and some modification (camera still not working yet though), but may or may not work with devices other than I8000, because currently I only tried out on my device.
From my experience, this ISO file is really amazing, no sleep of death issue, low battery consumption (dropped from 91% to 80% for 12+ hours) and pre-installed with few apps that you can try out.
Comment by MoDaCo member on the ISO
file
Short guide by Mishatir on ISO
Instructions:
1. Wipe out all Beta 1/2 files on your My Storage and format your SD card under Samsung Settings.
2. Download the ISO file here.
3. Unrar the files.
4. Connect your phone in WM mode and placed the "iso folder" under root of My Storage.
5. Run haret.exe in the ISO folder.
6. Android should bootup.
This ISO has few updates (kernel + modules.tar.gz) by Mishatir, if you want to update them,
- zImage --------> Replace zImage under ISO folder
- modules.tar.gz ----------> Rename to o2b2update.tar.gz and placed them under root of My Storage
To avoid Sleep of death , I use "Call End" key to lock and unlock the phone...Pressing" End key" seems to be easier and more responsive to unlock the screen.
Personally I don't recommend to update because since I update it I faced a few problems which eventually cause the Android not booting up....so try all this update at your own risk.
Anyway, this is a very nice and most stable release. Now I can use Android on my daily basis. For more questions, please leave a comment.
CREDITS
Credits to Almar and his dev team, I am not one of them. I'm here to spread this big news over XDA forum to inform every Omnia 2 users about this amazing breakthrough.

Just tried and its works great
Sent from my GT-I8000 using XDA App

problem
there is a problem when it is runing the linux help

Fantastic guys
Sent from my GT-I8000 using Tapatalk

killerkarara said:
there is a problem when it is runing the linux help
Click to expand...
Click to collapse
What problem you faced? Did you follow the instructions provided?

Here is some information for people who don't want to read the whole thread on Modaco.
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Download beta release here:
http://o2droid.phj.hu/index_en.php
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
To manage ext2 partitions from Windows PC and to correctly format your SD card:
To delete ext2 from Windows PC I use EASEUS Partition Master 6.5.2 Home Edition. It is freeware, and seems to work well. Then to format the micro SD I turn on mass storage in samsung settings, connect to PC and use the SD formatting tool 3.0 from sdcard.org. It uses FAT (not FAT32) and 32kb cluster sizes. I do quick format...
For more information and to report bugs:
http://code.google.com/p/omnia2droid/
Almar's (one of the developers) twitter:
http://twitter.com/INB2ENSECURITY
Big thread on Modaco:
http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/

ummh when installing the heret.exe for the second time it stops for some reason

killerkarara said:
ummh when installing the heret.exe for the second time it stops for some reason
Click to expand...
Click to collapse
I had similar problems, stuck on the linux part. It said it couldn't mount mmcblk0p5, wich is the SDcard. I solved it by reformating my SDCARD in fat32 and it worked.

ive done step by step on what to do but its stuck on the linux boot screen last line displayed is jumping to heart and it stays there. any help would be awesome. ive installed everything to the my storage section on my phone

First of all: INCREDIBLE WORK!!! CONGRATULATIONS!!!
I've tested and it is working, but unfortunately it is freezing time after time...
I have tried this:
bobzero said:
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
Click to expand...
Click to collapse
... but no difference

is this done using harnet?

yes it uses haret.

bobzero, there's a new updated kernel release by Almar...have you tried that out?

Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.

yes, it's working even better! battery drains slower now.

Soul_Master said:
Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.
Click to expand...
Click to collapse
definitely agree with the sentence

B7610 currently not officially supported by Almar's android
maverick_endit81 said:
definitely agree with the sentence
Click to expand...
Click to collapse
Currently Almar and his team only focuses on omnia i8000, perhaps there maybe a tiny possibilities that they will release a android for other samsung phone...try checking out forums and google
Below link is maybe useful to B7610 users: http://www.modaco.com/content/b7610...-android-on-b7610-thnks-to-devs/#entry1566239

i noticed some b7610 users on the modaco thread saying that it works, but with some additional glitches... wifi doesnt work, no menu button mapped...
try it out

bobzero said:
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Click to expand...
Click to collapse
"This video contains content from Believe and Sony Music Entertainment, one or more of whom have blocked it in your country on copyright grounds."
EDIT - Ah. Been a while since I've tried, but you can use an anonymising proxy (I used http://www.hidemyass.com) to get around the restriction on YouTube.

Thanx Almar and other devs team..~~
just to share my method to make android working in my omnia..
format SD card thru samsung setting.. download and combine 1gb 18jan android + 19jan zImage update + 2d/3d patch together. after that I copy that bunch of files into omnia 'My Storage' root. (It content o2beta, default, ext.tar, haret, zImage)
first, run the haret.exe from 'My Storage/o2beta' !! . after press RUN wait till it finish with the partition. more or less than 10minute to get this done. after that, ur phone will auto restart.
after restart, run haret.exe from 'My Storage' root. !! press RUN...
Kabbooom... new life begin
I installed pro launcher n make it my default home screen n it run smoothly..
angry bird is playable too.. to make it short, Am AMAZED with this 1st beta..
just my 2 cents..

[GUIDE] Booting an Android System when only Recovery is at your disposal

This guide and the linked ZIP package are for use with the HTC Desire Z.
Version 1.0.1
Provided by Catherall
== Boot CyanogenMod 7.1 from Recovery ==
Your phone may be in a state where Android cannot start any more, even restoring a system backup might be impossible. Then it would be great to have a handy way to boot a full CyanogenMod system anyway.
With the simple to follow commands in this guide you can boot CyanogenMod 7.1 from recovery.
What you need:
Custom recovery like one of the following:
--- ClockworkMod Recovery version 5.0.2.7
--- 4EXT Recovery TOUCH v1.0.0.4 RC3
--- Other recovery with similar kernel might work
SD card (~ 800MB free)
CyanogenMod 7.1 system and boot files on SD card
All needed files are contained in the zip package:
Boot_from_SD_v1.0.1.zip (md5: d8d3332dda267fd3f6f03ba7023c6d72)
http://dl.dropbox.com/u/64675947/android/Boot_from_SD_v1.0.1.zip
Extract all files from the downloaded zip file to your SD card.
The resulting directory structure looks like this:
Code:
SD card --+-- update.zip
|
'-- BootManager --+-- README.txt
|
'-- rom8 --+-- boot.img
+-- data.img
+-- log.img
+-- name
+-- system.img
'-- .android_secure
Boot into Recovery:
Shutdown your phone completely and remove battery for about 3 seconds.
Boot your phone into HBOOT by pushing Volume down and Power at the same time for about 5 seconds.
In the HBOOT" menu use Volume down to select Recovery and engage with Power.
You are in Recovery now.
Start Android system from Recovery:
Use Volume down and Volume up to select "apply update from sd card" and engage with Trackpad button. Confirm "install" by selecting "Yes - Install .." and engage with trackpad.
Installing update.zip only starts the Android system from the SD card, nothing will be installed on your phone!
When CyanogenMod is starting the CyanogenMod logo appears.
If you have a black screen then push Power once or twice until the screen is visible.
The default language of the system is "German". Select another language using "menu" button / "Einstellungen" / "Sprache & Tastatur" / "Sprache auswählen" - change to your prefered language and hit the home button.
Congratulations, you have a full working CyanogenMod 7.1, rooted, with terminal emulator and working network.
For installing new applications:
* Put the according APK file on the SD card
* Install the app by opening the APK file with the installed app "File Manager"
== Technical Remarks and Background Information ==
Testing for a fried ROM:
(as provided by amidabuddha in http://forum.xda-developers.com/showthread.php?p=18016711 ):
Connect your phone to the computer, boot into recovery and use the following adb commands:
Code:
adb shell
dmesg | grep mmc0
If the output contains the following strings then your emmc (internal memory) is corrupted, your "chip is fried":
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Files contained in the ZIP package:
update.zip: Flashable "install" file that can be used in custom recoveries. It contains the kernel boot files and uses chroot to initialze the Android system by executing /init from the boot files
system.img, data.img, log.img, cache.img: Loop files of system, data, devlog and cache partition of CyanogenMod 7.1
When you "install" update.zip in recovery then the contained /META-INF/com/google/android/updater-script starts up. All necessary files are copied to the boot RAM disk and the shell script startsystem.sh is executed.
The script startsystem.sh mounts the Android partitions from SD card and starts up Android using the following command:
Code:
chroot /tmp/boot.img-ramdisk /init
This starts the android system (using init) with the new root on the path /tmp/boot.img-ramdisk.
Side effects of using chroot:
The phone appears as "recovery" when using "adb devices".
Using adb shell connects to /bin/sh of recovery.
You cannot use adb to install apps. As a workaround put the apk file on the SD card and install it simply by opening it with the app "File Manager"
This guide has been tested on the following Recoveries so far:
ClockworkMod Recovery 5.0.2.7 (kernel 2.6.35.14-cyanogenmod-g9e5cdf1)
ClockworkMod Recovery 3.0.2.4 (kernel 2.6.32.28-cyanogenmod-g4f4ee2e)
4EXT Recovery TOUCH v1.0.0.4 RC3 (kernel 2.6.35.13-cyanogenmod-g4dc0bbe)
4EXT Recovery v2.2.7 RC5 (kernel 2.6.35.13-cyanogenmod-g4dc0bbe)
As chroot is used to boot up the Android system it is important that the recovery kernel is compatible to CyanogenMod 7.1.
You can find your recovery kernel version by booting into recovery and using adb with the following command:
Code:
adb shell uname -r
== Feedback and Questions ==
For feedback and questions visit Freenode IRC channel #G2ROOT.
You can use the web interface at http://webchat.freenode.net/ .
After login change channel using "/join #G2ROOT".
When there is real need for the linked zip package and this guide then both will be improved.
Packages for other phones can be provided. When you have another phone then get in touch with me.
== Credits ==
Guhl (inital idea and support)
#G2ROOT freenode IRC channel ("These guys are awesome!")
Inioch (testing on a HTC Desire Z phone with a "fried" / read-only emmc)
karsten95 and coldsun15 (testing)
Nipqer (testing)
amidabuddha (fried rom check)
== Thanks ==
During my work I was supported by
#virtuousrom freenode IRC channel ("Excellent!")
Many other people, you know who you are!
P.S. If this guide does not work for you then follow the advice of Ego_UK:
"Jump three times, then turn around and say abracadabra. Maybe this helps"

I had the exact same idea as this, I knew it would work well, I just couldn't be arsed to do it
Well done man, so many people would find this helpful, this should be sticked in the development forum!
Sent from my HTC Vision using XDA

Very nice, you should PM a mod to sticky this.

well done, but how can i boot to the normal system? and when i want to boot to this system, should i do this again?

Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.

Can this be ported to be used with EVO 4G?

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
Do a nandroid backup and find out

Nice guide !
catherall said:
Boot into Recovery:
Shutdown your phone completely and remove battery for about 3 seconds.
Boot your phone into HBOOT by pushing and at the same time for about 5 seconds.
In the HBOOT" menu use to select Recovery and engage with .
You are in Recovery now.
Click to expand...
Click to collapse
That bit should be "Volume Down" instead of "Power Down"
Sent from my Desire Z running CM7.

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
{
"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"
}
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Booting to phone system: Just power on your phone.
PJ.C said:
well done, but how can i boot to the normal system? and when i want to boot to this system, should i do this again?
Click to expand...
Click to collapse
Just boot your mobile phone as usual (power on your phone) and you are in your Android system as installed in /system partition. update.zip does not install anything permanently, it just uses init from a modified kernel, mounts partitions from SD card and boots CyanogenMod 7.1
When you want to boot again from SD card you have to go into Recovery and "install" update.zip to boot.
Best regards,
Catherall

Do not use /system ROM as ram
nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
First, I do not recommend to use the ROM as ram. Some emmc might get stuck in "read only" mode when used that way
When you need more "RAM" for system you could use a swap partition or file.
However, with booting from SD card you can have a system partition with more than say 368MB. If you want to use that on a full working phone I recommend to use the app "BootManager" from Google Play. They have done a good job to boot from SD card on phones with working ROM partitions.
In fact I used their applications have 9 different ROMs on my phone installed (8 on SD card) ready to boot when ever I want.
Best regards,
Catherall

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
cjward23 said:
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
crestofawave said:
Click to expand...
Click to collapse
Sorry about that Catherall. @nickeedoo this is for people with phones that have the dreaded EMMC issue. If your phone works there is no advantage or performance gains when using this method.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Porting to another HTC phone
ngh55 said:
Can this be ported to be used with EVO 4G?
Click to expand...
Click to collapse
Yes, this should be possible within an hour when I have somebody to test it together with me.
When you have a phone where you want to port the software then just come over to the freenode IRC channel G2ROOT and we will do it together. Then we can also make a posting on the according XDA section.
Web interface: http://webchat.freenode.net - channel #G2ROOT
Best regards, Catherall

I'm also going to express my apologies and I hope this wasn't taken seriously / in an offensive way.
But yeah, it's for people who have issues with their eMMC chip's.

Lol at the picture. Alright, I'm not totally sure how all this works yet, so this is me learning!

nickeedoo said:
Lol at the picture. Alright, I'm not totally sure how all this works yet, so this is me learning!
Click to expand...
Click to collapse
I don't have much grasp of how this works, but I'll put my little linux knowledge to best use.
So...recovery shares the same build blocks of a full-fledged linux operating system, like Android. It has it's own kernel, ramdisk, yadda yadda. "chroot" is a unix (also a linux) command that changes the apparent root directory for a given process. This is very useful for a number of cases, like testing an app in a virtualized environment which in other cases would have been sub-optimal, or for compatibility. As such, in our case the "given process" is the Android system itself. You basically change the root directory of the linux system (recovery) and then initialize Android on top of it.
If anyone knows more about how this works, then please do tell as I'm quite interested myself!

How it works
crestofawave said:
I don't have much grasp of how this works, but I'll put my little linux knowledge to best use. ...
If anyone knows more about how this works, then please do tell as I'm quite interested myself!
Click to expand...
Click to collapse
You pretty got the picture. The script update.zip uses the underlying kernel to chroot the new Android system. This is "simply" done by calling init (the starting point of the Android system) in the kernel files of the new booting system, which are contained in update.zip. They mount all partitions from SD card and boot the system.
Furthermore all interfering processes from recovery are set on hold using
Code:
kill -STOP <process id>
Otherwise recovery would respond on key strokes and block the screen.

@catherall I sent a sticky request for this thread. Might be a good idea if you do as well.

catherall said:
Yes, this should be possible within an hour when I have somebody to test it together with me.
When you have a phone where you want to port the software then just come over to the freenode IRC channel G2ROOT and we will do it together. Then we can also make a posting on the according XDA section.
Web interface: http://webchat.freenode.net - channel #G2ROOT
Best regards, Catherall
Click to expand...
Click to collapse
I like that idea, I'm going to #g2root tomorrow to see if the newest cm nightly can be ported for this.
EVO-4G powered by FherraZ-Mod

[Q] FP1 - 1.6 unified storage upgrade: Problems

hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.

fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/

_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.

hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?

see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642

Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...

jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.

Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…

Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.

_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse

[LIVE][USB][T100] Asus T100-TA Magic Stick

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.

Workarounds for low internal memory

I bought the XZ1C from USA to India as it is not available at all in Indian markets (and never will be - because no compact devices were launched in India). I love this device except for one thing. Low internal memory - and I bet others might also be annoyed by this. There's two workarounds that I could immediately think of but can't be implemented with this Device.
1. Adoptable storage : Adopt external SD card as internal storage - this is one of the coolest features Oreo has to offer, but can't be used in this device. I went through a lot of blog posts and followed the steps, also read about the adoptable storage leading to no solution. I have a Samsung 128GB EVO SD card and I tried to adopt it as an internal storage in more than one ways with no success.
2. Move apps to SD : I thought I could move at least some apps if not all to external SD but this feature that was introduced in Android 2.2 (I remember using it on my Samsung Galaxy Apollo i5801) and re-introduced in 5.0. But this is also not working. I also tried enabling 'Force allow apps on external' under developer options which didn't work.
As I don't have this phone officially supported in my country, I want to check if someone can contact Sony support in their country (US, UK, Germany) to help fix this through an update maybe?
Another purpose of this thread is to discuss alternate workarounds if anyone has tried any and worked for them.

Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I agree with you. I am going to wait for a while and see if Sony pushes an update that provides move apps to SD option (which I highly doubt they will). But if there comes a point where I desperately need space, I will root the phone. Out of 6 phones that I've used in past 6 years, this is the first one I haven't rooted and ain't planning to.

Possible Solution
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
What I've done now is to factory reset the phone with the sd card inserted and boot and setup the phone with the sd card in place this time. Then format it again thru the phone (I have not activated sd card encryption yet) and all of a sudden spotify, netflix, ... work with the sd card just as expected.
So perhaps one of you, who experience the same thing, might want try out if this is reproduceable.
Keep the sd card in the phone
Factory reset (I did it via the Xperia companion desktop software)
Boot it up again
Format SD Card
Click to expand...
Click to collapse

Antilogy said:
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
Click to expand...
Click to collapse
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disable by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
That means the TC should be able to do that.

Antilogy said:
That means the TC should be able to do that.
Click to expand...
Click to collapse
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can ?)

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
Dany XP said:
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can )
Click to expand...
Click to collapse
Sorry. I meant to say topic creator. In this case that would be @kaustubhg123.

You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).

Supa_Fly said:
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Click to expand...
Click to collapse
Sony have given developers and java enthusiasts the finger with this latest bootloader. There isn't a way to save the encrypted keys (unique to your phone) before unlocking it. So you can unlock it to do development, but it's a one way step, which breaks the camera and a few other functions.
In the past my two main reasons for rooting were to theme the phone a different colour and to save battery. Theming can be done without root now and my battery lasts three days anyway.
Having said that, I have just flashed sToRm//'s TWRP + KERNEL + ROOT + DRM fix/restore (because there’s a rooting enthusiast inside every android owner) and everything is working perfectly. The camera is working and all the software functions correctly.
But rooting the phone to get you control over moving apps to the SD card is a bit extreme and a lot of work for a very minor inconvenience. What are you doing with a small compact phone if you want to use two or three hundred apps?

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
What good reasons?
I have enabled all apps to save their things on SD card (The camera app stores all photos on SD by default but the stupid Album app stores its thumbnails data on internal memory for no reason). My main big issue is with WhatsApp which stores its data on internal memory and provides no option to store it on SD card. WhatsApp is almost 11GB on my phone now.

mhaha said:
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that..
Click to expand...
Click to collapse
The Xperia V & Z1c both allowed apps to store their data on SD (Spotify, Audible, etc.) but can't do it on this phone :/ Apparently, Oreo blocks us from using our SD card in this way.

luminoso said:
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
Click to expand...
Click to collapse
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card

reckfield said:
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
Click to expand...
Click to collapse
You can bind whatsapp folder in that case

luminoso said:
You can bind whatsapp folder in that case
Click to expand...
Click to collapse
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?

reckfield said:
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
Click to expand...
Click to collapse
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.

Raz0Rfail said:
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Click to expand...
Click to collapse
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
2. when will the new twrp launch? because the last update on twrp's website was december 2017
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem

reckfield said:
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
Xperifix will always download the twrp image from his servers, you have to go a little around to use your twrp file, or he updates his img-file on his server.
2. when will the new twrp launch? because the last update on twrp's website was december 2017
Your device twrp has nothing to do with the generic release from twrp. Read the text below your qoute.
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I don't know what he will change, but if he always redownload the twrp file from his server, he has to update the img-file.
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
Click to expand...
Click to collapse
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.

Raz0Rfail said:
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Click to expand...
Click to collapse
the descriptions are absolutely precise to follow and thanks you,
in the folder data, according your description there must be this directory C:\Xperifix\DATA\TWRP an .img-File.
on my xperifix there is not such folder. attach you some images, (I also reinstall xperfix 2.5 ruling out if I lost some folders)
{
"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"
}