Hi everybody, i am really sorry about my english i hope you guys can understand what i am trying to say.
a few mounths ago i rooted my Htc one m8 using the AIO toolkit. I flashed it with the TWRP 2.7.0.2 recovery.
Last week i wanted to update my Htc and found a guide how to update but i messed up. It said something like that I have to remove the root then install a file they had on their site on my phone.( I can't say which guide it was because i don't have the pc i used last week to do this.)
After i did that my Htc got stuck in a bootloop- I can access the Fastboot menu but when i choose Recovery or Factory reset option my phone just reboots but doesnt get past the HTC logo.
I am trying fixing it with the AIO toolkit but an error message shows up saying "device not found" or
"waiting for device" my pc is on windows vista an recognizes my phone- I installed the right drivers and on the fastboot menu it says "fastboot usb" highlighted in red.
I am a really noob at this so have you guys any idea how I can fix this? Why do i get the message "device not found" , when my pc recognized my phone and all the drivers are installed?
And also my pc is in safe mod with network because i get a blue screen when booting the normal way-
Do you think thats why i get the error message " device not found"?
Hi guys I just got my xz premium..and trying to unlock bootloader on this bad boy..problem is when I enter fastboot on my PC, and I entered fastboot mode on the xz premium..and enter " fastboot devices" nothing shows up? I went to device manager on my windows 10 PC..and it shows Android with a expectation mark on it..I tried updating the driver with the official Sony one but driver isn't signed and won't let me..does anybody know how to fix this issue..thanks
You have to disable driver signing enforcement since you're on W10. (And assuming 64bit). You can do this by going to Recovery > Advanced startup > Selecting #7 (usually #7. As long it's the the one that says disable driver enforcement).
When your computer restarts, you should be able to install the driver properly.
@iArvee thank you I'ma try that..I even downloaded Android sdk but I found a video online on how to do it but will try it out
I've just got a new Z5 and am trying to install LineageOS, like I did on my dearly departed HTC m8.
I've got the android platform tools installed, and the device shows up if I use "adb devices". "adb reboot bootloader" appears to work - it shuts the device down then the LED goes blue (the documented behaviour of being in fastboot mode). However, "fastboot devices" lists nothing.
*#*#SERVICE#*#* indicates bootloader unlock is allowed, I've got dev mode enabled, I've got my unlock code ready and waiting... No fastboot mode though. Any ideas?
Hang on a sec.
It's just occurred to me that something else might be wrong. Booting into "fastboot" is the same as entering recovery mode, right? Well, when I try doing it, all I get on my phone is the blue LED. Just a black screen. That seems obviously wrong, because it should be displaying Sony's built-in recovery mode stuff, right?
While we're at it, I've just tried again on my work computer, holding volume up and inserting a USB cable. The computer recognised and installed "S1Boot Fastboot", and I can see it in Device Manager under "Other devices". However, the status is "The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device."
This was the same on my home machine. I tried installing Sony's drivers, and the Android drivers, but each time I pointed Windows at the directory I'd unzipped to it would just say that it couldn't find any drivers there.
e: #$%&!
I'm trying with Sony's "Emma" tool. It says to hold vol-down and connect the phone, which gives a green light (not a blue one), but says "this phone is locked". But I've unlocked it! Sony's instructions at the address listed in the error message say to enable debugging then select "OEM unlocking" from the dev options, which I have done! What gives?
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Thank you!
Hyperlynx said:
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Click to expand...
Click to collapse
Thank you! I had the same problem. The device showed up as "Android" and I couldn't install the drivers.
You can find instructions and the download link here: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver
Hi, I was trying to unload the bootloader with the program huawei multy tool, everything went ok until the restart and the smartphone was stuck to "you device has been unlocked and can not be trusted etc. you device is booting now. to fix? If I try some command from adb it goes out "waiting for devices"
ps. google translate XD
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.