Develop Bugs

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?

grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium

All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk

Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....

borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?

grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html

zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted

~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'

anybody have any other suggestions to this? or a follow up?

It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium

Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.

grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)

ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?

grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app

not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img

Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"

grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm

ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

[Q] Phone only starting in Clockwork and Fastboot

After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM

luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?

Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot

After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.

Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!

luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.

if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip

[Q] NOOB bricked acer a100 help!

I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!

same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.

are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps

[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.

Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.

cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.

were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!

pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.

you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.

pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium

not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper

I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.

Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?

[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.

did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?

I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.

i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.

mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696

eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"

My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?

[Q] [HELP] Flashing System.img Failed

Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance

NyxHouse said:
Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance
Click to expand...
Click to collapse
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.

vivix said:
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.
Click to expand...
Click to collapse
The phone is indeed in bootloader mode and properly connected and recognized by pc.
Entering
fastboot devices
Shows the phone as well.
Can you please elaborate more on the drivers I need to install? Is it for the usb connection or for something else?
Thanks a lot for the reply

try this flastool version.

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!