Related
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.
laal75 said:
Problem
When I plug my phone into usb 2.0 ,usb 3.0 doesn't have any popup and I can't see it in inside device manger, windows shows "The last USB device you connected to this computer malfunctioned and Windows does not recognise it. " error message and I can't see my phone through fastboot.
Side Problems
I updated to cm14 which made my recovery, (twrp) just black screen and when i went back to cm13 it made my normal boot black screen too.
Note
Have tried multiple Cables. standard OP 3 cable and off brand white one.
Have tried many usb ports.
Have tried three computers. two Win 10, one ubuntu 16.04
Have got the Media Feature Pack for windows 10
Have got latest ADB (on all computers)
Have got latest Fastboot (on all computers)
Have got latest OnePlus 3 drivers
Thank you for reading, any suggestions or links to other threads would be very much appreciated.
Click to expand...
Click to collapse
Normally when your phone is not recognised, it indicates a driver problem. On Win10, it happens invariably. So search and find ways of properly installing OP3 drivers on Win10. There are umpteen threads in OP3 sub forum.
On black screen, are you using TWRP 3.0.2-23? If not search for it and install it. If nothing works, go to the Mega Unbrick Guide.
Hm thats odd, but its recognized in MTP mode?
I would suggest to only use ubuntu for that cause you don't have that struggle with drivers.. I will flash TWRP on my OP3t now and report back if its working
Black screen on recovery is because of the firmware compatibility with the recovery. Use eng.stk's modded twrp.
If "fastboot devices" doesn't return you anything, try typing the device id after fastboot. Like if you want to flash a recovery, type fastboot -i 0x2a70 flash recovery ---.img
If that doesn't work out, I don't know of any other workaround. If you find a fix, do let us know.
*Mod, please delete this.*
Unwanted post.
How did you go about installing fastboot drivers for Ubuntu? If your device isn't recognised in fastboot I'm sure it's a driver issue.
Needed to reinstall drivers, by disabling device and installing drivers then plugging my phone in.
Phones fine now.
Thanks for the help.
I've been researching and trying to sort this out on my own for a while now. I've turned up nothing, so I figured I'd ask for some help. I'll try to provide as much information as possible here.
I was attempting to unlock and root my Razer Phone from my Windows PC. I plugged it in and had it recognized over ADB with no issue. I sent "adb reboot bootloader" to start things off. Once it was in download mode, I sent the "fastboot -i 0x1532 devices" command to make sure it was recognized. It wasn't. I checked devices manager, and sure enough, it was not picking up the Google driver that every other device I own works with. I attempted to update the driver manually by pointing it to the inf file. It gave me an error stating that the driver is not designed to work with 64-bit Windows. I found that odd, as this is the exact same driver that I've used with my other devices for this stuff. I plugged in my HTC 10, since that was nearby. It was recognized via fastboot like it always was. Same cable I was using with the Razer and everything.
I booted to Linux Mint on the same machine and tried the same stuff. It would pick up the Razer only in fastboot, but not ADB. In fastboot, I could detect it with "fastboot -i 0x1532 devices", and it showed up just fine. When I attempted to run "fastboot -i 0x1532 flashing unlock" it just gave me the fastboot command reference list. (I don't have a screenshot, but it looked like this, in case you're unsure what I am referring to.) I rebooted back to the system and double checked that I had checked "Enable OEM Unlock", and I had done that already. I double checked everything with my HTC 10, and again, it all works fine on the HTC 10. ADB and fastboot are both recognized correctly on Linux.
So armed with this information, I moved over to my Linux server. I used a different cable this time, and got a similar result. The Razer phone was recognized over ADB and I was able to get into fastboot. Once there, it was detected with the fastboot devices command. I attempted to run the unlock command, and again was presented with the fastboot reference list as before. Double checked with the HTC 10, and all was workign fine with that device.
Does anyone have any ideas, or is it possible that it's the Razer phone that's the problem? I may have access to a Mac laptop later on, and I could attempt this from there, but this is getting nuts. I don't think I've ever had this much trouble getting into a device before.
Yeah I had this as well, basically you may have the latest drivers but are missing the latest adb/Fastboot executables. Apparently they have changed a few commands in the newer one and that way of unlocking isn't in the old version. Just google for the adb/Fastboot package from the Google site, can remember the exact name but it was the first hit on Google. I just extracted the whole zip to a directory and used it right from there. The reason you are getting the help screen from Fastboot is cause for that version at least, your giving it an illegal command.
I got the same problem till I put my usb in a usb 2.0 in the back of the pc in a highlight usb port witch I read after on Asus Website that suppose to charge your phone if you turn off your pc so basically a always on usb. Also I managed to unlock and brick my device only with one cable I tried 4 cables none of them worked .so for you to keep In mind
Try different cables
Try usb 2.0
Try driver from twrp for razer phone thread that worked for me
Seems to be an ongoing issue for me on my main desktop. I grabbed my old development laptop out of the closet, booted it up, and I was able to get everything recognized and working. I tried doing some more work this morning on my desktop and noticed that I'm having driver issues elsewhere, so it seems to be an issue with this machine. I'm still not sure why the Linux installation on the same machine was exhibiting the same issue, though.
Hi Guys so I received my mi mix 2, more than 72 hours ago, bound my account to the phone in dev options, logged in online to miui, cloud etc and on the phone , enabled usb debuging
Used MiFlash latest version 2.x - Then i saw theres a new 3.3.4 Version - Signed in Clicked unlock went all the way to 100% then said wait 72 Hours...... Ok now ive waited
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1) "
Im used to flashing and unlocked and this is first time a xiaomi device has done this, Ive checked and adb devices are working.... BUT when i boot to fastboot and fastboot devices its blank , ive installed the ADB drivers and the xiaomi usb drivers over and over again... Windows is in test mode, Windows 10 64bit test mode.
Fast boot devices is always blank...... Any Ideas.........Oh and i was on global stable, now ive updated to the latest global Dev 8.0 rom from miui website - Still no luck
Ok so ive narrowed it down to the USB-C cable, is not keeping fastboot active
Ive just tried it with a redmi 5 device with old micro usb and fastboot devces gets picked up every attempt....
My mi mix 2 detects fastboot for a few seconds then seems to go off..... Very strange and also annoying - Any Hel would be most appreciated.. Ive posted on senerex thread sorry but thought have more chance of help if i started a new thread here:fingers-crossed:
The same is happening to me, anyone nows how to fix this?
Having the same problem here with this device.
Fastboot seems to be working for the first couple of seconds after device is being connected via USB. I'm even able to get output for "fastboot oem device info". But after 2-5 seconds any fastboot command stucks and outputs either nothing or "<waiting for device>" until device is being unconnected. When device is unconnected, fastboot outputs error "no such device" and exits with status code 1.
Tried Ubuntu Linux with the latest version of sdk-tools installed. Also tried Windows 8 in Virtualbox with Google drivers and Mi PC Suite. Tried to connect Huawei P20 to the same PC and using the same cable and it worked.
Did you find any solution? Could it be so that fastboot is somewhat broken on my device?
zerodi said:
Hi Guys so I received my mi mix 2, more than 72 hours ago, bound my account to the phone in dev options, logged in online to miui, cloud etc and on the phone , enabled usb debuging
Used MiFlash latest version 2.x - Then i saw theres a new 3.3.4 Version - Signed in Clicked unlock went all the way to 100% then said wait 72 Hours...... Ok now ive waited
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1) "
Im used to flashing and unlocked and this is first time a xiaomi device has done this, Ive checked and adb devices are working.... BUT when i boot to fastboot and fastboot devices its blank , ive installed the ADB drivers and the xiaomi usb drivers over and over again... Windows is in test mode, Windows 10 64bit test mode.
Fast boot devices is always blank...... Any Ideas.........Oh and i was on global stable, now ive updated to the latest global Dev 8.0 rom from miui website - Still no luck
Ok so ive narrowed it down to the USB-C cable, is not keeping fastboot active
Ive just tried it with a redmi 5 device with old micro usb and fastboot devces gets picked up every attempt....
My mi mix 2 detects fastboot for a few seconds then seems to go off..... Very strange and also annoying - Any Hel would be most appreciated.. Ive posted on senerex thread sorry but thought have more chance of help if i started a new thread here:fingers-crossed:
Click to expand...
Click to collapse
Is your bootloader unlocked ? Usb debugging enabled? Nothing is wrong with your usb cable. Check your bootloader. If it's still locked download Xioami Tool, not MiFlash. Don't ever use MiFlash, Google and download XioamiTool. It can do everything and bring your phone back to life if you brick it. Make sure to buy the developer a coffee if it works.
---------- Post added at 09:35 AM ---------- Previous post was at 09:32 AM ----------
Use this to fix the problem.
http://www.xiaomitool.com/
zerodi said:
Hi Guys ..........
Been trying and 20 times im getting " Couldn't Verify Device' Unknown Error (-1):
Click to expand...
Click to collapse
Probably a stupid comment but have tried connectng to USB 2.0? I have with other devices earlier had problems when connecting to USB 3.0.
Hi
I have a problem in unlocking my redmi note 5 pro.
I followed every steps which said guide but im stuck in step when i have to turn on xiaomi unlock tool.
After entering fastboot and connecting to laptop, windows recognize my phone as fastboot devices i can use every command possible to use. But if only i run any xiaomi tools fastboot become inactive it shows: "press any key to continue".
I tried almost everything, windows reinstall, drivers reinstall, didnt work. PLZ help me.
It`s because i5-8xxx or i7-8xxx.Try another computer which isn`t these.
Try another port of USB, don't use 3.0 USB port. It's fix mine.
I have intel celeron :x
I tried both on usb 2.0 and 3.0 didnt work.