Related
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
I have a Nexus 9 Wi-Fi model, my PC runs Windows 8.1, and I am not new to rooting and custom ROMs. I attempted to install the M dev preview to the tablet following the instructions on Google's site. In the process, my console window showed one of the instances of "sending sparse 'system'" had FAILED. Now the device will not boot. It is stuck on the white Google logo splash screen. ADB does not recognize it, although it does appear in Windows Device Manager as "MTP USB Device". When I attempt to turn the device off or reboot it using any combination of power and volume keys, the screen will go blank for a few seconds and then return to the Google logo. I cannot turn the device off.
I've never seen this before, even with a failed flash... it's supposedly just the system partition that failed, anyway. Any ideas how I can break free of this?
EDIT: I ended up locating this post. If I hold the power button down until the screen turns off and then immediately press and hold power+voldn, it will launch the bootloader.
I've no experience with flashing M. But I have a suspicion that you flash of the system.img failed because of an obsolete fastboot on your PC. I'd suggest starting by updating your Android SDK. Then you can try fastboot flashing the M system.img again. Or fastboot flash the stock 5.1.1/factory image to return to stock.
soft bricked is all it is.
Made sure I had the latest Fastboot, ADB
Rebooted into Fastboot
Ran the Flash All batch file and it failed to install the System
I found instructions on flashing manually this from what was post is very common.
You extract all files, flash the boot, reset, and flash all the others.
Do a Google search it was easy enough to find.
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually
Yesterday I tried to flash a a new rom on my Xperia Z2 (unlocked bootloader).
From TWRP I did an advanced wipe and selected basically everything except my mircoSD (because it has the new files).
After a long time of waiting I tried to flash the ZIP file and it gave me an error. I thought this had to do with the wipe so I decided to reboot my phone.
As you can imagine, it got stuck on the Sony logo (because system would be empty).
From this moment I couldn't do anything with my phone, except from the tool Emma.
I now have some clean installation of Sony their Android 6.0.1 for the Z2 (23.5.A.0.570) but Im unable to flash TWRP through fastboot.
The command adb devices shows my phone, fastboot devices gives an empty response.
When I restart to the bootloader from adb and try to flash TWRP I get the message "< waiting for device >".
I tried on three different PCs including a clean install of Windows with all kind of different drivers, yet I cant get fastboot to work.
Am I stuck with this unrooted version of Android now or do you guys have any suggestions for me?
Thanks in advance!
Install drivers correctly
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
As I said I've tried all kind of different drivers (Android tools, Sony drivers and flahstool drivers). So for me it's hard to tell what I'm doing wrong.
My computer notices the phone (if I hold volume up and attach the charger), it just doesn't show up under fastboot devices.
EugenStanis said:
Install drivers correctly
Click to expand...
Click to collapse
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
PaulusE said:
Okay, apparently it was because of the driver signature stuff in Windows 10.. The fastboot command now works fine!
Next problem occurred though, flashed the newest TWRP recovery but as soon as I enter "adb reboot recovery" my phone just normally boots again..
Why do things never work out the right way for me as they are intended..
Click to expand...
Click to collapse
Manually boot into recovery by booting up your device normally and when you see a violet LED, press vol+.
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
jnelsoninjax said:
I attempted to install the custom OS, Asteroid, to my Zenwatch 2 (Sparrow) I followed the directions and now the watch will not boot, it is stuck at the Asus screen in a loop. I downloaded the recovery image, but I can not flash it do to Windows not recognizing the watch is connected. ADB gives me the error Device '(null)' not found. I have checked the device manager and there is nothing showing as an error (yellow !). Is there anyway I can recover from this?
Click to expand...
Click to collapse
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
matze19999 said:
go into fastboot mode and reflash your system.
dont work with fastboot / adb / root when you have no idea what youre doing!
Click to expand...
Click to collapse
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
jnelsoninjax said:
The problem is that the watch is not being detected by Windows, therefore I am unable to reflash it, I clearly stated this in my original post.
Click to expand...
Click to collapse
You said windows can't detect the watch in adb mode? What about the fastboot mode?
matze19999 said:
You said windows can't detect the watch in adb mode? What about the fastboot mode?
Click to expand...
Click to collapse
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
jnelsoninjax said:
No, issuing the command: Fastboot devices shows nothing connected at all(the same goes for adb). It also does not show up in the windows device manager.
Click to expand...
Click to collapse
Did you enter the fastboot mode?
matze19999 said:
Did you enter the fastboot mode?
Click to expand...
Click to collapse
The watch is showing CSC Fastboot Mode! So I would assume that it is in Fastboot mode
Were you able to get this fixed?
No, I have but been able to resolve this issue. It is not being recognized by Windows, therefore I can't flash the original os back to it.
Did you have TWRP installed prior to the failed flash?
CVertigo1 said:
Did you have TWRP installed prior to the failed flash?
Click to expand...
Click to collapse
No
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
CVertigo1 said:
I may have a way to get it working. I've had issues where Windows would not recognize a device, until I installed a cocktail of random drivers that eventually worked. What version of Windows are you running?
Click to expand...
Click to collapse
I am running Windows 10 X64 build 1803
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
CVertigo1 said:
If you have the space, follow this: https://docs.microsoft.com/en-us/windows/wsl/install-win10
It allows you to run non-graphical Ubuntu on top of Windows. I've found sometimes my Windows 10 PC won't recognize things with adb or fastboot, but it works great in Ubuntu Bash. If you're familiar with Ubuntu at all, then it'll be a breeze to figure it out. If not, it's a pretty straight forward learning curve. It's also child's play to get adb and fastboot working right in Ubuntu, whereas it can be finicky in Windows.
Another alternative is to make a Linux Live CD using a USB drive, but that is a much more temporary solution.
---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------
If none of those sound appealing, then I'd suggest deleting all drivers having to do with adb or fastboot, and start fresh by installing everything with this https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
OK, I will mess around and see what happens! I will have to do it tomorrow, but I will play around and see what happens!
Let me know how it goes and I'll walk you through it some more.
Any luck?
Sorry for the long time to reply. I installed ubuntu in window and installed the appropriate packages, however both ADB and Fastboot show nothing connected, even though the device is in CSC Recovery mode. Is there anything else I can try?
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
CVertigo1 said:
I actually tried playing with a few things on one of my computers the other day to try tracking this down. I was running into an issue where adb worked normally when the watch booted, but it would not work in recovery, and fastboot did not work either. Here is how I fixed it. Open up device manager in Windows and delete any driver pertaining to Android phones or adb. In my example, an Asus driver was causing the problem. I deleted that and reinstalled the generic Google drivers using the 15 second adb/fastboot installer that I posted in this thread. After restarting the computer, adb works perfect in Android and recovery, and fastboot works perfect as well.
TL/DR Delete all Android adb drivers in Windows, then run the 15 second adb installer that I posted in this thread, restart, and get your watch back to normal.
Assuming your bootloader is unlocked, you can flash everything I have posted here to get it running. https://forum.xda-developers.com/zenwatch-2/development/sparrow7-1-1debloat-rom-t3800067 If the bootloader is not unlocked, fastboot oem unlock will do it.
Click to expand...
Click to collapse
OK, I got windows to see the watch via fastboot and I downloaded the image that you posted (bloat free) now the watch started to boot, but so far it is just showing spinning dots, and has been for ~5 minutes or so, is this normal?