Hi all, been a while. I'm stuck at a point where there is so much info and so many changes. Here is where I'm at.
1. UNLOCKED bootloader
2. HBOOT 2.09.000
3. RADIO 1.13.11.0803
4. NOT Rooted
5. TWRP version 2.3.1.0 (touch version that doesn't work with my firmware)
Windows 10 OS
Android SDK installed and ADB working fine.
Fastboot not working
HTC Sync installed and uninstalled along with drivers
What I'd like to have is root, and a custom recovery. RUU does not work because when the phone is rebooted into bootloader the device is no longer recognized. Been around the block a few times but it's been a long while. I'm back and would love to customize this phone but have come to nothing but dead ends. Any guidance is very appreciated, thank you.
The MAIN issue I have is fastboot NOT working. ADB works. Been at this all last night and all morning No Joy. Can anybody help with getting the PC to recognize the phone in fastboot mode? I assume it's a driver issue, I've tried loading the SDK USB drivers and they won't load. So I'm using HTC drivers. No luck.
Well I've got it fairly sorted out. Using Cyanogenmod 12 something and up and running. Had to use a Win7 machine.
Related
Ok guys, I tried searching but couldn't find an answer.
I'm running Windows 7 x64. I previously have a non-rooted, 1.5 Droid Eris. I also had HTC Sync installed and working properly, and was able to sync my contacts and calender back and fourth.
I followed the guide HERE, with two exceptions;
1.) I already had a working USB driver for my phone, so even when I downloaded the Android SDK and the USB v3 drivers, there was no need to install them to gain root and upgrade to 2.1 - as proven by my currently upgraded Eris.
2.) In order to install the Recovery, I had to do the following from Command (while the phone was connected via USB w/ USB Debugging enabled:
With phone powered on
Code:
adb shell reboot bootloader
Once the phone gets into hboot and says "recovery usb" type
Code:
fastboot flash recovery recovery.img
with recovery.img in the current folder you are in, and fastboot in your path.
Click to expand...
Click to collapse
That said, I've got my Eris rooted and upgraded to 2.1 (I know, I already said this.. just refreshing you..), but I can't connect to HTC Sync anymore.
In device manager, my phone is recognized as "My HTC" under "Android Devices", as it always has. It's the same with or without USB Debugging enabled.
Am I missing something, or is this simply not possible at this time?
EDIT: I figured it out. Since nobody replied, I'll assume you guys don't need the fix.. if anyone does, feel free to PM me
ok. I'm tired so go easy on me. I'm running Windows 7 32bit. I have Dell PC Suite installed. I've got the full SDK installed. I've also got the R288920 drivers installed. I've been trying (since 3.00am) to get Fastboot to work and it would seem no matter what i do i just cannot. My Streak (Steve's 1.90) shows up in Device Manager as "Android ADB Interface". I've tried all 6 usb ports on my pc. I've tried Adb Composite. Adb Bootloader. Adb Interface and nothing works. I should also mention i had to do a clean install of Windows yesterday and prior to that Fastboot worked fine. I'm a semi-noob and i'm convinced that this is a driver problem. My question is this, can someone please tell me where i've gone wrong? As the man with the steering wheel down his pants said to the Doctor "this is driving me nuts".
Problem solved. Fastboot file was corrupted.
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Frosstyx said:
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Click to expand...
Click to collapse
the problem might be from usb cable.
try another one if you have.
Got it, I believe it was a driver issue, but I went through several things so not sure what finally worked...
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
dilyn said:
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
Click to expand...
Click to collapse
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
bigdaddy619 said:
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
Click to expand...
Click to collapse
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
bigdaddy619 said:
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
Click to expand...
Click to collapse
That's really strange. I had the drivers working prior to this episode. I thought that the device suddenly being unrecognizable had something more to do with it.
Oh well. Today I learned.
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
dg32 said:
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Windows 8.1 recognized my device in normal operation, but in any modified hboot failed miserably. (such that are used in conversions/etc)
I've long since reverted back to Win7 for anything involving Android....just so much less risky at this point.
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814