Related
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Please list the steps you follow from beginning up till the point you get the "waiting for devices" message.
Are you booted into fastboot on the phone? Are you using the Android SDK fastboot implementation or moto-fastboot? Do you have fastboot in your PATH or have you cd'd into the directory where you've extracted the fastboot package?
Having a similar issue... not my first go around on this model. I have been unlocked and the whole 9 yards...
I went back to locked stock 4.5.91 (to make sure I still could) successfully. Today I went through the usual manual and auto unlock methods and RSD mode will not work. I have the most recent drivers from Motorola. I tried alternate usb cables... I have the Flash Interface driver installed (3.2.11).
I launch RSD protocol but nothing happens on my PC and RSD Lite does not show device info....
Could Motorola have done this recently? Or is there an older RSD driver someone can point me to to try? My current one is 5-2011.
EDIT: Fastboot no go as well.... not trying to hijack just may be the same problem... I am going to factory again and give it a second go... ADB Devices does not see the phone either
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Dell2 said:
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
ethantarheels123 said:
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Click to expand...
Click to collapse
Tried that as well earlier... not sure where I am going at this point
defnow said:
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
Click to expand...
Click to collapse
Pretty sure I installed 64 but maybe I better double check...
I just started over completely, figured it out . Thanks for help guys, I can try out Alien3 now.
I confess my main problem was boneheadiness, I kept putting phone in fastboot mode(kinda sorta). When
fastboot came up I would connect phone to my computer, I never hit volume up to actually select fastboot.
I been kicking my computer for 2 days, I shudda kicked my dang self.
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
halfevildruid said:
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Click to expand...
Click to collapse
Have you tried the moto-fastboot package?
mysticdrew said:
Have you tried the moto-fastboot package?
Click to expand...
Click to collapse
been reading about this, everything I read wants the img files and I have all sbf. Thing is I can not unlock my bootloader...
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
I just trying this to solve on my computer (Asus G51), but nothing I can do, reinstalling drivers, RSD Lite, nothing helped to solve this problem...so I went to another one computer (Acer) and I did it without any problem, install RSD Lite then drivers, unlock my bootloader at first time...I don't know where's the problem is, but I want know it
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same result in fastboot, I'll try uninstalling HTC sync and disabling driver signature verification now and see how it goes
edit: same result, adb devices comes up empty when in fastboot after disabling driver signature verification and uninstalling HTC sync
It should be "fastboot devices" as the command.
Does your computer have native USB 3?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It should be "fastboot devices"
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
that returns nothing it just starts a new command line.
and two of the ports are usb 3.0 one is 2.0, I've tried all three
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the help, I hope this is all you need from the command window. I'm trying the adb and fastboot driver installation thread that you suggested now, hopefully this will have it resolved by the time you get back.
edit: unfortunately that didn't work, it said that the driver is already up to date. The phone shows up as "My HTC" under android USB devices already, even when in the bootloader/fastboot, but it shows the device status as "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I just have some extra things in the folder like some ROMs/recoveries but I don't think that would matter. I have adb.exe, fastboot.exe, and the two .dll's so I think I have everything I need.
And I tried fastboot reboot while in fastboot, I got waiting for device in command prompt. Also when I entered the command I got a "USB device not recognized" popup from the taskbar. Device manager shows the phone as My HTC with a yellow caution triangle on the icon and the device status "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Finally got it working, kept trying on my old computer that I unlocked it originally with and eventually it just decided to recognize it and worked.
Thanks so much for the help getting to this point.
kalbany said:
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Click to expand...
Click to collapse
I
Is there an error information, e.g: Windows code 10.
If yes, I googled it, it shows:
The error message probably occurs when you are trying to use a particular piece of hardware, such as a USB connected device or internal DVD drive. Take note of the device you are using when the error occurs in order to update the correct drivers.
error.info/windows/driver-10.html
Cheers,
Lun:
kalbany said:
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
I have Started a thread for HTC Droid Incredible phones in the troubleshooting area. Im having the same exact problem and im running Windows
as soon as i do the command: fastboot oem get_identifier_token, it just sits there and waits. and then i get a pop up from the system tray saying that my device has malfunctioned.
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Regardless of how old this thread is I'm running into the same problems now!
My Xperia XZ1 Compact doesn't seem to be recognized when in the bootloader (indicated by a black screen and blue led).
I tried "adb reboot hboot" and it booted into a new black screen, but didn't last long before rebooting.
I tried other button combinations during the sequence and those didn't change anything.
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
mikeny said:
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
Click to expand...
Click to collapse
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
darkandshadow said:
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
Click to expand...
Click to collapse
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
mikeny said:
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
Click to expand...
Click to collapse
You may have to try it manually. Download a fresh copy of the Android SDK tools
and put the "Platform-Tools" folder under your C:\
Fire up Command Prompt, change directory to that platform-tools folder.
Then type in "fastboot oem lock" (without the quotations).
Your phone will reboot and upon the bootloader, it should say **RELOCKED** at the top.
If you're still having issues, I would suggest loading up on another computer, or if that isn't possible, download Ubuntu and burn it as a LiveCD and see if your phone will be recognized (properly) through Linux. Sounds like the communication protocols for your phone are fuxed. As for uninstalling and reinstalling drivers like that, you may have to use regedit to completely remove trace portions of those previous installs.
It's a driver issue, uninstall and reinstall the drivers.
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.
The device works properly. I was able to unlock the bootloader using flashtool. The problem is, I can't get it into fastboot mode. I hold volume up, plug in the usb cable, it does a quick flash from amber to green, then nothing. From what I'm reading, it's supposed to stay lit blue. So something isn't right here, but it doesn't seem like the steps can be screwed up.
As a point of reference, I tried re-flashing the factory FTF, and even installing a different one. The results are the same. Device boots fine, but I can't access recovery or bootloader(most importantly).
Any help would be greatly appreciated!
InGeNeTiCs said:
The device works properly. I was able to unlock the bootloader using flashtool. The problem is, I can't get it into fastboot mode. I hold volume up, plug in the usb cable, it does a quick flash from amber to green, then nothing. From what I'm reading, it's supposed to stay lit blue. So something isn't right here, but it doesn't seem like the steps can be screwed up.
As a point of reference, I tried re-flashing the factory FTF, and even installing a different one. The results are the same. Device boots fine, but I can't access recovery or bootloader(most importantly).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
have you try flashtool command to command your phone go to fastboot mode automatically if you on flash mode?
Nicklas Van Dam said:
have you try flashtool command to command your phone go to fastboot mode automatically if you on flash mode?
Click to expand...
Click to collapse
Yes, of course. Using the flashtool does not work, neither does using adb reboot-bootloader.
InGeNeTiCs said:
Yes, of course. Using the flashtool does not work, neither does using adb reboot-bootloader.
Click to expand...
Click to collapse
i think this hardware issue, but have try it another way like from your reboot option from system?
Nicklas Van Dam said:
i think this hardware issue, but have try it another way like from your reboot option from system?
Click to expand...
Click to collapse
I just don't understand how my bootloader can be broken, but everything else still works?
I need to know how to fix this in order to move forward.
InGeNeTiCs said:
I just don't understand how my bootloader can be broken, but everything else still works?
I need to know how to fix this in order to move forward.
Click to expand...
Click to collapse
i don't know too, may be you need help from reconigzed developer or any senior member. i think like that
Thread closed until the OP checks his PMs and tells me which device he has
Install drivers from c:\flashtool\drivers
and choose fastboot, flashmode and z drivers
When you unlocked using flashtool did you get the code from sony?
Also, dial *#*#7378423#*#* goto service info and configuration, what does the last line say exactly
gregbradley said:
Thread closed until the OP checks his PMs and tells me which device he has
Install drivers from c:\flashtool\drivers
and choose fastboot, flashmode and z drivers
When you unlocked using flashtool did you get the code from sony?
Also, dial *#*#7378423#*#* goto service info and configuration, what does the last line say exactly
Click to expand...
Click to collapse
I'm on a mac, I got my unlock code from sony, and the last line says "Bootloader unlocked: Yes"
I can try it on a pc, but the problem isn't the method, it's the device. ADB correctly sends the reboot-bootloader command, it just doesn't get to the bootloader. I get a black screen. Same for when I try and access recovery. It's just really odd that the device still works this way.
Would trying this on a pc with the drivers listed be any different? I'm at work now and I can use my PC instead of my macbook if it'll yield different results.
InGeNeTiCs said:
I'm on a mac, I got my unlock code from sony, and the last line says "Bootloader unlocked: Yes"
I can try it on a pc, but the problem isn't the method, it's the device. ADB correctly sends the reboot-bootloader command, it just doesn't get to the bootloader. I get a black screen. Same for when I try and access recovery. It's just really odd that the device still works this way.
Would trying this on a pc with the drivers listed be any different? I'm at work now and I can use my PC instead of my macbook if it'll yield different results.
Click to expand...
Click to collapse
What were you expecting? There is no bootloader screen on the phone. You get a black screen when in fastboot mode, all commands are done from a command window on the computer.
Have you installed a recovery? If not then you cannot enter it. There is no factory or stock recovery accessible on xperia phones.
I would suggest using a Linux or windows machine, I have heard of nothing but problems using macs.
Is there any way I can reflash the factory bootloader with an ftf? I've done two so far and it hasn't seemed to help anything.
To my understanding, when the device is off, you hold volume up and then plug the usb cable in. This should make the led stay solid blue, but mine just blinks amber then green real quick, and nothing happens.
Can someone confirm that I'm not crazy here? It's not like this is my first time modifying an android device. I've been using android since the G1, I work as an IT manager, I use windows, mac, and ubuntu linux regularly, I've compiled my own roms from aosp...So this is really making me nuts!
gregbradley said:
What were you expecting? There is no bootloader screen on the phone. You get a black screen when in fastboot mode, all commands are done from a command window on the computer.
Have you installed a recovery? If not then you cannot enter it. There is no factory or stock recovery accessible on xperia phones.
I would suggest using a Linux or windows machine, I have heard of nothing but problems using macs.
Click to expand...
Click to collapse
The entire process worked fine up until trying to get into fastboot mode. Everyone is saying I should see a blue led, but that's not happening, and it doesn't respond to fastboot commands on my mac, and the pc installer doesn't install the drivers. I've tried searching for the driver files, but I'm not having any luck. I don't want an installer, I just want to manually select the windows driver files and force it to install.
Windows 8.1, latest version of flashtool, my device just shows up in device manager as c6833. When I tell it to search for drivers, it doesn't find anything even after having run the driver installer. Is there a website or a thread on xda that has just the driver files for the z ultra rather than a full installer?
Progress: I've pulled the driver files out of the installer. I'm going to try and get the device recognized on my pc in a bit.
InGeNeTiCs said:
Is there any way I can reflash the factory bootloader with an ftf? I've done two so far and it hasn't seemed to help anything.
Click to expand...
Click to collapse
Not sure what you mean, you have not altered the bootloader, just unlocked it. Also, flashing FTF's do not touch the bootloader
To my understanding, when the device is off, you hold volume up and then plug the usb cable in. This should make the led stay solid blue, but mine just blinks amber then green real quick, and nothing happens.
Click to expand...
Click to collapse
Yes, phone off, keep volume up pressed and attach USB cable (Volume down would be for flashmode) I think you have issues with the drivers on a mac
Can someone confirm that I'm not crazy here? It's not like this is my first time modifying an android device. I've been using android since the G1, I work as an IT manager, I use windows, mac, and ubuntu linux regularly, I've compiled my own roms from aosp...So this is really making me nuts!
Click to expand...
Click to collapse
You are not crazy, You can also try
Code:
adb devices
to see if the machine sees the phone when it is turned on, then try
Code:
fastboot devices
to see if it is actually in fastboot mode or not
InGeNeTiCs said:
The entire process worked fine up until trying to get into fastboot mode. Everyone is saying I should see a blue led, but that's not happening, and it doesn't respond to fastboot commands on my mac, and the pc installer doesn't install the drivers. I've tried searching for the driver files, but I'm not having any luck. I don't want an installer, I just want to manually select the windows driver files and force it to install.
Windows 8.1, latest version of flashtool, my device just shows up in device manager as c6833. When I tell it to search for drivers, it doesn't find anything even after having run the driver installer. Is there a website or a thread on xda that has just the driver files for the z ultra rather than a full installer?
Click to expand...
Click to collapse
The installer with flashtool is quite good, you can choose which files to use,
Just pick the fastboot, flashmode and Z drivers
gregbradley said:
Not sure what you mean, you have not altered the bootloader, just unlocked it. Also, flashing FTF's do not touch the bootloader Yes, phone off, keep volume up pressed and attach USB cable (Volume down would be for flashmode) I think you have issues with the drivers on a macYou are not crazy, You can also try
Code:
adb devices
to see if the machine sees the phone when it is turned on, then try
Code:
fastboot devices
to see if it is actually in fastboot mode or not
The installer with flashtool is quite good, you can choose which files to use,
Just pick the fastboot, flashmode and Z drivers
Click to expand...
Click to collapse
also note that on windows 8.x you have to be in the special boot mode to install unsigned drivers
Just curious did u manage to make ur phone work cuz I got similar problem with recovery(TWRP) it sometimes only show it rest of time it's black screen and in that black screen I can tap on reboot to system or poweroff. It's annoying sometimes cuz I need to flash some important stuff.