Database Users

[Q] Building CM 10.2 for Nexus-Q

I used wiki.cyanogenmod.org/w/Build_for_steelhead for building CM 10.2 for my nexus-q. After installing using CWM, I get a black screen and I see that surfacefllinger crashes (in a loop) when looking at adb log.
The last working CM is cm-10.1.3-RC2-steelhead.zip.
What version of CM are you using and what did you do in order to build it? I need a version with adb enabled out of the box (ro.secure=0) which is why I am trying to build my own..

wojciii said:
I used wiki.cyanogenmod.org/w/Build_for_steelhead for building CM 10.2 for my nexus-q. After installing using CWM, I get a black screen and I see that surfacefllinger crashes (in a loop) when looking at adb log.
The last working CM is cm-10.1.3-RC2-steelhead.zip.
What version of CM are you using and what did you do in order to build it? I need a version with adb enabled out of the box (ro.secure=0) which is why I am trying to build my own..
Click to expand...
Click to collapse
I managed to flash one of the nighties instead of building my own. My problem was that the script (repack-bootimg.pl) used to re-assemble boot.img was not using "--base 0x80000000" argument to mkbootimg.
I had luck changing default.drop so it gave me root/adb access and then flashing the repacked boot.img back to the device.
XBMC (xbmc-12.2-Frodo-armeabi-v7a.apk) is running on the box (installed using "apk install" - the installation did not install all the required files and I had to manually create /data/data/org.xbmc.xbmc/cache/apk/assets from the contents of the apk file).
I will have to use one of the snapshots, as 720p and up lags.

[MOD] Multirom for cancro [ABANDONED]

Introduction
MultiROM for the Xiaomi Mi3 and Mi4
MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them.
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links will be uploaded shortly in second post.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of a rom after first boot (with dalvik cache generated and connected to google account) takes approx 700mb of space.
Attention : MIUI does not work with multirom, so dont flash it.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Thanks a lot to Tasssadar for creating this awesome utility.
Thanks to @KINGbabasula for this thread template and @Gnome for his stuxnet kernel
Thanks to @TheStrix, @KINGbabasula, @rooque for their help in porting this to our device.
Special thanks to @Shahan_mik3 without whom i wouldn't have started developing roms and stuff
ABANDONED

Reserved
Download links
Multirom zip:- https://www.androidfilehost.com/?fid=529152257862710486
Recovery:- https://www.androidfilehost.com/?fid=529152257862710485
Multirom uninstaller :- https://www.androidfilehost.com/?fid=673368273298938678

woww that looks cool, MultiRom :victory: :victory:

Great!

Good Job!

Reserved ...will update after I brick my phone ??

Thank you for your work. Which ROM is recommended as primary ROM? In other words: With which ROM is your kernel compatible? Its compatible with Ivan's AOSP?

Any rom that runs with stuxnet.. I have tried xenon and eos.. Both work..

Compatible with MI4？ Can't get in recovery & system. after flash it.

Only for mi3 atm.. I wrote comming soon for mi4

vasishath said:
Only for mi3 atm.. I wrote comming soon for mi4
Click to expand...
Click to collapse
Oh, Expect your adapte for Mi4

Are miui roms supported ??

Hsmetric181 said:
Are miui roms supported ??
Click to expand...
Click to collapse
No

schspa said:
Compatible with MI4？ Can't get in recovery & system. after flash it.
Click to expand...
Click to collapse
Read OP for once.

Not compatible with blisspop and cynide rom(tried as primary rom)
Not booting into the internal rom

I did install MIUI on my USB drive but after choosing in multiboot menu it is not booting...it just goes back to recovery...any help?

MIUI isnt compatible with multirom.. And also, some roms dont work from otg

..

Miui works ryt ? @vasishath
Plz update the thread
And continue ur great work
Sent from my MI 3W using Tapatalk

Miui works as a primary rom, I can confirm it works well with kernel 10.05 stuxnet. I also use DU rom with this kernel as a secondary rom, so far everything works well.

EXFAT support for RN2 on MIUI 8

If you want to read/write your big microSD (64-128gb), on MIUI, but don't wanna format it to FAT32, there is way to do it:
1. You must have instaled init.d support on your device.
If you don't know how, just install sMIUI rom, from rom kitchen:
http://smiui.net/index.php/rom-kitchen/rom-kitchen-features/?codename=hermes&d_version=5.0&d_img=redminote2&realname=RedMi+Note+2
Or you can install only kernel (boot image ) with included init.d and busybox from:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes
Both includes busybox, so you don't need step 2.
2. Install busybox (google play)
3. Go to
http://forum.xda-developers.com/android/development/mod-exfat-ntfs-support-mediatek-mt6753-t3304866
and download exfat-ntfs-patch-mtk.zip
4. Copy exfat-ntfs-patch-mtk.zip to your phone, restart in recovery (TWRP), and flash it.
If you get screen without systemui and backscreen picture, just reboot in recovery and make wipe ONLY cache and dalvik/art cache.
All credits to @dr_root.

I tried it on my RN2, but i got a problem. For some reason it gets mounted under root account and therefor none-root apps don't have access.
I guess it's a SuperSU related problem, but i didn't found a way to fix it.

What MIUI version you run?
I run it only on eu.multi roms, without any single problem.

I tested it with sMIUI 6.7.28.
When i check with DiskInfo it says: SD Card mounted as root

pp23 said:
I tested it with sMIUI 6.7.28.
When i check with DiskInfo it says: SD Card mounted as root
Click to expand...
Click to collapse
Strange, my first try was with sMIUI (earlier version), and it was OK.
Try to install now ONLY sMIUI kernel for your version, restart, and then instal patch.

I think the problem is SuperSU and it's namespace separation. I can mount it correctly via android terminal with su --mount-master option, but i can't that to work with the init file.

pp23 said:
I think the problem is SuperSU and it's namespace separation. I can mount it correctly via android terminal with su --mount-master option, but i can't that to work with the init file.
Click to expand...
Click to collapse
Did you check settings>additional settings>privacy>unknown sources BEFORE flashing patch.
After patching, you must have file exfat-ntfs in folder /system/etc/init.d, with 755 permissions (-rwxr-xr-x).
And busybox in /system/xbin...

I have both with correct permissions. If not i would guess it would not be executed at all, instead just being mounted under root account only. I really think it's SuperSU namespace separation for mount points, since it works with --mount-master option. Changing/Deactivating the namespace separation in SU has no effect, it's still mounted as root. And this kind of behavior is exactly what namespace separation does.
And i know from a similar problem that i had this mounting problem started with SuperSU there too, as long as MIUI dev had it's own root it worked without a problem.

pp23 said:
I have both with correct permissions. If not i would guess it would not be executed at all, instead just being mounted under root account only. I really think it's SuperSU namespace separation for mount points, since it works with --mount-master option. Changing/Deactivating the namespace separation in SU has no effect, it's still mounted as root. And this kind of behavior is exactly what namespace separation does.
And i know from a similar problem that i had this mounting problem started with SuperSU there too, as long as MIUI dev had it's own root it worked without a problem.
Click to expand...
Click to collapse
Sorry,
since I have no problem with using my SDcard, I didn't check it before with Diskinfo... Yes, I have same SD Card mounted as root, but my device/apks use it with unlimited acces on LP rules.
Any app have right to r/w on SDcard, but only in extSD0/Android/data/yourapk folder.
MIUI file manager works properly (r/w) anywhere, but my favorite is Mixplorer, again, with no any limits.
But real problem is enabling documents in settings>installed apps, that cause black homescreen... and because this problem, apks can't acces other places on SD for eg. saving data.
Like I said, I have no problem on any xiaomi.eu_multi rom with sMIUI patchedboot.img.

Yay. I got it working. I had additionally to just add "su --mount-master -c " to the mount commands also to add before mounting "su 0 setenforce Permissive" and after "su 0 setenforce Enforcing" . I also added "allow_other" to the mount options just to make sure.
Now everything works again as before. (Still mounted as root but working)

pp23 said:
Yay. I got it working. I had additionally to just add "su --mount-master -c " to the mount commands also to add before mounting "su 0 setenforce Permissive" and after "su 0 setenforce Enforcing" . I also added "allow_other" to the mount options just to make sure.
Now everything works again as before. (Still mounted as root but working)
Click to expand...
Click to collapse
Glad to solve

the init.d link is dead,
anybody willing to refresh or upload it here?

21667 said:
the init.d link is dead,
anybody willing to refresh or upload it here?
Click to expand...
Click to collapse
Boot images with init.d:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes

I don't know whether it's a coincidence or not but since installing this mod with the sMiui rom, my USB port doesn't work as well as it did.
I'm having problems connecting to my PC with most of my USB cables whereas previously I had no problems whatsoever. It will no longer charge using my Aukey 5-socket wall charger with ANY cable in any socket whereas previously it always charged. The Aukey has a QC 2.0 socket and it always appeared to charge very quickly using this port. I can only get it to charge using the original Xiaomi charger but only with one or two of my cables.
My wife has an identical phone with an sMiui rom without the mod and without the modded sMiui bootloader and it has none of these problems.
I've deleted the init.d script and installed the latest sMiui rom without the modded bootloader but neither has resolved these problems.
Can anyone suggest what else I might try to eliminate any other cause rather than a hardware fault ?

fourlans said:
I don't know whether it's a coincidence or not but since installing this mod with the sMiui rom, my USB port doesn't work as well as it did.
I'm having problems connecting to my PC with most of my USB cables whereas previously I had no problems whatsoever. It will no longer charge using my Aukey 5-socket wall charger with ANY cable in any socket whereas previously it always charged. The Aukey has a QC 2.0 socket and it always appeared to charge very quickly using this port. I can only get it to charge using the original Xiaomi charger but only with one or two of my cables.
My wife has an identical phone with an sMiui rom without the mod and without the modded sMiui bootloader and it has none of these problems.
I've deleted the init.d script and installed the latest sMiui rom without the modded bootloader but neither has resolved these problems.
Can anyone suggest what else I might try to eliminate any other cause rather than a hardware fault ?
Click to expand...
Click to collapse
sMiui rom contain sMiui modded kernel (boot.img-not bootloader, noone touch your bootloader). So there is no difference between your and your wife's device, after flashing sMiui rom.
To test device, try to flash other rom, eg. some weekly from xiaomi.eu, or CM12.1.
To be sure, before flashing rom, make standard wipe (data/cache/dalvik), and format data (save data from internal mem. before).
I have zero real problems with several versions of weekly (with modded sMiui kernel+exfat mod) and sMiui (only exfat mod) roms.

maxx_hr said:
if you want to read/write your big microsd (64-128gb), on miui, but don't wanna format it to fat32, there is way to do it:
1. You must have instaled init.d support on your device.
If you don't know how, just install smiui rom, from rom kitchen:
http://smiui.net/index.php/rom-kitchen/rom-kitchen-features/?codename=hermes&d_version=5.0&d_img=redminote2&realname=redmi+note+2
or you can install only kernel (boot image ) with included init.d and busybox from:
http://smiui.net/index.php/mod-download/?mod=pboot&device=hermes
both includes busybox, so you don't need step 2.
2. Install busybox (google play)
3. Go to
http://forum.xda-developers.com/android/development/mod-exfat-ntfs-support-mediatek-mt6753-t3304866
and download exfat-ntfs-patch-mtk.zip
4. Copy exfat-ntfs-patch-mtk.zip to your phone, restart in recovery (twrp), and flash it.
If you get screen without systemui and backscreen picture, just reboot in recovery and make wipe only cache and dalvik/art cache.
All credits to @dr_root.
Click to expand...
Click to collapse
it's mandatory to replace your current system/etc/permissions/platform.xml
with the one i provided
only that way your exfat/ntfs formated sd card will be mounted correctly and will be r/w
and all apps will not have a single problem
no need for commands via terminal emulator this way!
Cheers

maxx_hr said:
sMiui rom contain sMiui modded kernel (boot.img-not bootloader, noone touch your bootloader). So there is no difference between your and your wife's device, after flashing sMiui rom.
To test device, try to flash other rom, eg. some weekly from xiaomi.eu, or CM12.1.
To be sure, before flashing rom, make standard wipe (data/cache/dalvik), and format data (save data from internal mem. before).
I have zero real problems with several versions of weekly (with modded sMiui kernel+exfat mod) and sMiui (only exfat mod) roms.
Click to expand...
Click to collapse
Thanks for your explanation and your suggested solutions. Unfortunately, none of them worked. Can you suggest anything else before I contact my supplier regarding a repair to my phone ?

fourlans said:
Thanks for your explanation and your suggested solutions. Unfortunately, none of them worked. Can you suggest anything else before I contact my supplier regarding a repair to my phone ?
Click to expand...
Click to collapse
hey mate try fasboot flashing latest global rom found on en.miui.com
REMEBER to use command FLASH ALL
backup personal things before trying

dissidius said:
hey mate try fasboot flashing latest global rom found on en.miui.com
REMEBER to use command FLASH ALL
backup personal things before trying
Click to expand...
Click to collapse
I wasn't quite sure how to flash the global rom using the 'FLASH ALL' option of FASTBOOT so I flashed it via TWRP after a factory reset.
Are these 2 methods equivalent ?
Still having problems with the USB socket after flashing this rom.
Thanks for your suggestion.

fourlans said:
I wasn't quite sure how to flash the global rom using the 'FLASH ALL' option of FASTBOOT so I flashed it via TWRP after a factory reset.
Are these 2 methods equivalent ?
Still having problems with the USB socket after flashing this rom.
Thanks for your suggestion.
Click to expand...
Click to collapse
no they are not equivalent!
so try fasboot flashing!

[Root] Phoenix OS x86/x64 v2.0.7 (13 June) Rooted Images

Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images

Oooh... now I can test this to see if it fixes my G+ compatibility issue

The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you

meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/

The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working

meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...

The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.

If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.

meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.

irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.

irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211

#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?

Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.

This will work on a Nexus 9 or it only works in pc's?

when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy

Waiting for rooted system.img for Phoenix OS 2.1.0

SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy

MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?

Guys, when to expect a rooted image for V 2.1.0 x86

thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?

EvolutionX_2.3 Fastboot ROM Ported_Unofficial

This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is EvolutionX Pie 2.3 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build. Also separate unlock bootloader not required... It will b done by flash process automatically.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
Unzip the downloaded file. Put it in a folder in desktop.
There are files named "system.zip, vendor.zip, recovery.zip and boot.zip" , unzip those all, refer readme guide for details.
Put those above unzipped .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fast boot mode, connect to PC and run the flash_without_data_erase.cmd or flash_all_erase_data.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot if your device is encrypted before flash or you were using any rom other than evoX.
Detailed process available in readme file inside.
Best of luck....Hit a thanks button if you like my works...
This ROM is included
TWRP+Magisk
opengapps pico
Gcam 7.2 (parrot)
Ampere app
Google Phone Dialer
Safetynet basic integrity Fixed but cts profile not fixed yet.
Bugs::
You tell me.
This ROM is a ported version and unofficial, converted into fast boot ROM for easy installation only.
Thanks to developers of
Magisk, Gapps, TWRP for this device and all those who have supported directly or indirectly.
Download Link ::
https://www.androidfilehost.com/?fid=4349826312261722798
https://drive.google.com/file/d/1222F_fuYa85Fa0_Nxcv-FL0lRLERdR3G/view?usp=drivesdk

reserved 1

reserved2

[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is EvolutionX Pie 2.3 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build. Also separate unlock bootloader not required... It will b done by flash process automatically.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
Unzip the downloaded file. Put it in a folder in desktop.
There are files named "system.zip, vendor.zip, recovery.zip and boot.zip" , unzip those all, refer readme guide for details.
Put those above unzipped .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fast boot mode, connect to PC and run the flash_without_data_erase.cmd or flash_all_erase_data.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot if your device is encrypted before flash or you were using any rom other than evoX.
Detailed process available in readme file inside.
Best of luck....Hit a thanks button if you like my works...
This ROM is included
TWRP+Magisk
opengapps pico
Gcam 7.2 (parrot)
Ampere app
Google Phone Dialer
Safetynet basic integrity Fixed but cts profile not fixed yet.
Bugs::
You tell me.
This ROM is a ported version and unofficial, converted into fast boot ROM for easy installation only.
Thanks to developers of
Magisk, Gapps, TWRP for this device and all those who have supported directly or indirectly.
Download Link ::
https://www.androidfilehost.com/?fid=4349826312261722798
https://www.androidfilehost.com/?fid=4349826312261722798
Click to expand...
Click to collapse
Can you please check and update the download links.

heaven992 said:
Can you please check and update the download links.
Click to expand...
Click to collapse
Only g drive is working of now

How is the rom anyone checked it?..
I am new here and finding daily driver rom

Meer Hossain said:
How is the rom anyone checked it?..
I am new here and finding daily driver rom
Click to expand...
Click to collapse
This one is best as per my experience. Till now this one is in use in mine one.

[email protected] said:
This one is best as per my experience. Till now this one is in use in mine one.
Click to expand...
Click to collapse
Pls provide command file for linux....

Please tell me which rom is best for gaming

Which Gcam 7 is working on max m2
Can you please give me the apk
By the way Does it work stock android pie

[email protected] said:
Only g drive is working of now
Click to expand...
Click to collapse
You have the latest version of Evo X?

how to go back to original rom?

Which os is better Havoc os or Evo X os

Asus max 2 evolution x updated do android Q

There's one issue after installing rom,
The receiver and me are unable to hear our voices.
I can't hear the connecting tune/caller tune too.
Plz help me out

Hey bro as I've used all GSI and you fastboot bundles I can say that this Evo X 2.3 is best in terms battery life as well as customisation. I request you to please update the vendor to latest WW......71 so more battery improvement can be done.

Plzz fixed sefety net