Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRoms, ROM for the Motorola Droid RAZR HD
Contributors
darkspadez, SlimRoms
Version Information
Status: Testing
Created 2014-07-01
Last Updated 2014-07-01
Reserved For Future use
Also Reserved
Wow this is great. I hope someone port this to atrix hd.
---------- Post added at 01:59 AM ---------- Previous post was at 01:51 AM ----------
Which of these models is gsm so i can try flashing this on atrix hd?
Awesome awesome!! Been waiting in anticipation for this will try as soon as possible!
EDIT: Ok, I have only had limited time to test. But briefly put things looks promising here:
Installed without any problems (using latest TWRP in my case).The same bugs that exist in CM 11 are also present here, which is it to be expected (e.g. broken video playback). This is perfectly natural for such an early release and no doubt these will get sorted out as development progress. I am glad to try out this early build. For an alpha it seems very stable and definitely looks promising! I initially tried the official Slim Gapps (as linked to). They seemed fine. Since then I have installed ART compatible Gapps from the CM thread (13/11 i believe). Now running in ART runtime mode. Yes this does introduce some problems and not all apps are compatible, however from my experience ART also introduce a previously unseen level of smoothness. Will continue to use this the next days and of cause eagerly follow development.
@darkspadez (and all other other involved devs of cause): Congrazt on this first public SlimKat build for our phones!
Sent from my XT925 using Tapatalk
SVLAN said:
Wow this is great. I hope someone port this to atrix hd.
---------- Post added at 01:59 AM ---------- Previous post was at 01:51 AM ----------
Which of these models is gsm so i can try flashing this on atrix hd?
Click to expand...
Click to collapse
925 is GSM.
help
I would love to try this ROM but can't seem to get my cmw recovery updated I down loaded the zip mentioned correct version thru ROMmanager and flashed it . But when I go to cmw recovery it still shows older version. Tried flashing it with that but gives me the dead android. Have to restore
DizzyFox said:
I would love to try this ROM but can't seem to get my cmw recovery updated I down loaded the zip mentioned correct version thru ROMmanager and flashed it . But when I go to cmw recovery it still shows older version. Tried flashing it with that but gives me the dead android. Have to restore
Click to expand...
Click to collapse
I am using latest twrp recovery found here in the RAZR development forum. I can't say if this the best option though. I can only say that in my case it worked fine (install, backup and restore).
I'm one of the devices running the buggy EMMC.
Error is the same as all the others (I wish there were a kernel fix for it):
set_metadata_recursive: some changes failed
Back to the drawing board...
DizzyFox said:
I would love to try this ROM but can't seem to get my cmw recovery updated I down loaded the zip mentioned correct version thru ROMmanager and flashed it . But when I go to cmw recovery it still shows older version. Tried flashing it with that but gives me the dead android. Have to restore
Click to expand...
Click to collapse
I was flashing fine with cwm 6.0.3.6 for the epinter build. I did finally update, but I had to use a .bat file in conjunction with a special fastboot.exe file to actually upgrade the recovery, because otherwise it would just fail to upload. I was having backup issues with TWRP, so I just stick with CWM now. Haven't had any issues. If you want to try that .bat .exe combo I found, let me know.
projekt8e said:
I was flashing fine with cwm 6.0.3.6 for the epinter build. I did finally update, but I had to use a .bat file in conjunction with a special fastboot.exe file to actually upgrade the recovery, because otherwise it would just fail to upload. I was having backup issues with TWRP, so I just stick with CWM now. Haven't had any issues. If you want to try that .bat .exe combo I found, let me know.
Click to expand...
Click to collapse
I was wanting to keep cmw also but can't figure out how to install or flash the new version that this ROM requires.
DizzyFox said:
I was wanting to keep cmw also but can't figure out how to install or flash the new version that this ROM requires.
Click to expand...
Click to collapse
I just flashed the CWM this morning via fastboot and everything went fine. Have you tried that way?
Sent from my XT925 using Tapatalk
I was expecting to read about the ROM, but only see comments about recoveries. Any comments on the ROM? Video recording/playback is working?
Working great on atrix hd other then i get no signal. Everything else seen to work. I also had to edit the build.prop to change the resolution to 320 so it doesn't look so small on my atrix hd
SVLAN said:
Working great on atrix hd other then i get no signal. Everything else seen to work. I also had to edit the build.prop to change the resolution to 320 so it doesn't look so small on my atrix hd
Click to expand...
Click to collapse
What kind of video playback works for you? YouTube? MX Player with S/W decoding?
So far yt and netflix
SVLAN said:
So far yt and netflix
Click to expand...
Click to collapse
Wonder when this was commited to compile. I see a bunch of changes related to this in the gerrit and wonder if CM11 will be getting this tonight as well.
Yeah I wonder the same as well. Maybe @skeevydude be able to fix few things with these commits for aosp 4.4
SVLAN said:
Yeah I wonder the same as well. Maybe @skeevydude be able to fix few things with these commits for aosp 4.4
Click to expand...
Click to collapse
Do you have any print services in Settings?
Spidinator said:
I just flashed the CWM this morning via fastboot and everything went fine. Have you tried that way?
Sent from my XT925 using Tapatalk
Click to expand...
Click to collapse
I must not have my PC set right. I get my phone in fastboot but when I try to open fastboot it just blinks and disappears. I may just have to try putting trwp on my phone. Thanks you are all a great bunch of gentlemen
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
CWM Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/cwm.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/cwm.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
With CyanDelta work?
negativman said:
With CyanDelta work?
Click to expand...
Click to collapse
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
gandhar said:
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
Click to expand...
Click to collapse
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
mackief said:
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
Click to expand...
Click to collapse
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
gandhar said:
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
Click to expand...
Click to collapse
About Ubuntu, it's not that simple.
It seems 4X kernel from CM team does not load into the system.
Unfortunately, I cannot debug which is the problem surely: but I'm sure I'll return on it in a week at least. I've some thoughts about how to make it loading and booting next to the kernel!
negativman said:
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
Click to expand...
Click to collapse
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
mackief said:
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Do not quite understand! Surely there's a new CWM 6.0.4.4. You can unlock it from Rom Manager? http://forum.xda-developers.com/showthread.php?t=2523732
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
mackief said:
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
Click to expand...
Click to collapse
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
[email protected] said:
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just pulled a log, as it does not boot.
Having some issues related to gralloc. Need to debug!
mackief said:
[...]
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Just take a look at my sig we already have 6.0.4.4 touch
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
When he unlocked from Rom Manager?
mackief said:
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
Click to expand...
Click to collapse
I will update it ASAP
negativman said:
When he unlocked from Rom Manager?
Click to expand...
Click to collapse
Not at all, as only official device maintainers can. And as I am not a maintainer, I can't
Just released new build of CWM.
Changelog:
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
We recently changed our Issue Tracker URL.
If you want to report a bug, please, follow the new instructions:
· Issue Tracker URL: Issues | Github
· Important notes: go to the linked URL, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue. Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different kernel, mod, plugins and dependencies we didn't tell to use).
Development for this project has been totally and officially stopped, as no more needed.
Greetings,
MoltenMotherBoard team.
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 Moto_MSM8960 Jellybean builds (latest: CannibalOpenTouch-2.99.10_msm8960_jbbl.img)
Cannibal Open Touch Moto_MSM8960 KitKat+ builds (latest: CannibalOpenTouch-2.99.10_msm8960.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:
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 Motorola Droid RAZR HD
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
Giving this a try, thanks!
Good deal will this work for jbbl?
TecknoFreak said:
Good deal will this work for jbbl?
Click to expand...
Click to collapse
Yep, I built it for jbbl bootloaders.
Sent from my XT1080 using Tapatalk
thenameisnigel said:
Yep, I built it for jbbl bootloaders.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
Not available at the present moment, but if you really want it, submit it in the feature requests tab if you're on XDA using a browser.
Sent from my XT1080 using Tapatalk
CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
thenameisnigel said:
Not available at the present moment, but if you really want it, submit it in the feature requests tab if you're on XDA using a browser.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I take back what I said, F2FS partitions are supported in COT. Like Drew said, there's no way to change the partition type yet. But if you have a pre-existing F2FS partition, you're all set.
CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
There is currently no way to switch partition types in COT recovery mode, though this is something we will consider adding in the future.
thenameisnigel said:
I take back what I said, F2FS partitions are supported in COT.
Click to expand...
Click to collapse
F2FS is supported code-wise but is not enabled by default, though this is something we'll be enabling shortly.
CWGSM3VO said:
One thing I couldn't find while playing with it was the option to format partitions as f2fs. Am I blind or is this option N/A?
Click to expand...
Click to collapse
drewwalton19216801 said:
There is currently no way to switch partition types in COT recovery mode, though this is something we will consider adding in the future.
F2FS is supported code-wise but is not enabled by default, though this is something we'll be enabling shortly.
Click to expand...
Click to collapse
Enabled. Alpha 10 that has F2FS enabled by default is up! Woot, woot!
Alpha 10 Jellybean & KitKat images are now up.
A little curious why you just have the option to backup to pc and not backup to internal or external sd card? Or is that just an older picture I'm seing? Looks good though.
cj360 said:
A little curious why you just have the option to backup to pc and not backup to internal or external sd card? Or is that just an older picture I'm seing? Looks good though.
Click to expand...
Click to collapse
Older picture. That was before we added on device backups.
Sent from my XT1080 using Tapatalk
Sweet! I'm in the middle of switching over to the KKBL versions of everything so I'll give this a shot!
---------- Post added at 04:08 PM ---------- Previous post was at 03:21 PM ----------
One bug I found is that this recovery does not boot after doing a "fastboot -w" to wipe the userdata (and cache) clean. I'm guessing it's trying to mount it?
Also, did not find a "back" button when I went into themes.
RECOVERY
TWRP & CM-Recovery
Z00A/Z008 ( LP Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 2.8.7.3 (LP based)
TWRP 2.8.7.7 (M based)
CM-Recovery 9-28-15 (LP based)
CM-Recovery 12-22-15 (M based)
{ Cm-Recovery doesn't use "version" tags so using build date as a version # }
SOURCES
Recovery built in a CM-12.1/13.0 environment respectively using device trees/kernel
from our CM device trees/kernel CM-zenfone2 github
Z00A LP Tree HERE
Z008 LP Tree HERE
Z00A M Tree HERE
Z008 M Tree HERE
Kernel Source
CM-Recovery source from CM-recovery
TWRP source tyipically from Omnirom
HOWEVER 2.8.7.6 beta uses modified TWRP source from omnirom (and patched from thier gerrit) from
HERE
Code:
Changelog:
1-22-16:
TWRP 2.8.7.7
- fixed OTG & external SDCARD mount
- from TWRP: language support, code cleanup and minor fixes(see twrp github for full list)
- this is pre-release testing main ly for soon to be released TWRP 3.0
12-22-15:
* updated builds
* should fix backups in TWRP
* should fix issues flashing newer ROMS after 12-17-15
12-7-15
* 2.8.7.5 TWRP builds
* fixed opengapps flashing
12-6-15
* split into new thread
* Marshmallow based recoveries now live
* TWRP is WIP prior to next major official tag, new theme included for testing
Z00A/Z008 ( MM Bootloader)
Just as the title says these are unofficial recovery builds for Asus Zenfone 2 Z00A and Z008 models
These have been tested and confirmed functional. These are built from current CM devices trees, CM kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-M1 (MM based)
SOURCES
Recovery built in a Omnirom-6.0 environment respectively using device trees/kernel below
Z00A/Z008 MM Tree HERE
Kernel Source HERE
TWRP source tyipically from Omnirom
Code:
Changelog:
Initial source built MM bootloader friendly based recovery release
Z00D
Just as the title says these are unnoficial recovery builds for the Asus Zenfone 2 Z00D (ze500cl) model
These have been tested and confirmed functional. These are built from experimental devices trees, modified Stock kernel source. Source links provided below. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Versions provided for both devices
TWRP 3.0.2-0
SOURCES
Recovery built in a omnirom environment respectively using device trees/kernel
from our my github
Device Tree
Kernel Source
Code:
Changelog:
5-3-16: Initial TWRP build
XDA:DevDB Information
Zenfone2 Recovery, Tool/Utility for the Asus ZenFone 2
Contributors
jrior001, crpalmer
Source Code: https://github.com/CM-zenfone2
Version Information
Status: Beta
Beta Release Date: 2015-12-06
Created 2015-12-07
Last Updated 2016-08-03
Niceeeeeeeeeeeeeeeee
Well this was unexpected, thank you so much for this!
Edit: Well I tried the MM version, and I must say I love the new look! It's kinda laggy, but that's very expected and I got a recovery log.
Aceofzeroz said:
It's kinda laggy, but that's very expected and I got a recovery log.
Click to expand...
Click to collapse
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
jrior001 said:
TWRP still uses some really old code for pixelflinger. We have been using a JB era patch from Intel to add x86 optimized acceleration, which Dees_Troy(TWRP dev) and the zenfone5/6 devs ported to KK & LP. I updated it for M, but this is about as good as it gets until TWRP overhauls that section of their code. Without this patch is basically unusable.
And yes the new theme is sexy It's months in the making from TWRP contributer @z31s1g and it's quite lovely.
Click to expand...
Click to collapse
Ah, I understand the situation now and glad that the patch worked out for the time being. Definitely better than not having the latest TWRP to play with, so my highest gratitude for the amazing work bringing up Marshmallow in time for the holidays! :thumbup:
Sent from the Ace's MB865 using Tapatalk
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Is there an easy way to update my TWRP? Any apps that can do this for me?
roach9 said:
Is there an easy way to update my TWRP? Any apps that can do this for me?
Click to expand...
Click to collapse
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Any difference for 2.8.7.4 vs .3 other than the look? Googled it and found nothing.
Sayan44 said:
I know Flashify can do that in many devices, I am not sure about ours, I think best way would be to flash it using fastboot.
Click to expand...
Click to collapse
Why not via TWRP itself? TWRP has a feature to flash an .img directly to boot or recovery.
Sent from my ASUS_Z00AD
I am on 2.8.7.3. I am thinking to flash cm13. Is it necessary to update twrp? Or I can flash cm13 using my old one?
Sent from my ASUS_Z00A using Tapatalk
rex_perfect said:
Marshmallow recovery can be used to flash lollipop Rom...??..and vice versa...??
Click to expand...
Click to collapse
Pretty much, LP version is stable and works for flashing M ROMs.
Sent from my ASUS_Z00A using Tapatalk
espeon said:
This is a bit wonky with device encryption. It'll boot the recovery without a theme loaded and ask for my pattern (as expected). I'll put that in and it'll decrypt and mount storage, then the "put in your pattern" prompt comes up again (this time, with my twrp theme loaded). I can cancel that prompt just fine and it'll sit on the main screen and I can proceed from there, so it's not a showstopper at least.
This didn't happen on 2.8.7.3.
edit: on flashing opengapps 6.0 micro, I'm warned that the recovery is missing the xz binary and can't flash the zip (and told me to update to the latest recovery for my device, lol). I'll upload the generated log shortly.
edit edit:
Code:
# Begin Open GApps Install Log
-----------------------------------------------------------------------------
ROM Android Version | 6.0
-----------------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: The installer detected that your recovery does not support
XZ decompression. Please update your recovery or switch to another one like TWRP.
# Begin User's gapps-config
# End User's gapps-config
Fortunately, flashing my L-gapps seems to have worked fine (...seeeeeems to. I'll see if it works. The setup app did at least update itself, so there's that.)
Click to expand...
Click to collapse
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
So what's the difference of this TWRP and TheSSJ TWRP?
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
The 2nd one happened after I decrypted; I forgot to mention that. I don't think it actually happened when I was encrypted using the L-based recovery (I upgraded my recovery, then decrypted, then tried flashing the rom + gapps)
Thread moved to proper forum
jrior001 said:
Will look into both issues, I am encrypted currently but without a pin/pattern and don't have that issue.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Heavybullets said:
Having the same issue actually, not encrypted, worked on .3 no pin or lock on screen either. Happened trying to install the latest Gapps package.
Click to expand...
Click to collapse
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Heavybullets said:
ended up fastboot installing the recovory, didnt work, factory reset, then try it, didn't work, fixing permissions, all that, nothing has worked for me, the latest .4 twrp still comes up with that "The installer detected that your recovery does not support
XZ decompression." Error.
Click to expand...
Click to collapse
well yeah when you have a missing binary reflashing it probably isn't going to do anything, assuming it didn't get corrupted
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
DOWNLOAD: Fixed....
Things that are different from official build:
fixed wrong theme color in screenshots on OP6.
Add support for QCOM haptics vibrator. (fixed vibration)
BUGS:
mtp (causes kernel panics) (can add a test build if needed)
flashing aroma packages
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDAevDB Information
[RECOVERY][enchilada] TWRP 3.2.3-0 Touch Recovery [UNOFFICIAL]
Contributors
Joemossjr
Dees_Troy
wuxianlin
@notsyncing on github for the fixes
Source Code: Github
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-07-07
Last Updated 2018-08-01
Donation Link: Buy this man a beer
Thanks for this. Add the version that supports MTP. Will test and let you know!
It's definitely bugged lol but I'll add it tomorrow
Thank you very much!
joemossjr said:
It's definitely bugged lol but I'll add it tomorrow
Click to expand...
Click to collapse
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
xXx said:
I'm working with your 3.2.1 version since the beginning and except aroma absolut everything is working. Never had any issue with MTP. Always worked stable so far. I did countless restores and all worked flawless even with swipe code in place.
So thanks very much to provide us with the very first working TWRP for the OP6.
Regarding aroma support, would you agree to my feeling that this is not an issue to be solved in the twrp framework but probably being a bootloader or firmware issue?
Click to expand...
Click to collapse
I'll be getting logs tonight while flashing an aroma package to see what's needed lol I feel like it's something simple but we will see. Thanks for the support everyone I do this on my free time lol I'll post the mtp enabled here shortly
mtp has been added to the downloads folder and is specified in the name!
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
thanks, very much appreciated :highfive:
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
Yes I have tested it and can confirm it's working. Just make sure you unmount mtp and remount it before attaching the USB cable (thanks to @DocRambone for the tip)
DocRambone said:
Simple temporary fix to avoid kernel panic on mtp:
Do not connect usb cable
Toogle unmount mtp, wait few second and enable mtp again in mount menu in recovery. Connect usb.
Click to expand...
Click to collapse
This works, thanks!
It's not working for me both new versions. Boot looped.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
mbr007 said:
It's not working for me both new versions. Boot looped.
Click to expand...
Click to collapse
Did you remember to flash magisk after reboot into twrp?
lollyjay said:
Did you remember to flash magisk after reboot into twrp?
Click to expand...
Click to collapse
Yeah you have to flash magisk if you already had it flashed before hand
joemossjr said:
mtp has been added to the downloads folder and is specified in the name!
Click to expand...
Click to collapse
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Can you add another mirror like androidfilehost please? Unable to access google drive...
xXx said:
I just flashed your new mtp enabled zip version and screen brightness went down considerably even it's on 100% already. Does anybody know a workaround to get it brighter again?
Click to expand...
Click to collapse
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
adiher said:
Seems to be a general problem. I've the same, but not only with this version of TWRP, also with the original version.
It starts by me sometimes flashing 3.2.1.0 if i remember right and I never found a solution to get the screen brightness full back again ?
Click to expand...
Click to collapse
I can make a new build that's higher
joemossjr said:
https://github.com/opengapps/opengapps/issues/493
seems like its a dead issue at the moment on twrp. aroma hasnt been updated in a while. I am in contact with a dev who may know how to fix it. Stay tuned
Click to expand...
Click to collapse
Could this have anything to do with why aroma isn't working?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
From the magisk 16.6 change log.
Note to ROM Developers
If you are embedding Magisk Zip into your ROM, and your ROM uses Aroma Installer, please be aware that on some devices (most likely Samsung devices), it is possible that the installation process of Magisk could break Aroma. Please test flashing your ROM zip before releasing to your users. If you found out you are the few unfortunate devices, unzip the Magisk zip, and do the following changes and re-zip the installer:
Code:
# Remove or comment out these 2 lines in META-INF/com/google/android/updater-script eval $BOOTSIGNER -verify < $BOOTIMAGE && BOOTSIGNED=true $BOOTSIGNED && ui_print "- Boot image is signed with AVB 1.0"
The reason why Aroma Installer breaks is unknown. Maybe consider letting the project that's abandoned for nearly 5 years go?