Database Develop

Kali Nethunter For Lollipop [CM12S] [Updated] - ONE Themes and Apps

Kali Nethunter For Lollipop
I am not the developer of that system I am only compiled it but thanks to the original developers
(Offensive Security , Binky Bear, Render kernel Developers)
My last thread I had a buggy system (Camera & alot FCs)
but with this update I hope most of the bugs are fixed and MultiBoot is Working
Instructions
( 1 ) Try to have the CM12S (YNG1TAS2I3) rom, I dont tried on nightly updates (update me on that)
( 2 ) Download the Rootfs and the Kernel Zips
( 3 ) Go to recovery (TWRP Recommened) and flash first the Rootfs (Take 30 Min) then the Kernel.​ * Works with MultiRom if you dont want it on your Primary rom
( 4 ) Wipe Davlik & Chache then boot and wait about 3-5 minutes then you have working kali
Downloads​Rootfs​ Kernel​
Screenshots
Sources​Kali Nthunter - https://github.com/offensive-security/kali-nethunter
Kernel, Patches and External Drivers- https://github.com/binkybear
Kernel - https://github.com/RenderBroken/msm8974_OPO_render_kernel
xda Thread - http://forum.xda-developers.com/oneplus-one/orig-development/kernel-render-kernel-t3051518​

Great stuff, much appreciated!

is it same as the one version 1.21 in the offciail website?
or its compiled by u also
https://www.offensive-security.com/kali-linux-nethunter-download/

Its compiled from the latest sources with version 1.21

oh thats great!
i already have cm12s on my primary rom with miui6 and hydrogen os on secodnary
does this work only on cm12s rom and not on other lollipop roms?
if not in that case i have to flash cm12s again to secondary then flash the net hunter files right as i wish to flash it to secondary rom..wondering if its fully supported on multirom.
anyway thanks for this post
keep it updated

Multiboot working good the screenshots I took from secondary CM12s with nethunter
about other roms I dont belive it will work because its based on render kernel for cm12s

Shapi300 said:
Kali Nethunter For Lollipop
I am not the developer of that system I am only compiled it but thanks to the original developers
(Offensive Security , Binky Bear, Render kernel Developers)
My last thread I had a buggy system (Camera & alot FCs)
but with this update I hope most of the bugs are fixed and MultiBoot is Working
Instructions
( 1 ) Try to have the CM12S (YNG1TAS2I3) rom, I dont tried on nightly updates (update me on that)
( 2 ) Download the Rootfs and the Kernel Zips
( 3 ) Go to recovery (TWRP Recommened) and flash first the Rootfs (Take 30 Min) then the Kernel.​ * Works with MultiRom if you dont want it on your Primary rom
( 4 ) Wipe Davlik & Chache then boot and wait about 3-5 minutes then you have working kali
Downloads​Rootfs​ Kernel​
Screenshots
Sources​Kali Nthunter - https://github.com/offensive-security/kali-nethunter
Kernel, Patches and External Drivers- https://github.com/binkybear
Kernel - https://github.com/RenderBroken/msm8974_OPO_render_kernel
xda Thread - http://forum.xda-developers.com/oneplus-one/orig-development/kernel-render-kernel-t3051518​
Click to expand...
Click to collapse
Does camera works with 4k video and slow mo

Shapi300 said:
Multiboot working good the screenshots I took from secondary CM12s with nethunter
about other roms I dont belive it will work because its based on render kernel for cm12s
Click to expand...
Click to collapse
Thanks for your work!
Tried it with katinatez CM12.1 temasek build and it didn't boot, propably because of the kernel, was just stuck in a bootloop, tried 2 times and waitet about 20 min each time. I also reflashed it each time and used multirom, i also made sure that cm12.1 succesfully booted before flashing nethunter.
Could/would you make a compatible build?

serialhacker said:
Does camera works with 4k video and slow mo
Click to expand...
Click to collapse
Honestly, if you know what Nethunter is used for, you wouldn't be interested in the camera... Well, maybe script kiddies would...
Anyway, camera works fine.

Even I bootlooped.
Tried on OwnRom. I'll try with CM12 later.

Does this rom work in multiboot with Exodus Rom as primary?

Got the ROM up and running, with multiRom. I was just wanting to know what external wifi card you use. I using a TL-WN821N and the light it on but it just loops the selection process in Wifite.

arunjitoberoi said:
Even I bootlooped.
Tried on OwnRom. I'll try with CM12 later.
Click to expand...
Click to collapse
Follow the instructions! It's for CM12S, not OwnRom and/or CM12.
Midzuel said:
Does this rom work in multiboot with Exodus Rom as primary?
Click to expand...
Click to collapse
Yes.
dbaler said:
Got the ROM up and running, with multiRom. I was just wanting to know what external wifi card you use. I using a TL-WN821N and the light it on but it just loops the selection process in Wifite.
Click to expand...
Click to collapse
I'm using TPLINK TL-WN722N. Works great.

Gamm86 said:
Honestly, if you know what Nethunter is used for, you wouldn't be interested in the camera... Well, maybe script kiddies would...
Anyway, camera works fine.
Click to expand...
Click to collapse
i know wat net hunter is used for, If i needed it solely for that purpose, i would have choose other alternative's.
Anyway i would like to utilize the camera, and don't want multi roms's

Just installed and it's working perfectly, however having difficulty rooting it at this point.

E:error opening /data/local/nhsystem/kali-armhf/dev/ram12
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram14
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram16
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram10
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram13
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram15
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/loop6
E:error: Not a directory
E:error opening /data/local/nhsystem/kali-armhf/dev/ram4
. this shown during all procedures in twrp , how to clear it ?

I i found my answer, what i did was
I delete nhsystem folder in roor data/local/nhsystem
Everything was fine.

Unable to download Rootfs and kernel files mentioned above

Download links
Can anybody help me.... post download links for Rootfs and kernel files mentioned in this site...
Thanks in advance...

Surya786 said:
Can anybody help me.... post download links for Rootfs and kernel files mentioned in this site...
Thanks in advance...
Click to expand...
Click to collapse
Does anybody even still have this version anyway?lost mine in HD failed, lol ate a lot of files.

Related

Earlier, I have been compiling several ROMs for the galaxy tab (P7510/p4wifi) based on KitKat 4.4. I now decided to move over to OMNI ROM as base: http://omnirom.org/
The nice thing of OMNI in my personal opinion is smoothness: it is relatively low in features, but at the same time it is not that resource hungry as some other ROMs. The end result is a smooth ROM.
Changelog of 15-Feb-2014
-Omni codebase of 14-Jan
Several small fixes, nothing spectecular
It features the Infamous kernel (same kernel as for JB4.3, without SELinux). The zram code has been optimized (based on google advice for low-RAM devices) and is enabled by default.
To see the additions on top of Omni, check github (additional patches are always shown on top):
Frameworks
Settings
OmniGears
First installation:
-Boot into recovery
-Factory reset
-Wipe system partition
-Install ROM
-Boot tablet (there sometimes are bootloops if gapps is flashed directly on top of the ROM without first booting the ROM)
-Reboot recovery
-Install SuperSU: http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip
-Install gapps (you should use a package specifically for KK4.4 and with the old-fashioned updater-script! - don't worry if you install an outdated gapps packages with the correct updater-script, as long as it is for KK4.4 the apps in the gapps package will be automatically updated -> only small gapps packages fit, e.g. banks core of pa 0-day gapps mini)
-Boot it up
-> some people report issues (e.g. bootloop or crashing gapps) if they flash ROM, gapps & supersu in a row after fully wiping the tablet. In that case, wipe again, flash ROM, boot the tab, reboot to recovery, and then flash the rest.
-> if coming from stock ROM, a factory reset may wipe you entire /data partition, so you loose you sdcard contents as well (I think this only happens with CWM, but I'm not sure)
-> in CWM "wipe system partition" can be found under mounts, and is called "format /system"
->If you get the message 'This package is for "p4" devices this is a "GT-P7500"' (or something likewise) update to a recent CWM or TWRP
Update installation (OMNI -> OMNI):
-Boot into recovery
-Install ROM
-Install SuperSU (in the SuperUser app you can create a script that will automatically backup/restore SuperSU on ROM updates so you don't have to reflash SuperSU).
-Boot it up
You can download any gapps packages for kitkat that you like, but one that many have used successfullyis PA 0 day gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
Downloads:
P4WIFI:
http://rootaxbox.no-ip.org/kasper_h/roms/p4wifi/omni44/
P4:
http://rootaxbox.no-ip.org/kasper_h/roms/p4/omni44/
Credits:
OMNI team for the code
AAccount for his help along the way to get KK4.4 to compile for our aging device!
pershoot for the basis for the device trees & kernel base
Code:
Basis of OMNI code: https://github.com/omnirom/
Common p4 device tree: https://github.com/kasperhettinga/android_device_samsung_p4-common
Device tree p4wifi: https://github.com/kasperhettinga/android_device_samsung_p4wifi
Vendor blobs p4wifi: https://github.com/kasperhettinga/android_vendor_samsung_p4wifi
Device tree p4wifi: https://github.com/kasperhettinga/android_device_samsung_p4
Vendor blobs p4wifi: https://github.com/kasperhettinga/android_vendor_samsung_p4

What does NOT work?
-There are graphical glitches. Although they mainly have been solved there seem to be some remaining issues with hwcomposer that may crash the tab.
-Bluetooth audio does not work (other Bluetooth functions do work).
-HDMI output (may be fixed according to some posts, didn't test myself yet)
-HD movies (in e.g. youtube) may stutter
Smoothness advice:
Go to performance settings:
-Overclock CPU to 1400MHz (Do this at your own risk!)
-Set IO scheduler to CFQ
-Keep governor on Interactive
Go to developer settings:
-Set the three animation scale options to 0.5x
-Activate "Force GPU rendering"
-Active "Disble HW-overlays"
-Set background process limit to 4 processes
(if performance/developer options are not yet shown, go to settings>about and press build number 7 times)
-> Thanks to all forum members contributing to this list
-> Do it at your own risk!
-> Don't complain about limited battery life (ROW+interactive+1000MHz leads to better battery life for sure)
Some other tips:
-For improvement of sound quality, you can use Viper4Android
-For more volume only, SpeakerBoost is earier to use
-For netflix, head over here: http://forum.xda-developers.com/showpost.php?p=49208063&postcount=445
-To be able to use Flash player, use a browser that doesn't use the kitkat browser engine (e.g. firefox can be used). Download flash player from adobe website (thanks to AAccount for finding out!).
- If you can't see your internal SD on PC: Go to Settings -> Storage -> 3 dot menu -> tick MTP.
-To use the multi-window feature, go to the recent apps screen, press&hold an app, and select put aside.

Great......downloading now
Sent from my GT-N7000 using Tapatalk

p4
is there any p4 version in progress br zezam?

Nice work :good:
you will get version and for the P7500 ?

kasper_h said:
Reserved
Click to expand...
Click to collapse
i'm new to Galaxy tab 10.1..LOL,,, can this ROM be installed directly from Stock ROM with TWRP,,,Please help ASAP

zezam67 said:
is there any p4 version in progress br zezam?
Click to expand...
Click to collapse
paiktaras said:
Nice work :good:
you will get version and for the P7500 ?
Click to expand...
Click to collapse
Kasper already said that he won't be building for the p4.
Looks like my P7500 is gonna be a P7510 soon..
BTW, we still need to flash supersu zip?
Sent from my GT-P7500 using Tapatalk HD

Xenodrome_ said:
i'm new to Galaxy tab 10.1..LOL,,, can this ROM be installed directly from Stock ROM with TWRP,,,Please help ASAP
Click to expand...
Click to collapse
Just wipe everything and flash the ROM.
eushaun99 said:
Kasper already said that he won't be building for the p4.
Looks like my P7500 is gonna be a P7510 soon..
BTW, we still need to flash supersu zip?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
You need to separately flash SuperSU. SuperSU can create a script for backing it up, so that on future ROM flashes you don't have to repeat this.

oooppppsss the ROM can not be installed in a P4
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"

esfjrg1 said:
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"
Click to expand...
Click to collapse
Doh, its a p4wifi ROM. If you don't use 3g, flash a p4wofi recovery first, reboot, and flash again.
Sent from my GT-P7500 using Tapatalk HD

esfjrg1 said:
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"
Click to expand...
Click to collapse
Flash P4wifi recovery, Then flash this ZIP again
Bad to see that it is really not for the GT-P7500 . So i will not update.... i really need my 3G
Why it is so difficult to get 3G working Did 4.4 change so much?

Traace said:
Flash P4wifi recovery, Then flash this ZIP again
Bad to see that it is really not for the GT-P7500 . So i will not update.... i really need my 3G
Why it is so difficult to get 3G working Did 4.4 change so much?
Click to expand...
Click to collapse
The problem is that in 4.4 the radio stuff has been redone. I also had problem with another device I develop for (SGS) to get the radio to work. And to develop a ROM for a device I don't own make it even more complicated. In the past weeks I sometimes flashed 10-15 testbuilds on a single day to try and fix something simple (like USB OTG). If someone else would test something for me, the progress would be way too slow.
But all my code is open source: someone with a p7500 can just grab all the code, adapt it to p7500 and compile it. And start the whole process of fixing bugs

I get a unfortunately, setup wizard has stopped error and can not pass it.. Anything to work around it?
Sent from my SPH-L720 using xda app-developers app

@kasper_h As you might awared, YouTube is broken. It ran the same problem at that time with my GT-N7000 with OMNI 4.4, they managed to fix it. Maybe you can check with herna on that thread.
So far so good running ART
Sent from my GT-N7000 using Tapatalk

I also get the com.google.process.location has stopped error but I can pass that one..
Sent from my SPH-L720 using xda app-developers app

kasper_h said:
First installation:
-Install gapps (you can download any gapps package you like, as long as it is specifically for JB4.3!)
Click to expand...
Click to collapse
Is there a difference between 4.3/4.4 gapps?
Sent from my myTouch 4G using Tapatalk

Chris4809 said:
I get a unfortunately, setup wizard has stopped error and can not pass it.. Anything to work around it?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Which gapps package? I flashed ROM & gapps myself today as well, just to test it once more. And it works flawlessly.
rogconnect said:
@kasper_h As you might awared, YouTube is broken. It ran the same problem at that time with my GT-N7000 with OMNI 4.4, they managed to fix it. Maybe you can check with herna on that thread.
So far so good running ART
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Youtube is a problem with some hardware blobs I believe. I had the same on AOKP. I have spend a lot of time, but could never solve it. I decided to ignore it
Chris4809 said:
I also get the com.google.process.location has stopped error but I can pass that one..
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
jaibar said:
Is there a difference between 4.3/4.4 gapps?
Sent from my myTouch 4G using Tapatalk
Click to expand...
Click to collapse
Yes, you should only use kitkat (4.4) gapps!

kasper_h said:
Which gapps package? I flashed ROM & gapps myself today as well, just to test it once more. And it works flawlessly.
Youtube is a problem with some hardware blobs I believe. I had the same on AOKP. I have spend a lot of time, but could never solve it. I decided to ignore it
Yes, you should only use kitkat (4.4) gapps!
Click to expand...
Click to collapse
If it is 4.4 gapps you might want update the OP.. It is telling us that we should use 3.4
Sent from my SPH-L720 using xda app-developers app

After enabled ART on first boot then rebooted. And then rebooted to recovery to install Banks 12-14_GApps_Core_4.4.2_signed.zip.. then I can signed in Google...so far no FC on Google apps.
Sent from my GT-P7510 using Tapatalk

I'm getting the "setup wizard has stopped" error also.
Coming from pac_P4wifi_4.3-Infamous_20131114
Followed install instructions.
Used gapps-jb-20130813-signed
Cannot find gapps for 4.4. The 20130813 (4.3) package seems to be the most current.

Actual:
I use CyanogenMod and Mokee teams sources and add some changes to device config.
Latest CM12 builds
СМ12.1 build 24.07.2015
normal- https://yadi.sk/d/l0sQrKeXi4rpT
experimental - https://yadi.sk/d/Sus83ATLi4rjv (aptx bt, mako gps)
news: - kernel, config updates . SoundControl removed, revert to deodex.
revert cm12.1 BT - https://yadi.sk/d/DHjDF-fAi4sQE
СМ 12.1 build 21/07/2015
normal - https://yadi.sk/d/EwsQB88Qhz7RD
experimental - https://yadi.sk/d/X07SjR3Fhz7Rm (GPS from nexus4, APTX BT)
+fixed updater-script - added ifelse(is_mounted("/system"), unmount("/system"));
СМ12.1 build 13.07.2015 - https://yadi.sk/d/CtPkfkpchq2Yb
СМ12.1 build 13.07.2015 w aptx support(experimental) - https://yadi.sk/d/LRV6F7N2hq2bS
fixed: wifi, BT, boot light, recovery, offline charging
Cm 12.1 03.07.2015 build - https://yadi.sk/d/GG3gFTtYhe3dQ
Changes in kernel, libs, binaries, configs
Tested - worked/
CM12.1 11.06.2015 build - https://yadi.sk/d/VyIKm27xhCdhE
CM12.1 20.05.2015 build - https://yadi.sk/d/WnR7d73mgkzcX
CM12.1 28.04.2015 build - https://yadi.sk/d/bn_IsRx1gJaRs
kernel w soundcontrol v3, many kernel and ril updates from см team
CM12.1 20.04.2015 build - https://yadi.sk/d/xiKPp0EBg7Kyo
kernel w soundcontrol v3, updates from см team
gps libs from мако(nexus 4) (possible gps work better) for recovery - https://yadi.sk/d/JU39SUbPg7Kmu
PAC 5 20.04.2015 build from neosuslik - https://drive.google.com/uc?id=0B6kPZoGYA4tfaFhOdjIxenNYbnM&export=download
Mokee 5.1 12.04.2015 build from neosuslik - https://docs.google.com/uc?id=0B6kPZoGYA4tfSGdlNldodnhuVTQ&export=download
CM12.1 build(06.04.2015) tested - https://yadi.sk/d/bzBHxTDmfoyck
move apps to sd fix added, dual recovery
kernel w SoundControl v3 for cm12.1 - https://yadi.sk/d/xPWTpM4ufpgnA - you need faux sound control or other app to tweak sound levels.
CM12 build (01.04.2015), ODEXed, fix for move apps to sdcard - https://yadi.sk/d/93AA69qtffk7Q
CM12 build (12.03.2015), ODEXed - https://yadi.sk/d/dTadZHj_fCZKN
CM12 build (04/03/2015), ODEXed - https://yadi.sk/d/K20AhXQ4f2ha9
CM12 build (28/02/2015) - https://yadi.sk/d/GGDHoe76ewFe4
CM12 build (20/02/2015) - https://yadi.sk/d/mmi7ic1Eeo5Eh
news:
new cm12 updates, bugfixes and bugs
Mokee5 build (25/02/2015) - https://yadi.sk/d/yI-cBxQheskpk
How to install:
a)
1. flash boot.img from archive
2. boot to recovery and flash firmware archive
b) reboot to recovery and flash firmware archive
Old(not actual now):
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
English screenshots - http://forum.xda-developers.com/showpost.php?p=56982062&postcount=77
More Russian screenshots - http://4pda.ru/forum/index.php?showtopic=475149&st=9040&view=findpost&p=35853307
Whats worked: see original theme - http://forum.xda-developers.com/xperia-z/orig-development/exp-lollipop-xperia-z-t2929369
Latest CM12 port(qsnc 09.02.2015 build based) - https://yadi.sk/d/QcxE0x0WedRUd
Updated boot.img w philz recovery and vibro for 09.02.2015 - https://yadi.sk/d/anPzmPL0eeiCg
CM12 for ZR, cm-12-20150112-INFECTED-yuga based:
CM12 for ZR: cm-12-20150112-INFECTED-yuga.zip port - https://yadi.sk/d/L_eIwqujdz6sb
30.12.2014 Update, pabx 5.0.8 build based:
boot - https://yadi.sk/d/BMTyrqVpdnfDQ
system - https://yadi.sk/d/uK10pxZSdnfDa
fix - https://yadi.sk/d/4CBtWW7wdnfDJ
20.12.2014 Update
system.img from 20.12.2014 - https://yadi.sk/d/LObcDGPOdXW4B
boot.img - https://yadi.sk/d/ynTfhBdHdXW3v
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/GU_LI9S2dYwya
04.12.2014 Update:
system.img from 4.12.2014 - https://yadi.sk/d/yeqUq35rdAgGG
boot.img - https://yadi.sk/d/jXkoWjC4dAgFZ
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/8fWVGGj5dAgHM
GAPPS - https://yadi.sk/d/wxoFZUWidAgJr
Worked SuperSu - http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
***************************************************
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
Fastboot:
fastboot flash boot boot.img
fastboot flash system system.img
flash fix(recommended before first boot), supersu, gapps ...etc via recovery
if no internal sdcard found try this(in adb or terminal console):
su
restorecon -FR /data/media/0
***************************************************
Google Apps installation
After booting your phone for the first time, download the gapps package and push it to /sdcard using adb (or MTP):
adb push gapps_50_yuga_004-00cb.tgz /sdcard/
adb reboot
Your phone will now reboot and automatically install gapps during the boot process. (note that your phone will reboot twice - this is normal).
recommend to keep the gapps package in /sdcard/ after the installation finished: Upgrading to a new release will erase your existing gapps installation - but if the package is still present in /sdcard/, it will be automatically installed during the first boot.
*************************************************

Thank you for your effort Looking forward to testing this ROM upon upload. And i know it sounds silly, but an english version will be uploaded right???

I've been checking XDA like 10 times a day for the past two weeks hoping for this, and now it's finally here!!! You sir, deserve a medal.
I have a question, and I'm not sure if it's supposed to go here or the Q&A thread, since it's not specifically related to this ROM, per se. I just want to know how you built this; where did you get the device tree/binaries (not really sure what I'm talking about here, I've only read the building tutorials, don't really understand them fully)? AFAIK, Sony hasn't released them for the ZR, so how'd you do it? Is there some way to port them from other devices or something? Even a reference point to start searching would be great.
Thank you for your work!
P.S. Also, does this question belong in the Q&A thread or not?

Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details

kash296 said:
Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details
Click to expand...
Click to collapse
Of course, no pressure at all on the dev; I just wanted to say kudos, and thought I might as well ask. [emoji12]

xenius9 said:
Coming soon... Now kernel worked, ROM started, need little fixes.
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
Bad news:
I have no time to develop, rom not work on all ZR-s - need additional kernel developing?(on many ZR models this rom work(on 2 phones work normal now), on other not (on my zr not work properly - mixed image on screen))
Now i have:
Kernel w twrp recovery - https://yadi.sk/d/WJw4gqmqcnLWd
SystemImage (from sony z, need add camera libs in vendor folder and some in etc/firmware and fix sensors.conf - from .283 stock firmware) - https://yadi.sk/d/S0Bh4H8gcmqRv
Xperia ZR specified files - https://yadi.sk/d/VZ8whMhccoCnt - zr camera libs, sensors.conf etc, you can install it via twrp recovery
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
test
Root - flash latest supersu via twrp recovery http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Click to expand...
Click to collapse
Um. So that means right now, it's a list of separate files??? Anyway awesome work.
P.S Sorry abt quoting the whole post, i hate that. But my comment wouldn't make any sense then

Awsome
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .

sshivampp said:
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .
Click to expand...
Click to collapse
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........

nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???

nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
Bluetooth is fine except I cannot accept or share file with apk extension
WiFi also seems to be fine till now and yes I can make calls, messages, and can connect to data network.
Camera quality is accepteble (photo preview is kind of buggy )
Till now what I cannot test its GPS as I don't use it. but can provide logcat if anyone wants
Edit: At latest lollipop release for xperia Z (18 November), RIL is broken, atleast in ZR with this kernel, don't know about Z
maybe kernel update will fix this
---------- Post added at 10:49 PM ---------- Previous post was at 10:40 PM ----------
kash296 said:
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???
Click to expand...
Click to collapse
I suggest exam first
BTW you can download gapps from here
or direct link of one I downloaded here (I don't remember the source page but it was from XDA)

Thanks for the gapps link. Holidays inbetween so it aint a prob for the exams. Downloading the image right now, will try out the bluetooth and see if i too get the same issue

Xenius you are genius. Booted and running smoothly without any FCs.
Sent from my Lollipop for ZR using XDA Free mobile app

.
Man
big tnxfor your awsome work:cyclops:
And can you upload your kernel source? May be developers like @Alx31TLse can build more lollipop roms:fingers-crossed:

Yes i can, now i build new kernel w new ramdisk(w working root).
18.11.2014 firmware working... new kernel too... root working
Files...soon.

All updates added. See 1st post.

xenius9 said:
All updates added. See 1st post.
Click to expand...
Click to collapse
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
P.S I found out the problem. My Gmail wasn't synced so my account wasn't fully functional. Never mind

kash296 said:
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
Click to expand...
Click to collapse
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps

xenius9 said:
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps
Click to expand...
Click to collapse
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.

kash296 said:
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.
Click to expand...
Click to collapse
Install it and test)))

xenius9 said:
Install it and test)))
Click to expand...
Click to collapse
I'm definitely going to. But why i asked is, cause they were mentioning about permissive kernels. So i thought i'd ask you about that.
And i forgot to ask. The exclamatory symbol on the signal icon ? Why is it coming?? Is it indicating any issue???

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.

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

STRATUM OS for HOT2
For which devices, should work
with all versions that are infinix hot 2
Click to expand...
Click to collapse
IMPORTANT
Code:
* Do NOT expect daily builds. I'll build when I'm free.
* Do NOT ask for support for flashing in this thread.
* Do NOT use this unofficial build and ask for support at the official threads.
What is working?
Code:
Service
Text Data
Call
Audio
WiFi
Google Now
GPS
MMS
Video playback
Audio playback
Internal/External
SDcard mounting
Themes All Layer features
Screen Record
Bluetooth
Wifi Shared
Video Recording
Youtube 720p
Sync Reboot fixed
Move Apps to SD
Xposed
What doesn't work -
You tell us !
Code:
1) Please flash Infinix Rom 1st before flashing this ROM (I tried changing the updater script to AndroidOne firmware partitions but didn't help)
2) Some apps may have difficulty accessing systemless root (like es file Explorer) I used root browser and it worked just fine.
3) xposed Framework zip sdk23 version 82 or less will work just fine, versions 83 or more will work fine too but it breaks the stock gallery app causing it to FC.
4) If you want to have Google now on tap flash gapps (I flashed open gapps mini 6.0, open gapps aroma won't even run)
5) Google plus FCs whenever you click on share or post a comment. I haven't figured out the cause yet (and it's not from xposed) tried even older apks and same out come. But you can view posts and even comment.
additional info BY @Bolumstar
Code:
Wipe data, cache, and dalvik cache
Code:
* Your warranty is now void.
Code:
*
* We are not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
Download Link : HERE
Supersu v2.74 Link : HERE
Flashing Method
Flash ROM
Flash SuperSU
Flash Xposed (if you want)
Reboot !
Credits:
Android Open Source Project.
Obaid Muneer
Aditya Kumar
Anuta Lores
DroidPeepz™ Inc
Pharaohs Team
Dev.Muttahir Aon Syed
Dev.Frank Boateng
Dev.Coulibaly Nonta
Dev.Hasan Al-Hallaq
Dev.Hussein Medhat
Dev.Mazen Yasser
XDA:DevDB Information
[ROM][6.0.1][AOSP][PRO/Layer]STRATUM OS for HOT2, ROM for the Infinix HOT 2
Contributors
Ibrahim Fath El-bab, Mahmoud9873, iykeDROID
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Stable
Created 2016-07-05
Last Updated 2016-07-18

Good work done
...keep it up
@iykeDROID™

Great Work ! <3

iykeDROID™ said:
Good work done
...keep it up
@iykeDROID™
Click to expand...
Click to collapse
thanks bro

Mazen Yasser said:
Great Work ! <3
Click to expand...
Click to collapse
thanks Mazen

Hey I was wondering how you got the 3.18.XX kernel to boot on MT6580 chipset. I've been trying to get 6.0 for my MT6580 device (Cubot Note S) however the stock rom kernel is only 3.10 so I've only managed to get 5.1 custom roms to work.

Great Effort Guys and the best MM ROM for Hot 2.
I've been playing around it for about a week now and am so happy and satisfied with it's performance and battery life.
Here are additional info:
1) Please flash Infinix Rom 1st before flashing this ROM (I tried changing the updater script to AndroidOne firmware partitions but didn't help)
2) Some apps may have difficulty accessing systemless root (like es file Explorer) I used root browser and it worked just fine.
3) xposed Framework zip sdk23 version 82 or less will work just fine, versions 83 or more will work fine too but it breaks the stock gallery app causing it to FC.
4) If you want to have Google now on tap flash gapps (I flashed open gapps mini 6.0, open gapps aroma won't even run)
5) Google plus FCs whenever you click on share or post a comment. I haven't figured out the cause yet (and it's not from xposed) tried even older apks and same out come. But you can view posts and even comment.
So far, this is my daily driver now. Well built Rom.
Thanks to all involved in Porting this ROM.

i couldn't flash it, it gives me error 7 :/

ProRedFed said:
i couldn't flash it, it gives me error 7 :/
Click to expand...
Click to collapse
flash Infinix Rom before flashing

You know Infinix ROM require SP tools to flash right?
What do you mean my system less root?

Well built ROM, Great work!!! Minor concern; clicking system update in settings force closes it, any reason??
---------- Post added at 01:40 PM ---------- Previous post was at 01:31 PM ----------
essgen said:
You know Infinix ROM require SP tools to flash right?
What do you mean my system less root?
Click to expand...
Click to collapse
You can also simply use the Infinix Flash Tool!!
System less root is a modified root access strategy which doesn’t modify any files in the /system partition especially on devices running marshmallow, makes it easier to even install OTA Updates!!!

Please i want to flash this.......does it have the 3G only on 1 sim issue?

Marshe said:
Please i want to flash this.......does it have the 3G only on 1 sim issue?
Click to expand...
Click to collapse
No it doesn't

Great effort guys.. Does is support OTG?

Ibrahim Fath El-bab said:
flash Infinix Rom before flashing
Click to expand...
Click to collapse
yes, i've already done that but no success

Am unable to flash it using twrp. Am running stock infinix ROM 5.1. am getting a filesystem ext 4 dev block/mmc error. Am trying to upload a screenshot Buh my browser keeps bouncing the page. please help

I've successfully flashed it..... thanks. can't seem to get the layers manager themes working though

Marshe said:
I've successfully flashed it..... thanks. can't seem to get the layers manager themes working though
Click to expand...
Click to collapse
i get a filesystem ext 4 dev block/mmc error every time i try to flash it just like you, how u passed that error ?

Very very nice work, amazing ROM in fact, very fluid and fast(maybe the fastest for this device) but gutted it doesn't support otg. Then
-layers don't seem to work(installs but after reboot nothing changes, still looks stock).
-layers app also force closes when you try to uninstall layers. (Can still b uninstalled another way)
-after changing nav bar from initial config(switching recents from left to right) recent button don't work.
Still a cracking daily driver for people that don't mind not having otg. Didn't test the camera tho cos am not a camera person.
Again amazing ROM
Many thanks to the devs.

Anushan said:
Hey I was wondering how you got the 3.18.XX kernel to boot on MT6580 chipset. I've been trying to get 6.0 for my MT6580 device (Cubot Note S) however the stock rom kernel is only 3.10 so I've only managed to get 5.1 custom roms to work.
Click to expand...
Click to collapse
FYI
the stock 6.0 of android one rom is 3.18.xx kernel, so it can be ported out easily without any problems appearing