Database Develop

[MOD] MultiROM (sharing kernel)

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for t705 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/t5peOTA-c84cv - this is modded recovery. flash via odin
2. https://yadi.sk/d/wEbLeriJc84dP - patched stock kernel
https://yadi.sk/d/EXpUO4tTc84db - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/wm-dD6bgc8EZ9 - flash this uninstaller through recovery, then flash original twrp
multirom apk from play store doesnt support this release.

reserved

more reserved

new version has been uploaded
changelog:
- wrong resolution and position on twrp, but usable -FIXED
- in List Roms installed roms dont shown -FIXED
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power) -FIXED

Great to see this for the Tab S, will it get ported to SM-T800?

Hi!
When I try to flash UNOFFICIAL CM like additional I get an error: Error executing updater binary in zip '/tmp/mr_update.zip'.
What am I doing wrong?

I´ve managed to install the latest cm11 build on my sm-705, but wifi doesnt work.
Does someone now how to fix it?

[/COLOR]
svardman said:
I´ve managed to install the latest cm11 build on my sm-705, but wifi doesnt work.
Does someone now how to fix it?
Click to expand...
Click to collapse
do the cellular functions work? calls and mms/sms, data?
thought the cm11 was for t700 wifi only. Odd that wifi does not work (assuming cell data and calls work..that would be strange)

No nothing of those thing works, wifi works IF I install cm 11 as the primary rom, but not if I installs cm 11 as the secondary rom.

svardman said:
No nothing of those thing works, wifi works IF I install cm 11 as the primary rom, but not if I installs cm 11 as the secondary rom.
Click to expand...
Click to collapse
yes that rom is not for the 705.

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.

Is it OK to use this Kernal on the t700 with stock Rom and cm12? I would like to give it a try just not sure.

Hello It is possible to try a multirom for T705 , set primary rom a Sam based rom (with SkyHigh kernel) and secondary CM rom (wifi only T700).
Thank you

Might give this another try.

Leonidas87 said:
Samsung Galaxy Note 4 Dual Boot/multi Rom support: https://youtu.be/CpegzNc4ZH0
Check this out. Trying to get support brought to our tablet.
Click to expand...
Click to collapse
Good luck would really like to see thay on our tab S

Ok everyone we have a new development
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
I got a developer to bring dual/tri/quad boot if you want to our Galaxy tab s 8.4 t700
Fallow the link:
http://forum.xda-developers.com/showthread.php?t=3137677
(MOD) Dual/Tri Boot Galaxy Tab S 8.4 T700

Dual boot patcher
I found this one but I think it's the same thing.
http://forum.xda-developers.com/showthread.php?t=2447534
It works fine on my t700

working with the dev to bring multiboot patcher to TM-800 so we can use touchwiz and cm/aosp roms along side it
already used on my note 4 and works very well:good:

[May 23] Omni Based ROM

Summarized Standard Disclaimer: use at your own risk.
This is a continuation of omni rom from @mcgi5sr2 To make this ROM, I've fetched sources from all across xda from nameless rom for the device specific stuff, to omnirom for the base rom, cyanogenmod for enhancements, and boeffla kernel for kernel enhancements. Very few of the additions are actually mine.
**Notice** This is not official omni for several reasons. It has quite a few cyanogenmod enhancements. The omni team is not fond of cyanogenmod and whether you are or note, you have to admit their additional features are useful. SELinux is disabled (permissive). It has caused me nothing but annoyances since I first installed fedora core 7. It's been more trouble to me than it's worth. If you want it, I will NOT be accepting pull requests for it. Please compile it on your own. On my desktop and laptop, it is fully disabled at the kernel level. (I compile the kernel manually for both to boot without an initial ram disk.)
Cyanogenmod enhancements include:
CM12 File Manager
CM11 Calculator (uglier but much more functional)
CM12 bash shell
CM12 nano text editor
CM12 discontinued Koush su
CM11 forward ported custom host name
CM12 music volume long press music control
CM12 ad hoc wifi detection
CM12 camera power shutter
CM12 open ssh utilities
CM12 trebuchet
CM12 custom app notification light colors
CM12 battery light on/off and custom colors
Boeffla kernel enhancements include:
Back/menu key backlight working and DON'T light up on every screen touch
1.7GHz cpu oc
Undervolting
GPU 5 step
GPU sysfs support
GPU overclocking (by sysfs)
My own personal touches aren't that long:
Jellybean style toasts
Disabled selinux
(Other additions more applicable to P7510 (galaxy tab 10.1 1st gen rom)
Not working / never tested:
Plugging in the charger while off probably causes something weird
Not sure how SuperSU will react since Koush su is built into ramdisk init scripts
First time flashing MY omni 5.1.1
Make titantium backup (highly recommended)
Get twrp
Flash twrp (if not already done)
Reboot into twrp (if flashing twrp)
Make recovery backup (I usually don't)
Full wipe
Format system
Install rom
Install gapps
reboot
install adblocker (very highly recommended)
Subsequent flashes
Install ROM
install gapps
reboot into rom
reapply adblock
The gapps backup recovery isn't run as it caused problems on my other rom at some point so I've never reenabled it since then.
Downloads: https://www.androidfilehost.com/?w=files&flid=31615
Credits:
nameless team (device specific stuff)
Lord Boeffla (kernel enhancements)
Cyanogenmod and omni team (rom)
My github: https://github.com/AAccount?tab=repositories
XDA:DevDB Information
Omni Based ROM, ROM for the Samsung Galaxy S III I9300
Contributors
AAccount
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: Omni, Cyanogenmod
Version Information
Status: Stable
Created 2015-05-11
Last Updated 2015-05-10

FAQ:
Notification LED stays lit after notification has been seen: open quick settings and close it again.
How to get FM working: https://f-droid.org/repository/browse/?fdfilter=spirit&fdid=fm.a2d.sf
I hate youtube app ads: get xposed and xposed youtube ad blocker.

Reserved #2

Nice. Since you've included some of boeffla kernel enhancements, do you have plans to add boeffla sound?
Great work btw. ??

myshakugan said:
Nice. Since you've included some of boeffla kernel enhancements, do you have plans to add boeffla sound?
Great work btw.
Click to expand...
Click to collapse
I think the stock nameless kernel already came with it.

AAccount said:
I think the stock nameless kernel already came with it.
Click to expand...
Click to collapse
Ah, cool. I'll try it out as soon as I get some free time. ?

Will try ASAP, Boeffla sound would be a hell of a good thing, as personally, the only thing which makes me kinda off CM12.1 is the lack of CM12.1 NG Boeffla's kernel ^^
(Greetings to lord boeffla and you anyway )

OxygeenHD said:
Will try ASAP, Boeffla sound would be a hell of a good thing, as personally, the only thing which makes me kinda off CM12.1 is the lack of CM12.1 NG Boeffla's kernel ^^
(Greetings to lord boeffla and you anyway )
Click to expand...
Click to collapse
Um...just fyi, there is cm 12.1 ng boeffla kernel. Here: http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm-ng/cm12.1_download/Test/

Supplied kernel comes with boeffla sound.

Want to give it a try but have to ask first, no theme manager?

Cool stuffs.
Looks to me that you've made the right choices in building.
nameless kernel ensures compatibility with existing custom kernels. As well as being the most functional stock kernel (but that;s just a guess)
DSP Manager FTW (no audioFX bs)
All hail apollo. so much simpler that that new CM thing
CM file manager. That's a solid file manager.
And so on.
I always loved omni more than CM, stability/speed wise (feature wise, CM wins). But i changed from Omni to CM with Archidroid. This makes me wonder how omni is performing now.
Just out of curiosity, when we flash a custom kernel like AK or Boeffla, we would be able to toggle Selinux right? Or did you exlude all selinux rules from your rom?

RoelD92 said:
Cool stuffs.
Looks to me that you've made the right choices in building.
nameless kernel ensures compatibility with existing custom kernels. As well as being the most functional stock kernel (but that;s just a guess)
DSP Manager FTW (no audioFX bs)
All hail apollo. so much simpler that that new CM thing
CM file manager. That's a solid file manager.
And so on.
I always loved omni more than CM, stability/speed wise (feature wise, CM wins). But i changed from Omni to CM with Archidroid. This makes me wonder how omni is performing now.
Just out of curiosity, when we flash a custom kernel like AK or Boeffla, we would be able to toggle Selinux right? Or did you exlude all selinux rules from your rom?
Click to expand...
Click to collapse
Flashing any custom kernel that changes the ram disk will break root. The root startup daemon is started by an init script. I don't remember touching any of the policy files but they haven't been updated since I forked the nameless repo. I would have to say it's "try at your own risk".
Also, 1 thing I forgot to put on the first post is that the CM12 custom notification light colors per app has also been ported.
----------------------------------------------Added--------------------------------------------------------
And yes no theme manager. I didn't try to port it. I first saw the theme manager in CM7.2 but never really used it.

AAccount said:
Flashing any custom kernel that changes the ram disk will break root. The root startup daemon is started by an init script. I don't remember touching any of the policy files but they haven't been updated since I forked the nameless repo. I would have to say it's "try at your own risk".
Also, 1 thing I forgot to put on the first post is that the CM12 custom notification light colors per app has also been ported.
----------------------------------------------Added--------------------------------------------------------
And yes no theme manager. I didn't try to port it. I first saw the theme manager in CM7.2 but never really used it.
Click to expand...
Click to collapse
It have layers support but no cm12 theme engine

Boot loop for me

Got also BootLoop when optimizing Apps...

Does this rom support 240 DPI resolution ?
(even changing this value in build.prop won't cause weird issues ? )

just booted it thanks . for the rom !! will see how it reacts

DaksAnkit said:
just booted it thanks . for the rom !! will see how it reacts
Click to expand...
Click to collapse
How? I mean did you flashed custom kernel?

HammDefy said:
Got also BootLoop when optimizing Apps...
Click to expand...
Click to collapse
Yep; same thing happened to me.

Here is what i did !
sameer23 said:
How? I mean did you flashed custom kernel?
Click to expand...
Click to collapse
I M ASSUMING YOUR PHONE IS ROOTED ! RIGHT ....
so .
i flashed stock rom of s3 through ODIN ,
then i flashed TWRP recovery ".tar " file also through ODIN .
then installed the .zip files of this rom on my sd card ,
entered into TWRP recovery mode ,
deleted DATA - DALVIC - CACHE
installed from sd storage ..
flashed it . then LP .GApps . ..
Rebooted .
and thats it i didn`t encountered any failures .
If you did ? well i will recommend flashing Stock rom n then trying this one with twrp:good::good:

[MOD][23 MAY] MultiROM v32

Hello guys!
After learing a lot from these great devs arround here i decided to start to try out a new project! Multirom!!
You might or might not have heared of it, THE multi-boot mod for the Nexus 7. I found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot.
Links
You can find everything at https://www.androidfilehost.com/?w=files&flid=32204.
multirom-20150521-v32-UNOFFICIAL-p880.zip : The multirom zip
CM12_Kernel_Patched.zip : CM 12 Kernel with Kexec-Hardboot Patch ; Thanks to @Adam77Root the patch and @laufersteppenwolf for building Kernel
multirom_uninstaller.zip : Selfexplaining
Known Bugs
-Reboot to recovery doesn't work.
-UI has some graphical bugs
-Double Press to boot Secondary Rom doesnt work -> Press twice on the Rom you want to boot and press Powerbutton at the same time till you recoginze a vibration
-You tell me more
Changelog
23 May 2015: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@Adam77Root for Thread Content
XDA:DevDB Information
[MOD][23 MAY] MultiROM v32, Tool/Utility for the LG Optimus 4X HD
Contributors
fritzcola
Version Information
Status: Testing
Created 2015-05-23
Last Updated 2015-05-24

Explanation
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share kernels if you are on the same Android version for example 5.0.x!
Source Codes:
Tree

Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved

CrazyWinner said:
Any screenshot? I didn't understand the ui bugs. What are they ? Great work fritzcola I will install my device when ui bugs are solved
Click to expand...
Click to collapse
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0

fritzcola said:
Look here! https://www.dropbox.com/s/whor0zf6xx7z4jh/VID_20150523_234854.mp4?dl=0
Click to expand...
Click to collapse
Ow it's no problem for me Installing now , great work !

thanks
its work good

HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks

mater2 said:
HI @fritzcola i have this bugs
after flash kernel
system ui has stopped on Euphoria rom
sim internet not work on ResurrectionRemix+BlissPop rom
some rom need to disable sim (plane mod )or it got bootloop from home screen PAC-ROM LP rom
work before but now i have this.
many times when add lolipop rom in multiboot i get error
blkdiscrad faild: operation not supported on transport endpoint
e:error executing updater binary in zip '/tmp/mr_update.zip
faild to install zip
thanks
Click to expand...
Click to collapse
That error with executing bla bla bla is rom related!

I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk

gugu6897 said:
I already have TWRP 2.8.6.0 installed. To use your MultiROM Mod do I just need to flash MultiROM zip? Or do I need to flash recovery img (I found in your link)?
Will the uninstall zip send me back directly to the Stock TWRP 2.8.6.0?
__________________________________________
It works. But I'm getting the same problem as @mater2.
"error executing updater binary in zip '/tmp/mr_update.zip";
I tried latest BlissPop 3.4 and Euphoria 1.1.
If it is ROM related how can we solve it?
I saw some users reporting the same problem with the Nexus 5. They said the problem was on the "updater-script" of the ROM.
Thanks for your work and attention.
Enviado de meu Optimus 4X HD usando Tapatalk
Click to expand...
Click to collapse
1. Create backup from primary rom
2. Wipe everything and install rom you want as secondary as primary
3. Make backup from Primary you want to have as secondary
4. Use option to add rom to MR with Backup
5. Restore backup from old Primary

Are iodak and werewolf supporting multirom ?

@fritzcola
@gugu6897
strange thing its work for me all roms i can multiboot after some days and try some roms except euphoria because its not work with patched kernal after that
the error Shows up i try to format every thing internal +cache+davlik
doesn't fix that .
its allow to add 4.4.4 or 4.1.2 rom but 5.0x didn't
thanks for your good work

CrazyWinner said:
Are iodak and werewolf supporting multirom ?
Click to expand...
Click to collapse
I tried Werewolf kernel. The answer is no [emoji17].
Enviado de meu Optimus 4X HD usando Tapatalk

@gugu6897 @CrazyWinner
the kernel in this post (patched kernel) only can used for multiboot.
when use patched kernel
maybe you will have bug with sim internet with all roms except blissbob.
every thing else work good

@CrazyWinner, looks like iodak (and mourta too) has kexec-hardboot, but my secondary ROM (MIUI v5) don't boot. I double tap it, but the device just power off.
Does someone know any ROM that works with MultiROM?
Enviado de meu Optimus 4X HD usando Tapatalk

Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app

fritzcola said:
Look at Known Bugs in post #1
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I forgot about that [emoji28].
Enviado de meu Optimus 4X HD usando Tapatalk

progress
is it 'save' and will you update this anytime soon??

an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing

Extractor 2.4 from @Alexey71
derders said:
an update to MultiROM v33 - MultiROM TWRP 3.0.0-1 would be amazing
Click to expand...
Click to collapse
+1
I just discover the win tool Extractor 2.4 from @Alexey71 , as I didn't succeed to get finish compiling mmb 5.1.1.37 (or 29), I played with @csk1jw 2xAosp LP &MM system.new.sdat:
http://forum.xda-developers.com/showpost.php?p=57742855&postcount=42
extraction + re-zip(boot.img+file_contexts +/system/) in @laufersteppenwolf Nameless 5.1.zip + twrp’ add 2nd multirom + reboot and IT JUST WORKS!
I can now multiboot, WITH Nameless 5.1 AS PRIMARY: mmb 5.1 as 2nd+
cm11+OEMlg JB (+ BlisspopLP+ crdoidLP).
Many thanks to native kexeced Nameless’ kernel for LP!
Unfortunately’ the re-zipped aosp MM did not boot (boot.img conflict? or primary slot required with kexec.. or I miss more).
I believe there won’t be any future update on mmbLP, so it will be good if, @csk1jw or @MoltenMotherBoard or @streambinder could make an old_fashion-zipped official ultimate edition to be used with gorgeous @fritzcola ’ multirom 2.8.6 .
Also if they explain me how to bake it, patched with microG, i try wakelockblocker's patch for a better battery control in ‘pure’ FLOSS.
I still hope that, in this combination, some could give a try to my infamous nightly-cm11+3; while waiting for a snappy MM snapshot...
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Basics multirom tips;
-If you think something is wrong, like battery drain or excessive reboot: in twrp menu go to advanced menu then fix permissions and re-flash multirom32 on primary rom before rebooting;
-Always use ext sdcard for twrp’s copy-backup and avoid using twrp’s File Manager to restore, otherwise they could be buried and waste your mem until a complete re-format; if needed: boot in primary rom (or install a rom ZIP!) and copy them to sdcard/twrp/backup/IdDevice… with your favorite apk.
-For better efficiency use native kexeced Nameless 5.1 for primary rom.
Actually I don’t know if mmb5.1 is 100% compatible with @laufersteppenwolf ‘s Nameless 5.1_kernel.
Be aware that the smell of night roasted marshmallows is scientifically attracting werewolves.

[ROM][P31xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project

Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!​
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P31xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30

Wow! Andi!

Nice to see that AOSP Lollipop came to us again! Great work dev, @Android-Andi ?
Sent from my GT-P3100 using Tapatalk

Amazing, pure LP AOSP for my tab 2.
I really appreciate it...

Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk

Bhaskara Rao said:
Is f2fs in Cache and Data supported in this ROM?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
No, sry. Think it needs quite more changes than i would like to add... But i will take a closer look next time

Wow, this is awesome. Now I need to see if I can port Layers on top. Thanks Andi!!!
Sent from my Nexus 6 using Tapatalk

Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.

Bhaskara Rao said:
Thank you, Andi for the latest AOSP. No issues on clean installation. ROM is fluid. YouTube is not working. Logs attached.
Click to expand...
Click to collapse
Thanks buddy I'll look into it next week, have some more time then

Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.

ilyichspb said:
Clean install of latest AOSP (aosp_p3110-20150807.zip) with Dhollmen 3.0.101 kernel.
Youtube is working, but 720P videos do not work.
Click to expand...
Click to collapse
Hey bruh @ilyichspb i also want to flash my kernel
I have tried but i softbricked my tab.
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Aosp is smooth and lagfree.great work Andi.:fingers-crossed::good:

AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Sent from my GT-P3100 using Tapatalk

[email protected] said:
So,it will be great if you tell me the steps to flash a kernel.:laugh:
Click to expand...
Click to collapse
full wipe
install (via CWM)
AOSP
kernel
gapps
reboot
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
Bhaskara Rao said:
AFAIK Dhollmen Kernel doesn't have a fix for emmc bug. Only Android-Andi's ROMs and Recoveries have it. Take an informed decision before flashing custom kernels.
Click to expand...
Click to collapse
Looks like you are right. I will keep an eye on that. So far everything is working fine.

Seems like google went to nightly builds, r12 source released

Thanks!, will try soon

What is the recommended recovery to install this rom. I'm still running old ketut's stock rom. Thanks

Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk

Bhaskara Rao said:
Android-Andi's latest TWRP.
https://www.androidfilehost.com/?w=files&flid=25704
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why

[email protected] said:
Whenevr i go to recovery i.e,twrp wipe>advance wipe>change system partition
Twrp says invalid partition select
I have tried this in both android andi's twrp and official twrp
I'm on p3100.
What to do.need help:victory:
I want to flash a rom withf2fs support thats why
Click to expand...
Click to collapse
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.

Android-Andi said:
AOSP doesn't support f2fs.
About f2fs: take my twrp with "f2fs" in it's name. If you have more question about recovery then use the recovery thread pls.
Click to expand...
Click to collapse
Sorry! I got the sol of my problem
i didnt select cache and data before tapping on change partition
One question
Does Your latest recovery i,e. 2.8.7.1 supports f2fs.
i want to post this in recovery thread but xda said that u have less than 10 posts

Zenfone 2 Recoveries [Z00A[[Z008][Z00D][TWRP][CM-RECOVERY]

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