Develop Bugs

Mac OS X Fastboot Mode <Waiting for Device>

Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks

i use windows but i also get problems when i didnt had a break after the flash parts/ update parts

brosenz said:
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
Click to expand...
Click to collapse
I know nothing about using Macs but have you installed the device drivers? As you are getting no serial number returned when using fastboot devices im guessing not.
Mark.
On a side note please do not post questions in the Development Forums as that is not the place for them.
Thanks.

The device is being detected while running in normal mode, meaning I do have the drivers, the problem is when I go into FASTBOOT MODE, I can no longer see the phone

Craiq said:
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
Click to expand...
Click to collapse
But for the simple command ./fastboot-mac devices should work and it's not

in bootloader mode u need other drivers
but dont know how to install them on mac

First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?

dhemke17 said:
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
Click to expand...
Click to collapse
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"

brosenz said:
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
Click to expand...
Click to collapse
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?

dhemke17 said:
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
Click to expand...
Click to collapse
I've done that, going into FASTBOOT MODE manually and the same result. Yes I am rooted.

I just want to go back to stock and re-lock the phone, is there other way to accomplish that ?
NOTE: I've tried Mac and PC (Galaxy Nexus Root Toolkit 1.3), different USB cables, different USB ports, reinstalled all the drivers on the Windows computer, NOTHING, the phone it's not being detected in FASTBOOT MODE.
Is it possible to go back to stock and re-lock from the Recovery Mode ?, I have ClockWorkMode 5.5.0.2 installed and working fine.

You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.

mskip said:
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
Click to expand...
Click to collapse
I used FASTBOOT to unlock and Root, no problem at all, use the phone for 10 days and them decided to go back to Stock and Re-Lock. If I connect the phone in normal operating mode to the computer it will be recognized and I can see the phone from the computer connected via USB, so the cabe, port on the phone and port on the computer are OK. I've tried different computer (Mac and PC), different OS (Mac OS X and Windows 7), different USB cable, different USB port.

Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.

dhemke17 said:
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
Click to expand...
Click to collapse
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks

brosenz said:
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
Click to expand...
Click to collapse
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol -... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...

dhemke17 said:
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol +... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
Click to expand...
Click to collapse
I do not know why but Vol + does not work in my phone

brosenz said:
I do not know why but Vol + does not work in my phone
Click to expand...
Click to collapse
My bad lol...down...volume down

I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just used your video to unroot my galaxy nexus 4.0.4 thanks a lot!

[Q] stuck at bootloader/odin mode

hey guys,
I sold my galaxy nexus today to my cousin, she picked up the phone, working perfectly and then came back with it half an hour later with the phone permanently in Odin Mode xD
I have experience with rooting, flashing and all of that and I can't seem to find a way of fixing the phone, basically what is going on is that every time the phone is turned on it goes straight to odin mode and from there is not able to boot or do anything, I took out the battery (believe me a lot of times) and still have the same issue, I tried booting into the bootloader but it gets stuck there and the computer does not recognize it either the toolkit or in the command prompt, I flashed via odin the following firmware http://forum.xda-developers.com/showthread.php?t=1827685 with no luck, I was just able to boot into the phone in safe mode, but from there if I reboot I'll encounter the same problem.
for me it seems like the bootloader is damaged?
any suggestions or help will be appreciated.... thanks!!

Oh boy. After reading all that I just see a bunch of errors after another error.
1) Toolkit
2) Odin
First off,
1) Delete all drivers for the Galaxy Nexus
2) Pull battery out of Galaxy Nexus then put it back in
3) Hold Volume Down + Volume Up + Power
4) Plug phone USB in.. computer should make a "BEEP" noise. If not then on the phone reboot back into bootloader and next time around it should come back.
5) http://forum.xda-developers.com/showthread.php?t=1514942 -- download these drivers and manually install the Galaxy Nexus drivers using those.
6) Set up ADB/Fastboot environment (I won't tell you how... just google it) dont use toolkits.... toolkits dont teach you how to get yourself out of these kind of situations. This is why I NEVER EVER EVER EVER endorse usage of toolkits.
7) use command prompt and prompt it towards your fastboot.exe (/sdk/platform-tools/)
8) type: fastboot devices
9) find phone? ok good
10) https://developers.google.com/android/nexus/images#takju (download the respective one. takju for GSM, etc etc -- download the right one, sprint, vzw etc)
11) fastboot flash those files.
12) fastboot oem lock
13) phone should boot
14) give it back to your cousin.
note: this leaves her available to get OTAs etc etc and you wont be responsible for anything root related. if she wishes to root / custom rom / etc (doubt it) then skip #10 and ahead. flash a custom recovery (just incase yours got screwed up) and flash a custom ROM as well as wiping factory, cache, dalvik, and boot into android.
cant boot into android but still want custom? skip #12 and above. fastboot flash those files, boot into android, drag new rom / kernel onto phone and then go back into recovery to flash it (or go into recovery and mount it to your pc and put the rom files etc onto the phone).
if this helps, hit the thank you. thanks. next time, please dont use toolkits and spend the couple of minutes reading this stuff on how it works rather than having it spoon fed to you aka toolkit!

zephiK said:
Oh boy. After reading all that I just see a bunch of errors after another error.
1) Toolkit
2) Odin
First off,
1) Delete all drivers for the Galaxy Nexus
2) Pull battery out of Galaxy Nexus then put it back in
3) Hold Volume Down + Volume Up + Power
4) Plug phone USB in.. computer should make a "BEEP" noise. If not then on the phone reboot back into bootloader and next time around it should come back.
5) http://forum.xda-developers.com/showthread.php?t=1514942 -- download these drivers and manually install the Galaxy Nexus drivers using those.
6) Set up ADB/Fastboot environment (I won't tell you how... just google it) dont use toolkits.... toolkits dont teach you how to get yourself out of these kind of situations. This is why I NEVER EVER EVER EVER endorse usage of toolkits.
7) use command prompt and prompt it towards your fastboot.exe (/sdk/platform-tools/)
8) type: fastboot devices
9) find phone? ok good
10) https://developers.google.com/android/nexus/images#takju (download the respective one. takju for GSM, etc etc -- download the right one, sprint, vzw etc)
11) fastboot flash those files.
12) fastboot oem lock
13) phone should boot
14) give it back to your cousin.
note: this leaves her available to get OTAs etc etc and you wont be responsible for anything root related. if she wishes to root / custom rom / etc (doubt it) then skip #10 and ahead. flash a custom recovery (just incase yours got screwed up) and flash a custom ROM as well as wiping factory, cache, dalvik, and boot into android.
cant boot into android but still want custom? skip #12 and above. fastboot flash those files, boot into android, drag new rom / kernel onto phone and then go back into recovery to flash it (or go into recovery and mount it to your pc and put the rom files etc onto the phone).
if this helps, hit the thank you. thanks. next time, please dont use toolkits and spend the couple of minutes reading this stuff on how it works rather than having it spoon fed to you aka toolkit!
Click to expand...
Click to collapse
thanks for your reply, just a quick question by installing the drivers you mean to do it while in the safe mode of the phone? I can't get the pc to recognize the phone while on bootloader.
when I get to the bootloader the phone is basically stuck. I can't select move or reboot.

davidquesada said:
thanks for your reply, just a quick question by installing the drivers you mean to do it while in the safe mode of the phone? I can't get the pc to recognize the phone while on bootloader.
when I get to the bootloader the phone is basically stuck. I can't select move or reboot.
Click to expand...
Click to collapse
That's not a good sign that you can't move using volume up/down keys in bootloader. You need the PC to detect your phone's ADB (ensure that USB debugging is enabled).
I never been to safe mode but try going into about phone -> and tapping "build #" 10 times (if you're on 4.2.X) to enable dev options and check usb debugging.

zephiK said:
That's not a good sign that you can't move using volume up/down keys in bootloader. You need the PC to detect your phone's ADB (ensure that USB debugging is enabled).
I never been to safe mode but try going into about phone -> and tapping "build #" 10 times (if you're on 4.2.X) to enable dev options and check usb debugging.
Click to expand...
Click to collapse
so.... bad news
I was able to flash again Jelly bean via odin an I was able to boot into android in safe mode (the only way it does), then using the command prompt I send it to bootloader and it got stuck and windows does not recognize it
my question is how my cousin bricked the device in like 30 minutes... because when I gave it to her it was perfectly working....

Formatted Data.. i am struck

Hi Guys,
I wanted to do a clean install. So,i formatted Cache, System.
But by mistake i formatted Data also.
Now the ROM zip file is also lost.
Can anybody help me as how to install a new OS now.
Cheers!!!!

Can't you mount data and enable USB storage?
Sent from my Nexus 7 using xda app-developers app

use GSM TOOLKIT

Device Driver installation is getting failed.. I am able to mount though...

Connect to a computer and paste TWRP ou CWM and a ROM.
In last case, reboot to fastboot and flash google image through Galaxy Nexus toolkit.

I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...

mac4rfree said:
I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...
Click to expand...
Click to collapse
You must flash a google image through nexus toolkit and your problem will be solved.

Nope don`t make it so complicated. Flash a rom + gapps though adb sideload.
http://teamw.in/ADBSideload

mac4rfree said:
I am not able to connect to Computer and copy any files to Phone.. But using Toolkit i should be able to push ROM to Phone.. please correct me if i am wrong...
Click to expand...
Click to collapse
Connect to the toolkit and flash a stock image. I had the same problem with you. Flashing stock image is the best option.
So do the following:
1. Download toolkit (mskip) and install drives (if not installed already)
2. Coonect your phone to a pc
3. Enter fastboot mode
4. From the toolkit choose the rom you want to flash
5. then choose the option to flash stock image (option 9 i think)
6. Sit back and relax
7. start rooting your phone again.
GOOD LUCK!:fingers-crossed:

Like most people here I also advice the same solution because this solution saved my friend who was in the same situation as you.
1. Download and install Galaxy Nexus Toolkit to PC
2. Download Galaxy Nexus Stock Factory Image from Google
3. Do the 3 finger boot (power+volume up+volume down) to get into Fastboot mode
4. Plug in phone to Pc
5. Launch Galaxy Nexus toolkit and Select the option that says extract and install stock factory image

New Problem.. My phone restarted and it went to bootloader screen.. now the GSM Tool Kit is saying "Waiting for device"... Now what to be done???

What has this got to do with Development again?

Sorry My Bad... I posted it in wrong section..

I downloaded and installled GSM Tool kit. I downloaded the Google image but when i tried to flash it is booting to bootloader screen but after that Tool kit is saying <waiting for phone>
I pushed the older zip file to sdcard using adb push command and installed it..

[Q] impossible to access the recovery

Hi guys
I have a huge problem, I have the physical buttons of the volume broken (absolutely non-repairable) while they are trying to install a new Romy (total Wipe and /system format) I accidentally pressed on system reboot into recovery.
in this moment i have the written google when access (obviously it is)
I tried with GNEX Toolkit V11.1 but I have a serious problem
the serial number of the writer but also writes offline
GNEXUS 4.2.2
How do I get into recovery?
Sorry for my bad English

pull the battery, put battery back in.
press and hold vol up and down, then press and hold the power button while still holding vol up and down
use volume buttons to go to recovery. press power button to enter after recovery is selected.
this is basic nexus 101. learn it. and stop using a toolkit.

I have the physical buttons of the volume broken. I usually use the function number 24 of the toolkit to get into recovery, but this time I formatted the /system and I accidentally restarted the cell without installing anything.
The various drivers are installed correctly
GNEX Toolkit gives me the serial number but not online.

pollopopo said:
Hi guys
I have a huge problem, I have the physical buttons of the volume broken (absolutely non-repairable)
Click to expand...
Click to collapse
So basically, you're left with a stock recovery, no adb because of that (Does sideload work out the box? Can't remember; if yes, then OP has a driver issue) and no system to boot from.
Yet another solution would be a USB jig and Odin. Maybe that works for you.
You should drop the toolkit.
a maguro wrote this.

i have the CWM recovery.
already happened once but I had formatted the /system folder, on that occasion was able to enter through the starter toolkit in recovery mode.

help me pleas...

pollopopo said:
i have the CWM recovery.
already happened once but I had formatted the /system folder, on that occasion was able to enter through the starter toolkit in recovery mode.
Click to expand...
Click to collapse
If you have cwm and you can enter the recovery you can adb push..
Sent from my Galaxy Nexus using XDA Premium HD app

This is not xda-spoonfeeeders, read the stickies
Sent from my Nexus 10 using Tapatalk 4 Beta

in the management of devices in windows says it is a samsung device but does not recognize the ADB interface. It is not the first time I connect drivers are all there and they work.

i use the gnex toolkit and the CMD (ADB command ecc...) but both give me the serial number, but respond "device offline" for any command

pollopopo said:
i use the gnex toolkit and the CMD (ADB command ecc...) but both give me the serial number, but respond "device offline" for any command
Click to expand...
Click to collapse
listen buddy, read this thread
http://forum.xda-developers.com/showthread.php?t=1812959
questions that you're asking were answered many many times. learn something for a change. stop using that godamn toolkit.

I have already tried etc. ... I can not get into recovery
I have the volume buttons broken and adb gives me "device offline"
http://imageshack.us/photo/my-images/822/dgq9.png/
I searched and searched but can not seem to solve the problem
all the drivers are installed, as well as "omap 4460" and all work properly.
I can not get him in the recovery through adb or toolkit

pollopopo said:
I have already tried etc. ... I can not get into recovery
I have the volume buttons broken and adb gives me "device offline"
http://imageshack.us/photo/my-images/822/dgq9.png/
I searched and searched but can not seem to solve the problem
all the drivers are installed, as well as "omap 4460" and all work properly.
I can not get him in the recovery through adb or toolkit
Click to expand...
Click to collapse
Forget it. Use a USB jig to get in download mode, its your only chance.
a manta wrote this.

thank you very much, as soon as I get from ebay hope to be able to solve everything

how do I prevent odin erase all sd memory??
I downloaded the original rom I extracted,
I extracted the file image-yakju-jdq39.zip
Inside there is the file system.img
I converted the file through GNEXUS toolkit. Tar
If I use this file with odin you can avoid that deletes all data on sd and change the recovery etc. ..?
Solved by the method mentioned above

Computer doesn't recognize Zenfone 2

My computers don't recognize my Asus Zenfone 2 Ze551ml. I've installed the intel drivers, the asus drivers, the google android drivers. I've restarted, tried different USB ports, tried different computers, and tried different USB wires but to no avail.
I originally wanted to unroot so that I could apply OTA updates but I couldn't get into recovery, all the phone does is restart into bootloader again. All the solutions I read require me to use ADB or get into recovery and since I can't get into recovery or get any computer to recognize the phone I seem to be stuck.
I haven't updated the OTA since 2.18.40.12 version. Can anyone help me figure out how to update my phone or get my computer to recognize it?
Thanks,

Please see the following for hardware reset/wipe cache partition procedure:
http://www.asus.com/us/support/FAQ/1011956/
Please see the following and scroll down for manual firmware update procedure:
http://www.asus.com/us/support/FAQ/1009748/
If you have any questions or concerns with Zenfone 2 please feel free to contact me direct at [email protected].
Sincerely,
ASUS_USA

Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,

Kalkin19 said:
Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,
Click to expand...
Click to collapse
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.

Or take out the sd card and copy to that, once back in phone you can then copy or move...

ultramag69 said:
Or take out the sd card and copy to that, once back in phone you can then copy or move...
Click to expand...
Click to collapse
Tried it this way and then rebooted the phone. The phone recognized that there was an update file, and when I allowed it to install it rebooted into the Fastboot screen and then did nothing. I waited a half hour before touching the phone. When I rebooted the phone it didn't update and nothing had changed.

cmendonc2 said:
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.
Click to expand...
Click to collapse
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.

Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app

yakub234go said:
Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
I have. I tried it on 2 desktops and 3 different laptops, I installed the necessary drivers on all of them and tried using different USB cables. No luck.

Kalkin19 said:
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.
Click to expand...
Click to collapse
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.

ultramag69 said:
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.
Click to expand...
Click to collapse
My computers don't recognize my phone even when it's on fastboot mode so I can't follow any of the steps

Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk

corrsea said:
Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks for directing me to that thread, it looks like, unfortunately, I have lost root access over the course of trying different solutions... Anyone know of a way to allow terminal to access root without superuser?

i have the same problem, computer sees my device in fastboot but i cant flash anything through recovery, everything is whiped i have no system on phone now i tried everything.
when i use adb drivers suggested in post above it says outdated server and still doesnt see my device in recovery mod.
i tried on 2 computers
i tried stock recovery matching my stock rom
i tried twrp
in general it says on my phone"you need sdb 1.0.32 or higher" but i use 1.3 version (15 secs install)
any suggestions?
thats the first phone ive ever bricked and i'm panicking right now...

Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD

krasCGQ said:
Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Sorry for such a delayed response, I haven't logged in and checked my messages in a while. This issue was fixed for me randomly. I kept plugging my phone into my computer and it eventually recognized it (after about 60 different tries). I quickly added adb, unlocked, rooted and have been having no issues since then. I appreciate your link! Hopefully it helps others in the future.