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

Cannibal Open Touch v2.1 (latest update: 12/1/2012) - Kindle Fire Android Development

{
"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.

Related

[ROM] Unofficial CM9 Testing builds for Epic 4G Touch

Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Follow me on twitter and github for updates, and what's going on right as it happens.
I think i already mentioned this once, but please, follow the instructions below when flashing this rom, for your phone's sake!
Here is my build from 03-15-12
And a mirror
MD5 checksum: 3ca7871541bf1fb5ecba70fd9661baef
Google Apps: HERE
Kernel: FC14
Recovery: Stock
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD... unless you unmount the internal storage
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Once again, follow the instructions below, for flashing this ROM!!!
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data or cache wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Here's a README in my github, that has thanks and whatever comes with a README
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.
EDIT4: Hey, i updated the OP with the build from yesterday, that i built. wasn't really planning on giving it out, but it appears that everyone is already using it, so might as well post the link in the OP. Please, don't ask what's changed, because not much has really changed: for this i wasn't planning on posting it... but oh well, it's out . Enjoy

Unacceptable
There seems to be a significant amount of animosity that permeates throughout the Android related forums. I'm not certain as to why this is, nor do I want to hear any reason for justification; what I do know is that it is unacceptable.
As moderators, we spend more time cleaning up flame & troll posts than working on our own community contributions. Unfounded accusations such as KANG'ing serve to drive away those valued members who try to contribute to XDA ... further lowering the quality of threads and posts on this forum.
XDA is about bringing together folks who have similar passions about mobile technology. I would have expected more maturity and professionalism. Instead, I find a thread full of inflammatory posts ... it is not constructive and serves no purpose.
While the Forum Moderator(s) take time from their busy schedule to effect cleanup and "damage control"; further detracting of this thread once it is re-opened will result in permanent holidays for those involved, rest assured that appeals will be non-negotiable. I would encourage members who have posted in this thread to reacquaint themselves with the forum rules - the best moderation is self-moderation.
Forum rules, please read!

To make sure this is clear from the beginning, and since I had to close the previous thread due to trolling and abuse, there is no kanging go on.
sbrissen and darchstar are and have been collaborating for awhile on this, helping each other out in the true spirit of the community. This thread will remain closed until darchstar is ready to have it opened.
http://twitter.com/#!/sbrissen23/status/178160581851889664
https://twitter.com/#!/darchstar/status/178170605747716096
If you look at the github and commit log you'll see the collaboration going on between the two. darchstar is publishing the builds per an agreement between the two. This is open source and community involvement at it's finest.
Any trolling will not be tolerated.

Just took the plunge and flashed.... No problems with the flash and loving the rom.
Sent from my SPH-D710 using xda premium

Great.
Just want to say thanks Darch loving all the builds

Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming

A HUGE thanks to the XDA community, darchstar, Sbrissen, and Team Rogue for putting out an excellent product on my E4GT!
Sent from my SPH-D710 using Tapatalk

Steady Hawkin said:
Game plan:
Get source for ICS kernel so we can shut down brix city! Good things are coming
Click to expand...
Click to collapse
+100000000000
coming from a new resident of brix city trying to upgrade from the 309 version to the 311 version blod, forgot I had changed the kernel to the fc07 rouge before nandroiding, stupid me, 35 dollars later and a refurb im back in business

@darchstar, are you wanting us to post bugs/issues here in the thread?

drdrewdown said:
@darchstar, are you wanting us to post bugs/issues here in the thread?
Click to expand...
Click to collapse
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here

darchstar said:
Sure, but i don't really want everybody to go on about the same issue over and over again. It really makes the thread really hard to look through, and find actual bug reports, with someone actually following proper protocol, and attaching as many log files as they can. i really do look at every post, btw. So yea please everyone be kind and help me out in this aspect here
Click to expand...
Click to collapse
cool, did you happen to see my post/everyone else commenting about the volume issue of playing music & receiving a notification of sorts (sms etc) where the volume gets really low until you toggle the levels
it's so easy to duplicate & i've tried looking through logcats but can't find anything particular. should i still pastebin something for you?
edit: i'm grabbing a cable now to capture some logs
&& it appears to only do it via the headphone jack

Anybody know of a vnc viewer that will work with this?
Sent from my SPH-D710 using xda premium

Good job Team, so far so good.. gonna test this out so more..

Thanks so much, been running great, and I could not be happier having darch, sbrissen, steady, and all the other greats on our team working together! Thanks again guys.

I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.

cidica said:
I'm not sure if this is a CM9 issue or a xda app issue but I just now noticed it with CM9 (since it's worked in the past with AOKP/Samsung leaks) Taking a screenshot and trying to upload it to any thread the app gives/says that the file is not a valid format. However I can upload it via the web without issues.
Click to expand...
Click to collapse
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium

JohnCorleone said:
I get that every time I try to upload from the app since they updated. I am using a pre-update themed version for that reason
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
meh that's lame. Oh well guess it's time for a bug report to xda for the app then

everything for me is working decently well using it as daily so i love it
only issue that irks me is the very weak signal

Love it! Better than any Sammy ics leak, and prefer it over anything official even!? Everything looks great and is smooth. Unable to install sprint NBA mobile though as unable to install on any storage seems like. Also, mms is funky sometimes. Have to toggle 4g to fix.
Anybody notice super heavy battery drain between 14%-4%?
Sent from my SPH-D710 using XDA

Fyi to all, the feedback thread was moved to general and I updated the OP with tips made by others.
Here is the link:
[FEEDBACK]Darchstar CM9 ROM *Help,Tips, and Tricks*
http://forum.xda-developers.com/showthread.php?t=1543349
Sent from my SPH-D710 using Tapatalk

[Q&A] Jellytime for Desire HD/Inspire 4G

FAQ (A work in progress)
Where can I download this awesome ROM?
http://code.google.com/p/jellytime/downloads/list
What's so awesome about this ROM?
http://code.google.com/p/jellytime/wiki/Changelog
Is a full wipe needed?
No, it is not required, but it is strongly recommended. If you choose to do a "dirty" flash, please do NOT post bug reports or issues you are having, as something from an earlier release might be causing the issue.
I flashed this awesome ROM but I don't have (insert Google app here) why?
Gapps were removed from the ROM back on Alpha 7. You simply have to download the gapps from HERE and flash via recovery.
Is Project Butter working on this ROM?
vsync was implemented in Beta 9 and triple buffering in Beta 10. So, yes, Project Butter in included.
I'm having an issue and want to report it but I don't know how.
First, check the Issue Tracker to see if someone else has reported the same issue. If no one has reported the issue then start a new issue and follow the provided template to describe your issue. Don't forget to attach your logcat.
I keep posting an issue to the Issue Tracker but it keeps getting deleted?
First, did you click the continue button on the page before the Issue Tracker? Yes? Are you sure you read that page and filed your report as explained on that page? No? Then there's your answer. Read the page that tells you how to properly submit a bug report and submit your issue properly. It will be marked as Invalid until it is properly filed after a day or two if is not filed correctly it will be deleted. For more information on how to file a log read below.
I keep reading about this "logcat" what is it and how do I make on?
"The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered."1 To learn more about logcats and how to create them please read both of these threads, they are very informative;
Adrynalyne's Guide
Lanternslight456's Guide
Is Jellytime better/faster then (insert your favorite ROM here)?
Its all a matter of opinion. You'll get 10 different answers from 10 different people. The reason for this is different people use their phones for different things, so what may be an awesome experience for one might be terrible and full of bugs for another. The best way to choose is to just flash Jellytime and find out for yourself.
How's battery life?
This is also a matter of opinion. Like the previous question you'll get 10 different answers from 10 different users. People use their phones for different things. The only true answer is to find out for yourself. If you are having battery issues however, there are a few things you can do. First, find out which apps are causing the most drain. Kill them and see if that helps. Second you can re-calibrate your battery (check THIS out). You can also read the post I made that has a few more suggestions HERE.
I can not flash this ROM why?
Ok, Jellytime is a ROM with a 3.0 based Kernel. For whatever reason (don't ask me why) but for some first time flashers the 3.0 based Kernel doesn't play nice. Have no fear, there is a "fix' for this. All you have to do is flash an up-to-date stock, sense based ROM. LIKE THIS ONE HERE. After you've flashed that you can flash whatever ROM with a 3.0 based Kernel to your hearts content.
1 - http://developer.android.com/tools/help/logcat.html

The purpose of this thread is to help those of you who aren't sure of something and to help find answers. All credits go to randomblame and his team for all their hard work and dedication. This will hopefully keep the dev thread clear of clutter so they can work more efficiently. Feel free to ask questions pertaining to his rom!
Over time I will be building a FAQ section (based on the questions asked here) that will be added here, to the Project Page Wiki, and hopefully to the thread page. Please keep this thread clear from flaming, there are no stupid questions. I ask that you read all posts here, the OP found above, and the Project Page before posting. Thanks
If you have a Question you would like answered please use this format;
Q: blah blah blah
If you are Answering a question please use this format;
"Quote question you are answering"
A: blah blah blah
If you are answering questions please provide any links to useful information about the question. If you are answering multiple questions please multi-quote them and answer them as above (quote then answer, quote then answer, etc). Absolutely no flaming. Any flaming will not be tolerated and will be reported directly to the mod.

I think the most important question for new users to Jellytime is:
Q: Is project butter implemented in this rom? If not will it be implemented? If not why it won't be implemented?
Sent from my Desire HD using xda premium

Ignore

Q: Does using V6 Supercharger break anything when using this ROM? I'm on RC 5.1, while it doesn't seem that V6 improves anything (JellyTime is already super fast!), I'm not quite sure if it breaks anything
Q: Is it safe to remove the stock launcher, nova launcher, and the news and weather apps?
Thanks

azrael97c said:
Q: Is it safe to remove the stock launcher, nova launcher, and the news and weather apps?
Click to expand...
Click to collapse
A: Yes.

Daimonion1980 said:
I think the most important question for new users to Jellytime is:
Q: Is project butter implemented in this rom? If not will it be implemented? If not why it won't be implemented?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Triple buffering and vsync are both implemented.

this was probably asked...sorry if it was.
whats the difference between the AOKP build 7 and the jellytime release 5.1?

ooglibooglie said:
whats the difference between the AOKP build 7 and the jellytime release 5.1?
Click to expand...
Click to collapse
I just answered you in your other post...but one is based on AOKP, and the other is based on CM10. And yes, this has been asked and answered.

bananagranola said:
I just answered you in your other post...but one is based on AOKP, and the other is based on CM10. And yes, this has been asked and answered.
Click to expand...
Click to collapse
okay thanks, what would be the better ROM to run the CM10 or the AOKP based? im currently running the CM10 5.1 release.

ooglibooglie said:
okay thanks, what would be the better ROM to run the CM10 or the AOKP based? im currently running the CM10 5.1 release.
Click to expand...
Click to collapse
Honestly, the best way to find out is to try it yourself. Nandroid your current ROM and install the other one. If you don't like it, just restore your backup. The differences between them are slight, and it comes down to personal preference.

Q: is there a faster way of getting screenshots? The only method I know for this rom is Power + Menu then choose screenshot. In sense roms I used to do Power + Home and a screenshot is taken right away. I also checked Settings > System > Hardware keys and there is no option for screenshots for custom actions

azrael97c said:
Q: is there a faster way of getting screenshots? The only method I know for this rom is Power + Menu then choose screenshot. In sense roms I used to do Power + Home and a screenshot is taken right away. I also checked Settings > System > Hardware keys and there is no option for screenshots for custom actions
Click to expand...
Click to collapse
AFAIK holding the Power and VOL Down button at the same time and holding until the screenshot is taken is the other way without doing the menu option. It takes a bit of getting used to and the timing has to be pretty close or it'll just activate either the power menu or the volume will go down. I'm not aware of another method, but if anyone has any suggestions, all are welcome.
---------- Post added at 07:54 AM ---------- Previous post was at 07:50 AM ----------
I'm sure there's probably a blog or thread on XDA somewhere for this, if so please just throw a link up, but I am curious about the differences in the CPU Governors that are available. Other than just trying them all to see how my DHD performs, it would be nice to know about the subtle differences that make one operate different from the other.

zphantom1 said:
AFAIK holding the Power and VOL Down button at the same time and holding until the screenshot is taken is the other way without doing the menu option. It takes a bit of getting used to and the timing has to be pretty close or it'll just activate either the power menu or the volume will go down. I'm not aware of another method, but if anyone has any suggestions, all are welcome.
---------- Post added at 07:54 AM ---------- Previous post was at 07:50 AM ----------
I'm sure there's probably a blog or thread on XDA somewhere for this, if so please just throw a link up, but I am curious about the differences in the CPU Governors that are available. Other than just trying them all to see how my DHD performs, it would be nice to know about the subtle differences that make one operate different from the other.
Click to expand...
Click to collapse
From the Ace Think Tank. http://forum.xda-developers.com/showthread.php?t=1663809

Is there any difference of users experiences dependant on which loader they use CWM or 4ext, eg. certain types of bugs, glitches associated with one or the other. I may try 4ext and see if it cures my occasional vertical rainbow screen [ which am still reading up on logcatting ]
Jim
ps ... purchased a faster sdcard class 10 as unsure of the 8gig one i have in now

Jimpy0 said:
Is there any difference of users experiences dependant on which loader they use CWM or 4ext, eg. certain types of bugs, glitches associated with one or the other. I may try 4ext and see if it cures my occasional vertical rainbow screen [ which am still reading up on logcatting ]
Jim
Click to expand...
Click to collapse
I have had problems installing inspiremod with TWRP, but nothing else that I'm aware of.

zphantom1 said:
I'm sure there's probably a blog or thread on XDA somewhere for this, if so please just throw a link up, but I am curious about the differences in the CPU Governors that are available. Other than just trying them all to see how my DHD performs, it would be nice to know about the subtle differences that make one operate different from the other.
Click to expand...
Click to collapse
Try WaccoPedia. Post #3. Very informative general android info
about the screenshot using power + vol down, can't get it to work hehe but thanks

Jimpy0 said:
Is there any difference of users experiences dependant on which loader they use CWM or 4ext, eg. certain types of bugs, glitches associated with one or the other. I may try 4ext and see if it cures my occasional vertical rainbow screen [ which am still reading up on logcatting ]
Jim
ps ... purchased a faster sdcard class 10 as unsure of the 8gig one i have in now
Click to expand...
Click to collapse
A: well i moved from cwm to 4EXT and to tell You frankly, i just hope that 4EXT will support all android phones in the future!!! all though still on RC version it is just a pleasure working in, both the .apk and the recovery touch it self. Besides the touch function 4EXT also has a much better, wider interface, no need to do jump in and out of dirs, the dev has made it so that You can for example choose if You wanna wipe cache and dalvik in one instance, and in tools You find all kinds of different and helpful combinations. 4EXT has everything + allot more then cwm. And not forgetting the .apk, from in there You can plan how You wanna for example wipe, install and so on, and by just pressing the button, it reboots and does the task You planed, reboots and that is that. Especially now when all the time wiping and re installing, it was tiresome and time consuming with cwm, but now....it is just quickly dun by the 4EXT.apk, just using half the time of what i used on cwm. As they say.....4EXT is the future recovery and i have been hearing that the dev. is also experimenting implementing rooting features, so You just install the .apk and it then roots a stock phone......that would just be great!!!

geko1966 said:
A: well i moved from cwm to 4EXT and to tell You frankly, i just hope that 4EXT will support all android phones in the future!!! all though still on RC version it is just a pleasure working in, both the .apk and the recovery touch it self. Besides the touch function 4EXT also has a much better, wider interface, no need to do jump in and out of dirs, the dev has made it so that You can for example choose if You wanna wipe cache and dalvik in one instance, and in tools You find all kinds of different and helpful combinations. 4EXT has everything + allot more then cwm. And not forgetting the .apk, from in there You can plan how You wanna for example wipe, install and so on, and by just pressing the button, it reboots and does the task You planed, reboots and that is that. Especially now when all the time wiping and re installing, it was tiresome and time consuming with cwm, but now....it is just quickly dun by the 4EXT.apk, just using half the time of what i used on cwm. As they say.....4EXT is the future recovery and i have been hearing that the dev. is also experimenting implementing rooting features, so You just install the .apk and it then roots a stock phone......that would just be great!!!
Click to expand...
Click to collapse
It also seems that people are having fewer issues with things not showing up using 4ext rather than CWM, or maybe that was ROM manager. But you are right - 4ext works wonders in multitasking like flashing wipe rom, rom, fix, fix, gapps, TiBu all at once.

[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.

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

Cannibal Open Touch 3.0 Alpha 11
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 hammerhead builds (latest: CannibalOpenTouch-2.99.11_hammerhead-2015032623.img)
How to install:
Download the latest Alpha image
Reboot to bootloader:
Code:
adb reboot bootloader
Flash the image with fastboot
Code:
fastboot flash recovery /path/to/downloaded/recovery.img
Boot into recovery mode
Alternatively, you may boot the image instead of flashing it:
Code:
fastboot boot /path/to/downloaded/recovery.img
Changelog:
Changelog:
3.0 Alpha 11 (2.99.11)
Lots, lots, and lots of changes.
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 Google Nexus 5
Contributors
drewwalton19216801, Sblood86, thenameisnigel, tdm, CyanogenMod, Koush and many others
Source Code: https://github.com/ProjectOpenCannibal/android_bootable_recovery
Version Information
Status: Alpha
Created 2014-08-01
Last Updated 2015-03-27

Reserved

Sounds sweet
sent from my Paranoid neXus 5

New RECOVERY
Just now I did fresh install of 4.4.4 and need to install root and recovery agin ,HAVE TO INTSALL THIS NEW RECOVERY
I will report bugs if I will found and Share my Experience .
sorry for my bad english

or965 said:
New RECOVERY
Just now I did fresh install of 4.4.4 and need to install root and recovery agin ,HAVE TO INTSALL THIS NEW RECOVERY
I will report bugs if I will found and Share my Experience .
sorry for my bad english
Click to expand...
Click to collapse
Sounds good, let us know what you think. Remember though that this is a very early alpha build (it's stable, but feature-completeness is maybe 5%).

Drew! I haven't seen you since the Optimus S/V days!
Nice to see you here. I'll flash ASAP and start flashing again.

Curiousn00b said:
Drew! I haven't seen you since the Optimus S/V days!
Nice to see you here. I'll flash ASAP and start flashing again.
Click to expand...
Click to collapse
Aha hey there n00b, its been a while

Recovery flashed successfully, not to bad at all.
Can't wait to see what cannibal will become! :thumbup:

I wanna flash but does this support multirom?
Sent from my Nexus 5 using Tapatalk

Juansegovia20 said:
I wanna flash but does this support multirom?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Not as of yet.
Don't know about future implementations, but by the look of it if I would guess, no.

F2FS supported?

so begins the Cannibal Time mauahahahahahaha

Never heard of this, sounds cool! Could you possibly implement encrypted backups at least?

Wakamatsu said:
F2FS supported?
Click to expand...
Click to collapse
Not yet, but it should be in a later build.
LeJolly said:
Never heard of this, sounds cool! Could you possibly implement encrypted backups at least?
Click to expand...
Click to collapse
Definitely something we'll be considering, but for now we're building out the UI and making sure things that need to work do.

drewwalton19216801 said:
Not yet, but it should be in a later build.
Definitely something we'll be considering, but for now we're building out the UI and making sure things that need to work do.
Click to expand...
Click to collapse
also if the tab options are little bigger in size... its too tiny to touch them i was using the volume keys to control mostly and not able to use the actual touch experience as the tabs were small...
maybe i got a thick finger if so please ignore

sacreddevil666 said:
also if the tab options are little bigger in size... its too tiny to touch them i was using the volume keys to control mostly and not able to use the actual touch experience as the tabs were small...
maybe i got a thick finger if so please ignore
Click to expand...
Click to collapse
That's one of those usability things we like to get feedback on. Upping the size of the touch items shouldn't be a big issue at all. Thanks for the feedback!

I just tried this recovery.... I tried flashing like 5 zips i think and all of them failed. But some other worked
Also i think we should have a confirmation button, i noticed if i touch a file it would get flashed as soon as i touch it, not complaining. Just reporting, wish i could provide you with a log cat
Sent from my Nexus 5 using Tapatalk

Love the idea & the implementation , hoping to see it being more widely used !!

Its a good idea to keep AB files instead of "nandroid" files on your computer and stored away from the device BUT what if you need it on the fly? You still want that option due to possibly needing it on the fly and I don't want to be forced into getting an OTG card reader JUST to be able to use a recovery. Just my thoughts and giving my opinion, awesome idea though.

One quick note, if you attempt to wipe you'll loose your entire /SD.
Plus, if you had an encryption password, it will be gone when you reboot; phone will show unencrypted.
After that I went back to TWRP 2.7.1.1, did a complete wipe, fastboot oem locked and unlocked (The whole shebang.) Flashed a different rom. Went to encrypt my device and was given a slew of force closes.
Have never seen that before, I wish you the best of luck.

ABANDONED [TWRP][20151015] dr4stic's TWRP 2.8.7.0 w/ stuff (Most Variants)

I BUILD ABANDON A TWRP!
THIS PROJECT IS ABANDONED (2015-12-06)
Blastagator's 2.8.7.3 release fixes the problem that started my quest: the sepolicy squashing that damaged the gapps permissions on CM-12 OS updates. Given that I had many more issues that came from my choice of CM-12.1 as a base (instead of whatever TWRP wanted) and that I lacked the time, inclination or expertise to pursue the issues, I have chosen to abandon this project. If it worked for you and you didn't need the extra features that were buggy, then by all means enjoy. However this project is no longer supported.
What is it?
It's TWRP! It's for a number of the G2's! Which ones? The ones supported by whatever the current CyanogenMod is. GSM: D800/1/2/3, CDMA: LS980, VS980. This is because, despite the TWRP documentation, I use CyanogenMod as a base, and if CyanogenMod doesn't currently support the given model, then I won't be supporting it with my TWRP. This TWRP is built with hints from (and thanks for) @blastagator's TWRP.
README.FIRST / DISCLAIMER
THERE BE DRAGONS HERE!!! USE THIS AT YOUR OWN RISK!!!
This is your one AND ONLY warning. I am not responsible for whatever happens to your phone. This software has the feature set to let you backup all of your partitions, but it also has the power TO BOTCH each and every partition on your device. This includes your EFS and other sensitive things. It is entirely possible that you may end up bricking your device. I really hope that doesn't happen, but I am also not responsible if it does. Please, behave responsibly and know that if you've taken the time to get this installed, well... your warranty is void.
Features
Flashes Gapps properly so that it doesn't crash on reboot
Thermal Support
Material Theme
{
"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"
}
Known Issues / Red Flags
I've only really tested on the D800 because that's what I have access to. However I've reports that it works fine on the other variants.
Reports that it doesn't work with blastagator's hybrid LP bootstack. (User says reboots into bootloader)
F2FS Support currently a bit borked. (User's say formatting doesn't work and causes ROM to bootloop, or is very slow and doesn't work.)
Users using AROMA will have issues installing things. Something about the installation process causes the recovery to reboot.
Cherry Picks / Links
Device Repo: https://github.com/dr4stic/twrp_device_lge_g2-common
CyanogenMod / 89474: Make recovery permissive (manually applied) - (20151003 - current)
TWRP / 12728: [WIP] gui: stock theme rework - (20151015 - current)
CyanogenMod / 110402: f2fs: Import latest F2FS + AIO Optimization - (upcoming)
TWRP / 14355: Fix broken fsflags support (upcoming)
TWRP / 14462: Support resuming block based OTAs (upcoming)
Releases / Changelog:
2.8.7.0 - 20151015
Added directives to tell twrp where our media REALLY is (blastagator suggested bad things happen if I don't)
Cherry picked a more material like theme because Rashed97 whined about ugliness
D800: twrp-2.8.7.0-20151015-d800.zip - 11.6 MB (MD5 Sum: 7e46ea96fed69a5cde9da73e26d6742e)
D801: twrp-2.8.7.0-20151015-d801.zip - 11.4 MB (MD5 Sum: 7a71cda865b0f32c1403938eb76eeb5e)
D802: twrp-2.8.7.0-20151015-d802.zip - 11.4 MB (MD5 Sum: 52143681915a53b910040fb6501dd324)
D803: twrp-2.8.7.0-20151015-d803.zip - 11.4 MB (MD5 Sum: e8ee2f05ca06be1924a45e49da29e439)
LS980: twrp-2.8.7.0-20151015-ls980.zip - 11.4 MB (MD5 Sum: f76642bd7f5bb2b0eb8bb2a20e4adfed)
VS980: twrp-2.8.7.0-20151015-vs980.zip - 11.4 MB (MD5 Sum: bdfdb1e2132ab08a8f7e42c06e3699a4)
2.8.7.0 - 20151003
Initial release
Download 2.8.7.0 - 20151003: D800 | D801 | D802 | D803 | LS980 | VS980
Thanks To:
The TWRP Development Team
@blastagator
@Rashed97

dr4stic said:
Hello folks,
I BUILD A TWRP!
Click to expand...
Click to collapse
When I see how many projects are done for the G2, I really think I should give a try... Anyway, !gg mate, I'll try this recovery .

What did you change? Or did you just build my repos and post a new thread?

blastagator said:
What did you change? Or did you just build my repos and post a new thread?
Click to expand...
Click to collapse
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
The build started as the end of my trying to figure out what the problem was with CM and Gapps that required it to be re-flashed each time a rom update was flashed. I experimented with running commands by hand, dissecting upgrade scripts, found that contexts were either not being set or being lost, etc... etc... And at some point the only answer I could come up with was that it was the recovery. I tried the CM recovery, which is worse than the black death, and it worked fine. Since your TWRP is the latest, I didn't understand why it wasn't keeping contexts. At that point I decided to build my own TWRP, so I started from the only official docs I could find. That's what my base started as.... the cm-10.1 repos they have on their github for g2.
After realizing that simply wasn't going to work, I started re-working and basing off of CM. I didn't necessarily want to look at your work because in my mind yours was done right and based on latest CM. I eventually looked at it for some hints (hence my attribution). It wasn't until I realized your device repos looked odd to me that I realized what happened. Your device repos were based from back when the G2 stuff was barely starting out on CM-12.1... it was still very 12.0 (which, in itself was a ball of vomit for the g2). It lacked the selinux stuff (which is why it was losing contexts) and you also used an alternate kernel (unsurprisingly, cuz the CM stuff was still in a state of vomit). There are no judgements. At the time you built the recovery, it's what was available and working. I don't think the G2 got selinux turned up until some time in very early August.
So, I decided to fork copies of the latest CM device repos which all work now, base everything off the current CM kernel (I figured this was safest for compatibility). I actually looked through the TWRP sources to hunt for actual BoardCommonConfig.mk settings (the docs seemed VERY lacking) and an understanding of how they all interacted. I looked at your repo for hints, but I didn't just copy it. As a result I use more current settings (a few of yours are actually deprecated). I'm assuming because of the age of your repo that your builds were lokified and you bumped them after the fact. Mine have all the changes that came with 12.1 including a lack of loki and being bumped as part of the build process. The rc files are all stock CM. Many things simply don't exist from your version because the recovery environment seems REALLY restricted once it's built. The few things that I did borrow, I moved into more appropriate locations and file names to be more respectful of the build process.
So, to answer your question: it started as a rather long and annoying bug hunt, then turned into a long but fruitful learning experience, and once I had a version that worked, I posted it for the few folks on the CM forum for whom this is a real pain in the ass.
It certainly wasn't a quick process and a grab for glory.... hell, once I realized that the CM build process needed to build a full ROM to get all the appropriate files into the recovery image, each one of those device builds took over an hour to build.
I started a new thread because I wanted to have a specific place where I could respond to issues if they arose, or at least tell people that I didn't care about their piddly little problems. I wanted a little more control over the support process, to be able to modify the OP with pertinent issues and links as they came up. It's something I wish had happened with CM-12.1 "official" threads.
There are things that I'm not sure of, and I try to indicate as much in the OP. The thread regulars indicated the history of needing thermal support, but I'm not sure if I got it right. Neither your recovery nor mine actually got the thermal libraries or binary included in the file system, however the process seems to be running. Nor are the configuration files included on the file system. f2fs support seems to simply be an additional package, and since the official G2 repos theoretically have f2fs support, I added that and moved along. The tools seem to be included on the file system.
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.

@dr4stic
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.

Lawlrus said:
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Click to expand...
Click to collapse
@Lawlrus, thank you for the explanation! After I investigated I assumed that's what was going on, but I didn't want to assume and then tell people something I wasn't sure about. I noticed that mine gets a slight toastier than blastagator's, but not a significant difference. I attributed it more to kernel tuning with the finalized CM kernel than anything else.

dr4stic said:
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
Click to expand...
Click to collapse
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
My builds are built with the Omni 4.4 Source, and these changes:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-11.0/blastagator_g2-common.xml
The device trees are actually based on cm-11, not 12.
As for SELinux, issues probably stem from this: https://github.com/blastagator/aicp...mmit/85953d0cf8dd3d33406ad8a745ced99e5039f766. When I committed it I thought it set SELinux to permissive. However, it actually completely disables SELinux, so the kernel won't automatically preserve contexts, etc. This seems like the most likely culprit for your issue. I will run a test build and revert that commit, if you'd like it to test.
As to cm-12, in general: I'm certainly interested in moving up, I just never really had a reason to spend any time on it.

blastagator said:
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
Click to expand...
Click to collapse
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight

Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.

dr4stic said:
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Click to expand...
Click to collapse
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.

sandys1 said:
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
Click to expand...
Click to collapse
Thanks for your suggestion. I'm already talking to blastagator. The problem is that his current build isn't actually based on CM-12, we are working from different sources.

jacoghi said:
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
Click to expand...
Click to collapse
I have a few d800's, it's the device I use. Which bootloader are you on? JB? KK? LP?

I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches

jacoghi said:
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
Click to expand...
Click to collapse
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.

dr4stic said:
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
Click to expand...
Click to collapse
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks

jacoghi said:
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
Click to expand...
Click to collapse
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.

dr4stic said:
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
Click to expand...
Click to collapse
I'm using cloudy 3.3 right now with xceeds kernel. After I got the fastboot mode, I could boot my system normally, if that helps. Rebooted again, got fastboot once more. Then booted system up again and installed autorec, which corrected the problem.

Well, messed around with this for a bit, decided to format /data to f2fs.
Dont do that. Not on this recovery. Formatting to f2fs takes forever (probably hangs entirely as i waited at least 10 minutes before rebooting)
Then noticed my /data wouldnt mount on reboot, causing my rom to bootloop and, even worse, the recovery to bootloop.
Due to a (probably unrelated) bug the lg flash tool didnt work either, so had to open up the device to boot in qhsusb mode and manually format /data to ext4.
This is the closest I've been to a complete brick on this phone since I got it.
Please update the OP to warn people about f2fs.
Nice work on the kernel update, but I personally am going to avoid this recovery until the above issue is solved

My problem is that it would not reboot nor power off while in this recovery. But it works by pressing power button.

It is ok now by removing the theme file ui.zip.

Develop Bugs

welcome