Database Users

(GUIDE) How To S-Off and ROOT Aria 2.2.2

Thanks to AlphaRev Team we can now S-Off the Aria(Removes Security Flag)
**This is for any Aria either shipped with or upgraded to 2.2.2 Firmware**
For an alternative guide check out post #84 by zervic in THIS Thread
Requirements you must have:
*All Drivers installed on Windows PC (See Aria Superthread)
*Aria S/W v2.2.2 (either from the Update RUU or Factory Shipped)
***WARNING*** Installing the Aria Update RUU will format the phone. Any info not backed up will be lost. SD Card is not affected
---If you have ClockworkMod installed you can make a Nandroid backup which can be restored later
*HBOOT 1.02 (installs with the Update RUU)
Difficulty Level= Medium/Some experience required
How To S-Off
-If you have s/w version 2.1 or Custom ROM follow installation instructions for Un-Rooting in the Aria Superthread
if needed: Download ATT Aria Shipping ROM 2.2.2
1- Make sure USB Debugging is checked in Applications/Development
2- Go to Revolutionary Website and click "Download For Windows". a form will pop up which we will fill out later
3- Save file to PC and keep web page open
4- Plug in phone with data cable then run downloaded program Alpharevx.exe
{
"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"
}
5- Take note of where it reads "Enter Beta Key [Serial: your personal serial ]
5- On AlphaRev website fill in the short form with your info including the alphanumeric serial given from the program (case sensative)
6- Click "Generate Key" and copy the beta key into the AlphaRev.exe program (case sensative) and press Enter
Congrats!! you should now have S-Off. If fail, check the alphanumeric serial and key for accuracy
_____________________________________________________________________________________________________________​
Install Clockwork Recovery
Download CWM 2.5.0.1 OR CWM 2.5.1.7 Off-Mode(no annoying recovery screen while charging)
Download Android Flasher
1- Extract Clockwork Recovery.zip to folder
2- Connect Phone with data cable then Run Android Flasher
3- Check box "Recovery" and click Begin
4- Navigate to Clockwork Recovery folder extracted earlier and select "Recovery.img" click Open
Once complete the phone will boot into recovery
If you made a Nandroid backup before running AlphaRevX it can now be restored
NOTE: you may also install CWM using ADB command, but this is much quicker
___________________________________________________________________________________________________________​
How To Install Superuser Permissions
Three options to aquire this:
1- Restore your Nandroid backup from CWM Recovery
2- Install a Custom ROM which includes SU
3- Follow the steps below to add SU to the Stock 2.2.2 ROM
Newer SU 3.0.6 Signed
-Older SU 2.3.6.1
-Copy SU_2361.zip to SD Card
-Boot into CWM Recovery
-Select Install Zip file from SD
-Select Choose Zip File
-Select SU-2.3.6.1-ef-signed.zip and confirm install
-Reboot and you now have SU in the App Drawer
Enjoy!! and please support the Dev's that make this possible

Thanks for creating a guide.
zedbra said:
How To Install Superuser Permissions
-Download SU 2.3.6.1
-Copy SU_2361.zip to SD Card
-Boot into CWM Recovery
-Select Install Zip file from SD
-Select Choose Zip File
-Select SU-2.3.6.1-ef-signed.zip and confirm install
-Reboot and you now have SU in the App Drawer
Click to expand...
Click to collapse
Just wanted to point out that this step is OPTIONAL. This will allow you to acquire root with your default, stock ROM. However, if you intend to install a custom ROM (Cyanogenmod, Liberated, etc.) then you should just skip this step entirely and go straight to installing the ROM of your choice.

Sweet write up! If I'm not busy this weekend, I may take a jab at it. Thanks duder.

Finally, a well done step by step writeup, that pulls all of the pieces together along with the necessary links.
Well done.
Thanks

Thank you for the comments guys!!
@drumist thanks for pointing that out. this was explained in the guide i made on other forums. fixed it here now
@cHarley04 the download for 2.2 RUU is linked in the Aria Superthread, which is linked in the first step on how to S-Off
maybe i will include the direct link for simplicity

I was just about to do this and went to alpharevs sight and the windows download link is replaced with, "windows version is under review, sorry". Noooo! I'm off today, kids and wife are asleep and my little little aria almost saw the future. Oh well, next weekend hopefully that puppys up and running. I know there's a Linux download link but I like sticking to what I always use, sucky windows.

tommyguns818 said:
I was just about to do this and went to alpharevs sight and the windows download link is replaced with, "windows version is under review, sorry". Noooo! I'm off today, kids and wife are asleep and my little little aria almost saw the future. Oh well, next weekend hopefully that puppys up and running. I know there's a Linux download link but I like sticking to what I always use, sucky windows.
Click to expand...
Click to collapse
same here
got excited at the first sight
but...

Yeah I would have no idea how to run a virtual linux instance so I could do this... hopefully AlphaRev gets the windows version cleared soon, so I can root and use wifi hotspot.

Suleeto said:
Yeah I would have no idea how to run a virtual linux instance so I could do this... hopefully AlphaRev gets the windows version cleared soon, so I can root and use wifi hotspot.
Click to expand...
Click to collapse
Vm player is easy to set up a virtual machine with and you can get it free from vmware.
Sent from my Liberty using XDA App

mtnlion said:
Vm player is easy to set up a virtual machine with and you can get it free from vmware.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
this is true, you could also burn the live ubuntu CD. then just boot PC from CD Rom
EDIT: Windows support is back online

yay!!!
got s-off but now im trying to load off mode charging recovery through android flasher and its giving me ERROR: the process adb.exe not found and fastboot.exe not found?n Ive downloaded and extracted it and try opening through android flasher and when i click on the image file a pop up says, adb is not recognized as an internal or external command. How do i go about installing a recovery?

Have you got the recovery.img out and put it on your download folder?
Signatures are fancy.

im trying to understand attn1 instructions and im stuck at #4. Extract recovery.img from the archive to the same directory/folder/map as fastboot? where can i find this? Thanks for the fast response. noob alert!

tommyguns818 said:
im trying to understand attn1 instructions and im stuck at #4. Extract recovery.img from the archive to the same directory/folder/map as fastboot? where can i find this? Thanks for the fast response. noob alert!
Click to expand...
Click to collapse
open up the clockworkrecovery rar with winrar or a program like it and youll see a file that says recovery.img that's the file you'll want to extract into the adb folder with the fastboot.exe

so guys is this still for only 2.1 users or can you already have the 2.2.2 installed

bkeaver said:
so guys is this still for only 2.1 users or can you already have the 2.2.2 installed
Click to expand...
Click to collapse
This is specifically for, 2.2.2
The first step in the process, is to upgrade to 2.2.2 if you don't have it.
If you already have 2.2.2, you just skip that step.

cHarley04 said:
This is specifically for, 2.2.2
The first step in the process, is to upgrade to 2.2.2 if you don't have it.
If you already have 2.2.2, you just skip that step.
Click to expand...
Click to collapse
let me ask 1 more way so that I am not mis-understanding..
if my wife took the OTA update from AT&T and it upgraded her phone to 2.2.2 which put the security in place preventing you from rooting this will allow me to undo that?
sorry for the extra question

I'm a knucklehead sandwich!!!! I was missing the fastboot.exe!! It was late and I was a few beers deep. All good now. S-off woooohooo!!!!!

bkeaver said:
let me ask 1 more way so that I am not mis-understanding..
if my wife took the OTA update from AT&T and it upgraded her phone to 2.2.2 which put the security in place preventing you from rooting this will allow me to undo that?
sorry for the extra question
Click to expand...
Click to collapse
Yes!!!
Sent from my HTC Aria using XDA App

@Tommyguns, glad you got iy M8
@bkeaver, yes the guide is for factory phones with 2.2(same as OTA update), and for those who want to upgrade from 2.1 using the 2.2 update RUU.
pretty sure it says that in the guide, but i will check and make adjustments for clarity if needed
Edited first post. also please take special attention to anything posted in RED
zedbra said:
Requirements you must have:
*All Drivers installed on Windows PC (See Aria Superthread)
*Aria S/W v2.2.2 (either from the Update RUU or Factory Shipped)
***WARNING*** Installing the Aria Update RUU will format the phone. Any info not backed up will be lost. SD Card is not affected
---If you have ClockworkMod installed you can make a Nandroid backup which can be restored later
*HBOOT 1.02 (installs with the Update RUU)
Click to expand...
Click to collapse

[Guide][HOW TO]Install a GNU/Linux and tools to make Custom ROMs

HOW to install a distribution of GNU/Linux and configure the necessary tools for the development of ROMs
Autores: TugaPower aka danieldmm e porfirio
Firstly, it is important to say that GNU/Linux is open source software / free, robust, reliable, free and easy installation for any user, even if you have few computer skills.
There are dozens of distributions of GNU/Linux, all available free at: http://distrowatch.com/, so choose that of your choice and according to the hardware capabilities of the machine will be installed where the distribution chosen by you.
The choice of authors this "HOWTO" is based on the distribution of GNU/Linux, Ubuntu 11.10, with the XFCE desktop environment and also the GNOME desktop environment. This is abolished by default the manager's main Gnome desktop environment and in its place put XFCE, to perform the daily tasks of work, which is very lightweight and fast. Or if they want to be more direct, Xubuntu and will soon install from scratch, which will get the same results. Personally, I'm a fan of this graphical environment (XFCE), attending to its lightness, speed, customization, etc..
What will be explained in this HOWTO:
1. Install Ubuntu or any other distribution, such as: Xubuntu, manager native XFCE desktop environment, Kubuntu, manager native KDE graphical environment; Lubuntu, manager native LXDE graphical environment, which uses less hardware resources on the machine all present in this work. Basically, we are always talking about Ubuntu, what changes is only the GUI (Graphic User Interface), where the user goes to work.
2. The process of installation and basic configuration for any of these variants, it is always the same.
3. Do not expect to find in this work, the whole process complete installation and configuration. Only the main roads and where possible, with visual aids. However there are situations so redundant, that does not need that same help. Not the purposes of this HOWTO, other possible configurations, eg setup SAMBA, APACHE, a home FTP server, desktop, etc..
4. Let's begin as follows:
4.1 Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer;
4.2 From the field 16 is a normal installation via live DVD of Ubuntu (Xubuntu, Kubuntu, Edubuntu, Lubuntu).
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU/Linux.
4.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
GETTING STARTED
1. Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer.
1.1 To start this process, you must be made to download an image of the Ubuntu operating system for the machine architecture, or x86 (for CPU 36 bit) or x64 (for 64-bit CPUs).
1.1.1 However, this day, there is some controversy on this subject. Some say that if the machine has 4GB of RAM or more, we always use the 64 bit version, even if the CPU is x86 and also say that if the machine has less than 4GB of RAM, we use the 32 bit version regardless of the CPU is x36 or x64.
NOTE: Rarely, modern computers, whether desktops, laptops, at least have at least 4GB of RAM standard. However, do not relinquish that each CPU (x86 or x64), must have the OS corresponding to your architecture. Therefore it is up to each one choose the best option.
2. ISO Images
2.1 Ubuntu 02.01 11.10 (32bit)
2.2 Ubuntu 02.02 11.10 (64bit)
3.Universal USB Installer
3.1 Now we do download the appropriate version of the distribution, we will have to download the USB Installer: www.pendrivelinux.com/downloads/Universal-USB-Installer/
But what is the purpose of this installation process?
3.2 Firstly, we can be a machine, you have not installed a drive read / write CD / DVD.
3.3 Secondly, avoid using a CD or DVD drive for installation.
4. Run the USB Installer, as Administrator of the OS and this not to happen errors during the copy of the OS to the thumb drive. This procedure is performed as follows:
- Click on the icon of the program with the button on the right mouse button and select Run as Administrator option.
5. After installing the USB Installer, run the program and click on I Agree.
{
"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"
}
6. Now we set the distribution of GNU/Linux, we will be using. I choose Ubuntu 11.10.
7. Now calm down! I hope you remember where it was saved the iso image of Ubuntu! Only then will the USB Installer will be able to recognize and perform the installation on the pen drive. Will normally be in downloads.
8. Insert the flash drive and expect it to be recognized by Windows. In this case explanation, their location is in F.
9. At this point, we select the Format F: Drive to FAT32.
NOTE: If you wish, can create a little more memory to the pen, in case it is likely to change. This is an optional. If your interest, as it is put in the picture.
Now we have everything configured properly, we will click Creat.
10. At this point you will get a WARNING message. All contents of pen drive will be erased. Click YES and continue.
11. Now it is time for a coffee, etc., etc. and wait for the installation process to complete. After this step, we will be ready for installation on the computer distribution.
11.1 While the above task does not end, we can and must perform other actions, such as creating a partition for the Ubuntu operating system.
11.2 Let's Start Menu;
11.3 Clicking the right-click Computer and then Manage;
11.4 Now on the left menu, click Disk Manager;
Arrived here, the C partition, let's click and select Shrink Volume.
12. Let us wait quietly, and very soon we will be faced with the option to reduce the partition chosen. For a minimal installation of Ubuntu, will require approximately 10 GB. However, if we want to later install the updates, music, videos, etc. ... recommend 25 GB. To be closer to the 25GB, 26GB put!
13. The next step is to reduce and click new partition will be marked in black. We will then activate this partition:
13.1 Click on the partition, with the right mouse button and select New Simple Volume.
13.2 Click Next> Next> and choose a letter to the new drive (eg U).
13.3 Now let's change the Volume Label. Put Ubuntu.
13.4 Next Run. We have created the partition and active.
NOTE: Wait now that Universal USB Installer program in the following screen appears indicating that the installation was completed and then click Close.
14. Restart the computer.
15. Immediately press F12 and select USB stick and then press ENTER.
15.1 will appear something like this:
Calm ..... very quiet .... Choose the option Install Ubuntu on a Hard Disk.
16. Now it is like to install via DVD, which I dispense to comment on "How to install Ubuntu 11.10 per DVD." See 4.2 The field from the field 16 is a normal installation of Ubuntu live via DVD.
16.1 After appearing Choose Setup Language, Portuguese choose and click Next. (You pick the language that you anderstand)
Preferably, you must have a fast Internet connection, so that the OS be upgraded soon. In the situation of not being currently available internet connection, do not put the "seen". No problem your installation will proceed smoothly. You can do it later.
17. Then will click on: One more thing, in order to choose the partition for installation.
18. CAUTION ... CAUTION!
18.1 In this field, we have all the possible CARE! The Windows partition can die!
18.2 Should be selected before the partition created in Windows (which is named Ubuntu), and then click Modify. After selecting the partition that was created on Windows (Ubuntu). In the new partition size, and put 21,000 Mount Point select /. After running OK.
The aspect should be this:
19. Now let us take the remaining space in the example 1490MB. Click Modify, and followed by the option Use as we choose and swap area and click OK.
It should be something like this:
20. Next, click Install Now and wait ......
21. Choose the location of the user:
22. Now the installation of the default keyboard ....
23. Enter personal information and click Continue.
24. Installation completed. Reboot the PC.
25. And Behold .....
Choose from the boot menu option Ubuntu .... There is also the option Windows ... Choose!
26. I chose .... Ubuntu with the Gnome GUI!
7. There is a method, also very reliable, to expedite this process, but directed to Mint distribution, which can be obtained here: community.linuxmint.com/tutorial/view/744
NOTE: TugaPower friend and colleague, will use the Mint 12 in the process of compiling ROMs. (In this case S2 i9100 ROM 4.0.3 ICS)
Version used: Linux Mint x64 12 vKDE
Download Links: http://blog.linuxmint.com/?p=1927
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU / Linux.
4.3.1 Installing the JAVA
Open the Synaptic package manager and install the openjdk-7-jdk and mark their dependencies:
Approval for the changes made​​:
Download the required files:
Installation of the necessary files and OpenJDK 7:
Now we have to install JAVA on the machine fully realized, we will proceed to their inspection.
To do so open the command line terminal to write the following command: java-version
4.3.2 Check if the package is installed 7zip more specifically p7zip-full, if not select for installation:
Once this is done we can then proceed with the installation of the Kitchen.
4.4 Installing the Kitchen
4.4.1 Initial Procedures
All information to carry out this section were collected on: forum.xda-developers.com/showthread.php?p=5626292#post5626292
Therefore, our choice falls on dsixda Android's Kitchen (Support Several devices)
(The Custom ROM made in this Guide its based to the Galaxy S2 i9100)
Download link of Kitchen: http://github.com/dsixda/Android-Kitchen/archives/master
Informational Page on Kitchen: http://forum.xda-developers.com/showthread.php?p=5626292#post5626292
After these preliminary procedures have been performed, we proceed to next steps.
By default, you will be allocated in the Downloads folder files.
4.4.2 Click on the file up with the right button of mouse and perform the extraction of the file to the Downloads folder:
4.4.3 Change the file name for kitchen (it's easier to work).
4.4.3.1 Move or Copy to folder or Personal Home:
They should stick with a structure like this:
4.5 Perform download the ROM Stock
NOTE: I personally recommend two sites:
http://forum.xda-developers.com/showthread.php?t=1075278
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regional
Download the ROM to be used in Kitchen, in this case we use the XDA, specifically the XWLP7:
NOTE: The screenshot references XWLP4 because at that time had not XWLP7
4.5.1 Download the kernel corresponding CF-root (This way remains CWM Recovery Busybox and SuperUser GB, if ICS SuperSU depends the kernel used to cook the ROM.
4.5.2 Download the kernels on CF-root: http://forum.xda-developers.com/showthread.php?t=1103399
NOTE: This case will be used the latest available to ICS, the CF-root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
NOTE: It is already available in the XDA KERNEL CF ROOT XWLP7.
4.5.3 Copy the file from the ROM inside the Kitchen to the folder original_update
4.5.3.1 If the file is in the form *******. Tar.md5 have to remove the. Md5 so that it only ********. Tar
After these steps have been made ​​in all its fullness, then we have all the necessary files to start our cooked
4.5.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
4.5.4.1 In order to run our furnace we have run the Kitchen in a command line also known as terminal or console, for it will open a command prompt within the folder Kitchen:
In order to execute the Kitchen just run the following command as root sudo. / Menu in the terminal:
6. First thing to do is point 1 or set a folder where we work. In this process the Kitchen will get to select and give the stock ROM original_update previously placed in the folder, simply enter the next screen and then select the ROM list:
Therefore, we select the first option because we only have a ROM in the kitchen, so just to enter a default because it's one
6.1 In the kitchen will then ask if we want to keep the name.
This name stock is organized as follows: WORKING_DATA_HORA, this can be changed to whatever you want, the only thing required is to keep the WORKING_
In this case I press the button to change the name ye WORKING_XWLP7_TugaPower:
To continue then just press Enter.
7. The kitchen will start the process of extracting the file from the ROM to the folder with the name we gave earlier WORKING_ ********
In this process we have to decide if we want to use the CSC (NET configuration and applications) that are included with the Stock ROM or NO.
By default this is set to YES ...
Thus, we can, because the Kitchen gives the following list of apks existing CSC and if we add the folder WORKING_ *****
Remember that in most cases, there is no problem in using the CSC Stock ROM, just advise not to use the apks the CSC because they are essentially propaganda NETWORK, which can be set to follow in the next menu to the Kitchen already well default to not add the apks:
Ready to the next step?
8. After the CSC will appear in the information regarding the boot.img, here we select the letter n because for the effect of Custom ROM do not need!
9. Then will come the question if we want to see information about the ROM.
This option is your choice will; default is Y. I personally put n. Now let's return back to the first screen which means that the necessary files are all ready ....
10. In this field, you may want to check whether there is a need to use option 2 and 3.
10.1 In the case of using the KERNEL Stock are advised to do option 2 and 3.
If the kernel you are going to use is for example the CF ROOT or any other that already have root then there is necessary to make the option 1 and 2.
10.2 In this case I will use the CF KERNEL, we will open the zip file of CF ROOT Kernel, find a file ****.tar, opening the file we find the zImage (KERNEL), selecting the zImage we proceed to the extraction process to the working folder of the Kitchen, in this case to the folder: Working_XWLP7_TugaPower
A new window will appear saying that the file already exists, just select and replace the existing ...
11. We will now switch to the Kitchen 7. Kitchen is a default to NO WIPE ROM, option 7 serves to change this ...
12. In this case I do WIPE version, you just will access option 7 in the next field and put y:
12.1 This procedure will eventually lead back to the main menu of the Kitchen. Now we have to think whether we want a ROM or deodexed ODEXED Stock ...
12.2 If we use a version ODEXED we can switch to the option 99 which will be explained below, because I'll use this version deodexed and before passing the option will be option 0 99: ADVANCED OPTIONS
IMG]http://i.imgur.com/XtfZp.png[/IMG]
13. Here I select option 11 to deodexed ROM:
13.1 Now we need one more aspect to consider: what kind of ROM, if GB or ICS.
In this case as I am using a ROM ICS will change the level of API's Kitchen and they default to GB, so I'll use the v
14. Then I confirm that I change the level of the API key y.
In this case I set the API level to 15 which corresponds ROM will be concerned that I'm using ICS 4.0.3:
14.1. Now set the API, I will proceed to the DEODEX ROM for option b, which is advised, because this way, will deodexed the system / app and system / framework.
15. Will be asked if you want a log deodex, this is your charge, if you put y, a file will be created in the root folder of the Kitchen with Deodex process, this log can be used to screen for possible errors that occur in deodexed; I always use the log file because the design is not great and always give way if there are problems in deodexed.
16. After this step made ​​the Kitchen will carry out the relevant technical Deodexed ROM:
17. Now just wait, if you can go for a coffee or a cigarette because it still takes a bit if they do not get any errors and the process goes well deodexed will be presented the following screen:
18. Pressing the Enter, go to the submenu of Kitchen Advanced Menu.
We will then press 0 to return to the main Kitchen; next step we change the name of the build of the ROM (this information that appears in the menu on the About the Phone.
18.1 For this press the key 8 from the Main Menu of the Kitchen, in which case I will change to XWLP7 Stock by TugaPower:
http://i.imgur.com/I6ZXw.png[IMG]
19. Press Enter, then we will change back to the Main Menu Kitchen, now is the time better, create CWM zip file for flashing the ROM :)
19.1 For this we will then press the Option 99:
[IMG]http://i.imgur.com/eYhj4.png
NOTE: Because you are beginning to learn how to make Custom ROMs recommend the first option which is already the default and that the Kitchen, then just do enter in the respective options that appear to the end:
Until we reach the end of file creation can change the name of it, this is the last question that makes the kitchen:
Done this you can find the ROM inside the OUTPUT folder in the Kitchen ...
You only need to copy to the memory of the phone and make the flash.
Have a good cooked and good flash
ROM that was created in TUTU --->
XWLP7 Stock By TugaPower

a hell lot of screenshots, foolproof guide, really great one for beginner

Thanks.. Must have !!

Thanks fool proof, full of screens and has each and every detail.
:thumbup:

randommmm said:
a hell lot of screenshots, foolproof guide, really great one for beginner
Click to expand...
Click to collapse
aditya_7298 said:
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
Click to expand...
Click to collapse
Thanks guys...
Cheers

wow really Great Guide.....................

[GUIDE][GT-I9082/GT-I9082L][GRAND DUOS][04/06/2013]Make your own custom rom!!

THIS GUIDE WILL NOT MAKE YOU DEVELOPER OVERNIGHT. THIS GUIDE ONLY GIVEN TO GIVE YOU HEAD START IN ROM DEVELOPMENT.
I am glad that i am posting this in our new forum...(thanks xda)
IT IS HIGHLY RECOMMENDED THAT YOU SHOULD KNOW SOME BASICS OF LINUX COMMANDS FOR ANDROID DEVELOPMENT.
DISCLAIMER- I AM NOT RECOMMENDING TO ADD PAID APPS OR SOME OTHER DEVELOPER'S WORKS IN UR ROM. PLEASE DON'T PUBLISH ROM WITH PAID CONTAINS OR OTHER DEVELOPER WORKS.
AND
"DON'T SPAM DEVELOPMENT FORUM WITH UR ROMS IF IT DOESN'T CONTAINS ANYTHING NEW."
STEPS:-
1.Things needed
2.Setting up Cygwin in windows
3.Setting up linux (if you are going to use windows then skip this)
3.Setting up a dsixda kitchen
4.Using a kitchen to make a rom
5.Customise the rom
Click to expand...
Click to collapse
1.THINGS NEEDED
1.DSIXDA Kitchen
http://github.com/dsixda/Android-Kitchen/tags
(for any kitchen related issues please report to original kitchen THREAD
2. GT-I9082 /I9082L kitchen compatibility file http://d-h.st/qr5
3. Latest Firmware from sammobile.com/firmwares or samsung-updates.com
4. 7-zip (to extract tar.md5 file) in windows.
5. Notepad++
6.cygwin or linux (ubuntu or its variant preferred)i recommend using Linux for your development (sometimes cygwin causes symlink errors in updater script)
i use linuxlite or ubuntu 10.04 or ubuntu 13.04 64bit.
In windows android development is difficult and for porting and debugging ,tar,untar and many other functions linux is the only way.
7.JDK www.java.com
Click to expand...
Click to collapse
2.SETTING UP CYGWIN IN WINDOWS
(I am not using cygwin for my development ,although it is setup in my pc.I personally prefer linux)
Download Latest JDK from http://www.java.com/en/download/manual.jsp choose windows offline version
Download cygwin package from http://content.wuala.com/contents/neroyoung/XDA%20ROM%20Dev%20Tools/Cygwin.zip
-->Install JDK first .
-->extract cygwin.zip C:\
-->We need to install cygwin, open the setup.exe, just keep hitting next until you are on the select packages screen, go to "Devel" menu and select to install gcc, gdb and make, in "Interpreters" check perl, in "Archive" check zip and unzip, in "Web" check wget, in "Editors" check nano and vim and in "Utils" select cpio, util-linux and ncurses. Make some tea and wait for the cygwin install to finish and we are ready to go to the next step.
Click to expand...
Click to collapse
NOW CYGWIN IS READY TO GET KITCHEN
3.SETTING UP LINUX
i personally recommend linux for kitchen and other android development use.
i use linux lite(based on ubuntu LTS release) http://www.linuxliteos.com/ I also use ubuntu 13.04
if u want to use ubuntu then i recommend version 10.4 or 13.04 or use kubuntu latest release.
Installing linux along with windows on other partition as dual boot can be done but need experience.
Following are 2 methods are easiest and currently recommended by me.
FIRST METHOD
Most easy and recommended
INSTALLING UBUNTU ALONG WITH WINDOWS WITHOUT FORMATING HARD DRIVE OR PARTITION
-->Download Ubuntu 13.04 64bit
-->Download WUBI 13.04
-->make sure ur one of the partitions on ur pc have atleast 25 to 30 gb space.
-->After downloading put wubi and ubuntu iso in same folder
(note don't use wubi on windows 8 pc)
-->Double click on wubi.exe
-->Select Drive with maximum space. select 22gb in installation size.
-->set ur administrator password & re-enter it in confirm password box.
-->click install & wait for finish screen.
-->select reboot.
-->on rebooting it will start installation automatically.
-->wait till installation finishes & reboot to default ubuntu log screen.
-->login with ur username/password
-->make sure ur internet is connected.
-->Press Ctrl+Alt+T to open terminal & type following
(if it ask for password then type it and press enter)
Code:
sudo apt-get install gnome-shell gnome-session-fallback indicator-applet-appmenu gnome-tweak-tool ia32-libs
-->after that logout (it is round setting like icon in top corner) and select the session as "genom fallback with no effects" from login screen (round icon beside ur_username on login screen)
-->now relogin
-->go to applications>>ubuntu software center
-->search java>>select openjdk7 java runtime environment>>click install. Wait till installation.
Click to expand...
Click to collapse
NOW SETUP KITCHEN
SECOND METHOD
Those who want to set up linux in virtual machine need fast pc with lots of ram.
--> install virtual box http://www.virtualbox.org/
-->after installation open virtual box
--> click new-->in name box type ubuntu or kubuntu , it will automatically select linux and ubuntu or kubuntu in below boxes.-->click next-->select ram size u want to devote to virtual machine i recommend atleast 1024mb.
-->click next you will see menu to creat a virtual hard disk.Select create new hard disk-->select hard disk type as vdi in next screen.-->in next screen select dynamically allocated.-->in next screen click yellow icon beside ubuntu or kubuntu and select where you want to put your hard disk. You need atleast 15 to 20 gb space for hard disk. then click create.
-->now click start in virtual box on selecting kubuntu. it will ask for you bootable disk. browse and select ubuntu or kubuntu or linuxlite bootable disk. It will boot into boot menu. select install to hard drive.(google for installation instructions for ubuntu or kubuntu or linuxlite)
-->now boot up your virtual machine
-->login with user you created.
then follow the instruction s in this post http://forum.xda-developers.com/showpost.php?p=5626300&postcount=3 under linux/ubuntu section.
Click to expand...
Click to collapse
NOW YOUR VIRTUAL MACHINE IS READY TO SETUP KITCHEN
4.SETING UP DISXDA KITCHEN
A] cygwin instructions
-->Download kitchen from above link.
-->extract it to C:\cygwin\home\
-->rename the extracted folder to "kitchen" from "Android-Kitchen-xxx" (easier to navigate)
-->Now fireup cygwin from desktop icon.
-->In command window type "cd ../kitchen" press enter
-->then type ./menu
--> and you ready to go...!!!
Click to expand...
Click to collapse
B] Linux instructions
-->Download the kitchen
-->extract it to home/your_username directory
-->rename the extracted folder to "kitchen" from "Android-Kitchen-xxx" (easier to navigate)
-->Open the terminal & type "cd kitchen" press enter
-->then type ./menu press enter.
--> and you ready to go...!!!
Click to expand...
Click to collapse
NOW YOU HAVE YOUR KITCHEN SETUP FOR USE.
MAKING I9082/I9082L ROM DEVELOPMENT COMPATIBLE WITH KITCHEN
-->Now go to \kitchen\tools\edify_defs in linux or cygwin folder
-->copy the compatibility file I provided above to this folder.
-->VOILA NOW OUR GRAND IS COMPATIBLE WITH KITCHEN.!!!!
Click to expand...
Click to collapse
4.USING KITCHEN TO MAKE A ROM
-->Download the firmware of choice from www.sammobile.com/firmwares or www.samsung-updates.com
-->Unzip it.
-->You will get tar.md5 file.
-->If you are using windows then open the tar.md5 with 7-zip. or in linux open it with archiever
-->7-zip will show an error just click ok.
-->Now your tar.md5 is open.
-->extract system.img,boot.img,cache.img to"original update" folder in kichen folder.
-->Fireup the kitchen as stated above.
-->select option 1 - Set up working folder from ROM
-->press enter to continue.
-->press enter again to copy imgs to working folder
-->now in linux it will automatically copy them ,extract them to working folder
-->but in cygwin it will show prompt to extract system.img. (read the instructions when it prompt) extract it to working folder.-->it will show prompt to extract cache.img to system folder.-->Now you have your working folder setup for use. do it.
-->now select option 2 , 3 one by one to get root and busybox respectively.
-->now select 0 advanced options
--> in that select 14 to add init.d support
-->select 11 Deodex files in your rom . here press "v" to change the API level. Set it to 16 or 17 .(JB4.1.2 is level 16 and JB4.2.2 is level 17 )Now select "b" to deodex both app and framework folder.
--> now go back to main menu. and select 99 build the rom from working folder. here select 2 lazy mode.
--> Wait for some time. you will get prompt that baffin_signed_xxxx.zip is created in output_zip folder.(this lies in kitchen's folder)
Click to expand...
Click to collapse
HERE IT IS... YOUR FIRST CUSTOM ROM.:good:

5.how to customise your rom.
So first thing now for you to customize your own rom.
You can do this in linux or windows
DISCLAIMER- I AM NOT RECOMMENDING TO ADD PAID APPS OR SOME OTHER DEVELOPER'S WORKS IN UR ROM. PLEASE DON'T PUBLISH ROM WITH PAID CONTAINS OR OTHER DEVELOPER WORKS
A]Remove & add apps
B]Remove unnecessary files.
C]Add your own ringtones,alarm,notification sounds
So lets start....
First u have to make back up copy of ur rom.(I am a back up freak...)
A]Remove & add apps
REMOVE APPS
Extract your rom to some directory like "myrom"
Now you get system,boot.img,meta-inf folder extracted.
Go to >>system/app
DELETE THE APPS YOU DON'T NEED.
I AM GIVING YOU THE NAME OF FILES I REMOVE AS PER MY NEED.
\system\app
ACCUWEATHER
AccuweatherDaemon.apk
AccuweatherWidget.apk
AccuweatherWidget_Main.apk
WeatherWall.apk
ALLSHARE
AllshareMediaServer.apk
AllSharePlay.apk
AllshareService.apk
CLOCK
AnalogClockSimple.apk
DigitalClock.apk
DualClockAnalog.apk
DualClockDigital.apk
SimpleAlarmClock.apk
CAMERA FEATURE
BestGroupPose.apk
FaceLock.apk
GroupCast.apk
SAMSUNG MESSANGER
ChatON_MARKET.apk
FONTS
ChocoEUKor.apk
CoolEUKor.apk
HelvNeueLT.apk
RoseEUKor.apk
CHROME BROSWER
ChromeBookmarksSyncAdapter.apk
ChromeWithBrowser.apk
CSC
CSC.apk
LIVE WALLPAPER
DeepSea.apk
LuminousDots.apk
NoiseField.apk
PhaseBeam.apk
SecLiveWallpapersPicker.apk
DROPBOX
Dropbox.apk
DropboxOOBE.apk
GALLARY
EasyGalleryWidget.apk
EMAIL,EXCHANGE,VPN
EdmSysScopeService.apk
EdmVpnServices.apk
EnterprisePermissions.apk
Gmail.apk
SecEmail.apk
SecExchange.apk
FLASH ANNOTATE SERVICE
FlashAnnotate.apk
FlashAnnotateSvc.apk
SOFTWARE UPDATE CLIENT (MUST REMOVE BECOZ IT WONT WORK)
FotaClient.apk
GAME HUB
GameHub_2.0_ICS.apk
MAPS
GMS_Maps.apk
Street.apk
Velvet.apk
GOOGLE SEARCH AND OTHER SERCICES
GoogleSearchWidget.apk
GoogleTTS.apk[TEXT TO SPEECH SERVICE]
Magazines.apk[PLAYSTORE MAGAZINES]
Music2.apk
MusicHub_31.apk
PlusOne.apk[GOOGLE+1]
VoiceRecorder.apk
VoiceSearchStub.apk
YouTube.apk
HELP
HelpHub.apk
PickUpTutorial.apk
WebManual.apk
KIES OVER WIFI
kieswifi.apk
SAMSUNG SERVICES AND APPS
MobileTrackerEngineTwo.apk
S-Voice_Android_phone.apk
SamsungApps.apk
SamsungAppsUNA3.apk
Samsungservice.apk
SamsungTTS.apk
SamsungWidget_FavoriteApp.apk
SamsungWidget_ProgramMonitor.apk
SimpleFavoritesWidget.apk
SlideShow.apk
SMemo2.apk
SNoteProvider.apk
SSuggest.apk
PAGE BUDDY
PageBuddyNotiSvc.apk
POLARIS
PolarisViewer.apk
CLOUD SERVICES
sCloudDataRelay.apk
sCloudDataSync.apk
sCloudSyncBrowser.apk
sCloudSyncCalendar.apk
sCloudSyncContacts.apk
sCloudSyncSNote.apk
WIFI DIRECT
SecFileShareClient.apk
SecFileShareServer.apk
SETUP WIZARD
SecSetupWizard.apk
SOCIAL
SNS.apk
GTALK
Talk.apk
talkback.apk
VIDEO & OTHER VIDEO APPS
TrimApp_phone.apk
VideoHub.apk
YAHOO SERVICES
YahoonewsDaemon.apk
YahoonewsWidget.apk
YahoostockDaemon.apk
YahoostockWidget.apk​
Click to expand...
Click to collapse
Now that u deleted the apps u dont need.
make a zip of "system,boot.img & meta-inf" by selecting all . >>>right click >>add to archive(winrar) or some other zip program u use>>ur zip is ready to flash through cwm.
ADD APPS
There are 3 ways to add apps to your rom
1.Including apps in system/app
2.including apps in data/app
3.Using cwm zip for adding apps
1. Including apps in system/app
This can be done by following method
>> install apps from play store in ur rooted rom.
>>go to file manager like es or root browser or root explorer
>>open data/app folder
>>you will get your install app apks there.
>>copy them to your external sd card.
>>now open ur extarcted rom's system/app folder
>>copy the apps u wanted to install in this folder.
>>make a zip of system,boot.img and meta-inf
>>now flash ur rom .
2.Including apps in data/app
This can be done by following method.
>>enable data/app in ur rom while making rom in dsixda kitchen.
>>extarct ur rom
>>copy the applications u want in data/app
>>make a zip of all the containts in extracted folder & flash.
3.using cwm flashable zip to add apps
this is done as follows
>>extract cwm zip
>>mostly u will get system & meta-inf folder
>>open system folder and see what folders u have in that.
>>copy these folders in ur rom's system folder.
>>make a zip of ur rom
>>flash through cwm.

reserved#1

reserved #2

reserved#3

k2wl said:
THIS GUIDE WILL NOT MAKE YOU DEVELOPER OVERNIGHT. THIS GUIDE ONLY GIVEN TO GIVE YOU HEAD START IN ROM DEVELOPMENT.
I am glad that i am posting this in our new forum...(thanks xda)
IT IS HIGHLY RECOMMENDED THAT YOU SHOULD KNOW SOME BASICS OF LINUX COMMANDS FOR ANDROID DEVELOPMENT.
STEPS:-
1.THINGS NEEDED
2.SETTING UP CYGWIN IN WINDOWS (I am not using cygwin for my development ,although it is setup in my pc.I personally prefer linux)
NOW CYGWIN IS READY TO GET KITCHEN
3.SETTING UP LINUX
i personally recommend linux for kitchen and other android development use.
i use linux lite(based on ubuntu lts release) http://www.linuxliteos.com/
if u want to use ubuntu then i recommend version 10.4 or use kubuntu latest release
instaling linux along with windows is complex and i am not covering that in this guide.
NOW YOUR VIRTUAL MACHINE IS READY TO SETUP KITCHEN
4.SETING UP DISXDA KITCHEN
A] cygwin instructions
B] Linux instructions
NOW YOU HAVE YOUR KITCHEN SETUP FOR USE.
4.USING KITCHEN TO MAKE A ROM
HERE IT IS... YOUR FIRST CUSTOM ROM.:good:
Click to expand...
Click to collapse
hi k2wl,
i also use cygwin+kitchen and have a same file as baffin on home\kitchen\tools\edify_defs, and also do the same steps as you mentioned, but the updater-script is not same as yours. it stuck on boot loop--WO 3G, when i flash my baffin_zip, no samsung arround on the screen.
i upload my updater-script, can you help me check it? what's wrong with it ?
my device : I9082_CU Chinese Unicom mobile, wether i should change the device name to cu_baffin or not ? confused.........
i also can flash your roms based on XXAMCD and ZTAMD1, maybe not the name issue.
help.........

tonylin880806 said:
hi k2wl,
i also use cygwin+kitchen and have a same file as baffin on home\kitchen\tools\edify_defs, and also do the same steps as you mentioned, but the updater-script is not same as yours. it stuck on boot loop--WO 3G, when i flash my baffin_zip, no samsung arround on the screen.
i upload my updater-script, can you help me check it? what's wrong with it ?
my device : I9082_CU Chinese Unicom mobile, wether i should change the device name to cu_baffin or not ? confused.........
i also can flash your roms based on XXAMCD and ZTAMD1, maybe not the name issue.
help.........
Click to expand...
Click to collapse
my friend its a issue of symlinks....
i recommend to use linux+kitchen for perfect rom making....i have faced this for some other device previously and from that time i always use linux for development.
(i have been linux user since 2000...)
install linuxlite/ubuntu/kubuntu in virtual box and put kitchen in it. copy the compatibility file in the fore said folder and and fire up your kitchen. Rest procedure is same.
i am giving u my updater script for your convenience . replace your updater script with this and reflash again.
TELL me the results of reflash!!!
also attach build.prop here ...i wana look at it.

k2wl said:
my friend its a issue of symlinks....
i recommend to use linux+kitchen for perfect rom making....i have faced this for some other device previously and from that time i always use linux for development.
(i have been linux user since 2000...)
install linuxlite/ubuntu/kubuntu in virtual box and put kitchen in it. copy the compatibility file in the fore said folder and and fire up your kitchen. Rest procedure is same.
i am giving u my updater script for your convenience . replace your updater script with this and reflash again.
TELL me the results of reflash!!!
also attach build.prop here ...i wana look at it.
Click to expand...
Click to collapse
hi, k2wl
i have try to use your updater-script to replaced.but also faild....i have wiped all before flash.
the build.prop and boot.img are attached, please check it.
i also unpack the cache.img to the system file, is this the reason why can not flash? because i see nothing csc related files in your roms.
and i will try to build lunix, and do it again.

tonylin880806 said:
hi, k2wl
i have try to use your updater-script to replaced.but also faild....i have wiped all before flash.
the build.prop and boot.img are attached, please check it.
i also unpack the cache.img to the system file, is this the reason why can not flash? because i see nothing csc related files in your roms.
and i will try to build lunix, and do it again.
Click to expand...
Click to collapse
it is not the csc... ur build.prop and boot imgs are ok. do rom building in linux and give me feed back.
if u going to use ubuntu then use HELLS-KITCHEN | Ubuntu-Based | ROM Developing Distro http://forum.xda-developers.com/showthread.php?t=2152398
it already contains kitchen.

awesome guide brother..
Making rom is jst about experience. When a person like you makes rom they keep getting better and better. So rom made by you will be any day better than a first time user.
People should be able to make their own Rom. So that you can focus on development of powerful custom Rom and kernels. Your contributions for sgg are huge...

Just a note, installing linux alongside windows is a very, very simple job. You only need to partition your hard disk to have like a 100GB empty partition, and make an Ubuntu bootable USB using Rufus (Awesome program), and just boot using the USB and follow the steps to install Ubuntu.

@DBZo07
ya basically that is main purpose of this tutorial.

@panda00
or u can use UNetbootin to have bootable linux usb.

k2wl said:
@panda00
or u can use UNetbootin to have bootable linux usb.
Click to expand...
Click to collapse
Yes, Rufus has the same function, but I prefer Rufus, because Rufus is universal (i.e. works with windows ISO as well) and it's portable (no need for an install)

k2wl said:
it is not the csc... ur build.prop and boot imgs are ok. do rom building in linux and give me feed back.
if u going to use ubuntu then use HELLS-KITCHEN | Ubuntu-Based | ROM Developing Distro http://forum.xda-developers.com/showthread.php?t=2152398
it already contains kitchen.
Click to expand...
Click to collapse
finally i have download the big file 1.5G hells-kitchen beta5, work on virtualbox ,but no password to login. confused
what's the passwords?
shall i try to download ubuntu and kitchen.....

tonylin880806 said:
finally i have download the big file 1.5G hells-kitchen beta5, work on virtualbox ,but no password to login. confused
what's the passwords?
shall i try to download ubuntu and kitchen.....
Click to expand...
Click to collapse
password is "p"

This guide helped me to have my own customized rom.. Thanks k2wl for your efforts... Hats off man..
Possible customization were done looking at your rom features and my requirements.
Turned out to be awesome one..
Further, dpi is set to 160 without any single bug.
Battery usage is awesome. Still haven't used your custom kernel, which I don't wanna try for now.
Again, thanks man for this guide finally got perfect awesomeness. Now, I can focus on my exams rather than such hunting around for better.
God bless you.. Later...
Here are screens
{
"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 GT-I9082 using Tapatalk 2

DBZo07 said:
This guide helped me to have my own customized rom.. Thanks k2wl for your efforts... Hats off man..
Possible customization were done looking at your rom features and my requirements.
Turned out to be awesome one..
Further, dpi is set to 160 without any single bug.
Battery usage is awesome. Still haven't used your custom kernel, which I don't wanna try for now.
Again, thanks man for this guide finally got perfect awesomeness. Now, I can focus on my exams rather than such hunting around for better.
God bless you.. Later...
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
hey thanks for those kind words...u r using xperia launcher... does it block ur notifications??? or any other errors u may got???

Nope, no such errors... There was a guy who posted https://www.dropbox.com/s/reyimmczzn7e6nq/Sony_Xperia_Z_Walkman_by_Ravi.zipWalkman + launcher flushable zip which worked well.
Sent from my GT-I9082 using Tapatalk 2

DBZo07 said:
Nope, no such errors... There was a guy who posted https://www.dropbox.com/s/reyimmczzn7e6nq/Sony_Xperia_Z_Walkman_by_Ravi.zipWalkman + launcher flushable zip which worked well.
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
ok i thought that u include in the rom and then install the rom....becoz if u try to include it in rom..it will generally crashes the notifications and many other problems...

[DIY GUIDE] Create a personalized ROM yourself! [UPDATED: 28-07-2014]

Introduction
After releasing my 'Update to .253' thread, I've figured it is something you might want to do your self, maybe because you like to use your own created FTF, or even want to modify your ROM a bit before flashing. This guide will help you through it, as secure and successful as possible!
Anyone can do it!
There is no need to unlock your bootloader to work this guide, however it did help me out of some sticky situations myself, as long as you keep a cool head while working on your ROM, you'll be able to get out of any situation.
The XDA mantra: MAKE BACKUPS!
Before you do anything on your phone, make sure you create a solid backup first. As CWM and TWRP both do not backup your internal storage, create a backup of it's contents too before trying to install your very own ROM.
Prerequisites
Flashtool version 0.9.x.x (the latest) - Windows / Linux / Mac
Needed to flash your phone, also needed to create the FTF bundle. The Linux version is already installed in the VM but you can download any other version too, to do the flashing and FTF building before hand in a desktop enviroment you are accustomed to.
[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool
This thread will help you make an FTF file for your DIY project, as we already have this excelent thread I will save myself the trouble of creating a guide for that
VMWare Player (76Mb) (Free for non-commercial use) and [NUT]'s UbuntuHost VM (Bittorrent: 4.84Gb)
The VM you download is OK to use on any 4.1.2 ROM as base.
If you wish to use a 4.2.2 ROM, you will need the DIYGuide UPDATE PACKAGE 1 (Bittorrent: 169Mb).
If you wish to use a 4.3 or 4.4 ROM, you will be needing DIYGuide UPDATE PACKAGE 2 (Bittorrent: 159Mb). Flashtool however needs to be updated to 0.9.15.0 if you are going to build a 4.4 ROM
See the index below for the link to the guide post that explains how to use it.
This you will need for the tricky bits, as modifying a ROM is safer on a Linux host with less chances of breaking file permissions. As most of the world around us uses Windows, I've created a VM to support you in your tasks. I've installed the Linux tools you need, for me this VM works just fine.
The VM needs about 10Gb space on your pc and you need around 1Gb of free RAM when trying to use it smoothly.
This VM also contains a build script, simple but effective, which will create the (unsigned) flashable zip for you, grabbing all the files it needs along the way and giving you time to edit what ever you want during the building process.
I've made sure you have fastboot and adb commands to be found in the PATH variable, and that the connection to most android phones and tablets will most probably work just fine. You can do adb and fastboot commands to your phone without having them in the directory where you keep the files, easy to use!
The VM has one user, which is called XDA Community. To log in on Ubuntu, use the following credentials:
User: xda
Password: xdauser
This user has SUDO privileges, so expect to type that password again when prompted to do so while installing packages or even when running the rombuilder script.
Download and install WinRAR or 7Zip to be able to unpack my VM.
Included in the ROM you will build using this DIY Guide
Your DIY ROM will be rooted with SuperUser (or SuperSU when you used an update package), including the reboot fix. It will also include XZDualRecovery 2.3 RELEASE (or newer if you used an update package). So you will end up with a cool ROM!
Extra's
You will be able to use my AROMA ROM Mutator package to fix your JB 4.1 ROM if anything might fall to pieces in the future regarding root. You'll also be able to use it to make the switch from SuperUser to SuperSU using the mutator, if you might change your mind in the future.
Guide Index
Chapter 1: Introduction and Prerequisites
Chapter 2: Installing VMWare Player and getting 'UbuntuHost' running
Chapter 3: Preparing the FTF for NOOB use
Chapter 4: Preparing and Extracting the ROM
Chapter 5: Building the (unsigned) flashable ZIP
Chapter 6: Installing your DIY ROM
Addendum: How to replace the recoveries to suit your device
Addendum: How to update your VM
Frequently Asked Questions

Installing VMWare Player and getting 'UbuntuHost' running
I'm assuming you have downloaded the VMWare Player application suitable for your system. Installing it is a basic knowledge to most Windows users, so I'm not going to elaborate on the actual installation.
I'm also assuming you have downloaded the VM. You can now unpack it to your Documents folder.
Now, fire up VMware player and when you see the following...
{
"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"
}
Then click on 'Open a Virtual Machine' and navigate to the folder you just extracted:
Click on the UbuntuHost.vmx and confirm the choice. You'll end up with this view:
Now you can either double click on the name in the list on the left or click play on the right to start it.
Remember, the password is xdauser
NOTE: This Ubuntu has the Unity interface which means, among other things, the menus are moved from the application window to the top bar. Move your mouse over it and the menus will appear.
And you are ready for the next chapter!

Preparing the FTF for NOOB use
Why would you do that? Well... to make sure you won't screw up flashing the wrong bits and make it erase your userdata... better safe then sorry!
This step is actually also needed to unpack the system partition from the FTF you created using the guide I put in the OP.
Copy the FTF you created to the VM by dragging the file in to the VM window. You can see Ubuntu recognizes it as a ZIP, which it essentially is.
Open it by double clicking on it.
Now delete userdata.sin, cache.sin and appslog.sin from it. Then drag system.sin to the DIY Guide folder on the desktop. Once it's unpacked, delete system.sin from the FTF as well.
That was easy, wasn't it? Lets move on to the next chapter.

Preparing and Extracting the ROM
Click on the Terminal icon on the left, type 'cd FlashTool' and then './FlashTool'.
NOTE: Use 'sudo' and your password you used to login to run FlashTool as root if you run in to problems.
In the Tools menu, you can select Sin Editor, select the system.sin in your DIY_Guide folder in your home.
Then click 'Extract data' to start the extraction, now go get a cup of coffee, this might take a while
Once it's done you will end up with a file called 'system.ext4' inside your DIY_Guide directory.
Click Close and close FlashTool using the orange X in the top left corner.
You can rename it to something you like but it should end with '.ext4' to allow the scripts to recognize it. Just open up the DIY Guide folder on the desktop and right click on the system.ext4 file and choose 'Rename'. For purpose of demonstration I renamed mine to 'nuts.ext4'
NOTE: The scripts allow for more then one flashable system to be created, so you can repeat the above multiple times, just remember to rename the system.ext4 to something else, otherwise you'll just end up overwriting the same file over and over again
Because of size considerations, the virtual disk is not really big (10Gb) so you'll run out of space fairly quickly, do not forget to empty the trash after this step!
That's it for this chapter, lets move on!

Building the (unsigned) flashable ZIP
Now we can open the Terminal by clicking on the icon on the left with the '>_' sign in the 'monitor'. Change directory to DIY_Guide and type 'ls -la' to show the following
You can start the build process using the rombuilder script by typing './rombuilder' and it will ask you for your password before it starts.
Once it successfully mounts the system partition it will open it for you. The script will pause for you to complete whatever modifications you want to do to it. Remember the XDA Mantra? Well... a backup would be good to make right now.
If you have more then one system.sin extracted, the above process will repeat itself until it passes all the various .ext4 files it has found.
NOTE: The mounted ext4 image has been mounted as root and as the contents are owned by root, you will need to sudo your actions when modifying the contents!
Tip: To make it easy on yourself you can use the terminal to open a file manager running as root. Type ctrl+shift+t, this will open a new terminal tab. In there type 'sudo nautilus' which starts the file manager again, but with an appropriate warning at the top of the explorer window, that one will be running as root. Be careful, you might wreck your entire VM if you mess things up big!
Once you are finished with the modifications or just enter through to the next bit, it will pack up the system partition and repeat or when done it will continue to create a flashable ZIP for each of the different .ext4 files you created.
You're almost done! Lets move to the next chapter...

Installing your DIY ROM
FOR 4.1.2 ROM's:
Before doing these steps, remember to have any recovery installed on your phone if you are doing this with a locked bootloader, otherwise you won't be able to flash the zip you've built!
Put your '$NAME.flashable.zip' on (the external) SDcard;
Put the 'FTF' inside the FlashTool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash everything in the 'FTF' to your phone and boot the phone straight to recovery after that;
NOTE: If you have an unlocked bootloader, you CAN flash the kernel, but you do not need to, to keep your custom kernel.
Flash '$NAME.flashable.zip' in recovery (Works in both CWM and TWRP!)
Reboot to system without clearing (dalvik-/)cache.
And you're done! :victory:
FOR 4.2.2 AND 4.3 ROM's:
Before doing these steps, remember to have any recovery installed on your phone if you are doing this with a locked bootloader, otherwise you won't be able to flash the zip you've built! You will need XZDualRecovery 2.5 BETA or newer to make this work.
NOTE: This guide assumes you are coming from a 4.1.2 ROM. If you have a 4.2.2 ROM already installed, you can skip this one and use the above guide.
Put your '$NAME.flashable.zip' on (the external) SDcard;
Put the 'FTF' inside the FlashTool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash '$NAME.flashable.zip' in TWRP, then TURN YOUR PHONE OFF AFTERWARDS - DO NOT BOOT IT YET!
Flash everything in the 'FTF' to your phone;
Now boot to system without clearing (dalvik-/)cache.
And you're done! :victory:

Addendum: How to replace the recoveries to suit your device
Download XZDualRecovery specific for your device, the flashable package to be precise.
Drag the file to the VM window and open the zip. You will see 2 folders in there, traverse in to system/bin where you will see the files you need most.
Open the DIY_Guide on the VM's desktop, traverse to updater/system/bin and drag all the files from the zip in to this directory, replacing all the files already in your VM and you are set to go
On the Xperia Z Ultra, Z1 Compact, Z1 and (Tablet) Z2, don't forget to copy the disableric file from the tmp folder inside the recovery zip to the updater/system/xbin folder. Forgetting to do so will cause your system partition to be not fully accessible from the fully booted ROM.
For completeness, you could copy the dr.prop file inside the zip to the updater directory too: this will ensure people downloading your package will know what XZDR version was included.

Addendum: How to update your VM
The update package 1 contains the following:
FlashTool 0.9.11.0
XZDualRecovery 2.5 BETA
The Remount-Reboot fix
Superuser has been replaced by SuperSU
IMPORTANT NOTE: This update makes your flashable ZIP assume you are updating from a 4.1.2 ROM to a 4.2.2 ROM. So the resulting flashable ZIP will move the contents of your internal storage to the new 4.2.2 location. If you are creating a package to go from a 4.2.2 ROM to a 4.2.2 ROM, you will need to edit the updater-script to stop it from doing that
Code:
ui_print(" Moving contents of the internal storage to it's new location...");
ui_print("");
ui_print(" NOTE: This may take a while!");
ui_print("");
run_program("/sbin/busybox", "mv", "/data/media", "/data/temporary");
run_program("/sbin/busybox", "mkdir", "/data/media");
run_program("/sbin/busybox", "mv", "/data/temporary", "/data/media/0");
set_progress(0.850000);
Remove the above portion from updater/META-INF/com/google/android/updater-script using gedit and you're set! :fingers-crossed:
The update package 2 contains the following:
Flashtool 0.9.13.0
SuperSU 1.86
XZDualRecovery 2.7.62.
How to update:
Download the update package from the link in the OP;
Open the Home directory in the VM on the bar on the left;
Drag the file in to the home directory straight from your host PC's location where you stored the downloaded package;
Remove the FlashTool and DYI_Guide folders or rename them (to rename, right click on them to get the menu with the rename option);
Now open the diyvm-update.tar.gz, drag the 2 folders in to the Home directory.
All done! :good:

Frequently Asked Questions
Q: Could I use this for any other Xperia device?
A: Sure you can! The proof is starting to pop up now and then
Just make sure you put in the right recovery pieces to support your specific device
Q: Am I allowed to release my ROM to the public?
A: Of course! I only require a simple mention or a humble thank you in your topic, where ever that may be. I like to know where my work travels to, so post or PM me the links to it
Q: Am I allowed to change the updater script to suit my needs?
A: You are allowed to change whatever you wish, I have NO copyright or license stuck to my work, simply because I consider anything with a license or copyright not to be 100% pure open source.
Q: I would like to make a ROM for my device, but there is no XZDualRecovery for it?
A: Try to integrate a recovery package available for your device. You can of course also request XZDR support, but it can take some time before that happens.
Q: I want to expand the storage capacity of the VM, is there any guide for that?
A: Yes, @gregbradley posted one here.
Q: My VM disk is slowly filling up, while I am keeping the trash empty, how come?
A: @GavTheStoner found out why, read his post on the subject and the solution he found.

Would be very useful! Thank you for the nice and clear guide!
Could you please also provide the script and other files needed such recovery etc. ? The whole VM image is large...

Fishmanzero said:
Would be very useful! Thank you for the nice and clear guide!
Could you please also provide the script and other files needed such recovery etc. ? The whole VM image is large...
Click to expand...
Click to collapse
No
It's not hard to find parts in my releases...
Sent from my C6603 using xda app-developers app

Great guide! Thanks a lot for this!
Gesendet von meinem Xperia Z via Tapatalk

Don't suppose anyone's come up with a way to rebuild to FTF?
Would love to be able to do that and just load with FlashTool.

Johbremat said:
Don't suppose anyone's come up with a way to rebuild to FTF?
Would love to be able to do that and just load with FlashTool.
Click to expand...
Click to collapse
Me too, but unfortunately that's just impossible... Sorry
Sent from my C6603 using xda app-developers app

Great Guide
Thanks for sharing - I was able to create my own deodexed and zipaligned 10.1.1.A.1.307 firmware. I tweaked it a bit so it doesn't reboot when changing system to R/W.
Next I'll try creating one for the Japanese 10.1.D.0.343 build

I was able to create a working 10.1.D.0.343 build for the SO-02E variant using your guide. Is it cool with you if I upload it and share it for our Japanese friends? I'll give you credit of course. :good:

lancebukkake said:
I was able to create a working 10.1.D.0.343 build for the SO-02E variant using your guide. Is it cool with you if I upload it and share it for our Japanese friends? I'll give you credit of course. :good:
Click to expand...
Click to collapse
Of course you can
If I didn't want you to release it to the public I'd have that explicitly stated in the OP ... which I haven't, so go right ahead! :good:
--- ON A DIFFERENT NOTE ---
I'll be updating the VM soon to reflect the changes in the updater script, the remount-reboot fix and the latest XZDualRecovery.
I'll also make a tar archive with a little guide in one of the reserved posts to help you update your VM so you won't have to download it all over again

Thanks!
But its possible to create a ROM out of a CWM Backup on Windows.. I.E. thats more simple
Thanks for the VM though

jader13254 said:
Thanks!
But its possible to create a ROM out of a CWM Backup on Windows.. I.E. thats more simple
Thanks for the VM though
Click to expand...
Click to collapse
I know it is, but that is basically a TAR backup and requires a few extra steps: flashing the FTF to your phone, then booting to recovery to make that backup, dragging that to your PC and stripping the META info from the nandroid backup process adds to the TAR (which makes it a non-standard tar archive!) and you still risk losing all permissions and ownership information on the files inside the archive when extracting that to integrate it in your flashable zip... which is a ZIP and does not know about the extended file permissions and ownership from a Linux system... so you will have to make your updater-script reset permissions or instruct your users to do so using recovery... :silly:
Using this VM and my method of using the SIN file to extract a ROM prevents a huge heap of possible issues and keeps the updater-script nice and small and the installation a breeze

[NUT] said:
I know it is, but that is basically a TAR backup and requires a few extra steps: flashing the FTF to your phone, then booting to recovery to make that backup, dragging that to your PC and stripping the META info from the nandroid backup process adds to the TAR (which makes it a non-standard tar archive!) and you still risk losing all permissions and ownership information on the files inside the archive when extracting that to integrate it in your flashable zip... which is a ZIP and does not know about the extended file permissions and ownership from a Linux system... so you will have to make your updater-script reset permissions or instruct your users to do so using recovery... :silly:
Using this VM and my method of using the SIN file to extract a ROM prevents a huge heap of possible issues and keeps the updater-script nice and small and the installation a breeze
Click to expand...
Click to collapse
I just used a nice tool called "yaffey" which keeps the file structure and I set permissions via updater-script.
Works really fine but may be more difficult
Reall great way though and big thanks for this guide

[LINUX][POSTMARKETOS] Native Linux on the Asus Eee Pad Transformer TF101

Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"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"
}
XFCE
MATE
JWM

Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

Reserved
Reserved

aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)

be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1

Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?

Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.

aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.

Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.

This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.

Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)

Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.

oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated

Awesome work.
Any chance of dual boot?
Thank you

riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)

XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release

Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?

gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.