Develop Bugs

Flashing cynogenmod without google apps

I hope I'm not asking a question that has been answered else where that I could find. So basically I have an AT&T galaxy note 2 that I bought with Cleanrom on and has TWRP. I have been reading up and watching videos and want to flash a new rom. However I find roms I don't see the google apps with the rom file. From what i see you need to flash the rom and then flash the google apps onto it to have the play store.
For instance, I downloaded the stable release cm-10.2-20130924-NIGHTLY-t0lteatt.zip that came out today. I put it on my phone, and i see in twrp where i can install it. However on the cynogenmod website they don't have a separate file to download for google apps. Is this like a universal file or do all roms not need these files?
ALSO, I just want to make sure it is okay to just flash the rom in TWRP and I do not need to go about this another way.

You will need to flash gapps after you flash the ROM and you boot up first time. You'll need the most current gapps package for 4.3 ROMs. Check goo they have all the gapps listed.
Sent from Bad Azz VZW LG G2 Cyan Tapatalk

moosc said:
You will need to flash gapps after you flash the ROM and you boot up first time. You'll need the most current gapps package for 4.3 ROMs. Check goo they have all the gapps listed.
Sent from Bad Azz VZW LG G2 Cyan Tapatalk
Click to expand...
Click to collapse
Okay, glad I know that now. Thank you
Do you know if it is fine to flash cynogenmod right in TWRP? I read somewhere the fastboot should be used, but it wasn't the exact same situation i'm in so i wanted to clarify before i screw anything up

tadcrazio said:
Okay, glad I know that now. Thank you
Do you know if it is fine to flash cynogenmod right in TWRP? I read somewhere the fastboot should be used, but it wasn't the exact same situation i'm in so i wanted to clarify before i screw anything up
Click to expand...
Click to collapse
You flash it in twrp
Sent from my Nexus 4 using xda app-developers app

Fastboot is for HTC phone flashing. Samsung flashes in a custom recovery.

Okay, I guess i'm just confused when I see things like this.
To install this ROM you will need to have an unlocked bootloader and a custom Recovery such as TWRP or ClockWorkMod installed
Copy the downloaded ProBAM to your phone.
boot in bootloader
select fastboot mod
flash boot.img via fastboot that is located in the .zip fastboot flash boot boot.img
Boot into your custom recovery
Back up your ROM
Enter custom recovery
Make full wipe "included "system"
Install the ROM
install GAPPS package
Reboot - the first boot can take up to 2 minutes
From what i can see, I can start up in recovery and just flash the .zip.. Don't see how I can get into fastboot mod in TWRP

Fastboot flash instruction should be ignored when using a Samsung device ...
Simply install the appropriate TWRP or CWM recovery to the device ....
From that point you can choose the compatible rom of your choice ...and flash the .zip from within the new recovery ...
No fancy HTC stuff here ...
Also ...it is highly recommended to thoroughly read the install instructions of each rom prior to flashing...as they often contain special instruction that can get missed ...
Welcome ....you have a great device that is very easy to flash when done properly ....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

gregsarg said:
Fastboot flash instruction should be ignored when using a Samsung device ...
Simply install the appropriate TWRP or CWM recovery to the device ....
From that point you can choose the compatible rom of your choice ...and flash the .zip from within the new recovery ...
No fancy HTC stuff here ...
Also ...it is highly recommended to thoroughly read the install instructions of each rom prior to flashing...as they often contain special instruction that can get missed ...
Welcome ....you have a great device that is very easy to flash when done properly ....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Those were the instructions for my device, thats why I am so nervous. If it is really as easy as just deleting cache and factory data and stuff and installing it buy the .zip i might do it a whole lot more often!!

tadcrazio said:
Those were the instructions for my device, thats why I am so nervous. If it is really as easy as just deleting cache and factory data and stuff and installing it buy the .zip i might do it a whole lot more often!!
Click to expand...
Click to collapse
Those are the steps, buddy. Honestly, the hardest part of the process is holding all three buttons to boot into recovery.

rangercaptain said:
Those are the steps, buddy. Honestly, the hardest part of the process is holding all three buttons to boot into recovery.
Click to expand...
Click to collapse
oiii, i'm missing something. How do i do this part? Or were those just copied instructions and i can disregard? Sorry for making this more difficult than it is.
boot in bootloader
select fastboot mod
flash boot.img via fastboot that is located in the .zip fastboot flash boot boot.img

I would like to know where you are looking at the instructions --they are not for a samsung galaxy model...

I had it on my desktop I'm on my phone now. It was a thread for the probam ROM for note 2 att version. Cant seem to find it on my phone at the moment.

Fastboot is an HTC thing. Not Samsung. Double check your sources.
Sent from my CLEAN Note II

Okay looks like someone commented on the threading saying the instructions were wrong and they were changed. Now I feel much more confident. Will do tonight when I get home.

Is having 2 Custom Recoverys bad?

After achieving S-Off, thanx to Romrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!

fullmetal509 said:
After achieving S-Off, thanx to Roadrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!
Click to expand...
Click to collapse
OK so first off you can't have 2 recoveries. Also it is called rumrunner. ROM manager is not support for this phone. And Twrp is better. Lol

fullmetal509 said:
After achieving S-Off, thanx to Romrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!
Click to expand...
Click to collapse
That's ROM Manager's somewhat backwards way of asking you what to do about its recovery image.
The options, from top to bottom, are "Install CWM", "I have already installed CWM", and "I have already installed TWRP."
If you choose the one that applies to you, it will stop bothering you.
ROM Manager works fine, btw - once you've convinced it that you have CWM-m7vzw installed (it can even install it itself(!)) you can back up and restore and flash ROMs 'til your heart's content–even CM10.2 nightly updates.

I have a similar question, I have cwm on my htc and want to go over to twrp. What's the best way to remove cwm?

bsbuggs said:
I have a similar question, I have cwm on my htc and want to go over to twrp. What's the best way to remove cwm?
Click to expand...
Click to collapse
You do not need to remove cwm, all you need to do is put the twrp.img file in your adb/fastboot folder, boot to the bootloader, select fastboot usb - sometimes it loads automatically to this -, type fastboot devices to confirm your device then type "fastboot flash recovery twrp_filename.img" - type that without the quotes and the actual filename with .img. Once you enter that and hit enter you should get some text saying it is being sent to your phone and it should tell you if it worked or failed.

Thanks I appreciate the help..
Sent from my HTC6500LVW using Tapatalk

Guess I need to try and install twrp again. Some folks over in the omni room forum are saying that the latest cwm is what's causing baseband issues when flashing roms (no service)
Sent from my HTC6500LVW using Tapatalk

[Q] CyanogenMod + ClockworkMod = stuck at "Samsung" screen on boot

I was trying to install the CyanogenMod[1] Firmware (CM) for my Samsung SPH L710 (Sprint) using these instructions[2]. I was using Mac OS X / Heimdall command line binary, downloaded here[3], version 1.4.0. The CM instructions for my phone recommended 1.4RC1 but this package had me using a non-standard library location on my computer whose path wasn't in my standard PATH. Regardless, the Heimdall binary I'm using works as expected.
I installed ClockworkMod (CWM) recovery image using Heimdall. The CM page recommends I use 6.0.3.1 which I installed without unexpected results. I rebooted my phone into "recovery" mode (Vol Up, Home Power) where I followed the step to backup my phone; which I did. Next, I did the "wipe/factory reset" an unnerving step, given how I've customized my phone. Next I proceeded to install CM itself. I tried installing two versions: cm-10.2.0-d2spr.zip[4] and cm-10.1.3-d2spr.zip[5] I downloaded both zip files using the Android File Transfer utility on Mac. The location, from the boot's perspective, is /scard/0/cm-10.1.3-d2spr.zip. The CWM Recovery / zip installer failed to both, throwing an assert error. I followed the instructions here[6], essentially stripping out the assert (first line). Nevertheless, the installer still failed.
I wanted to restore my backup and give up on the venture. However, I was unable to do so. I was getting the MD5 checksum error when trying to restore my backup via CWM. My restore directory was missing a "nandroid.md5" file, so using the "adb shell" I restored[7] it using these instructions. Now I could run my backup, but, my data configuration fails to restore. (I believe there's system, data, and two other categories) It seems the backup is corrupt? Over on this[8] CWM page they recommend 6.0.4.5, not the 6.0.3.1 version, which I flashed my phone with. Afterwards, after booting to recovery mode, CWM shows an odd message "root access is missing. Root device? This can not be undone" My impulse is "NO" since rooting is simply adding complexity to this already out of control problem. I click "No"
This is when the phone is now stuck on "Samsung" at boot.
I restored 6.0.3.1, to no avail. Yes, I can still adb into my phone, access the boot downloader screen and recovery screen, but I can not get past "Samsung" Reverting to 6.0.3.1 leaves me with a backup I can not restore.
I profoundly appreciate any ideas or help on this matter.
Update: my current (broken) system info:
Code:
adb shell getprop ro.build.version.release
4.3.1
adb shell cat /proc/version
Linux version 3.4.66-cyanogenmod-g34da3e6 ([email protected])(gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Nov 27 13:54:11 PST 2013
Obfuscated links to the above references (replace '-' with '.' in the domains)
1: wiki-cyanogenmod-org
2: wiki-cyanogenmod-org/w/Install_CM_for_d2spr
3: bitbucket-org/benjamin_dobell/heimdall/downloads
4: download-cyanogenmod-org/get/jenkins/49849/cm-10.2.0-d2spr.zip
5: download-cyanogenmod-org/get/jenkins/42488/cm-10.1.3-d2spr.zip
6: youtube-com/watch?v=QW1znjDLe-k
7: geekyzz-blogspot-com/2013/02/how-to-fix-nandroid-md5-mismatch-in_23.html
8: clockworkmod-com/rommanager

i'd flash the latest cwm > http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.5-d2spr.img
then reflash the cm 10 zip (you may want to download it again)
then flash gapps from here http://forum.xda-developers.com/showthread.php?t=2397942
good luck!

For what it's worth, Philz Touch is probably the best recovery out there right now, it is awesome enough that it made me switch from TWRP, a recovery that I swear by.
http://forum.xda-developers.com/showthread.php?t=2446393

Mr. Struck said:
For what it's worth, Philz Touch is probably the best recovery out there right now, it is awesome enough that it made me switch from TWRP, a recovery that I swear by.
http://forum.xda-developers.com/showthread.php?t=2446393
Click to expand...
Click to collapse
+1 - I use it

Thanks for the recommendations
I appreciate your agreeing on Philz Touch for recovery. However, my more fundamental problem remains, that I cannot boot past the Samsung screen. A friend recommended using this stock ROM: rwilco12-com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S3%20%28SPH-L710%29/Stock%20ROMs/JB/LJ7 but that failed to install. I copied the zip file via adb push to /scard/0 and tried using CWM to install via the recovery screen; but it failed, saying "installation aborted."
Thanks! — Kyle

I think what we are all getting at is that part of your problem might be your choice of recovery. If you aren't currently using Philz, maybe try switching and starting over.
Sent from my SPH-L710 using Tapatalk

So I've installed Philz Touch 6.00.8. Tried to install CyanogenMod, same assert error. Elsewhere http://forum.xda-developers.com/showthread.php?t=2303308 is talk that I need Fre3's MD4. So, I installed it, and now the device won't power at all.

Screen Ack said:
So I've installed Philz Touch 6.00.8. Tried to install CyanogenMod, same assert error. Elsewhere http://forum.xda-developers.com/showthread.php?t=2303308 is talk that I need Fre3's MD4. So, I installed it, and now the device won't power at all.
Click to expand...
Click to collapse
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
Mr. Struck said:
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
Mr. Struck said:
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Sorry Tapatalk not cooperating. So I assume you are aware of this based on your first post in this thread. Did you delete all the asserts up to the part that says "mount..."?
Sent from my SPH-L710 using Tapatalk

"He's dead, Jim."
The phone no longer response to the power button. The MD4 firmware update hosed something in a big way.

Screen Ack said:
"He's dead, Jim."
The phone no longer response to the power button. The MD4 firmware update hosed something in a big way.
Click to expand...
Click to collapse
If you had taken the 4.3 update with KNOX, you can not downgrade the bootloader to MD4 - this WILL brick your phone.
There are a number of threads highlighting this eventuality.
Anyway downgrade bootloader from 4.3 to 4.1?
[STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP)
3-4 others in General. I've not found a "debrick" image for this phone as of yet.
There is this thread : [GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) but I am not sure that would work for you.
I'm sorry this happened and I hope you can get your phone fixed.

jdelano said:
If you had taken the 4.3 update with KNOX, you can not downgrade the bootloader to MD4 - this WILL brick your phone.
There are a number of threads highlighting this eventuality.
Anyway downgrade bootloader from 4.3 to 4.1?
[STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP)
3-4 others in General. I've not found a "debrick" image for this phone as of yet.
There is this thread : [GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) but I am not sure that would work for you.
I'm sorry this happened and I hope you can get your phone fixed.
Click to expand...
Click to collapse
I second that sorry as well. I hate to say it, but from what I have read and researched, when Knox prevents a bootloader change, it is the ultimate brick, as in not even a JTAG can fix it. Very crappy, and I think Samsung is going to take a small hit in the future from previous owners who move away from them the next time a device update is in store thanks to the garbage known as Knox that was forced on a lot of unsuspecting device owners.

[Q] Can't boot after failed root attempt

SOLVED
So today I decided I would try to install a custom OS/ROM whatever it's called on my HTC One X. I unlocked the bootloader successfully without any problems. Then I went on to root the phone, and this is where it all went wrong. I found a tutorial and followed it to the tiniest detail. I am unable to link to it because I am a new user. When my phone rebooted it went to the "HTC Quietly Brilliant" boot screen. I left it there for 30 minutes and it still didn't move on. What do I do now? I am a super noob at this, and I admit that I am an idiot for not reading more up on it first, it just all seems so super complicated.
Thanks in advance for any help and guidance.

well, pm me the link so i can check the instructions you followed and maybe help you

lukes91 said:
well, pm me the link so i can check the instructions you followed and maybe help you
Click to expand...
Click to collapse
I sent you the link. Thanks for your help.

http://rootmyandroid.org/root-htc-one-x-windows-linux-mac-osx.html
Here is the link, so everybody can help you.
Sent from Somewhere Over The Rainbow...
---------- Post added at 08:17 PM ---------- Previous post was at 07:28 PM ----------
so it hanged just after you run the script to root device, right? after you ran the script in the shell, did it return any error?

lukes91 said:
http://rootmyandroid.org/root-htc-one-x-windows-linux-mac-osx.html
Here is the link, so everybody can help you.
Sent from Somewhere Over The Rainbow...
---------- Post added at 08:17 PM ---------- Previous post was at 07:28 PM ----------
so it hanged just after you run the script to root device, right? after you ran the script in the shell, did it return any error?
Click to expand...
Click to collapse
No, no error, it said "Daemon launched successfully" or something along those lines, my phone turned off and turned back on to the HTC boot screen.

Ok, try this: if the phone is still on keep the power button pressed till it restarts and press also vol down button until you arenin the bootloader; if the device is off, enter bootloader keeping power and vol down button pressed... Now my suggestion is to flash a custom recovery and a custom rom, you will get root privileges and the phone will work again...
Sent from Somewhere Over The Rainbow...

If you are unlocked (you see it in bootloader) you can flash a custom recovery and a custom rom. Look up for your favorite Recovery and flash it.
Download the img File to directory where you have the fastboot files and run this code in command prompt
Code:
fastboot flash recovery name_of_recovery.img
After it you can boot into Bootloader and turn to recovery to get access to phone and SD Card/flash Rom

Did you flash boot.img and erased the cache?
Sent from my HTC One X using Tapatalk 2

Okay, so I successfully flashed TWRP and launched into recovery mode with it. How I get the custom ROM files on my SD card, when I plug my phone into my computer with USB it doesn't show up in the drives section, so I can't open up the SD card.
Another thing is that with the latest version of TWRP for my phone touch doesn't work in the recovery mode. There's a version that does, but it says it doesn't have USB mount or something like that. What's the next step?

You need to mount sd card via recovery, and having the touchscreen working is better as it will be easier to move inside aroma installer... Use philz recovery (if you want a sense rom use 5.15.9, if you want kitkat use the last version), enter the recovery, plug the phone into pc, mount sdcard via recovery, copy the zip over it and follow the instructions to install rom... You can find the instructions in every rom thread op... Ask if you need more help
Sent from Somewhere Over The Rainbow...

Thanks for all the help, I am really starting to get a better understanding of how this actually works. I flashed Philz recovery and went into recovery with it. Then I went to mount and mounted USB Storage. Is this the right thing? It still doesn't show up on my PC

ChaosDuck said:
Thanks for all the help, I am really starting to get a better understanding of how this actually works. I flashed Philz recovery and went into recovery with it. Then I went to mount and mounted USB Storage. Is this the right thing? It still doesn't show up on my PC
Click to expand...
Click to collapse
which version did you flash? sometimes it keeps a couple of minutes before popping up the sdcard in pc, but i ensure you that 5.15.9 usb mout feature works fine... some users (me too) faced some issues with some 6.x.y version (sorry, i don't remember which one as i still use sense rom and so philz 5.15.9)

lukes91 said:
which version did you flash? sometimes it keeps a couple of minutes before popping up the sdcard in pc, but i ensure you that 5.15.9 usb mout feature works fine... some users (me too) faced some issues with some 6.x.y version (sorry, i don't remember which one as i still use sense rom and so philz 5.15.9)
Click to expand...
Click to collapse
I flashed latest version 6.19.3. There are only 3 versions available as far as I can see. They are:
6.19.3
6.12.8
6.07.9
I'll try flashing the two other versions and see what happens.

ChaosDuck said:
I flashed latest version 6.19.3. There are only 3 versions available as far as I can see. They are:
6.19.3
6.12.8
6.07.9
I'll try flashing the two other versions and see what happens.
Click to expand...
Click to collapse
you can find 5.15.9 here

lukes91 said:
you can find 5.15.9 here
Click to expand...
Click to collapse
Thank you! It finally showed up on my PC after a minute. I wanted to try Android 4.4.2 KitKat custom ROM "Carbon" so I want to ask a bit of an off-topic question. What are the GApps thing that I am told to install with the ROM? Why are they so important, what do they do?

ChaosDuck said:
Thank you! It finally showed up on my PC after a minute. I wanted to try Android 4.4.2 KitKat custom ROM "Carbon" so I want to ask a bit of an off-topic question. What are the GApps thing that I am told to install with the ROM? Why are they so important, what do they do?
Click to expand...
Click to collapse
those are google apps (i bet you understood what they are for just reading the full name ) i'm sorry to tell you that philz 5.15.9 can't flash 4.4.2 android, so you should update it... but now you have the zip on sdcard at least... give a look at latest TWRP you can find here in the OP #2 (everyhing should work with this version, but i still didn't test it, so i can't ensure it... i told you to use Philz 5.15.9 because i was 100% sure USB mount works with that recovery, and we needed to put a rom zip on sdcard ) now that you understood how things work, you can choose the recovery you want according to your reqirements have a nice flash man, and feel free to ask me if you need any further help

lukes91 said:
those are google apps (i bet you understood what they are for just reading the full name ) i'm sorry to tell you that philz 5.15.9 can't flash 4.4.2 android, so you should update it... but now you have the zip on sdcard at least... give a look at latest TWRP you can find here in the OP #2 (everyhing should work with this version, but i still didn't test it, so i can't ensure it... i told you to use Philz 5.15.9 because i was 100% sure USB mount works with that recovery, and we needed to put a rom zip on sdcard ) now that you understood how things work, you can choose the recovery you want according to your reqirements have a nice flash man, and feel free to ask me if you need any further help
Click to expand...
Click to collapse
I flashed to the newest Philz recovery again and successfully installed both ROM and GApps. Rebooting phone now, I hope it works... Been on HTC screen for a while though.

ChaosDuck said:
I flashed to the newest Philz recovery again and successfully installed both ROM and GApps. Rebooting phone now, I hope it works... Been on HTC screen for a while though.
Click to expand...
Click to collapse
have you flashed boot.img via fastboot and erased cache via fastboot? the commands are
fastboot flash boot boot.img
fastboot erase cache
remember that first boot can take a while (in some cases up to ten minutes)

lukes91 said:
have you flashed boot.img via fastboot and erased cache via fastboot? the commands are
fastboot flash boot boot.img
fastboot erase cache
remember that first boot can take a while (in some cases up to ten minutes)
Click to expand...
Click to collapse
Ahhh yes, it seems that was the only thing I still needed to do. It's on the Carbon launch screen now. Thanks a bunch man, I literally love you! :laugh:

ChaosDuck said:
Ahhh yes, it seems that was the only thing I still needed to do. It's on the Carbon launch screen now. Thanks a bunch man, I literally love you! :laugh:
Click to expand...
Click to collapse
lol, you're welcome, happy i've helped you

Temporary CWM possible?

Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?

This would be the wrong section, but that's alright it'll get moved once a moderator sees it if I'm not mistaken! I don't think that method will work at all tbh.

tasar said:
Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?
Click to expand...
Click to collapse
Thanks for pointing out
It works! Well, at least i can start CWM, but i didn't try functionality yet.
Use this version: http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352
Choose T4 option.
You will get some distorted animated logo at the center for several second, then you will get CWM menu.

Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!

Need CWM version compiled for Zenfone 2.

sorg said:
Need CWM version compiled for Zenfone 2.
Click to expand...
Click to collapse
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.

Reviewers said:
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.
Click to expand...
Click to collapse
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
tasar said:
Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!
Click to expand...
Click to collapse
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.

sorg said:
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.
Click to expand...
Click to collapse
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM

Reviewers said:
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM
Click to expand...
Click to collapse
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).

sorg said:
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).
Click to expand...
Click to collapse
can you share one click batch file with us? if we only could back up the rom it would be awesome..

With this temporary CWM custom recovery, am I able to flash any zips in it? Sorry about the noob question, wanted to use it to flash the disguised version of Cerberus.