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.
Related
Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?
jeezy85 said:
Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?
Click to expand...
Click to collapse
How this post belongs in dev area???
Go to android hd rom and ask your question or post it in Q&A!!!!
Come on
how do i delete this thread?
jeezy85 said:
how do i delete this thread?
Click to expand...
Click to collapse
Mods going to move it or if you ask they are going to delete it.Please read forum rules before posting
Flash stock images in fast boot. You can't mount USB storage on this phone anyways.
Sent from my Galaxy Nexus using xda premium
happen to me too....
I flashed an Pauls update instead of core and messed my phone up.
flash stock image then use ADB and push the rom to the sd/update.zip - then flash.
That should fix it.
You're phone is not bricked. Reflash the factory images using fastboot. http://groups.google.com/group/andr...hread/2dde45a058a737b9/43c3a418144fc6c5?pli=1
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
Hold the Volume Up Key + Volume Down Key and then press the Power button.
jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
fastboot is fastboot recovery is recovery
Yeah, what Stea1thmode said
fastboot is a bit more lower level [i think] than recovery
pulling my hair out lol
im completly lost
ive downloaded the stock image... just dont know how to flash it
First of all naughty naughty please do not post questions in the development forum. I moved it over to Q&A
Ok now thats over with follow *THIS* guide to get fastboot drivers set up on your pc. Some users spend hours trying to figure it out (myself included the first time) and that guide is detailed. Install the pdanet program on your comp to get the needed drivers then boot your phone into fastboot mode and connect to your pc via usb cable. If it doesnt install the automatically then you can do it manually via the Device Manager.
Once the drivers are installed open up a command prompt and goto the folder you put the fastboot.exe file in. Type fastboot devices and it should return a number which means your phone is recognised.
Next goto *THIS* thread and follow the instructions to fastboot the Stock images back to your device and restore your phone.
Once everything is back and working READ every instruction thoroughly before doing anything in future Luckily this phone is next to impossible to brick
Mark.
thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S
jeezy85 said:
thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S
Click to expand...
Click to collapse
I have windows 7 too so it will work its just a pain to get them on.
Did you install the pdanet drivers to your pc? Did you update the drivers in the Device Manager? Please list your exact procedure you followed and where you are getting stuck.
Mark.
ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?
jeezy85 said:
ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?
Click to expand...
Click to collapse
Why are you trying to boot up the phone if you know it doesnt boot?
You need to do everything through the fastboot screen. Hold Volume Up and Volume Down buttons while pressing the power button until the big green Android icon appears and it will say fastboot on the screen.
Have your Device Manager open (from settings on your pc) so that you can dee the item pop up in the list that you need to update the driver for.
PdaNet drivers are the best ones that work for fastboot.
Mark.
when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing
jeezy85 said:
when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing
Click to expand...
Click to collapse
Yes thats the item you need to update the driver for.
Make sure you have installed the samsung drivers (and maybe pdanet drivers if you want to be safe) on your pc first. Then double click on the Android 1.0 item and then select Driver, Update Driver. Click Browse My Computer and then Let me pick from a list.
It should give you a few options. If you see it then select Android Adb Device but if not try one odf the samsung adb interface drivers.
Mark.
mskip i LOVE YOU!!!
starting to get somewhere got the drivers installed...
ok i typed this command in cmd where the stock img is
fastboot-windows flash all flash-all.sh
i get this
sending 'all'<0 KB>....OKAY
writing 'all'.....FAILED <remote : Unkown Partition>
Any ideas?
try just flashing the image zip.
Code:
fastboot -w update image-yakju-itl41f.zip
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
paleost0ner said:
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
Click to expand...
Click to collapse
Sounds like your sdcard failed. You said you can get into recovery, so try getting ahold of another sdcard with Viper ROM zip file on it and flash it.
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
l7777 said:
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
Click to expand...
Click to collapse
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Sent from my HTC6535LVW using XDA-Developers mobile app
mikelikesbikes said:
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Click to expand...
Click to collapse
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
l7777 said:
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
Click to expand...
Click to collapse
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Sent from my HTC6535LVW using XDA-Developers mobile app
---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need? Looking at the instructions I see the SD card must be formatted to fat32. I have no idea if mine is, but I have extras. I can format one of them to fat32, keep that file on it, and in case I ever need it I can pop it in the phone and flash it?
Sent from my HTC6535LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my HTC6535LVW using XDA-Developers mobile app
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Click to expand...
Click to collapse
Yes. It must have a special name and be in the root of the sdcard. I don't remember exactly what the name is for the M9 but it is posted in the RUU threads.
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.