Related
Hello
I installed Cyanogenmod 11 on my Galaxy Note 3 few months ago, and I am fairly displeased with the stability...
I use the snapshot version M8, clear the Davnik cache, clear/wipe cache partition...
However, the device is still very unreliable, and is rebooting unexpectedly far too often...
The customs roms which are announced as very stable are the ones based on Samsung TouchWiz firmware...
Therefore, I am now giving a try to the one called " X-note "...
I use the clockworkmod recovery version 6.0.5, and the " X-note " zip rom file from there...
However, when I try to install the rom, the following message appears... :
" Starting aroma installer version 2.70RC2
2013 by amarullz xda developpers "
Nothing else happen afterwards...
Would someone be able to help me with this issue... ?
I also tried with an other rom called " Bobcat ", and the same message appears...
Thank You for your Help...
Arnaud
Hello do you have the last bootloader?
Those are 4.4.2 based rom. Have your phone upgraded to 4.4.2 bootloader?. Dont confuse with cm11 4.4.2 as it can run on 4.3 bootloader
Thank You for your replies...
By using the following apps, Phone INFO ?Samsung?
It is said that the bootloader version is N9005XXUDMJ7
Otherwise, I would not if it is a 4.4.2 bootloader...
Arnaud
Hi arnaud! You may be interested in Temasek's CyanogenMod build. You can find the thread in the Android Development forum.
Thank You for this interesting recommendation...
Arnaud
I can recommend you Temasek's CyanogenMod build as well. I am using it as daily rom. Give it a try. If you don't like it you can try Crash ROM.
I am now using Temasek's CyanogenMod , and no more crashes are occurring...
Thank You for this recommendation...
Arnaud
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Simax8 said:
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Click to expand...
Click to collapse
I'm using the GPE ROM, its great!! Rogers i337m
Sent from my GT-I9505G using XDA Free mobile app
Simax8 said:
I've been looking for custom roms with android 5.0 (lollipop) to flash on my Samsung Galaxy S4 SGH-i337m (jfltecan), however I can't find any. I know Cyanogen mod has cm12 for the jflte but not for jfltecan, can I still flash cm12 for jflte on my device or will it brick it? I used to have an s3 and I flashed carbon rom for d2att, edited some lines as to bypass status 7 and it worked fine. I was just wondering if I could do the same for my s4. Thanks!
Click to expand...
Click to collapse
I'm on sgh-i337m with cm12 for the jflte and it's working great you need to change the name of device in updater script and all is working
sorry for my bad english
mugensiz said:
I'm on sgh-i337m with cm12 for the jflte and it's working great you need to change the name of device in updater script and all is working
sorry for my bad english
Click to expand...
Click to collapse
So you are not having any issues at all? I am considering doing this. Do you have a link to a guide you used?
I use the AntaresOne Rom from this Link http://forum.xda-developers.com/showthread.php?t=2557353 with my sgs4 (sgh-1337m) from Fido and the only issues are wifi is kinda wonky(doesn't always save network info, doesn't always connect, sometimes drops connexion, but it DOES work fine when connected) and battery sometimes drains really fast. NB that this last issue has been labelled "cosmetic" by someone who knows a great deal more than me about Android. I have NEVER had my phone run out of battery and shutdown., just some days at 6pm it says 25%, other days it reads 76%. Kinda random. About to test the "Danvdh's GPE Edition ROM" 5.0.1 Lollipop, will post when I can confirm working or not.
EchoeROM is a good one.
No service after flashing...
I was on SlimKat 4.4.4 which was good, but wanted to upgrade to Lollipop after seeing it on my Nexus 5 (which is now broken). I have a Bell SGH-I337M
I first tried the CM12 Optimized build, wouldn't ever get past the boot screen...
Tried GPE, and it installed and ran fine, but my service was cutting in and out (so basically useless)
Tried SlimLP, it also installed fine but I was having the same service problem as with GPE.
How are you guys installing these ROMS? The only info I could find to fix the problem involved modem/radio.. I tried flashing a LP modem with the ROM but it didn't work. And all the radio-related information was from 2011 so I didn't bother with it. Any help would be much appreciated, I've been messing with this for 2 days now and get seem to fix it
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ
ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work
Hmm, no idea then. If you find any solution kindly don't forget to tag me.
AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )
i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4
Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )
Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.
I have a Verizon Galaxy S4 that I unlocked the booloader using GeTex's thread. I have been trying to find an CM-based rom running lollipop.
Every time I download a KLTE rom i have LTE, but I don't have calling or mms. I found a couple of roms I wanted to try but when I download the KLTEVZW variant the message in Recovery says, You can't install a KLTEVZW rom on your KLTE device.
I'm assuming you're using the klte CM recovery, which doesn't specifically says to NOT use for the kltevzw yet. Use the most recent TWRP recovery from this website instead: https://dl.twrp.me/klte/
Any rom that explicitly says it supports kltevzw should work fine.
I dunno about a CM12 (Lollipop) rom for kltevzw, but here is a link to an (ALMOST official) unofficial port of CM13 (Marshmallow) that works very well in case you want to check it out: http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-cyanogenmod-13-0-mm-t3348205
camcorder123 said:
I'm assuming you're using the klte CM recovery, which doesn't specifically says to NOT use for the kltevzw yet. Use the most recent TWRP recovery from this website instead: https://dl.twrp.me/klte/
Any rom that explicitly says it supports kltevzw should work fine.
I dunno about a CM12 (Lollipop) rom for kltevzw, but here is a link to an (ALMOST official) unofficial port of CM13 (Marshmallow) that works very well in case you want to check it out: http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-cyanogenmod-13-0-mm-t3348205
Click to expand...
Click to collapse
actually I was using TWRP 3.0 fromt he bootloader unlock thread here. http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-cyanogenmod-13-0-mm-t3348205
I found Haggertk's last Resurrection Remix build before it went official and flashed that. I wanted LP because of some themes I had bought , but I'm happy with what I'm on.
swing4thefence said:
I have a Verizon Galaxy S4 that I unlocked the booloader using GeTex's thread. I have been trying to find an CM-based rom running lollipop.
Every time I download a KLTE rom i have LTE, but I don't have calling or mms. I found a couple of roms I wanted to try but when I download the KLTEVZW variant the message in Recovery says, You can't install a KLTEVZW rom on your KLTE device.
Click to expand...
Click to collapse
The error message from recovery is because the ROM maintainer needs to update their updater-script to allow klte recovery to install that ROM. There is an assert that compares the device name to kltevzw and bombs out if it fails, that needs to be updated to allow klte as well.
Any AOSP/CM-based ROMs that are using the latest CM13.0 kltevzw source, or have merged the changes into their own repositories, will be OK.
Sent from my SM-G900V using Tapatalk
swing4thefence said:
actually I was using TWRP 3.0 fromt he bootloader unlock thread here. http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-cyanogenmod-13-0-mm-t3348205
I found Haggertk's last Resurrection Remix build before it went official and flashed that. I wanted LP because of some themes I had bought , but I'm happy with what I'm on.
Click to expand...
Click to collapse
So it looks like that version of TWRP is actually for the KLTE so is that why the rom installers think I'm on a klte
Oops, misunderstood a little bit. TWRP for klte supports the kltevzw completely - are you using the official & most recent recovery from TWRP.me? It supports MTP (finally) and is much improved from earlier versions for the klte, so there isn't really any need to use an unofficial one unless you want encryption. I can't really think of anything else that would cause this, I myself have used this rom, and many other kltevzw roms, with no issues.
I've tried the recovery from the bootloader thread when the unlock first came out, but it was much buggier than the official recovery.
There's always ROM Manager, if you're looking to flash incompatible firmware......... Just kidding. Don't use that.
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.