Database Users

Please help me install the recovery image on my rooted Nexus one!

Hi all,
I am completely at my wits end here and just don't know what to do
I have successfully unlocked my stock Nexus One boatloader, and have installed superboot to root it.
- I am using Windows 7 64 bit with all USB drivers for the nexus one correctly installed
- I have remembered to reset debuggingt mode in the Nexus USB settings
- Rooted apps seem to be working fine - I've just been playing with the LED torch app and I have a 'Superuser Permission' icon in my programs list
I am attempting to install the Amon_Ra recovery file - I've tried two different versions of it with no joy so far.... 1.7.0 and 1.6.2
I am able to boot into fastboot (with the skateboarding droids) with no probs. I can see the device using fastboot devices. However, when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up.... Here is the terminal output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9C(-REMOVED-) fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3948 KB)...
---
Anybody have any idea why it hangs here and if there is anything else I can do to maybe figure out why? I'm pretty certain I've almost cracked it - installing this recovery image is a problem
Thanks in advance!
Gil

don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.

SiNJiN76 said:
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
Click to expand...
Click to collapse
Thanks for the quick response!
It still fails even when I don't rename the recovery image.
Re 'using a terminal on my phone' - is there a guide to this anywhere? Do I download a shell or something?
TIA!
Gil

Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.

It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?

Thanks everyone for the help so far.
SiNJiN76 said:
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
Click to expand...
Click to collapse
I have tried these steps - when I issue the su command, I get root and a dialog box prompting me to allow it. However, when I type the flash_image command, I get the following message:
flash_image: not found
How is it that I don't have the flash_image command on my Nexus?!
aoch88 said:
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Click to expand...
Click to collapse
I think fastboot is detecting my device, because I managed to display the serial number (I obsficated most of the output above for security reasons) and I also successfully unlocked the bootloader. After I unlocked the bootloader, I tried to copy over the recovery image, and it just hung, so I then went and installed Modaco's superboot version ERD27 with himem enabled. This allowed me root access but still will not allow me to flash with the recovery image.
In addition, I have noticed that since I installed superboot himem, I am having a couple of network issues. Firstly - my 3G signal has now dropped from virtually full strength all the time to now never more than 50% strength, and frequently gives network errors when accessing the android store. It has also said "emergency calls only" a couple of times and probably worst of all (!) no longer checks my gmail automatically (I have plenty of emails but don't get notified - texts work fine though and my contacts are all still there and my account seems to be linked) - could the superboot have affected this in any way?
Thanks all for your help - I'm getting a little worried I may have totally borked my phone now
Gil

A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?

Try to redownload the recovery image, maybe you got a bad download.

thisisgil said:
when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up....
Click to expand...
Click to collapse
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0

thisisgil said:
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Click to expand...
Click to collapse
Another thing I discovered recently: Never use a port on a USB hub. Always use a USB port on the PC directly. I was having trouble flashing ROMs on my Acer Liquid and they went away when I stopped using a port on the hub.

without a doubt i bet its a naming issue, this is one of those things that go unmentioned and overlooked. either u do or dont have file extensions showing or not and or the .img does or does not need to be changed to .zip, i messed with this for days last year when flashing my g1. just go and change whatever you hide/show known file extensions is set to and see if ur problem is solved.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

AndyBurns said:
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
Click to expand...
Click to collapse
Thank you AndyBurns. I registered just to say that. You saved me a lot of time.
I had the same problem. Had the USB cable plugged into my front 1.1 ports instead of the back 2.0 ports. Switch ports and now I'm good to go.
Thank you.

Hi all -
Just wanted to post a follow up to this message, in the hope that it may help someone in the future!
Basically, I was not using the original USB cable that came with the nexus one (lost it), and instead was using a cable that I bought from a mobile phone retailer - it was basically one of those 6-in-1 multi USB cables where I had to put an adaptor on the end to switch it from mini to micro USB to fit the Nexus one.
Anyhow, for some reason, despite the fact that I could charge the phone using this new cable, and access it through device manager, explore the contents of the phone, root it etc etc, it would not do the flash as described above. I went out and bought a dedicated 1 metre gold plated micro USB cable, and it worked great
Dodgy cables - should have thought of this before I spent days frigging around and maybe even almost bricking the phone with a bad flash

[Q] Streak will not boot to fastboot or recovery

Pretty sure the phone is toast, but wanted to confirm. I was erasing each of the partitions (boot, system, recovery, etc.) in order to write the latest Dell 2.2 packages, and after I erased each parition, my dog knocked my phone off the table, and the battery flew out.
Now it will not boot in any form (obviously because I blew everything away). I assume there is nothing I can do at this point, is that right?
Guess I will be sending it back to Dell.

Fixed it
I was able to follow steps found at whirlpool.net.au wiki dellstreak22 to correct the problem and get running again.

i'm in the same situation, no boot, fastboot or recovery. It remain with a black screen. I tried to use the guide but the Streak doesn't respond. Please give me an help

try that
whirlpool.net.au/wiki/dellstreak22

No luck
freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
I have same problem.
I tried the thread above but when I try to install the Qualcomm driver on my x64 system (I followed certificate advice) I get an error message, the Qualcomm with ! mark changes to a com port with a ! mark in the device manager on the pc so I am not able to use the QDL. Get an error message that this driver is not for my system.
Can somebody please advice.....
Kind regards,
Pascal

freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
the baseband upgraded correctly but my streak doen't go in fastboot mode it remain with the black screen. I think that is definitely bricked

[Q] Bricked Nexus 7 3G - Can't Get to Bootloader - Anyone Able to Help?

Hi all,
I think I just toasted my Nexus 7 3G while trying to upgrade the radio/bootloader, but before I toss it in the trash I wanted to see if many someone had any ideas I have yet to try.
Thanks in advanced to anyone who can help me!
The Problem:
Nexus 7 wont boot and is stuck on the Google logo with the unlocked bootloader icon. Cant boot to boot loader using Power + Volume Down. When I do Power + Both Volume Up and Down the screen goes black after showing the Google logo and my PC detects the device but cant find drivers and dont get anything out of fastboot commands. Power + Volume up does nothing.
Because the unlocked bootloader icon I doubt I could get away with sending it back.
What I did:
I was running CM10.1 with Bootloader unlocked
I installed the following 4.3 ROM - http://forum.xda-developers.com/showthread.php?t=2381991
Rebooted <-- Everything was fine but running on older Radio/Bootloader
I started following the following instructions to upgrade radio + bootloader - http://forum.xda-developers.com/showthread.php?t=2175086
I used TWRP to install the Recovery zip
Rebooted to bootloader
Fastboot Flashed bootloader
<<Forgot to Flash Recovery>>
Rebooted <-- everything was working
Rebooted to bootloader
Fastboot Flashed Radio
Rebooted << TWRP launched instead of stock recovery
Rebooted to bootloader
Fastboot Flashed bootloader
Fastboot Flashed recovery << Did not reflash recovery zip first >>
Rebooted <-- seemed ok
Rebooted to bootloader
Fastboot Flashed radio
Rebooted <<No Recovery Showed Up>>
Stuck with Google logo with unlocked bootloader icon and cant get back into bootloader

Hi Mazeri,
I having the same issue as I explained in the original thread.
I was flash the bootloader recovery and radio. Recovery and Bootloader flashes seemed to be ok but the radio flash run ok but when the n7 rebooted got stuck in the google logo.
I have tried all kind of key combinations with no success.
Here is the transcript of my flash commands:
Code:
~/Downloads ⮀ fastboot flash bootloader bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 4.140s]
finished. total time: 4.399s
~/Downloads ⮀ fastboot flash recovery Recovery_Stock_Tilapia_4.3.img
sending 'recovery' (10240 KB)...
OKAY [ 1.223s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 3.676s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
015d2XXXXXX0d fastboot
~/Downloads ⮀ fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
sending 'radio' (16384 KB)...
OKAY [ 1.943s]
writing 'radio'...
OKAY [ 4.760s]
finished. total time: 6.702s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
~/Downloads ⮀ fastboot devices
How do you detect the device in your pc? What command are you running?
Im on a mac os x. If I do a fastboot reboot recovery, I get a 'waiting for device' message but there is no information for any combination of key presses.
If you are on a PC, have you tried any toolkit? I've read in a couple of thread that Wug's toolkit have worked to unbrick some devices with issues with the bootloader.

All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.

Mazeri said:
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Click to expand...
Click to collapse
Also, I tried with the Nexus 7 tool kit and it failed to detect ADB. Fastboot also does not see the device.

Wug Toolkit also does not seem to work as it requires ADB or Fastboot to be working.
If I could get the device driver to kick in that might work... but something we did while flashs is making the device show up without details such as no device name and no mfg info... so Windows just shuts it down and calls it unknown.

I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....

amakaru said:
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
Click to expand...
Click to collapse
Maybe we should check what do ourt n7's have in common... It's strange that the flash worked for other n7 but not for ours.
Maybe that radio file is intended for certain devices (?).
Mine is a EU Nexus7 3G bought in early January this year. I guest is in warranty yet but because of the unlock icon in the start screen, the warranty is void
But I think this is not a problem related with the bootloader since the google logo appears and the unlock icon (so the n7 bootloader detects that it is unlock).
The flashing worked with the bootloader but it crashed when the radio was flashed for the three of us, so it is something related with the baseband. The OS installed should not be related since the bootloader and radio baseband are independent from the OS (Maybe you can get a soft brick, stuck in the colored X logo but bootloader should work).
I'm going to try to work finding a solution... but personally Im not feeling very optimistic

Now when I use three button (hold down power & vol + & vol - ) my computer show in device manager : "Android devices/ASUS Transformer APX Interfaces"

Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.

I have a US Nexus 7 3G, got it right when they went on sale.
ameinild said:
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
Click to expand...
Click to collapse
Bummer news :'( but I was expecting as much. If we don't find a fix, can we replace the main board to fix or is this problem beyond that point? Don't think selling a bricked device is worth it unless we have 0 options.

adb/fastboot commands
Another one bites the dust.
I should have followed the thread more closely. One of the steps (noticed this after the fact) is to "fastboot reboot", unfortunately this does not reboot the bootloader.
I should've noticed this yesterday after the initial fastboot reboot when I flashed the recovery image. Anywho, I believe the last step after flashing the radio should be "fastboot reboot-bootloader" not "fastboot reboot"? Maybe someone with more adb/fastboot experience could verify? Thanks.

bootloop after radio update!!!
my nexus 3g is from poland!!!
please, help!!!

Still no update guys, and no luck also
Right now I am thinking we will need to replace the main board, but I want to get that confirmed before buying a replacement.

I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine

my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.

sambistt said:
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
Click to expand...
Click to collapse
There isn't a place to know the parameters or whatever we need?
What can we change physically (motherboard, or any specific chip) to solve this problem?
If we return it to Asus or Google can it be repeaired? How much does it cost? Assuming the warranty is void because of the unlock icon..
---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ----------
eternal70 said:
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
Click to expand...
Click to collapse
That was not the reason. I didnt upgrade to 4.3 before flashing the bootloader and the radio and I got the same result. The bootloader is not connected to the OS, but the OS is connected to the bootloader. I mean that it doesnt matter the OS in order the bootloader to run. But maybe it is possible to have the n7 soft bricked if the bootloader installed is not compatible with your OS.
Softbricked is when you are stuck in the OS logo (in case of the stock version is the colored X). This is very easy to fix, just runt in fastboot mode and flash the new OS and that's all. Everyone has experienced this situation eventually.
Our n7 are hard bricked. This mean that the bootloader or the radio (or both) are corrupted or bad flashed. In our case is the radio band (since we can see the google logo that is the bootloader). The weird thing is that while the bootloader is running (we can see the google logo and the unlock icon), we can't enter in the fastboot mode. Since we cant put the n7 in fastboot mode then we cannot flash anything (not os, not radio, not bootloader).
For now, the only way to flash bootloader and radio chip of the n7 is via APX. the problem is the APX configuration to flash the nvidia chips has not been released (as far as I understand, correct me if im wrong), so there is no way to know how to do it.
The only hope is changing this chips physically. Because everything is integrated, that means to change the motherboard, my guess (you can find tutorials in iFixit). What's the downside? The motherboard is basically the N7 so if you change it you change everything (the storage, the 3G, etc). You can check for motherboards in ebay easily just with search: Nexus 7 Motherboards. Range price varies from 20$ for 8GB to 140$ for 3G . Another question is if we can put a 8GB or 16 GB motherboards in our 3G N7, but I think so... it would not be a problem.
Everything I said a personal opinions and I can be wrong, so correct me if I'm wrong.
I have to say, I still have a very very very little hope that could be a fix for this, since we can see the google logo. But I'm thinking in ordering a 8G motherboard just in case

i`m thinking to give my n7 3g to my brother for parts and never buy tablet anymore, only ultrabooks.

My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app

There isn't a place to know the parameters or whatever we need?
Click to expand...
Click to collapse
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
DomieMic65 said:
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
really? your brother flashed radio module?

sambistt said:
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
really? your brother flashed radio module?
Click to expand...
Click to collapse
I don't know. Sorry.
I just mentioned this in case it may give you a clue.
I will ask and report.
Sent from my Galaxy Nexus using xda app-developers app

device not unlocked cannot install image oneplus 2

Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help

http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257

I have tried all those methods and none of them worked for me

pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.

I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem

Can anyone please help me with this?? :'(

pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008

eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down

pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.

eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj

pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??

eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?

pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password

eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953

pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me

Problem Solved

Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...

CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.

CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.

551ML stuck on fastboot after stupid action, 'fastboot wipe cache' doesn't work.....

Noob so sorry for the stupid mistake.
Have a 551ML, on bliss w/ TWRP and was supposedly rooted already(can't remember which method I used, but the start screen was white background/black words). Have been using the phone for a year without issue.
One day some kind of stupid just came over me, and I followed this thread:
http://forum.xda-developers.com/zenfone2/general/unlock-zenfone2-android-6-0-beta-unlock-t3411264
without even sure what was I suppose to be doing...(not blaming OP, I am the dumba** here)
everything went through just like suggested, but now the phone start screen shows un-rooted(black background, white words), and the phone is stuck on fastboot... Can't get into recovery or normal boot.
Can anyone advise what am I suppose to do now? I am thinking I need to unbrick the device using this guide:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But I am stuck at:
1.2 Connect with computer IntelSoc Zenfone 2:
Can't seems to get the computer to register my 551ML as a 'MOOREFIELD device'?
Can anybody gives me some pointers or maybe there are some easier way for my situation?
p.s. here are the fastboot info, in case it might help:
HW_VERSION - UNKNOWN
IFWI VERSION - 0094.0183
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
continue the fastboot process
Thx in advance!

nexusroad said:
Noob so sorry for the stupid mistake.
Have a 551ML, on bliss w/ TWRP and was supposedly rooted already(can't remember which method I used, but the start screen was white background/black words). Have been using the phone for a year without issue.
One day some kind of stupid just came over me, and I followed this thread:
http://forum.xda-developers.com/zenfone2/general/unlock-zenfone2-android-6-0-beta-unlock-t3411264
without even sure what was I suppose to be doing...(not blaming OP, I am the dumba** here)
everything went through just like suggested, but now the phone start screen shows un-rooted(black background, white words), and the phone is stuck on fastboot... Can't get into recovery or normal boot.
Can anyone advise what am I suppose to do now? I am thinking I need to unbrick the device using this guide:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
But I am stuck at:
1.2 Connect with computer IntelSoc Zenfone 2:
Can't seems to get the computer to register my 551ML as a 'MOOREFIELD device'?
Can anybody gives me some pointers or maybe there are some easier way for my situation?
p.s. here are the fastboot info, in case it might help:
HW_VERSION - UNKNOWN
IFWI VERSION - 0094.0183
SERIAL NUMBER - 0123456789ABCDEF
SIGNING - ?
SECURE_BOOT - ?
continue the fastboot process
Thx in advance!
Click to expand...
Click to collapse
flash boot image
then flash recovery image
then any rom you want

Thank you for replying so quickly!!
Can you be more specific on how to 'flash boot image'? I have tried to put the asus OTA image on the SD card, but it didn't triggered....

small update:
I have extracted boot image(boot.img) from ASUS Z00A firmware, and download the correct twrp recovery(twrp.img), and tried the following commands:
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot erase cache
and the result is still the same. Only able to reboot to bootloader no matter what, with the 'continue the fastboot process'.

Can anybody share some thought? really miss using my Z00A......:crying:

nexusroad said:
Can anybody share some thought? really miss using my Z00A......:crying:
Click to expand...
Click to collapse
Here is your rescue: http://forum.xda-developers.com/zenfone2/general/wwze551ml2-20-40-19420160713-raw-t3437416

Thank you so much!! The ASUS Flash tool works, and I have my Z00DA back to life!
For people with similar issue and want to use the tool, please noted that it takes a while(~15 min for the flash) + the tools does not shows any progress %, and afterward it will takes another 10 mins for the phone to start, so be very patient.....