Develop Bugs

Cannibal Open Touch v2.1 (latest update: 12/1/2012)

{
"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"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Amazon Kindle Fire (first generation)​
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Warning: Does NOT currently support KitKit
Main Features:
1. Theme support
2. Touch screen button controls!
3. GooManager support!
4. Advanced Backup
5. Delete old backups!
6. Persistent settings
7. User-defined backup locations!
8. ADB Sideload
9. Touchscreen calibration
10. Backported “retouch binaries” patch for ICS/JB compatibility
11. Backported extfs tools for better ICS/JB management
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
Flashing instructions:
Flashing instructions can be found at the download link below.
Main Recovery Screenshots:
Main Gallery (external link) (Nexus 7 screen shots; will update soon)
Available Themes:
Themes Gallery (external link) (Again, Nexus 7 images shown here)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
Cannibal Open Touch Download (external link)
For those of you who are either uncomfortable or incapable of using fastboot for some reason webdroidmt has done an updated Smirkit 2.1 for y'all, please see the original Smirkit release page for usage instructions.
XDA:DevDB Information
Cannibal Open Touch v2.1, a Tool/Utility for the Amazon Kindle Fire
Contributors
Sblood86, drewwalton19216801, thenameisnigel
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2012-12-01
Created 2013-09-04
Last Updated 2013-11-28

Good to see you posting COTR here! Thanks.
Mike T

Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Thanks again for an alternative to TWRP. Btw, when the skull logo first came up, I thought I got a virus or something. LOL Looks cool.
Mike T

webdroidmt said:
Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Click to expand...
Click to collapse
I can't imagine what would effect speed but cool
webdroidmt said:
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Click to expand...
Click to collapse
Previous backups should work just fine yes as for themes we don't have a lot yet but there is an outline for creating them on both github and the POC forums. The apps capabilities are limited to Drew's java capabilities as I find java to be; well, it's unsavory, we'll leave it at that
To that end I'm not sure but maybe.
webdroidmt said:
I thought I got a virus or something.
Click to expand...
Click to collapse
Love it!

Thank you Sblood86 this is a great Christmas gift awesome work. Updated index.

I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app

Sblood, is there a way in settings to change the time? Thanks.
Mike T

webdroidmt said:
Sblood, is there a way in settings to change the time? Thanks.
Mike T
Click to expand...
Click to collapse
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.

Sblood86 said:
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.
Click to expand...
Click to collapse
Thanks for your reply, obviously it would be nice for proper timestamping of the nandroids, as now it reads 5 hours ahead for me.. But even without that, I've previously been enjoying using COTR and this new version with themes gives me a little something extra to play with.
Started messing around with the themes I d/l from the git, took the devildroid one and substituted the devildroid background out with the droid jellybean machine that's been floating around the web. Simple but looks pretty nice, I like green :laugh: and gives me a better idea how to work with the themes going forward. Gonna' work with the HTML color picker to see what other combos I can come up with.
Btw, just for the heck of it, I updated my smirkit with COTR 2.1 and flashed it instead of fast booting it.
Anyway, thanks again for this update.
Mike T

Ixthusdan said:
I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
There can be only one.

flashable zip?

smirkit with COTR 2.1
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T

portezbie said:
flashable zip?
Click to expand...
Click to collapse
Hmm; suppose it wouldn't be a bad idea I just didn't really consider it lol...
webdroidmt said:
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T
Click to expand...
Click to collapse
I almost messaged him in regards to that but I knew he didn't have a KF so I figured we'd leave it be lol
Edit: linked to the OP as well.

great work, but..
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
isaiahhhhh said:
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.
Click to expand...
Click to collapse
I understand the reluctance but also can state fairly plainly that IF you had been following CWM issues closely you would know that the only issues that CWM ever had with the kindle was Flashing 3.y kernels (resolved a long time ago with the first iteration of my recovery {before we renamed it}) and the super bricks with the ICS+ based recovery (solved by removing the EMMC wipe calls); this is a gingerbread hybrid so the last of those 2 isn't even remotely possible...
A fairly moderate amount of research would prove both of those statements; I would NOT release something that I wasn't confident worked. The only risk to bricking your devices while using this recovery is improper usage and/or flashing or doing something you shouldn't be doing...
Just to reinforce that statement I haven't used TWRP since last December when I rooted my Kindle Fire; it has always ran a variation of CWM or similar and guess what; it still works
I also have a jellybean based recovery for us; works flawlessly (I've been running it on my kindle for months without any emmc crashes {yes I do have the faulty samsung emmc so if there were still erase issues I would have a brick sitting on my desk; again, I don't }) apart from USB mass storage (which is the only reason we released the hybrid instead of the jellybean based recovery).
Now I know you guys are going to make up your own minds and so forth and I wouldn't ask for anything less; part of the reason I love Android devices is the Open Source nature and the fact that you aren't required to use one specific program so if you don't like the recovery that is entirely your right. Having said that I'd hate for fear to be the only thing that kept y'all from trying something new; read the recovery discussion in Hashcode and DooMLoRDs old recovery threads if you would like to know more on the subjects, also my CM7 thread discusses the my original iteration of CWM based 'hybrid' (gingerbread-ics) recovery (the release of which overshadowed as Hashcode released his ICS based recovery at the same time and people did have issues with it do to kernel wipe errors: these never occurred for those using the hybrid recovery and I'm sure you guys could find a few people to confirm that).
One final thought; instead of looking for posts saying it works, try finding one saying it doesn't (I personally never post when something works as it's implied in the fact that noone has screamed out saying it doesn't)
Edit: I forgot to mention we released 3 dev previews and a release candidate of this to our beta testers at the POC forums long before a public release (the rc was actually only out for a week but that was mainly to make sure we hadn't broken anything {layout related} since dev3).

COTR
A vote of confidence here for COTR. Don't get me wrong, I like TWRP with all its features, "pretty" UI and I especially like renaming my backups from within the recovery. But I had posted back in the summer that TWRP was becoming consistently unreliable for me in flashing ICS & JB roms, usually resulting in a flash failed error. At first I thought it was just bad downloads but this was with the MD5 matching and it would eventually flash after rebooting and reflashing on the second or third try. In a nutshell, every time I flashed a rom, I wondered if it was going to flash or bomb out on me.
With CWM not being a viable option, I was very happy to see Sblood release COTR and I've been using this as my recovery since August. I like supporting Sblood's work but more importantly I have confidence that my zips are going to flash every time as long as they are not corrupt.
Let me just say, I'm a flashaholic. I generally test just about every rom in this forum and I'm running nandroids just about every other day. Matter of fact, I maintain 3 different roms on this forum with 3 different Google accounts...they're cheap :laugh: Since I've been using COTR, I've not had one bad flash and I've backed up and restored more times than I can count without issue.
Now, if only the next version of COTR allows for renaming the nandroids. LOL Actually, I see from the COTR forum that it's on the to-do list. Well, that's my two cents and I guess we should all use what we're comfortable with in the long run.
Mike T

Looks promising. I flashed it using my favorite tool dd and it worked so far with my own unsigned zip file that resets all my custom tweaks via goo manager. I haven't tried any other features yet.

How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app

firered365 said:
How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It's controlled in the screen firmware and driver controller in the kernel; simply put, you don't/can't. Sorry.

[ROM][Linux] Ubuntu Touch Preview on TF300T [WIP]

I am working on porting the latest upstream version and will update this post as things start working.
Things to do:
[DONE] Create boot image that boots into the Ubuntu Touch rootfs.
[DONE] Create Android container started by Ubuntu.
[WIP] Customize configurations and work on kernel and android system to make things work properly (e.g. audio).
[TODO] Setup apparmor security.
Testing, debugging and optimization...
Any help is welcome!
The information and images below are very out-of-date.
The port of Ubuntu Touch to our beloved TF300T is more or less working now.
Please see section "Known Issues" below.
And please read the instructions carefully, including the linked threads, before doing anything to your tablet that might result in a very expensive paper-weight.
Known Issues
Just listing major issues that are specific to the TF300T port.
This is not the place to discuss general issues with Ubuntu Touch.
Camera is broken.
Dock not fully supported.
There are probably more; please follow this thread and report any new issues you find.
Downloads
Please read the section "Installation" below carefully, if you are not sure what these files are.
That section also contains verbose information on the different bootloader versions.
The binaries are generated automatically by Jenkins.
Generally they are not tested and may be broken.
Please report any issues in this thread, so they can be fixed and broken binaries can be removed.
Bootloader 4.2
These are the latest binaries that should be up-to-date with respect to Canonical's binaries.
Well, sometimes allow a day or two...
Android Base-System
The Android base-system is a stripped-down version of CyanogenMod 10.1 with some additional patches.
This is, where the major effort for porting Ubuntu Touch goes into.
Ubuntu Touch Root FS
This is the Ubuntu Touch file system.
Flashing this ZIP will preserve network settings and the phablet home directory, if you had installed Ubuntu Touch before.
It should work for all devices, however a stripped-down version with some changes for our TF300T is provided.
Please see the list of changes below.
Media Files
These media files are part of Canonical's root fs, but they rarely (never?) change.
Splitting the media files into a separate image significantly reduces the size of the rootfs that receives regular updates.
Unless you manually remove /data/ubuntu, these files will persist re-flashing the rootfs.
Bootloader 4.1
These are out-of-date and are no longer being maintained.
They will be kept, till dev-host deletes them (30 days after the last download):
Android Base-System
Ubuntu Touch Root FS
The rootfs for bootloader 4.1 also includes the media files. There is no separate download.
Android Source Code
The patched repositories of the Android/CyanogenMod/Ubuntu source trees are available on GitHub.
For details, please see section "Building the Android Base-System from Source" below.
Ubuntu Touch Root FS Changes
The "official" Ubuntu Touch root fs does not quite work on our TF300T yet.
So a stripped-down version with the following changes is provided:
Run amixer on boot to fix mixer levels.
Disable save/restore of alsa settings.
Split media files into a separate image.
Remove several big and unnecessary files.
The official Ubuntu Touch image does work, but for these issues:
Flashing with TWRP fails.
For details, see the bug report on launchpad.
There is no sound, unless you adjust alsa mixer levels manually.
Rebooting from Ubuntu goes into a boot-loop.
When Ubuntu is properly shut down, it saves the current alsa settings.
Restoring them on the next boot crashes the system and causes the boot-loop.
Note that rebooting from Android or using adb works fine.
If you happen to run into the boot-loop, use the TWRP file manager (in the Advanced menu) to remove /data/ubuntu/var/lib/alsa/asound.state.
Installation
Please read the following instructions carefully, and make sure you understand each step and what it will do to your tablet.
The steps are working for me, but you are ultimately responsible, for what you are doing with your own tablet.
I will not be responsible, if you brick your tablet, or if your wife gets angry at you for being too preoccupied with your tablet.
Step 1: Unlock Your Tablet
If you want to give Ubuntu Touch a try, your tablet needs to be unlocked.
There are lots of threads helping with this, please use search to locate this information.
Step 2a: Which Bootloader Do I Have?
Unfortunately, Asus has released several incompatible bootloaders.
To find out, if you can use this port of Ubuntu Touch, go to the bootloader screen by holding the power and vol-down keys.
Once you see the bootloader screen with three or four icons in the center, check the long version number at the top of the screen.
It looks something like: "WW_epad-10.6.1.15.3-20130416".
The first two letters are your SKU and should not matter.
The version number following "epad" is what will be referred to in the following.
Version 10.6.1.15.3
This is the latest version from Asus, generally referred to as "bootloader 4.2" in the XDA forums.
The latest Ubuntu Touch binaries are developed and tested on this bootloader, so you should be fine.
Version 10.6.1.8
This is an older version of the bootloader 4.2.
The latest Ubuntu Touch binaries might work for you, though upgrading your bootloader is recommended (see below).
This version is known to cause issues with the latest TWRP recovery, so be careful.
Version 10.4.2.20
This is the old incompatible bootloader, generally referred to as "jb bootloader" or "bootloader 4.1" in the XDA forums.
The latest Ubuntu Touch binaries will not work for you, upgrading your bootloader is strongly recommended (see below).
Older binaries that work with this bootloader are still available for download though.
Any older version not listed
Your bootloader is really out of date and you should upgrade as soon as possible (see below).
Any newer version not listed
You are on uncharted territory. Proceed with care!
Let us know about your experience in this thread!
Step 2b: Upgrade Your Bootloader
If you have not yet installed bootloader 10.6.1.15.3, it is recommended to upgrade.
Please check the following threads (and several others; search might be helpful):
[GUIDE][26/04]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Step 3: Install TWRP Recovery
You need a custom recovery installed for flashing the Ubuntu Touch binaries.
Please check the following thread for getting and installing TWRP recovery:
[RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery!
Step 4: Backup and Wipe Your Android System
Before flashing Ubuntu Touch, you need to wipe some parts.
It is strongly recommended to make a backup of your Android system too.
Check section "Restore Android" below on how to restore it.
If you are running CyanogenMod 10.1:
Use TWRP to backup "boot" and "system".
Backing up "data" is not strictly necessary, but recommended.
Wipe "cache", "dalvic cache" and "system".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
If you are not running CyanogenMod 10.1, but another ROM:
Use TWRP to backup "boot", "system" and "data"
Wipe "cache", "system" and "data".
In TWRP 2.5 you should use "Wipe -> Advanced Wipe" and check the respective boxes.
Note that this will not wipe the contents of your "/sdcard" Android folder.
Step 5: Flash Ubuntu Touch
If you want a clean start or you had installed Ubuntu Touch for bootloader 4.1, please remove /data/ubuntu manually before flashing.
You can use the TWRP file manager in the Advanced menu for that.
If you want to upgrade from a previous Ubuntu Touch for bootloader 4.2, please see section "Upgrade Ubuntu Touch" below.
Flash the following images (see above for downloads):
ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
ubuntu-touch-media-XXXXXXXX.zip
Step 6: Reboot Your Tablet
Note that there is no boot animation yet, so the screen will be black, till the shell is starting up.
This make take some time, please be patient!
Restore Android
Boot into TWRP recovery.
Wipe "cache" and "dalvic cache".
Select the last backup done before installing Ubuntu Touch.
If you were running CyanogenMod 10.1:
Restore "boot" and "system".
If you were not running CyanogenMod 10.1, but another ROM:
Restore "boot", "system" and "data".
Reboot your tablet.
Upgrade Ubuntu Touch
Generally, the system and the rootfs can be upgraded individually.
However, sometimes Canonical introduces breaking changes, that require them to be upgraded together.
Upgrade ubuntu-touch-system-XXXXXXXX-tf300t-bl4.2.zip
If you are running an older version of that ZIP, you can just flash the new one.
If you have returned to your Android system, please follow "Backup and Wipe Your Android System" under "Installation" above before flashing the new ZIP.
Upgrade ubuntu-touch-rootfs-raring-XXXXXXXX-tf300t-bl4.2.zip
You can flash this ZIP anytime.
Network settings and the phablet home directory will be preserved. This includes the media files from the separate ZIP:
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Upgrade ubuntu-touch-media-XXXXXXXX.zip
You can flash this ZIP anytime.
It will just overwrite existing files and add new files; old files will not be deleted.
If you want to start clean, remove /data/ubuntu manually and re-flash both rootfs and media.
Building the Android Base-System from Source
Basically you can follow the guide for building CyanogenMod with one exception.
Initialize your CyanogenMod source repository with:
Code:
repo init -u git://github.com/f69m/android -b phablet-10.1-tf300t
You can also run this command in an existing repository.

Thats great, but ...
f69m said:
Current Status:
Ubuntu Touch is booting and can be accessed via adb, but the screen stays black.
Click to expand...
Click to collapse
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.

Shu. said:
I have the exact same issue even on the official build released for nexus 4
Click to expand...
Click to collapse
Oops, that is intersting, thanks!
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed, if your interest is to have something to play with.
On the other hand, I'd like to see, what is already there and possibly help improve it by contributing to Canonical. And any work we do now will speed up porting, once there is a better release available.
Just trying some more Kernel tweaks after looking at the TF700 port that seems to work (see http://forum.xda-developers.com/showthread.php?t=2162472).

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
Shu. said:
I have the exact same issue even on the official build released for nexus 4 ... The current release of Ubuntu is just such a mess, nothing more than a buggy preview with loads of fake apps and content, and very limited functionality.
I'd love to see Ubuntu on tf300, but I would say (in my humble opinion,) lets wait for a better release, and then we'll get started.
Click to expand...
Click to collapse
Agreed but I have gotten it up and running on my nexus 4 without much issue, its cool for about 20 min( being generous) but then you realize you can't actually do anything. I feel that its gonna be an awesome platform especially for a transformer tablet though if it goes where they say it will. Full Ubuntu when docked and then touch when not....sounds like what these tablets were made for.
Sent from my Nexus 4 using xda premium

Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.

matonka007 said:
Still not working build ? (
It's pity, i would like to try it, I know, that there is only something functions, but I can try the UI, and how it is look like
Maybe someone from TF700 thread who port it for TF700 can help us.
Click to expand...
Click to collapse
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.

ColMustard said:
Just checked the wiki.ubuntu.com/Touch/Devices site, looks like someone has committed to porting it. Though I wouldn't be in a rush to get it just yet seeing as it barely functional. I guess time will tell where this leads.
Click to expand...
Click to collapse
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
doubljdog said:
lol, if you looked at the developer on the wiki you would realize that the developer on it is the originator of this post
Click to expand...
Click to collapse
Yes I realized that after I posted this. Just pointing out that someone has committed to porting this.
Edit: Thanks for pointing out the obvious though,I'm sure nobody else would have figure this out
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD

So, is there someone working on it, or not?
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...

How did you load the patch in your make file? I am adapting your patch to my device.

secosan said:
So, is there someone working on it, or not?
Click to expand...
Click to collapse
Yes, I am working on it, and so are some others.
I installed the one from tf700 on my tf300 and it works decent, except wi-fi, so I'm guessing its not that hard, but i'm not a dev..so...
Click to expand...
Click to collapse
That is interesting, thanks!
What happens on the tf300t using the CM tf300t base code is a segmentation fault.
The nv video drivers send a null file pointer to fputc() in the Ubuntu libc.
Just trying to do a quick fix, by building my own libc that silently ignores the null pointer, but that is sure not a final solution.
Eventually we need to figure out, where the null pointer comes from and avoid it.
I'll let you know, how it works, once the lenghthy ARM compilation has finished and I had a chance to try it.
WLAN is working fine, BTW, just the display is black.

giveen said:
How did you load the patch in your make file? I am adapting your patch to my device.
Click to expand...
Click to collapse
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?

Canonical started the daily building of Ubuntu Touch, good news I tryied the build for TF700 too, but it have bad DPI.
PS: f69m, I do not know about developing, but if I can help you write.

Re: [DEV] Porting Ubuntu Touch Preview to TF300T
f69m said:
Are you referring to my patches on GitHub?
Not quite sure, what you are asking for.
Anyhow, the patches for the package makefile and for the kernel are on GitHub
https://github.com/f69m/ubuntu-touch-tf300t.
The changes to the Android repository manifest are described on
https://github.com/f69m/ubuntu-touch-tf300t/wiki/Build-Ubuntu-Touch-for-ASUS-Transformer-TF300T
Apart from those patches it is really the same as building CyanogenMod. Just faster, as only a part of the CM tree is built.
Does that answer your question?
Click to expand...
Click to collapse
I was referring to the screen res patch, but I figured it out from your guide.
The problem I am having that my kernel not compiling with Ubuntu options even though I sent them in my defconfig.
They should be working but they are not.
Sent from my Nexus 7 using Tapatalk 2

What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?

matonka007 said:
What is this link?
http://ubuntuone.com/06vcR0nyoTd9DYb2OgRSlT
Is on https://wiki.ubuntu.com/Touch/Devices as Android Base image, it is your build f69m ?
Click to expand...
Click to collapse
Definitely not my build, I have no images out yet, but mine should be coming soon!
The entry in the device table was not added by me.

Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.

It sound great
Yes, Dropbox is good choice
And http://d-h.st/is not bad for sharing files

f69m said:
Woohoo, I am seeing something!
The Ubuntu package build for my patched libc is still running tests, but I pulled the libc.so binary from the build directory.
This is a manual hack right now, I need to repackage the root FS for flashing and then will make it all available via Dropbox.
Hope that will allow quick downloads for everyone.
Click to expand...
Click to collapse
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github

-angel* said:
Oh and then also please dont forget to update the install instructions on the official ubuntu page and here because on Ubuntu it links to your building guide on Github
Click to expand...
Click to collapse
Of course, l will make sure to update everywhere, once the image is released, though the entry in the Ubuntu wiki was not done by me.
Got a flashable filesystem now, but that version is crashing on me. Must be something small I am overlooking atm.
So taking a little break and then will finish with refreshed spirit.

TWRP 2.6.3.2 TeamWin Recovery Project 10/5

Default [RECOVERY] [10/5/13] TWRP 2.6.3.2 - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.6.3.2 for the Galaxy Note 3 (T-Mobile)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Special credits:
Dees_Troy for quick porting.
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
CRudner and Reb0rn for testing
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.6 features
Older Releases
What's new in 2.4:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes
-Support for exFAT formatted sdcards
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Other minor bugfixes and improvements
-cm10.1 build support
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
What was new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
Gerrit Instance - http://review.teamw.in
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
n7100 Device Config: https://github.com/bigbiff/android_device_samsung_n7100
Kernel: https://github.com/bigbiff/kernel_samsung_sgh-i317
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://teamw.in/project/twrp2
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
XDA:DevDB Information
TWRP, a Tool/Utility for the Samsung Galaxy Note 3
Contributors
bigbiff, Dees_Troy
Version Information
Status: Testing
Created 2013-10-05
Last Updated 2013-10-05

Reserved

Reserved 2

good.
using your work on note 2 and now on note3. :good:
But can i use this (tmobile version) on my french mobile (LTE SM-N9005) without problem??

someone have a workong link for 2.6.3.2 version?

does this work on SM-N900?

kenzolo said:
someone have a workong link for 2.6.3.2 version?
Click to expand...
Click to collapse
here http://teamw.in/project/twrp2/198

micky387 said:
here http://teamw.in/project/twrp2/198
Click to expand...
Click to collapse
are you able to download 2.6.3.2 version?

Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4

micky387 said:
Follow this link.
For odin method http://goo.im/devs/OpenRecovery/hltetmo
Envoyé depuis mon SM-N9005 avec Tapatalk 4
Click to expand...
Click to collapse
come on micky I understand...but I can't downlod 2.6.3.2 version (404 error page note found)

404 - Not Found
micky387 said:
Follow this link...
Click to expand...
Click to collapse
404 - Not Found

Are all hlte devices supported it is only htletmo listed on the official device list
Sent from my SM-N9005 using Tapatalk 4

Works fine on N9008, thank you very much, finally a decent recovery
Using 2.6.3.1, 2.6.3.2 download gives error 404 as someone else said.

I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.

Yeah the devs derped the upload of 2.6.3.2 - neither of the two downloads (typo and no typo) work, both are 404. Been like that since yesterday afternoon. Running 2.6.3.1 for now.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
wencel said:
I confirm that I cannot download 2.6.3.2 either.
There are two links in the list:
openrecovery-twrp-2.6.3.2-hltetmo.tar
penrecovery-twrp-2.6.3.2-hltetmo.tar (without the "o" in the filename)
.. but none works, its probably gone from the server or the name has been somehow changed without updating the links too.
However, questions for those who tried the Recovery - did you try the root the phone using the recovery? And can you delete/reset all traces of root or custom modification from the device in case you'll need to use the warranty ? Thank you for quick reply.
Click to expand...
Click to collapse
Once you modify ANY of the phone's partitions, you trip the KNOX_WARRANTY_VOID flag in the bootloader.

With twrp 2.6.3.1...anyone who has sucessfuly created backup and restored without issues? Just asking becoz the cwm recovery still cannot restore properly.
[email protected] from Bad Ass Note III-SM-N9500

Thanks for your hard work! Still waiting on a SM-N9005 version. Not really sure what's required for that or if the above is compatible, but I'm happy to wait until goomanager has a compatible one =)

Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?

dark_dude said:
Is this only ccompatible with the T-Mobile variant and do backup and restore work without problems?
Click to expand...
Click to collapse
Just downloadet the TWRP 2.6.3.2 file from Goo.im

inffy said:
Just downloadet the TWRP 2.6.3.2 file from Goo.im
Click to expand...
Click to collapse
Is this link？
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.6.3.2-hltetmo.tar

[OFFICIAL][RECOVERY] Cannibal Open Touch v3.0 Alpha Builds (latest: Alpha 10)

Cannibal Open Touch 3.0 Alpha 10
Disclaimer:
While we try to test our work as much as possible, it is always a possibility that something could go wrong and screw up your phone. We are not responsible for any damage that is done to your device, either directly or indirectly, as a result of using Cannibal Open Touch or any other Project Open Cannibal projects. Any damage done to your device is your responsibility and your responsibility only. We do this for fun, and we simply like to share our work.
What is Cannibal Open Touch?
Cannibal Open Touch is a custom recovery (like ClockworkMod or TWRP), created purely out of love for the platform and the desire to contribute something cool to the community. The name embodies everything that Cannibal Open Touch is. We take what we believe are the best features of popular recoveries like TWRP and ClockworkMod and, well, cannibalize them along with rolling out our own features.
Features:
Full Touch UI
Complete theme support, including app for management of themes (we'll get to that in a sec)
On-device backup and restore
Backup and restore via ADB
Much much more planned!
Bugs:
During installation, the standard Android installing icon gets displayed instead of the custom dialog box.
If you find a bug, please do not report it here! Instead, report it in the GitHub repository!
Screenshots
See the Screenshots tab above. (Or click me if you're using Tapatalk!)
Nandroid has been replaced!
Nandroid is in fact gone, and has been replaced with a much more robust backup solution. Backups can now be made either with ADB (the recommended way) or via the new Backup and Restore item in the main menu. Backups made via the built-in menu can be copied to a PC and restored via ADB, and backups made via ADB can likewise be copied to your device and restored using the Backup and Restore menu.
Code:
adb backup -f mybackupfilename.ab boot system data cache
You can also restore said backup by using adb, like so:
Code:
adb restore mybackupfilename.ab
Downloads:
Cannibal Open Touch d2lte builds (latest: CannibalOpenTouch-2.99.10_d2lte.tar)
How to install:
Download the latest Alpha image
Reboot to Download Mode:
Code:
adb reboot download
Flash the image with ODIN
Boot into recovery mode
Changelog:
3.0 Alpha 10 (2.99.10)
Themes are now stored in /cache/cot/themes to fix an issue introduced with FDE.
3.0 Alpha 9 (2.99.9)
Real menu scrolling! (but volume keys still work)
All backup/restore operations now verify that you want to take action
Resized UI to be more usable on all device resolutions
Themes can now display a battery charge indicator (depends on individual theme settings)
3.0 Alpha 8 (2.99.8) (not released)
Not released
3.0 Alpha 7 (2.99.7)
On-device backup and restore
3.0 Alpha 6 (2.99.6)
Complete theme support
Recovery settings (Theme settings and Unsigned ZIP flashing)
The preceding list is not 100% complete. See the project source code page for the full commit list.
Cannibal Open Touch themes app:
We are currently seeking Alpha testers for an app that will let users download and choose themes without rebooting to recovery mode. Currently there are 20 slots open. If you wish to join please PM me. The only requirement is you must have a Google+ account and are willing to submit proper bug reports, should any arise.
Cannibal Open Touch Themes:
You can now make your own themes for Cannibal Open Touch! See the example themes (it's pretty self-explanatory). Themes must be installed in /sdcard/cot/themes/theme_name (or /data/media/cot/themes/theme_name) in order to work. Please feel free to submit pull requests to have your custom themes added to the theme repository. They will also be packaged and made available to download via the Cannibal Themes app (mentioned above)!
Contribute to Project Open Cannibal
If you like our work and want to see more, consider a donation to the project!
Project Open Cannibal gerrit: http://review.projectopencannibal.org
Credits:
tdm, for the superb touch code (and lots more)
sblood86, for joining the project and leading the charge to greatness
thenameisnigel, for picking up our webhosting while I was gone
anyone else who has ever contributed to any Android-related project
XDA:DevDB Information
Cannibal Open Touch, Tool/Utility for the T-Mobile Samsung Galaxy S III
Contributors
thenameisnigel, Sblood86, drewwalton19216801, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery-cm
Version Information
Status: Alpha
Created 2014-11-23
Last Updated 2014-12-03

Reserved

Reserved

WOW! First!
CWM was dying on S3, so this is a great addition!

Nice to see some new stuff coming out not for me tho I prefer twrp with a theme

immorality said:
Nice to see some new stuff coming out not for me tho I prefer twrp with a theme
Click to expand...
Click to collapse
BTW, we have themes as well. You can download theme from https://github.com/ProjectOpenCannibal/CannibalThemes_themes/ and unzip them to /sdcard/cot/themes.

@thenameisnigel
I don't see any themes actually uploaded I'll check in every now an then maybe see something I like (screen shots I'd rather not have random zip files)

immorality said:
@thenameisnigel
I don't see any themes actually uploaded I'll check in every now an then maybe see something I like (screen shots I'd rather not have random zip files)
Click to expand...
Click to collapse
There are themes uploaded there. They've been there for months now, and the contents of those files are located at http://github.com/projectopencannibal/sdcard_themes
Sent from my XT1080 using Tapatalk

OnePlus One DroidKit | by iTechy OPEN SOURCE! | No longer being maintained

Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirements​To run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
Downloads​No Download as no longer maintained and buggy​QR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issues​You tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06​

FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit

I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...

GOOD JOB .....Bro

kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you

Anyone already try this tool? I want download, but size so damn high

zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up

timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD

... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.

itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:

ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)

I can´t flash twrp with this toolikt any one have a clue?

Do you have the adb drivers installed? Or is it throwing an error?

Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk

Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.

dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...

Download link is not working. Please re-up. Thanks

godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1

If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.