Develop Bugs

What am I doing wrong? Loading baconbits.

So I perm rooted and it says S-Off in fastboot and I have superuser access I believe.
I got rom manager and downloaded clockwork through rm. I try to install rom from SD card, select the baconbits rom, it asks to backup or clear, I have tried both.
The phone boots to htc screen, then shows a black screen with a phone and a red symbol over it. I waited 20 minutes on that screen and nothing happened.
I was able to push vol up and power to get a console but I can't load anything there. It will reboot just fine after that but I have no changes and still cannot overclock.
Does this have something to do with the user keys or whatever?
Thanks in advance for reading this and any help that gets offered. I hate to have my first post on a forum being a "help me" post.
Sent from my T-Mobile G2 using XDA App

Go into Rom Manager and try to flash Clockwork recovery again. This has happened to a lot of people... Flash it a second time, and it should be good.
Dan

Did you download the "g2-recovery-test-keys.img" from the 3rd post quoted below?
Place that file in the C:/android/tools or whatever your cd line is, which should in the tools folder. Now go the 6th step. FYI the sixth step I tried from fastboot and recovery, none worked until I reinstalled the drivers my computer kept prompting me for and immedatly got the OKAY's from the 7th step.
Edit: The code "fastboot flash recovery g2-recovery-test-keys.img" should be copied pasted onto your cmd.
ciwrl said:
Noob walkthrough:
1.Setup Android SDK and install drivers/udev rules as needed
2. S-Off your g2 http://goo.gl/Sc134
4. Copy vision-baconbits-0.3.zip to your sdcard, rename it update.zip (you can do this via adb using: adb push vision-baconbits-0.3.zip /sdcard/update.zip)
5. Reboot to fastboot mode (adb reboot bootloader)
6. Flash the recovery http://n0rp.chemlab.org/android/vision/g2-recovery-test-keys.img : fastboot flash recovery g2-recovery-test-keys.img (if you get 'waiting for device' your phone either isnt in fastboot mode, or you will need to fix your sdk drivers)
7. You should get two 'OKAY's once recovery flash is complete
8. Press the power button once; then the vol down button to highlight 'recovery'; then the power button again to select the 'recovery' option
9. The phone will reboot to recovery
10. Press volume up+power to show the recovery menu
11. Select the 'Apply:update.zip' option, using volume keys to navigate, and power button as [enter]
12. Once the zip applies, reboot
If you get signature verification errors on the zip, it means your fastboot flash of recovery failed to apply, redo it
Click to expand...
Click to collapse

Bingo, That worked. Glad it was that simple. I actually had to flash clockwork a third time to get it to go all the way.
Sent from my T-Mobile G2 using XDA App

[GUIDE] Noob's Guide #6: I just HTC Unlocked, what now?

First thing you need to know is that no matter what happens, even if your phone is abducted by rabid kittens, I am not responsible for your actions. Second is that you just voided your warranty, no doubt about it. HTC has your serial number with record that you unlocked your bootloader. Thanks to JAS_21 for the idea for making this guide. So, the next things you are going to want to do are to flash clockworkmod recovery, and then su. Then you can flash a ROM. Let's start with clockworkmod.
You want to get the android-sdk working, which you can find a guide to here.. Then you want to go to this thread. Download the file attached to the post. Use winzip if you have windows or just click on it on mac to unzip the file. Plug your phone into your computer and select "charge only" mode. Copy the cwm img file to the tools folder of the android SDK. Now, it's time to open up ADB. Open up a command prompt on windows or a terminal window on Mac/Linux. Follow these commands.
Code:
cd [insert location of android-sdk here]/platform-tools
adb reboot bootloader
You should now see Fastboot USB on your phone. Open a new command or terminal window. Type the following:
Code:
cd [insert location of android-sdk here]/tools
fastboot flash recovery cwm-recovery-vivow.img
fastboot reboot
Congrats, you have now flashed clockworkmod recovery. Now, onto installing root access. Next, grab the su zip attached to the OP of this thread. Plug your phone into your computer and select "disk drive" mode. Copy the su zip file to the root of your sd card. Unmount your sd card and select "charge only" mode on your computer. Reboot into recovery. The easiest way is probably to open up a command window and type:
Code:
cd [insert location of android-sdk here]/platform-tools
adb reboot recovery
When your phone is in recovery, click "install zip from sd card," then "choose zip from sd card," then the su zip file. Hit the back button once. Then select reboot system now. When your phone reboots, download superuser from the market. Now you are ready to use root apps! If you want to flash a ROM, continue on.
Download the ROM of your choice. If you want to, use my guide for choosing a ROM found here. Download the ROM zip file. Plug your phone into your computer and select "disk drive" mode. Copy the rom zip file to the root of your sd card. Don't unmount your sd card yet.Next, make a copy and put it on your desktop. Use winzip on windows or just click on mac/linux to unzip the rom file. In the root of the ROM, you should see a boot.img file. Copy that to your tools folder of your android-sdk folder. Now, unmount your sd card and select "charge only" mode on your computer. Next, follow the following steps.
Before installing the ROM...
1. Download Titanium Backup from the market, allow superuser permissions, then click menu>batch>backup all user apps.
2. Make sure fastboot is off in settings>power.
3. Put the ROM zip on the root of your SD Card
4. Download SMS Backup and Restore, and backup your SMS.
5. Back up your contacts by checking "back up my data" or something like that under settings/privacy.
How to install the ROM...
1. Turn off phone, and hold power and volume down until you get a white screen that says Hboot.
2.Volume down/up is for scrolling; power is for selecting.
3. Scroll down and select RECOVERY.
4. Scroll down and selected BACKUP AND RESTORE.
5. Select BACKUP and wait for it to finish.
6. Hit the back button to go back to the main menu.
7. Scroll down and select WIPE DATA/FACTORY RESET.
8. Scroll down and select WIPE CACHE PARTITION.
9.Hit the back button to go back to the main menu.
10. Scroll down and select ADVANCED, then WIPE DALVIK CACHE.
11. Hit the back button to go back to the main menu.
12. Scroll down and select INSTALL ZIP FROM SD CARD, then CHOOSE ZIP FROM SD CARD, then whatever the ROM zip is.
13. Let it do its thing. This may take 5-10 minutes. DON'T PULL THE BATTERY.
Next, it is time to flash your boot image. Follow these commands.
Code:
cd [insert location of android-sdk here]/platform-tools
adb reboot bootloader
You should now see Fastboot USB on your phone. Open a new command or terminal window. Type the following:
Code:
cd [insert location of android-sdk here]/tools
fastboot flash boot boot.img
fastboot reboot
You are done with flashing the ROM now, congrats. To get your data back, follow the steps!
1. Run the initial setup. When you're setting up your google account, make sure the "keep data backed up" or whatever box is checked. This will make sure to restore your/keep your contacts backed up.
2. Redownload Titanium Backup. Hit menu/batch/restore missing apps with data.
3. Redownload SMS B+R. Restore your SMS.
4. Enjoy your new ROM!
I hope this guide clears things up for some people. If you have ideas or suggestions for this guide or others, feel free to comment. If I helped you, please hit the thanks button. I would really appreciate it!

Excellent guide!!!

i keep getting an error when trying to flash the recovery. when i type in fastboot flash recovery cwm-recovery-vivow.img it comes up saying cannot load cwm-recovery-vivow.img
also im s-on with hboot .98. could that be the problem?

reaper540 said:
i keep getting an error when trying to flash the recovery. when i type in fastboot flash recovery cwm-recovery-vivow.img it comes up saying cannot load cwm-recovery-vivow.img
also im s-on with hboot .98. could that be the problem?
Click to expand...
Click to collapse
Had the same issue but solved after looking over the instructions for doing this if you were downgrading. Instead of placing the image file on the root of your sd card, place it in the folder that contains fastboot in your android sdk. Do that and you will be able to flash it and continue with the instructions.

Oh wow. You guys are right. That's a typo. I'll fix that.
Sent from my ADR6350 using xda premium

Excellent post! Easy to follow, worked...what more could you ask for?

Yeh I thought that might have been the problem. But I ended up relocking the bootloader, downgraded using attn1s tool and after that it was all smooth sailing. Running mikrunny v1.01. But this is an excellent guide
Sent from my ADR6350 using XDA App

Excellent guide! Thanks!
Sent from my ADR6350 using XDA App

no boot.img?
When I try to flash the boot.img at the last step, it says error: Cannot load 'boot.img'. I tried to start the phone and it sticks as the htc splash screen ... any ideas?

Did you put it in the sdk tools folder?

just wondering...am i going to have to flash the su zip everytime i flash a new rom? Just flashed miui and when I superuser was not on the list of apps. I downloaded it, but have this feeling its not going to work until a flash su.zip

Nope, cuz most roms are already rooted.

I was having trouble getting my ADB to function correctly, so I went with the manual "update.zip" method to flash Clockwork. However, when HBOOT recognizes the PG32IMG.zip file, it just says its "Checking.." forever, and I don't know whether it's working or frozen up. How long is that part supposed to take? I'm so close!

Thanks for this post. Helpful and easy to follow!

frick frack and frick. Now my phone isn't recognized by my computer. Had zero issues with this before. I'm running the latest version of miui and cant get the phone recognized.

Noob question. Is it still possible to flash kernels on HTC sec unlock? Will the boot.img flash need to be done each time from now on? Great guide by the way.
Sent from my ADR6350 using XDA App

Every time you want to flash a Rom or kernel you need to flash the boot.img.
Sent from my ADR6350 using xda premium

Everytime I reboot the phone it gets stuck on the HTC logo. I have to rerun "flashboot boot boot.img" to get it to boot.
Please help.

ph1nn said:
Everytime I reboot the phone it gets stuck on the HTC logo. I have to rerun "flashboot boot boot.img" to get it to boot.
Please help.
Click to expand...
Click to collapse
That's an issue with the unlock I'm assuming.
Sent from my Mikrunny'd Superphone using Magic (TapaTalk)

It's unlocked via HTC's unlock tool.
Should i relock the phone, forget this guide, and use attn1's guide?
I already installed ClockworkMod 5.5 and CM7.2 nightlies, everything works unless i have to reboot then it loses the boot image. Any thoughts?
-----
edit: It was because of S-ON. I relocked my phone and used attn1's guide to bring the phone back to hboot 0.97 and then s-off. This guide is not useful it seems if you want to go AOSP.

[Q] Only boot into CWM recovery mode

My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.

If you're using Galaxy Nexus Toolkit v5.4 from mskip, you don't need to extract anything, just copy .tgz file into the appropriate folder and the toolkit will do the rest for you.
Try reflashing the stock image from google again (make sure you choose the one for CDMA version).
After that, use toolkit to flash CWM, and the touch version is fun.

highmoon said:
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
Click to expand...
Click to collapse
If you're using Windows. You can be saved at this point. The good thing is that your device is being recognized by ADB in recovery.
The toolkit installed the SDK onto your computer
Here is what you do to go save yourself
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
go to C:\Android-sdk-windows\platform-tools and put the ROM and Gapps in there
Now, with your phone plugged into computer and in recovery, open up a command prompt
In recovery, navigate to "Mounts and Storage" and be sure to select MOUNT DATA
type
cd c:\android-sdk-windows\platform-tools
adb push EXACTNAMEOFROM.ZIP /data/media
(depending on the file size, it will take about a minute or two)
adb push EXACTNAMEOFGAPPS.ZIP /data/media
adb reboot recovery
------
Okay, now that you have rebooted recovery , go to "install zip from sd card" and MAKE SURE you see the ROM and Gapps package, but DON'T flash them yet.
Go back,
Wipe data
Wipe Cache
Go to advanced and select Wipe Dalvik Cache (ignore the SD-EXT error that's normal)
Go to Mounts and Storage - and select Format System
Go back
Go to install zip from sd card, flash ROM, then slect install zip from sd card again and flash Gapps
REBOOT
Enjoy

Again...
Samsuck said:
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
Click to expand...
Click to collapse
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.

Up to you, you can also just flash stock images and start over.
My method should work too, and leave you with root
Your choice

highmoon said:
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You could do it either way.

Okay, I found a solution without wiping everything.
(Flashing a stock ROM image, or other ROMs would wipe your everything...)
But thanks people!
For those of you, who would encounter something like this (including me again), I'm leaving a note.
0) This problem happens because your Boot partition, overwritten by ClockworkMod recovery image, is no longer compatible with the rest 4.0.4 image. So you need not only "recovery.img", but also "boot.img". Unfortunately, boot.img is not there in the 4.0.4 ROM. But luckily, someone else extracted it.
1) Get the 4.0.4 stock image from here
(android.clients.google.com/packages/ota/verizon_prime/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip)
2) Extract "recovery.img" from the file above.
3) Get "boot.img" in here (aospdev.com/rhcp/dev/404boot_root.img)
4) Get into FASTBOOT mode
5) fastboot flash boot boot.img (if not renamed, "404boot_root.img" above)
6) fastboot flash recovery recovery.img
6) Enjoy

HTC One X won't boot

I am relatively new to the android rooting scene and have installed a file from zip using clockwork recovery to remove the 3 dot menu from applications but afterward my phone now doesn't boot, its just stuck at the HTC ONE screen i have tried factory reset from clockwork and it didn't work. i am wiling to do anything even if everything is erased and if it could be mac friendly even better but anything is fine

benny_w95 said:
I am relatively new to the android rooting scene and have installed a file from zip using clockwork recovery to remove the 3 dot menu from applications but afterward my phone now doesn't boot, its just stuck at the HTC ONE screen i have tried factory reset from clockwork and it didn't work. i am wiling to do anything even if everything is erased and if it could be mac friendly even better but anything is fine
Click to expand...
Click to collapse
I guess you are on a stock rooted rom?
Seems the version provided in the thread was incompatible with the stock rom version your are currently on:
A few solutions:
1. Search a custom rom in the development threads and flash it, choose an ICS rom though if its a sense rom..flashing a jellybean rom is a bit more advanced and isnt suggested for beginners.
2. If you know which stock rom your are using (1.28, 1.29 or 2.17) you can search for a corresponding rom and push/flash just the android.policy.jar from it back to yoru device - thats the file taht got overwritten when you flashed the 3dot removal zip.
3. If you got a nandroid backup, just revert to your backup in recovery.
...there are a few other solutions, which requires relocking your bootloader etc.
IF your are already rooted I would suggest to flash a custom rom, this is the easiest way to get your oen x back to live and running a custom rom can bring a lot of advantages: better battery life, smoother UI and a lot of stuff that enhances the user experience on the One X.
Cheers, Jan

Restore a nandroid from before you flashed the mod. Or find your relevant ruu, relock your bootloader and run the ruu from your pc
sent from my One X using xda venom premium

j4n87 said:
I guess you are on a stock rooted rom?
Seems the version provided in the thread was incompatible with the stock rom version your are currently on:
A few solutions:
1. Search a custom rom in the development threads and flash it, choose an ICS rom though if its a sense rom..flashing a jellybean rom is a bit more advanced and isnt suggested for beginners.
2. If you know which stock rom your are using (1.28, 1.29 or 2.17) you can search for a corresponding rom and push/flash just the android.policy.jar from it back to yoru device - thats the file taht got overwritten when you flashed the 3dot removal zip.
3. If you got a nandroid backup, just revert to your backup in recovery.
...there are a few other solutions, which requires relocking your bootloader etc.
IF your are already rooted I would suggest to flash a custom rom, this is the easiest way to get your oen x back to live and running a custom rom can bring a lot of advantages: better battery life, smoother UI and a lot of stuff that enhances the user experience on the One X.
Cheers, Jan
Click to expand...
Click to collapse
thanks so much for the great response what would be the best custom rom to install for just a better htc sense UI rom and what would be the best way to do it
EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!
So i know that i have 1.29 so how would i go about flashing the android.policy.jar could i just download the 3dotremover fix

Flashing a new rom
So how would i go about flashing a CM9 ICS rom to my htc considering that i can't access the sd card as it wont boot

benny_w95 said:
So how would i go about flashing a CM9 ICS rom to my htc considering that i can't access the sd card as it wont boot
Click to expand...
Click to collapse
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.

staviq said:
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.
Click to expand...
Click to collapse
Thanks so much i have spent hours on end searching the web for a fix originally it said that i couldn't mount the sd card but i tried anyway and it worked but thanks a lot

help
staviq said:
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.
Click to expand...
Click to collapse
Hi there, I am trying to follow these instructions but when i type adb devices I dont get a device listed at all, please help as I flashed the boot.img right before I was about to install a new rom but the rom had errors and so the installation was aborted and now im stuck in an eternal boot loop.
please help!

ADB commands only work in recovery or when you're booted in Android (not possible in your case). What you need to do is put your phone in fastboot mode and get into recovery from there (plenty of info on how to do that available on these forums).
Once you're in recovery mode ADB devices list should show your device and then follow the rest of those instructions.
If you can't get into fastboot from your bootloop force phone off by holding power button for 5 second, then once off hold volume down only and phone should boot in fastboot
Paranoid Android Pro Nexus 7 on Tapatalk HD

ZE500CL Can't boot TWRP/Recovery, Can't factory reset

Picked one of the 2e's up cheap. Check your Walmarts, it's on clearance for $11.
Followed the Root instructions. No problem there.
Followed the bootloader unlock instructions. It seemed to work but my splash screen didn't change.
Went to install the Russianbear Rom. That left me with a blackscreen and nothing else.
From there, I managed to get into TWRP and flash the Stock ASUS ZE500CL Rom. That went in fine and the phone is 100% functional.
But now, I can't boot into recovery or even access TWRP. If I Power+Vol +, to where it gives the option of Recovery/Reboot/Power etc, Recovery just brings me back to the same menu. I reflashed TWRP on through ADB. Still no go.
I rerooted and installed TWRP manager to attempt to reflash just brings me back to that same menu.
I wanted to reset it to stock again with the ZE500CL rom, or if possible, test a different rom for ****s and giggles. Just to see what flavors are out there.
Any input into how to get TWRP or another flasher working would be appreciated.

Fastboot flash twrp. I've had issues with twrp manager on that phone
Sent from my ASUS_Z00AD using XDA-Developers mobile app

jflow36 said:
Fastboot flash twrp. I've had issues with twrp manager on that phone
I did. Fastboot Flash Recovery Twrp.img through CMD. Still nada.
It's the first TWRP I used. and the crap thing is, I can't even revert to stock because that involves going through a recovery.
Click to expand...
Click to collapse

Try adb reboot recovery in Android. Remember to turn on USB debugging

HungNgocPhat said:
Try adb reboot recovery in Android. Remember to turn on USB debugging
Click to expand...
Click to collapse
done that too. Nada. And yup, still in Debug mode.

I take this from a Vietnamese post, you should read the post to see the screenshots: http://amtech.vn/threads/tat-tan-tat-ve-recovery-tren-zenfone-2-ze551ml-ze550ml.365204/ (these are different methods, not steps in one method)
Translated:
I. If your are unlocked and rooted, download Terminal Emulator from Play Store, copy your TWRP image to /sdcard, rename to recovery.img, then open Terminal Emulator, type
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
Remember to grant access to Terminal Emulator after typing su.
II. Download Rashr from Play Store (must be rooted and unlocked)
Copy your TWRP image to your sdcard. Open Rashr and choose Recovery from Storage then navigate to your TWRP image. Select YES at the prompt. (grant superuser if prompted)
III. Copy your TWRP image to your SDcard, then boot temporary TWRP, choose Install... then select Image... then choose the image. Select Recovery. Slide to confirm flash.