Database Users

[I9000][Heimdall][Jan.30.2012] Firmware packages for stock ROMs

Heimdall firmware packages for stock GT-I9000 firmwares​
Heimdall 1.3 included support for "Heimdall Firmware Packages," an XML-driven way to define, create, and distribute firmwares. This is a powerful tool for ROM developers, but I haven't seen it being used yet. In order to encourage and support the use of these new firmware packages, I've packaged up a few stock Samsung firmwares for use with Heimdall.
For those that don't know, Heimdall is an open-source, cross-platform tool written by Benjamin Dobell which can flash complete ROMs, kernels, modems, etc to Samsung Galaxy S devices. It's preferable over Odin as its source code is open and it is therefore undergoing public development, and we can review the code. In comparison, Odin is a closed-source, Windows-only internal Samsung utility, and what we know very little about it.
Downloads​
These are stock ROMs, just as you'd find on Samfirmware or wherever else. I have not modified them other than unpacking and repacking for flashing with Heimdall (meaning they are odexed). If the upstream firmware includes bootloaders, I've included them*. I'll do my best to indicate additional information next to each ROM.
Gingerbread:
XXJVQ (2.3.4): MultiUpload
XXJVR (2.3.4): MultiUpload
XXJVS (2.3.5): MultiUpload / BayFiles
XXJVT (2.3.5): MultiUpload
XWJVZ (2.3.6): MultiUpload, BayFiles / MediaFire (md5sum: dbfcb621f666b224751a3bd2bf9abbba)
XXJVU (2.3.6): BayFiles (md5sum: ede04385b889651c31ce669044ec5ee6)
*Note: Even though I've included bootloaders you'll be able to remove them in Heimdall's GUI right before flashing if you so please.
Froyo:
XWJSD (2.2.1): MirrorCreator - thanks Motthat
Credits...​
Thanks to Benjamin Dobell for writing Heimdall. Thanks to [Ramad] for the idea of listing unadulterated stock ROMs. Thanks to Supercurio for being a role model of openness and transparency. We need more pro-community devs.

Flashing instructions
Flashing instructions​
Make sure you've installed Heimdall version 1.3 or higher. Do not unzip the firmware package, we open it up directly in the heimdall frontend graphical user interface! This procedure will wipe your device and you will lose all your installed applications.
Step 1: Open Heimdall's frontend (heimdall-frontend on Linux)
Step 2: Load the downloaded tar.gz into Heimdall
{
"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"
}
Step 3: Press "Load / Customize"
Step 4: Reboot your phone in Download mode and connect it to your computer
Step 5 (optional): Customize the installation before flashing by removing or adding different files (such as pre-rooted kernels or different modems)
Step 6: Press "Start"
Your phone will begin to flash and then reboot.

Reserved...

It's great to see some Heimdall Firmware Packages for the GT-I9000. The instructions and screenshots you've included should make it super easy for beginners to get going. Keep up the good work!

I put together an XWJSD package (latest 2.2.1 firmware) which you're welcome to add to the collection. http://mir.cr/0XZMZGFA

Mothatt said:
I put together an XWJSD package (latest 2.2.1 firmware) which you're welcome to add to the collection. http://mir.cr/0XZMZGFA
Click to expand...
Click to collapse
Ok, cool. I thought it might be useful to have some Froyo packages around. I've added it, thanks!

You are both legendy legends from the land of the legendary legend people! I was beginning to get beside myself with frustration - no matter how hard I tried I simply couldn't get kies/samsung drivers installed ON ANYTHING - I tried about 4 different Win7 x64 machines, a 2008R2 and even a Vista x86 and NONE of them would get me a working install. I inherently mistrust odin and when I saw heimdall (so I could run it on Linux) I was just over the moon. Not having any heimdall-native packages though, I got pretty frustrated and ended up soft-bricking my phone at about 2am this morning . So after arriving after a long day at work I was very happy to see some packages finally get released and what's more - my phone was back up and running from the death-screen in under 10 minutes!
So now I can experiment with lots of funky ROMs and I know I'll always be able to get my I9000 back again!
You both rock.
A

AntonDreams said:
You are both legendy legends from the land of the legendary legend people! I was beginning to get beside myself with frustration - no matter how hard I tried I simply couldn't get kies/samsung drivers installed ON ANYTHING - I tried about 4 different Win7 x64 machines, a 2008R2 and even a Vista x86 and NONE of them would get me a working install. I inherently mistrust odin and when I saw heimdall (so I could run it on Linux) I was just over the moon. Not having any heimdall-native packages though, I got pretty frustrated and ended up soft-bricking my phone at about 2am this morning . So after arriving after a long day at work I was very happy to see some packages finally get released and what's more - my phone was back up and running from the death-screen in under 10 minutes!
So now I can experiment with lots of funky ROMs and I know I'll always be able to get my I9000 back again!
You both rock.
A
Click to expand...
Click to collapse
Yes, we're really lucky that this phone is so robust and the bootloaders are open. As long as download mode is working you can resurrect your phone (and even sometimes when download mode isn't working)!

Thanks for these man, it really is the best way to flash everything, pity it isn't as widely used as it should be! Keep it up

First of all thank you!
Kies for Mac was really harassing me for such a long time nor I could using Odin on Parallels.
After playing with some roms and messing up my device (Samsung Galaxy S)I was happy to come back to an official release.
Your guide to Heimdall was simply great.
Now that I'm on Gingerbread JVR 2.3.4 I wanted to root my phone.
Here I found CF-Root and I downaloaded the zip file for my firmware (JVR)
http://forum.xda-developers.com/showthread.php?t=788108
The file is zip and when you unpack you get a Zimage file.
I'm using Heimdall fronted 1.3.0 how can I flash this file in order to toot my phone ?

Realy glad that you let us take one more step to the use of Heimdall.
Is this JVR rom NEE/XEE csc compatible?
Don't want to screw up to KOR again

zidz said:
Realy glad that you let us take one more step to the use of Heimdall.
Is this JVR rom NEE/XEE csc compatible?
Don't want to screw up to KOR again
Click to expand...
Click to collapse
I'm not sure... I've never bothered to figure out what the deal with CSCs is. I downloaded XXJVR from samfirmware, does that help ?

aorth said:
I'm not sure... I've never bothered to figure out what the deal with CSCs is. I downloaded XXJVR from samfirmware, does that help ?
Click to expand...
Click to collapse
I've downloaded it from SamFirmware, that one is a KOR one :/

enomis74 said:
Your guide to Heimdall was simply great.
Now that I'm on Gingerbread JVR 2.3.4 I wanted to root my phone.
Here I found CF-Root and I downaloaded the zip file for my firmware (JVR)
http://forum.xda-developers.com/showthread.php?t=788108
The file is zip and when you unpack you get a Zimage file.
I'm using Heimdall fronted 1.3.0 how can I flash this file in order to toot my phone ?
Click to expand...
Click to collapse
Anyone?????

jaystarrr said:
Anyone?????
Click to expand...
Click to collapse
On the flash page add the pit file then Click the Add Button under Partition (Files) Section. Choose Kernel from the Partition Name dropdown box, then click browse and select the zImage file.

Error loading firmware tar.gz file
Hi,
Do you know what can be this error, i installed heimdall and frontend, downloaded tar.gz files from this post, and i get "Failed to open package:
/home/jtextori/Téléchargements/XXJVQ_heimdall.tar.gz" ??
Thanks

If you root it you must reflash the orginal KERNEL

Don't know if it is what you mean, but moving the file into a directory without accentuated characters allowed to load the file into heimdall-frontend ! it was that simple !

Thx soo much for the job! and also thx for the heimdall developper. happy to can do a flash to my galaxy phone from my mac.

jtextori said:
Hi,
Do you know what can be this error, i installed heimdall and frontend, downloaded tar.gz files from this post, and i get "Failed to open package:
/home/jtextori/Téléchargements/XXJVQ_heimdall.tar.gz" ??
Thanks
Click to expand...
Click to collapse
maybe the file are bad downloaded and are bad. my md5 is: 502288c2261cdfbe41ce401128cffb27
and the file size are 259.060.144 bytes (259,1 MB)

[GUIDE] Rooting s3 mini from Linux with heimdall

Hey.
Just wanted to share my rooting experience.
My girlfriend just bought her S3 mini few days ago - and because Samsung Dive sucks balls (can be erased by doing factory reset), I felt the need to root, so cerberus anti-theft (http://cerberusapp.com, try it out, its awesome) could be written to /system (which requires root & survives factory resets).
Because I use Ubuntu Linux, I couldn't use Odin. Also from what I've read Odin reflashes whole phone, including bootloaders, recovery images and so on.
Because I've had XXALJL build originally in my phone, I've used this uk rooted rom as my rooting source.
Also, because the baseband is identical, I only flashed the system image, where /system/bin/su resides.
If you have a different baseband than your rooted image, this guide will not help you and you probably need to either: a) use odin to reflash everything. b) use your brain to figure your what to flash and where.
So here we go!
Flashing
I'm using ubuntu 12.10, 64 bit:
Code:
[email protected]:~/Downloads/rooted# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=quantal
DISTRIB_DESCRIPTION="Ubuntu 12.10"
Code:
[email protected]:~/Downloads/rooted# uname -a
Linux cyrix 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
The only thing you should be concerned about is whether you're using 32 or 64 bit OS.
I've used heimdall 1.3.1, because 1.3.2 has issues and I didn't want to risk. Perhaps 1.3.2 or 1.4-RC1 would work just fine too, but I've used 1.3.1 and that did work for me.
Get heimdall 1.3.1 from http://www.glassechidna.com.au/products/heimdall/ (choose 32 bit (i386) or 64 bit (x64) debian package appropriately). Install those. And lets get down to bussiness.
I RECOMMEND RUNNING ALL COMMANDS FROM ROOT USER
Some guides recommend rebooting your pc after heimdall install (it inserts some udev rules). I didn't do that (completely forgot), but do it, just to be on a safe side.
So first step is to determine what partition identifier does your system partition has. Put your device into download mode (power off. Then hold vol down + home + power & click vol up once).
After doing that, connect your usb cable to computer and run:
Code:
# heimdall detect
It should say:
Code:
Device detected
If it doesn't - none of the following commands will probably work.
Then - lets see what our PIT (partition information table? not sure about the acronym) looks like:
Code:
# heimdall print-pit
What we are looking for is system partition. Mine looked like this:
Code:
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
From this we can see that our partition identifier is 20.
So extract the downloaded .rar ROM file, then again, extract rooted.tar and go into that directory. And lets flash our system image (around 900mb).
If everything is fine it should look like this:
Code:
[email protected]:~/Downloads/rooted# heimdall flash --20 system.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading SYSTEM
100%
SYSTEM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Do not touch your PC while flashing. Do not move the phone. Do not fiddle with the cables. Hold your breath and wait. If all is fine, the phone should turn off itself. Wait until you get charging screen, then turn it back on.
You should have supersu installed. You can also install terminal emulator and try running su to make sure you have the root.
Congrats on having root!

Great tutorial! Thanks a lot, from a fellow Linux user!

Hi dudes,
I have mi SGS2 soft bricked and I'm trying to recover it.
I've already opened a post here.
The thing is that I have discovered Heimdall by chance.
Fed up with the errors from Odin I decided to try in Linux.
I think my System partition is missing.
Find attached my result for heimdall print-pit.
Hope you can help me.
Regards,
Mario.

thanks for remaind me about heimdall, that was long time since heard about this tool. :beer:

Thanks! (But should I backup something first?)
Thanks, exactly what I was looking for
One quick question: by rooting with Heimdall (on Linux), will I loose all my apps/accounts ? (It will take ages to recover them all..)
(also, where could I get updated as new Heimdall-friendly firmwares become available?)
Thank you again for your time.
arturaz said:
Hey.
Just wanted to share my rooting experience.
My girlfriend just bought her S3 mini few days ago - and because Samsung Dive sucks balls (can be erased by doing factory reset), I felt the need to root, so cerberus anti-theft (http://cerberusapp.com, try it out, its awesome) could be written to /system (which requires root & survives factory resets).
Because I use Ubuntu Linux, I couldn't use Odin. Also from what I've read Odin reflashes whole phone, including bootloaders, recovery images and so on.
Because I've had XXALJL build originally in my phone, I've used this uk rooted rom as my rooting source.
Also, because the baseband is identical, I only flashed the system image, where /system/bin/su resides.
If you have a different baseband than your rooted image, this guide will not help you and you probably need to either: a) use odin to reflash everything. b) use your brain to figure your what to flash and where.
So here we go!
Flashing
I'm using ubuntu 12.10, 64 bit:
Code:
[email protected]:~/Downloads/rooted# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=quantal
DISTRIB_DESCRIPTION="Ubuntu 12.10"
Code:
[email protected]:~/Downloads/rooted# uname -a
Linux cyrix 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
The only thing you should be concerned about is whether you're using 32 or 64 bit OS.
I've used heimdall 1.3.1, because 1.3.2 has issues and I didn't want to risk. Perhaps 1.3.2 or 1.4-RC1 would work just fine too, but I've used 1.3.1 and that did work for me.
Get heimdall 1.3.1 from http://www.glassechidna.com.au/products/heimdall/ (choose 32 bit (i386) or 64 bit (x64) debian package appropriately). Install those. And lets get down to bussiness.
I RECOMMEND RUNNING ALL COMMANDS FROM ROOT USER
Some guides recommend rebooting your pc after heimdall install (it inserts some udev rules). I didn't do that (completely forgot), but do it, just to be on a safe side.
So first step is to determine what partition identifier does your system partition has. Put your device into download mode (power off. Then hold vol down + home + power & click vol up once).
After doing that, connect your usb cable to computer and run:
Code:
# heimdall detect
It should say:
Code:
Device detected
If it doesn't - none of the following commands will probably work.
Then - lets see what our PIT (partition information table? not sure about the acronym) looks like:
Code:
# heimdall print-pit
What we are looking for is system partition. Mine looked like this:
Code:
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
From this we can see that our partition identifier is 20.
So extract the downloaded .rar ROM file, then again, extract rooted.tar and go into that directory. And lets flash our system image (around 900mb).
If everything is fine it should look like this:
Code:
[email protected]:~/Downloads/rooted# heimdall flash --20 system.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Uploading SYSTEM
100%
SYSTEM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Do not touch your PC while flashing. Do not move the phone. Do not fiddle with the cables. Hold your breath and wait. If all is fine, the phone should turn off itself. Wait until you get charging screen, then turn it back on.
You should have supersu installed. You can also install terminal emulator and try running su to make sure you have the root.
Congrats on having root!
Click to expand...
Click to collapse

pminervini said:
Thanks, exactly what I was looking for
One quick question: by rooting with Heimdall (on Linux), will I loose all my apps/accounts ? (It will take ages to recover them all..)
(also, where could I get updated as new Heimdall-friendly firmwares become available?)
Thank you again for your time.
Click to expand...
Click to collapse
This only rewrites /system partition, while all your apps/accounts are stored in /data. So in theory you shouldn't lose things. However I do recommend you always backup your stuff with `adb backup` before doing this. You can never be too sure.
As for new firmwares - no idea. OTAs should probably work.

Thanks For the other Debian guys out there, I've just found out "adb" comes available for Sid ( packages debian org /sid/android-tools-adb -- there is a similar package in the Ubuntu repos) and requires MTP mode with USB debug on: bernaerts dyndns org /linux/245-ubuntu-precise-install-android-sdk
While the backup goes on (I'm doing "adb backup -apk -shared -all -f 08062013.ab", hope it's right), I'm looking for the right image file.
May this one fit? "Android 4.1.2 XXAMD3 official firmware"
www hotfile com /dl/209515302/bd1d1a3/I8190XXAMD3_I8190OXAAMD3_DBT.zip.html
UPDATE: no it's not, i should look for something fitting GT-I8190N; checking what I can do from OTA..
UPDATE 2: I've found this file: GT-I8190N-BTU-I8190NXXALL6-1356151513.rar ; I'm going to try to push its system.img with heimdall *crossed fingers*
Thank you again for all your help, you're awesome!
arturaz said:
This only rewrites /system partition, while all your apps/accounts are stored in /data. So in theory you shouldn't lose things. However I do recommend you always backup your stuff with `adb backup` before doing this. You can never be too sure.
As for new firmwares - no idea. OTAs should probably work.
Click to expand...
Click to collapse

After a weekend trying to revive the I8190N (at least it was raining..) I tried to sum up my problem with Heimdall here:
forum xda-developers com/showthread.php?t=2317198
pminervini said:
Thanks For the other Debian guys out there, I've just found out "adb" comes available for Sid ( packages debian org /sid/android-tools-adb -- there is a similar package in the Ubuntu repos) and requires MTP mode with USB debug on: bernaerts dyndns org /linux/245-ubuntu-precise-install-android-sdk
While the backup goes on (I'm doing "adb backup -apk -shared -all -f 08062013.ab", hope it's right), I'm looking for the right image file.
May this one fit? "Android 4.1.2 XXAMD3 official firmware"
www hotfile com /dl/209515302/bd1d1a3/I8190XXAMD3_I8190OXAAMD3_DBT.zip.html
UPDATE: no it's not, i should look for something fitting GT-I8190N; checking what I can do from OTA..
UPDATE 2: I've found this file: GT-I8190N-BTU-I8190NXXALL6-1356151513.rar ; I'm going to try to push its system.img with heimdall *crossed fingers*
Thank you again for all your help, you're awesome!
Click to expand...
Click to collapse

Is there any way to make Phone to original Samsung phone with heimdall? Unroot, Stockrecovery etc?

arturaz said:
Just wanted to share my rooting experience....
Click to expand...
Click to collapse
Thank you, arturaz!
Why did I waste so much of my valuable lifetime by trying to get Odin to work on XP/W7 in a VBox?
Gonna donate to Benjamin now. He really deserves a beer or two
BTW: heimdall can be found in the Debian testing branch now. Look out for "heimdall-flash" (Don't be confused by some "heimdal"-packages [only one 'L'], which are something completely different)

Hey I'm using Linux Mint 32bits, I wonder if I can use the ubuntu 32 version for the software Heimdall ? if so, which one ?
Thanks

I'm not sure I understand the question.

Hello,
lov8 said:
Hey I'm using Linux Mint 32bits, I wonder if I can use the ubuntu 32 version for the software Heimdall ?
Click to expand...
Click to collapse
because linux mint and fork ubuntu I would say yes
lov8 said:
if so, which one ?
Click to expand...
Click to collapse
????

Fred6681 said:
Hello,
????
Click to expand...
Click to collapse
Ah! I have the version 1.4 RC1 from the Linux mint repository. I hope this version is stable enough. I will give it a try in a few days .. :-/

Alternatively you can root your phone by flashing a custom recovery using heimdall, then going in recovery mode and installing supersu.
Tested with heimdall 1.40 and TWRP custom recovery, worked fine.
You have just to pay attention and find the right partition id for flashing "recovery.img".

Why no solution to "Device not detected" ?!
Im using Ubuntu 13.10 64, the S3 Mini is in download mode but not seen by Heimdall... any solutions?
Thanks

ateap0tist said:
Why no solution to "Device not detected" ?!
Im using Ubuntu 13.10 64, the S3 Mini is in download mode but not seen by Heimdall... any solutions?
Thanks
Click to expand...
Click to collapse
Which version of heimdall are you using?

Clostry said:
Which version of heimdall are you using?
Click to expand...
Click to collapse
Heimdall v. 1.4

Can you post the output of this commands? With phone in download mode attached ofc.
Code:
lsusb
heimdall detect --usb-log-level debug

heimdall tar gz error
When I try to load the system.img file (from cm10.2_golden.maclaw.20140118.ODIN_TWRP.tar.md5) from heimdall, before beginning to flash, I get the following error: Tar header contained an invalid file size.
I tried to load the uncopressed file too, then the file cm10.2_golden.maclaw.20140119.zip not for odin and I get the same error, what am I doing of wrong?
Thanks

[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

One Plus One Toolkit v1.2b + ADB/python library - OSX, Linux, and Windows!

i present to you the latest STABLE release from vvn's secret underground laboratory.......
THE HALF-ASSED ONE PLUS ONE TOOLKIT v1.2b!
UPDATED!!! LATEST RELEASE: August 24, 2014
{
"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"
}
i'm copying and pasting from the thread i have on the oneplus one forum because i am lazy and i already worked hard enough coding the damn thing read on for changes/updates/fixes, or check out the README file which is also the changelog!
LATEST UPDATE RELEASED (cumulative v1.1 and v1.2b update since oneplus decided to release 33R so damn fast)!
TOOLKIT SOURCE CODE/PYTHON SCRIPT:
http://pastebin.com/y511TjV1 -or- http://notworth.it/opo/opotoolkit.py
PYADB LIBRARY SOURCE CODE:
http://pastebin.com/7VSpinAz -or- http://notworth.it/opo/pyadb.py
README FILE:
http://notworth.it/opo/README
download ZIP file containing scripts and adb/fastboot binaries:
http://notworth.it/opo/1plus1-halfassedtoolkit_v1.2b.zip
SHA1: eb2ddd5eeddd51cbc863100422ffa84bfb568a8e
same ZIP above PLUS a few useful apps:
http://notworth.it/opo/1plus1-halfassedtoolkit_v1.2b-withapps.zip
SHA1: 6528af01ce50e544f5b1c143659f0ef357b0895b
##################################################################
HALF-ASSED ONEPLUS ONE TOOLKIT v1.2b
BY vvn (eudemonics on xda-developers)
release date: AUGUST 24, 2014
##################################################################
PASTED FROM README FILE:
this is a very half-assed project, as you can guess from the name, and i cannot guarantee fast or frequent updates.
REQUIREMENTS FOR SCRIPT TO WORK:
* opotoolkit.py is the main script. that's the one file you REALLY need.
- get it here: http://pastebin.com/y511TjV1 -or- here: http://notworth.it/opo/opotoolkit.py
* my PYADB library needs to be in the same directory as filename "pyadb.py".
- get it here: http://pastebin.com/7VSpinAz -or- here: http://notworth.it/opo/pyadb.py
* obviously, you'll need python 2.7. download python here: https://www.python.org/downloads/
* you need ADB and FASTBOOT from the android SDK. download the SDK here: https://developer.android.com/sdk/
* finally, you need an OS that supports Python and the android SDK, which I'm afraid narrows it down to:
- Linux (all flavors)
- Mac OSX (exotic jungle cats and beyond)
- Windows (pretty much all releases, or starting from whichever one could support Python.)
i apologize for limiting your options like that.
you can either put the scripts and other files in the same directory as your android SDK,
or set an environmental path variable for your android SDK directory.
##################################################################
USE AT YOUR OWN RISK. i am not responsible for any damage to your device.
i have tested every function except the unlock bootloader and sync functions.
everything works except the uninstall APK function, but i think i just don't quite understand the adb command.
to report bugs, ask questions, offer suggestions, explain the adb uninstall and sync functions(?!), ***** at me, propose marriage, or send anonymous death threats, email me: vvn (at) eudemonics (dot) org
feel free to share, modify, whatever.
some credit would be nice but it's not a big deal if you don't. donations are super nice.
but buying & sharing my EP would be the most awesome way to show your appreciation. really, it would mean the world to me.
you can stream and buy the EP at: http://dreamcorp.bandcamp.com or any major online music retailer (itunes, google play, amazon, spotify, cdbaby, etc.) - just search for "the dream corporation" and album title "last night on earth"
follow on facebook: http://www.facebook.com/dreamcorporation
and of course, more music on soundcloud: http://www.soundcloud.com/dreamcorp
##################################################################
CHANGES IN v1.2B (released same day as v1.1):
new SuperSU binary - we are now on v2.02! many thanks to chainfire for the development and maintenance of SuperSU. also updated the TWRP image, which is bacon 2.7.1 or 2.7.1.1 i believe.... it's the one that's about 12mb. the 15mb version was the one that was giving me the problems i complain about below.
also added some more flashing options and made the sideload/install from device/fastboot options a bit more flexible instead of always following the same path.
probably not even noticeable to most people, but for some reason TWRP hasn't been behaving all the time, especially with installing the SuperSU binaries for rooting. so instead of TWRP or stock recovery being the only options, i added ClockworkMod and Philz as options to whatever functions (flash and sideload) that use a custom recovery and were previously only able to use TWRP. i've tested rooting with the towelroot method on my samsung galaxy note 3 and it works perfectly, doesn't even trigger the knox 0x1 bit (as long as firmware is NE6 or earlier) and no reboot required. towelroot will not work for the oneplus one though - i tested the latest superSU (2.02) update on the OPO's latest update (33R) and it flashes successfully through Philz Recovery.
developing and running the script primarily on a Macbook Pro OSX 10.8 with Python 2.7.x, though sometimes i work on it in a Linux Debian environment. i have no clue how this script will run in Python 3, i could try it and find out, but i just don't care.
also new - check out the sweet ASCII art i added (even in oneplus' signature colors)! since it's the first thing you see when you run the script, you probably can't miss it. added because, obviously, it's an absolute REQUIREMENT that every terminal application (at least, the ones that matter) include some uber leet ASCII. like, the functionality doesn't even matter. handling exceptions doesn't matter (i don't do much of that here, by the way). all that matters is whether or not you have ASCII art, and how uberleet it is. otherwise, nobody will give a **** about you or your app. (at least, that's what i was told. mommy????)
in a future release there will be more functionality for other phones. i plan to add a script for deodexing, and maybe if i am not too tired i'll create a stock ROM with root already injected into it.
my github repository is still being a jerk and won't let me commit anything. sorry. keep checking my pastebin until then to get the latest updates:
http://pastebin.com/u/eudemonics
there might be some errors. i don't know. i thought i fixed the ones i came across. i really need sleep.
##################################################################
CHANGES IN v1.1:
- most files in script can be downloaded directly from script by demand to proper location, making it an easier install and a more seamless user experience
- added support and files for latest updates: XNPH33R released 8/22/2014, and XNPH30O updates #1 and #2
- can now flash entire factory stock ROMs - full XNPH30O and XNPH25R stock images - or flash your own custom ROM
- updated PYADB library to return STDOUT response instead of just a '0' success or error if not 0.
- reboot functions should behave a bit more sanely now that the piped STDOUT response can be used as qualifiers
- added more details and instructions in certain procedures, especially those having to do with booting into recovery.
- several root options available now: superSU is recommended for OnePlus One. TowelRoot is recommended for Android firmware releases earlier than June 2014. I also included a "superuser" zip file which is also supposed to be for rooting, but unless you are well acquainted with what it does, which devices it supports, and what to do with it, I would advise you not to try flashing it.
- i shuffled a lot of items around, it's very likely that there may be some syntax errors floating around. Please report any errors you come across to me at vvn (at) eudemonics (dot) org. thanks!!
~*~
NOTES FROM RELEASE v1.0:
MORE UNIVERSAL FEATURES TO SUPPORT ALL ANDROID DEVICES!
added a bunch of features to the pyadb python library, as well as including them in the toolkit. if there are any features you'd like to see in the toolkit, whether for the oneplus one or for android devices in general, please let me know and if it's possible, i'll add it! wiping and flashing options work now - you can choose the specific partitions you want to wipe, or flash everything back at once. i have also added the towelroot option, which should work on quite a few android devices as long as they are running firmware released before june 2014. also included a few APK's in the package that aren't available from the google play store, so you can install 'em if you want. tested most functions on my macbook pro (running OSX mountain lion) and they all seem to be working, except the uninstall APK function, but it's not a problem with the code, it's my failure to grasp what the <package> parameters should be. also, the latest OTA updates (30O) aren't installing from the fastboot update method, so i've added other options to install them such as ADB sideload and through custom recovery. i haven't tested the sync, wipe, restore, or unlock bootloader functions yet. they should all be working though, except maybe the sync (as i don't completely understand the ADB command myself. i just know the sync command alone without any args syncs your device's /system and /data directories).
one thing that may or may not work sometimes is running the reboot function from the toolkit while you're in recovery mode. i'm not sure if it's even possible to send a command from the computer to make it reboot while in recovery mode, though it shows up under "adb devices" as device type "recovery". i've added to the dialogue of the script directions to carry out certain functions from the device, such as rebooting from recovery back into android. also, the latest OTA updates (30O) *might* not install from the fastboot update method, so i've added both the ADB sideload method as well as installing updates from a custom recovery.
USE AT YOUR OWN RISK. i'm not responsible for anything that might happen to your device as a result of using the toolkit. if you use the correct files in the package and follow the toolkit directions onscreen, your device should be just fine. i assume if you have the technical know-how to install python, the android SDK, and run the script, then you've got a pretty good idea of what you're doing already. if you need help, send me a message. the best way to reach me, to get the quickest response, is probably on facebook, as i do not log onto xda-developers or my email accounts regularly:
http://www.facebook.com/dreamcorporation
requirements: python 2.7, android SDK, opotoolkit.py, pyadb.py
you can either supply the files referenced in the script, or download them from my site. links are in the opotoolkit.py source code pastebin link.
opotoolkit.py source code: http://pastebin.com/ciAj8NJy | download: http://notworth.it/opo/opotoolkit.py
pyadb.py source code: http://pastebin.com/g2Z08JN1 | download: http://notworth.it/opo/pyadb.py
for your convenience, i put together a ZIP file with most of the files you need - scripts, superSU, recovery images, apps, adb/fastboot binaries, etc. all that's missing are the stock images referenced in option #8.
download package here: http://notworth.it/opo/android-1plus1-halfassedtoolkit_v1.zip
there are also a couple large ZIP files available if you want to use the flash stock images functions in option #8 - links are in the source code for opotoolkit.py. or you can just download the XNPH25R stock firmware file from the official cyanogenmod page and unzip the contents into a subdirectory called "XNPH25R" of the script location, and the OTA updates for XNPH30R can be placed into another subdirectory of the script location called "XNPH30O". i will eventually add the functionality to download all the files directly from the toolkit itself, to make it easier for you guys so you don't have to scramble all over the place downloading and collecting files.
any APK's you'd like to install from the toolkit to the phone should go into the /apps subdirectory (already included in the ZIP package file along with a few apps). i have created the github repository for the project, but github is still refusing to acknowledge its existence on the web. once i get it sorted out i'll add a git link. keep checking this space as well as the pastebin links for any updates!
##################################################################
installation:
download and install python 2.7: https://www.python.org/downloads/
download and install android SDK: https://developer.android.com/sdk/
download toolkit package: http://notworth.it/opo/android-1plus1-halfassedtoolkit_v1.zip
-or-
download the python scripts/copy + paste source code from pastebin links into a text editor:
opotoolkit.py source - http://pastebin.com/ciAj8NJy | download: http://notworth.it/opo/opotoolkit.py
pyadb.py source - http://pastebin.com/g2Z08JN1 | download: http://notworth.it/opo/pyadb.py
extract files from the ZIP package or save the *.py scripts to a new directory, "opotoolkit" or whatever you want to name it.
it should work with the adb and fastboot binaries provided in the ZIP, but if not, you should install the android SDK. i recommend even MORE that you create an environmental path variable to the android SDK so you can run the commands from any directory.
setting up an environmental path variable (optional - recommended):
if you're on windows you can go to my pastebin, find the only powershell script on there, and steal/adapt the code to create your own environment path variable. but it's much easier to configure in system properties - i'm not on windows right now so these may not be exact instructions, but you should be able to right click on "my computer", select "properties", go to the "environment" tab in system settings, and add the environment path there. linux and OSX users just need to add the android SDK directory to their ~/.bash_profile or ~/.bashsrc or wherever environment paths are defined. if you still don't understand environmental path variables or symbolic links, i highly recommend google (or startpage.com, the private version).
if you don't want to go to the trouble of creating the environmental path variables, and you want to use the android SDK on your computer, then just extract all the files from the ZIP into your android SDK directory.
##################################################################
how to run the toolkit:
plug phone to computer via USB, turn on android debugging.
open command prompt or terminal window to scripts directory. start toolkit by entering:
"python opotoolkit.py"
if everything is installed and in the right places, you should see a menu like the attached screenshot. if for some reason you get a permission denied error, try launching the command prompt or terminal as administrator or superuser.
i'll continue working on it and adding more when i can so keep checking this space. everything's open source; use, share, steal whatever you want from the code. some credit would be nice, though.
you can use the pyadb.py library to incorporate adb/fastboot commands into your own python projects. i'll be adding more features to that, but for now most of the common features are covered.
here's the github link - it still won't acknowledge my repository exists, and if i try to create it again locally it gives me a fatal error. so it's not letting me add or commit any files, since it says the repository doesn't exist - though trying to create the repository gives me the warning that it already exists. [[email protected]#[email protected]#] let's just say github and i are not exactly BFF's.
project github home whenever it decides to start working: https://github.com/eudemonics/1plus1toolkit
i've been working to expand this so it can be used with all android devices, though it'll require people to supply their own device files to use with it! just because the toolkit can flash device firmware DOES NOT MEAN that the included files meant for the oneplus one will work on a NON oneplus one device! hopefully that's not something i needed to emphasize. if there is enough positive feedback and support i'll create a GUI since people like to click things more than type into a terminal window
my half-assed oneplus one toolkit was featured on cyberwarzone!
http://cyberwarzone.com/android-toolkit-python-2-7/
not gonna bug you for donations - all my code is open source - if you'd like to donate, please do so by purchasing my EP. hey, you might even like the music, too:
buy it here: http://dreamcorp.bandcamp.com
or search for it on itunes, google play, amazon, spotify, last.fm, cdbaby, and so on.
there are also links in the description for my video:
https://www.youtube.com/watch?v=2i-F4jiKtGg
##################################################################
special thanks to chainfire for superSU, cyanogenmod for CM11S, geohot for the towelroot exploit, oneplus for manufacturing such an excellent and affordable product, and everyone here on xda-developers for growing and developing the android community into the vital and creative force it is today!
XDA:DevDB Information
Half-Assed One Plus One Toolkit v1 in Python/ADB-python library - ALL OS' SUPPORTED!, Tool/Utility for the ONEPLUS ONE
Contributors
eudemonics
Version Information
Status: Stable
Current Stable Version: 1.2b STABLE
Stable Release Date: 2014-08-24
Current Beta Version: 1.2.3 BETA BLOCKERS
Beta Release Date: 2014-08-22
Created 2014-08-18
Last Updated 2014-08-25

Reserved

Reserved

How to create custom EDL packages?

I have an interest in creating some custom EDL packages for personal use, to automate a few things and just generally make things easier. Like modem packages, bootstack packages, etc. Can someone point out some tutorials that outline things like:
1. Structure of an EDL and the meanings of the files and what they do (ex. firehose file, gpt***, rawprogram***, etc)
2. Utilities for packaging an EDL
3. Anything else I can't think of offhand
I know that many of the files in an EDL are nothing more than raw partition images that are to be written to a corresponding partition on the device, other files are partition layout/size files, and others provide instructions for the EDL flashing program to execute.
I already have some experience in how to create zip packages that are flash able in TWRP, as well as experience with Linux commands and scripting, so that should prove useful as well.
Thanks!

I've been experimenting with my current Edls. (ones I have downloaded not my own)
Changing boot.img and splash.img etc.
There are various tools on the net to modify the img, extract and repack img files if your into modifications to the img?
I'm not 100% sure however I think the Edl is created via twrp of your current setup. (backup files) (Please correct me if I'm wrong)
If I understand correctly,
Firehose is an exploit used to access the phones root directory. (again please correct me if I'm wrong)
I've had to modify firehose in some cases for it to work. (Causes error if incorrect)
You should be able to pack with WinZip or winrar if using Windows, I'm not sure with Linux tho.

@Syberclone: Well, like I said, they are mostly just raw partition images that correspond to partitions on the device. Like for example, boot.img is boot partition, recovery.img is recovery partition, etc. As far as modding a boot.img, there is Android Image Kitchen, which runs on Android, Windows, and Linux, maybe Mac too. There are surely also tools out there that can create/modify TWRP images, but I'm not aware of any by name. However, neither of those has anything to do with creating an EDL.
I have seen a feature in @Oki's Oreo TWRP that can back up the bootstack/firmware into an EDL, but there must be PC tools out there for this.
It's my understanding that firehose is the binary/executable programmer file that the EDL flasher tool (MiFlash/A7 EDL Tool, DFU MultiDL Tool, etc) uses.
There is no WinZip, WinRAR or 7-Zip for Linux, but there are other far superior archiving tools for Linux that can do the same and much more. Linux is a far superior OS than Windows in almost every way (except gaming), in my experience. It is much more stable, rarely crashes (unless you screw up), and has a diversified range of software for accomplishing almost any task. There are a lot of things you can do with Linux that are either difficult/impossible/impractical in Windows.

@Syberclone: Well, like I said, they are mostly just raw partition images that correspond to partitions on the device. Like for example, boot.img is boot partition, recovery.img is recovery partition, etc. As far as modding a boot.img, there is Android Image Kitchen, which runs on Android, Windows, and Linux, maybe Mac too. There are surely also tools out there that can create/modify TWRP images, but I'm not aware of any by name. However, neither of those has anything to do with creating an EDL.
I have seen a feature in @Oki's Oreo TWRP that can back up the bootstack/firmware into an EDL, but there must be PC tools out there for this.
It's my understanding that firehose is the binary/executable programmer file that the EDL flasher tool (MiFlash/A7 EDL Tool, DFU MultiDL Tool, etc) uses.
There is no WinZip, WinRAR or 7-Zip for Linux, but there are other far superior archiving tools for Linux that can do the same and much more. Linux is a far superior OS than Windows in almost every way (except gaming), in my experience. It is much more stable, rarely crashes (unless you screw up), and has a diversified range of software for accomplishing almost any task. There are a lot of things you can do with Linux that are either difficult/impossible/impractical in Windows.

Yes, I am familiar with the Edls and how they are structured.
I am familiar with Linux too, and it is diverse and has a lot of great OS's and great applications, I have many discs with Linux but very rarely use them or Windows much any more. We could debate the ins and outs, ups and downs of all OS's however that's kind of off topic.
The topic at hand is Edls, its only been since I've owned this Axon 7 that I've experienced Edls, I've seen some tools that could possibly do the job, however haven't had time to really study these.
One such app is "Smart Flasher tool" that is a Qualcomm chipset app for use with several different phones.
This looks very promising from a couple of YouTube vids I've watched, however the download links seem to be malicious.
There is also Sahara and firehose, as well as eMMC raw tool utility.
Both via a Russian website.

The most amazing thing would be if there were a one step process of unlocking the bootloader, and getting TWRP + a custom ROM installed.
For example, imagine if there were an EDL package that flashed the device to a state where it cleared partitions as needed, and got a working and rooted copy of lineage installed, thus instead of users having to follow like a 20+ step guide, they would instead just enable OEM unlock, reboot into EDL, then flash a single package that did everything.

@Razor512: That's the lazy way of doing things. I would rather do it step by step, and get the learning experience and understanding of the overall process. An all in one package does it all for you, but that's spoonfeeding. You dont learn anything, unless you already understand how everything works.

AnonVendetta said:
@Razor512: That's the lazy way of doing things. I would rather do it step by step, and get the learning experience and understanding of the overall process. An all in one package does it all for you, but that's spoonfeeding. You dont learn anything, unless you already understand how everything works.
Click to expand...
Click to collapse
The process is simple enough, but it can get time consuming since you have to be present for it all when you want to jump back to the stock builds once in a while, e.g., if traveling, and you want android pay and other stock functions under android 8.0, and then jump back to lineage, or if you are periodically testing lineage in the hopes that a ported dolby atmos finally works reliable, it is easier if you have an EDL package that you can flash. Also, if things are not good, just flash the stock ZTE EDL and be back on stock immediately.