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.
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
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Sony Xperia T (mint)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
For stock rom:
http://forum.xda-developers.com/showthread.php?t=2657190
Click to expand...
Click to collapse
XDA:DevDB Information
[mint][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia T
Contributors
Phil3759, DooMLoRD, [NUT]
Version Information
Status: Stable
Created 2014-03-29
Last Updated 2014-03-29
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
This rules that this has been ported, as I use the PhilzTouch on my Galaxy Tab2. I even donated a few $$ to him!
One question, with the shared kernel "feature" of the T, how did you avoid having it revert back to stock CWMrecovery anytime one flashes a new ROM?
Regardless, I'll try this out tonight.
Hey i always wanted this to get ported! Im using the leaked 4.3 rom and it does work but it only boots into the recovery everytime. Is this a bug or is there a way to fix this?
hhamzah49 said:
Hey i always wanted this to get ported! Im using the leaked 4.3 rom and it does work but it only boots into the recovery everytime. Is this a bug or is there a way to fix this?
Click to expand...
Click to collapse
It will be repacked into other kernels later...
Sent from my C6902 using xda app-developers app
So how do I go about installing this?
Is it as simple as boot the "T" into flashboot mode and running
fastboot -i 0xfce flash boot philz_touch_6.09.3-mint.img
But I'd rather not blow away my phone if this is wrong.
Can I use this for the xperia V, too ?
alex m. said:
Can I use this for the xperia V, too ?
Click to expand...
Click to collapse
No
Sent from my LT30p using Tapatalk
Is there a trick to using PhilzTouch on the T to avoid the shared kernel?
I installed it via "flashboot boot philz.img" and at first glance, it seems to work the same as on my Galaxy Tab 2.
But then it turns out that its not really useable.
a) I was unable to boot back into my normal ROM. Rebooting always brought it back to PhilzTouch.
b) Even if I could have found a way to boot my phone, it turns out that PhilzTouch recovery was overwritten by the stock recovery as soon as I installed a newer CM nightly which I tend to do nightly.
hi all
can i use for TX ? do i need UL or not ? thanks
How to install this recovery?
fastboot flash boot boot.img gives me each time a reboot in recovery
fastboot flash recovery boot.img gives me an error.
Anyone got this working?
Sent from my Xperia T using xda app-developers app
Thanks alot! Used it to get root on the new 4.3 update:good::good:
silasje1 said:
Thanks alot! Used it to get root on the new 4.3 update:good::good:
Click to expand...
Click to collapse
Would you please share how you did it? A how-to would be great including which ROM you came from and all the steps in clear chronological order.
zilboris said:
Would you please share how you did it? A how-to would be great including which ROM you came from and all the steps in clear chronological order.
Click to expand...
Click to collapse
You need Unlocked Boatloader at first!
1. install the 4.3 rom (any you like). Flashing the FTF with everything included
2. Flash this CWM recovery and install SU zip
3. flash FTF and exclude all except KERNEL.
Done! (limited time to write so made it short)
@Phil3759
@steveboss is reporting an extremely sensitive touch interface, is there any way you can confirm it is working out of the ordinary?
[NUT] said:
@Phil3759
@steveboss is reporting an extremely sensitive touch interface, is there any way you can confirm it is working out of the ordinary?
Click to expand...
Click to collapse
I need video of this "extremely..."
Phil3759 said:
I need video of this "extremely..."
Click to expand...
Click to collapse
Hello, I send you video tomorrow
@steveboss where's the video?
@Phil3759
I'm having trouble to get philz to recognize the internal sdcard partition (its a real partition, not part of userdata)... what ever I try, it just keeps failing...
Do you have a possibility to build philz based on the CM10.1 or the freexperia 'jellybean' repo for this device?
I'm starting to suspect the CM10.2 repo might contain some issues as it was put together with pure CM in mind, which might make it incompatible with the stock sony JB4.3 kernel...
The Xperia T made a jump from JB4.1.2 to JB4.3 in one step up, receiving it only a month or so ago, while the CM10.2 repo has been around for far longer...
The 'original' locked bootloader package has made the same jump up recently and CWM started causing problems for it's users too.
[NUT] said:
@steveboss where's the video?
Click to expand...
Click to collapse
I`am sorry, I don`t have any camera now, maybe at weekend
[NUT] said:
@steveboss where's the video?
@Phil3759
I'm having trouble to get philz to recognize the internal sdcard partition (its a real partition, not part of userdata)... what ever I try, it just keeps failing...
Do you have a possibility to build philz based on the CM10.1 or the freexperia 'jellybean' repo for this device?
I'm starting to suspect the CM10.2 repo might contain some issues as it was put together with pure CM in mind, which might make it incompatible with the stock sony JB4.3 kernel...
The Xperia T made a jump from JB4.1.2 to JB4.3 in one step up, receiving it only a month or so ago, while the CM10.2 repo has been around for far longer...
The 'original' locked bootloader package has made the same jump up recently and CWM started causing problems for it's users too.
Click to expand...
Click to collapse
Look at the fireball device repo (fstab file) to use vold with real sdcard partition
Else use compatibility recoveryonly option in fstab with real blk device path
Phil3759 said:
Look at the fireball device repo (fstab file) to use vold with real sdcard partition
Else use compatibility recoveryonly option in fstab with real blk device path
Click to expand...
Click to collapse
ooh, that could be the trick :cyclops:
Thanks for the hint :good:
I'll update you once I know if it works or not.
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
Official Thread will be soon up! Head over there guys.
This thread is dead!
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on CyanogenMod so use custom kernels compatible with them!
A special thanks to @forkbomb444. crDroid is available thanks to him. I'm using his devices, kernel, proprietary vendor and many other repos to build
All the source code for crDroid is available in the Github
repo. And if you would like to contribute feel free to pull a request.
Kernel features beyond CyanogenMod ones (Work in Progress) [Future Release]
• Boeffla Charging Control
• Boeffla Sound.
All this can be initiated through some script knowledge.
INSTALLATION METHOD
First time installing crDroid to your I9300, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Flash GApps zip
-Note: Flash ROM and GApps together or else you'll have a hard time.
- Flash SuperSU (not mandatory. We have
CyanogenMod su access inside)
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore Apps using Titanium Backup!
Upgrading from earlier version of crDroid:
- Copy crDroid ZIP to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Reboot
Download Link:
https://www.androidfilehost.com/?fid=24415232478677728
GApps: opengapps.org
Full support
https://plus.google.com/communities...4243234a-de8a-4262-bd30-68582ebeb472?hl=pt_br
Don't expect any support if you
- are not running stock crDroid-kernel
- have installed any mods such Xposed!
- have modified system files
Special thanks:
- Google
- CyanogenMod
- @forkbomb444
- @temasek
- @Darkened_Sky
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
Source: http://www.github.com/cyanogenmod
https://github.com/crdroidandroid
Reserved 1 (Screenshots)
Someone please share some screenshots!
FAQ
Do read this before asking questions!
1. Q: How do I get root?
A: Enable it in developer options.
2. Q: But can I use SuperSU instead of the built-in SU?
A: Sure. Make sure that the built-in SU is disabled in developer settings. Afterwards flash SuperSU. By default after a clean flash built-in SU is disabled, so you can also directly flash SuperSU after a clean flash
3. Q: Which gapps do I need?
A: This ROM is based on CM13/Android 6.0x/Marshmallow. Therefore choose your gapps accordingly. If you want to use the recommended opengapps, choose the ARM 6.0 version. I highly suggest to use either the pico or the nano package. All other gapps can later still be installed via playstore!
4. Q: Help! I have a problem/issue/bootloop/....?
A: Please follow these steps:
1. Make sure that the problem is not already mentioned in either this thread or in the CM13 thread.
2. Make sure that you can reproduce the problem on your device with absolutely no additional modification and after a clean flash. This includes being on stock kernel, no xposed, no SuperSU, no theme!
3. Try to replicate the problem on official CM13. If it appears there, please ask there.
4. If your problem couldn't be solved with above steps, post here, with an exact description of how to reproduce and if possible with logs.
5. Q: Is xposed working?
A: Yes but make sure to use the latest and the correct version for Marshmallow. Inform yourself in the xposed thread. Everything is clearly explained there which version you need. The version that works for you on official CM13 will also work here.
6. Q: Can I use custom kernels?
A: Yes. Users which use SuperSU frequently report problems with bootloops after flashing a custom kernel. Therefore I'd suggest to use built-in SU.
7. Q: I have added files to my system, but after each ROM update they disappear?
A: Yes during a flash the /system partition is wiped.
yess i'v ben waiting for this rom to get MM
ayoubadri said:
yess i'v ben waiting for this rom to get MM
Click to expand...
Click to collapse
What you waiting for? Give it a try
nice new rom for s3 thinks Dev
spide3 said:
nice new rom for s3 thinks Dev
Click to expand...
Click to collapse
Download and Flash! Enjoy
P.S: I am not the developer of this ROM! I have just created this thread. Though I can do a bit of coding. So, for all bootloops or random reboots I need proper information
sunny1234590 said:
P.S: I am not the developer of this ROM! I have just created this thread. Though I can do a bit of coding. So, for all bootloops or random reboots I need proper information
Click to expand...
Click to collapse
ROM is awesome, but i havenot mobile data... cellular radio working, i have reception but i havenot mobile data. APN is right. GT-I9300
jujuna said:
ROM is awesome, but i havenot mobile data... cellular radio working, i have reception but i havenot mobile data. APN is right. GT-I9300
Click to expand...
Click to collapse
No bug on my device. Using stock kernel?
Are you maintaining this ROM now?
sameer23 said:
Are you maintaining this ROM now?
Click to expand...
Click to collapse
I have opened this thread on the behalf of the original developer but yes, I'll keep it updated with new builds. So, kind of Yes!
sunny1234590 said:
No bug on my device. Using stock kernel?
Click to expand...
Click to collapse
my kernel is 3.0.101-CM-gbe3d845 [email protected] #1 << is it a stock?
jujuna said:
my kernel is 3.0.101-CM-gbe3d845 [email protected] #1 << is it a stock?
Click to expand...
Click to collapse
Yes, it is stock. Try a clean flash and report back!
Do you face this issue on official CM13 also?
sunny1234590 said:
Yes, it is stock. Try a clean flash and report back!
Do you face this issue on official CM13 also?
Click to expand...
Click to collapse
yes, on Official CM13 i had this proble. only AICP marshmallow rom i havenot this problem. crDroid, bliss, an etc i have this problem. my installation was clean 100%.
jujuna said:
yes, on Official CM13 i had this proble. only AICP marshmallow rom i havenot this problem. crDroid, bliss, an etc i have this problem. my installation was clean 100%.
Click to expand...
Click to collapse
I see! Can you tell me which baseband version you have?
And it's strange considering the fact that AICP is also based on Official CM13 just like crDroid!
sunny1234590 said:
I see! Can you tell me which baseband version you have?
And it's strange considering the fact that AICP is also based on Official CM13 just like crDroid!
Click to expand...
Click to collapse
i know, its weird for me too.. my baseband version is I9300XXEMG4 and IP 192.168.0.100 fe80::237:6dff:fef2:c4a0
jujuna said:
i know, its weird for me too.. my baseband version is I9300XXEMG4 and IP 192.168.0.100 fe80::237:6dff:fef2:c4a0
Click to expand...
Click to collapse
That's a slightly older baseband version if I am correct. Just try to flash the latest baseband and see if it makes some difference though I doubt.
Since, I can't reproduce this error so, it's not a bug for me at least. Someone else must confirm about the mobile data thing.
Hi guys,
I can't give root permission to apps.
I've enabled Developer Options, and enabled Root Access to Apps, but when I try to run an app that needs root, it doesn't ask permissions.
Could you give me a hint?
Thanks
sunny1234590 said:
That's a slightly older baseband version if I am correct. Just try to flash the latest baseband and see if it makes some difference though I doubt.
Since, I can't reproduce this error so, it's not a bug for me at least. Someone else must confirm about the mobile data thing.
Click to expand...
Click to collapse
i flashed but no result
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: https://dl.twrp.me/gts210vewifi
BUGS:
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.
XDA:DevDB Information
[RECOVERY][T813] TWRP 3.3.0-0 Touch Recovery [OFFICIAL], ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337, luca020400, Olivier
Source Code: https://github.com/TeamWin
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2017-01-24
Last Updated 2019-04-15
Wonderful to see this official! Just great!
Flashed!!
It works nicely and looks very good!
Thanks for this beautiful present
link dont work....pls reup...thy
hasbai said:
link dont work....pls reup...thy
Click to expand...
Click to collapse
Is it good now?
yes...the link works...can u make to a TWRP flash mod?
hasbai said:
yes...the link works...can u make to a TWRP flash mod?
Click to expand...
Click to collapse
Flash mod?
Can't you just flash it with heimdall?
sry...i mean twrp zip
hasbai said:
sry...i mean twrp zip
Click to expand...
Click to collapse
Use heimdall or flash the image in twrp ( there's a switch on the bottom I think ).
Hi,
Thanx a lot to bring some love to our Value Edtion :good::fingers-crossed:
Dumb question maybe but when I click on the link it takes me "TWRP for gts210vewifi". Thought this was for the SM-T813 9.7" tablet???
pastorbob62 said:
Dumb question maybe but when I click on the link it takes me "TWRP for gts210vewifi". Thought this was for the SM-T813 9.7" tablet???
Click to expand...
Click to collapse
Yes, that's the codename of it.
Just two things I would like to report:
Brightness level doesn't work. It's always max.
Second, not sure if this is a recovery issue, I made a backup of the stock rom. The rom was pin protected, but after restoring it the pin was not recognized. So I had to reset device in order to use the back up. It erased my sd card too, but I had another external backup up of the data, so it was safe
New twrp!!! Flashing it now!!!
varben said:
Just two things I would like to report:
Brightness level doesn't work. It's always max.
Second, not sure if this is a recovery issue, I made a backup of the stock rom. The rom was pin protected, but after restoring it the pin was not recognized. So I had to reset device in order to use the back up. It erased my sd card too, but I had another external backup up of the data, so it was safe
Click to expand...
Click to collapse
>Brightness level doesn't work. It's always max.
I forgot to fix that yesterday, I'll get that sorted out today ~ https://gerrit.twrp.me/#/c/2078
hmm, maybe I did something stupid here. Flashed the new twrp 3.0.3-2 through twrp and the tablet boots only in twrp now... the only selection I saw on which partition to flash was "boot"... so it boots only in recovery now
varben said:
hmm, maybe I did something stupid here. Flashed the new twrp 3.0.3-2 through twrp and the tablet boots only in twrp now... the only selection I saw on which partition to flash was "boot"... so it boots only in recovery now
Click to expand...
Click to collapse
Oh wow, I forgot to add /recovery to fstab. Thanks for reporting this issue...
LuK1337 said:
Oh wow, I forgot to add /recovery to fstab. Thanks for reporting this issue...
Click to expand...
Click to collapse
So, if I reflash the rom now without wipes, will it be ok to reboot to system?
varben said:
So, if I reflash the rom now without wipes, will it be ok to reboot to system?
Click to expand...
Click to collapse
Yes.
So, for the moment, who wants to flash this needs to use the official twrp app from play store.
https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=en
Edit: @LuK1337 is so fast!!! A new fixed TWRP now! Forget the above...