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.
Related
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
DeviceSettings said:
So I tried the S off and I failed a couple of times with the wire trick. My timing was more than likely off. I re-ran the program and tried again. After it rebooted to check my alcohol level like it had the time before it could not find the device. It just kept counting to 45 secs over and over and kept asking me to check device drivers and adb and fastboot. And it worked fine before. Before I even started I checked adb devices.
Now the phone boots to the juopunutbear screen and it when I try to run the program it says that the device is not detected. So I rebooted in hboot and tried to run some adb or fastboot commands and the phone is not detected at all. I tried my mac too and no luck. I tried a different usb cable and no luck either.
So no I cant push anything to my phone and its just reboots to the juopunutbear screen. I think I bricked it. I dont know what to do. I cant push files to the phone. Any help?
Click to expand...
Click to collapse
I'm not sure what's happening with your computer not seeing the phone, but if you have a microsd adaptor you could get a stock RUU onto your card and flash back to stock.
Edit: or just your boot.img. If you can get into hboot you're not bricked.
Part fix
As previous poster said, put a PH...IMG with boot on it and you'll be able to boot up again. Yours is third phone reported here with USB problem after failed S-0ff.
I can boot my rom, but no radio or wifi, No charging, and no computer can see it for fastboot. Hoping for cure soon.
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Same thing happened to me. I just finished uninstalling HTC Sync and Android SDk, then reinstalled both. Now the drivers are working properly, and computer sees my phone again. This should help.
***edit: this process helped with my computer finding software drivers to connect phone to computer. Before- "Windows could not find drivers for Android device" (device manager in windows)
I could never get it to work in the first place. Cleanflash finds and flashes to it just fine but the s off just can't see my phone once it reboots.
Sent from my ADR6425LVW using XDA
DeviceSettings said:
Thanks guys. I am downloading an RUU now. Hopefully it works. I hope the usb connection is not fubar'd ...but i took the risk so its on me.
Click to expand...
Click to collapse
If the phone is rebooting to the screen with the arrow when you press power to enter fastboot then try going to recovery, your regular recovery will probably not show up but another stock hboot menu will. Then try selecting fastboot there and see if you can run fastboot commands without rebooting to arrow screen.
Sent from my HTC Vigor
Success getting it to reboot with the boot.img from the rom I was running....But unfortunately the usb is fried. Can not charge the phone or connect to a computer. So I guess that is another potential risk with using this method.
Ouuuuch :/
Sent from my ADR6425LVW using xda premium
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
DeviceSettings said:
Yeah sucks. I'm trying everthing I can, but its looking more and more bleak
Click to expand...
Click to collapse
Warranty!
(edit: kidding, no need for a ****storm)
I bought my One with bootloader unlocked but the guy who sold me the phone unrooted the phone before shipping and i've tried to follow the rooting and the unlocking bootloader through fastboot methods but every time i open sdk manager it just says i have to update, i update then it says restart, and no mater what i do, cmd just keeps telling me fastboot is not a recognized command... blah blah... short question is, is there a rooting app i can purchase or if anyone can give me a helping hand?
Edit: I have followed the steps exactly, switched off fastboot in power menu, and powered off entered fastboot from bootloader, plugged in device, entered cmd and tried it but i get the aforementioned error.
Edit 2: I made the folder and placed my files and it seemed to go a little smoothly but it says waiting on device and just hangs there. The computer is still not recognizing the phone, i still get USB not recognized. try reconnecting the device....
Oh also, trying to install a recovery to this, so i can root... but just an easy way
Please help me, someone... the bootloader says unlocked btw. but fastboot does nothing when trying to flash via cmd.
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
sakumaxp said:
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
Click to expand...
Click to collapse
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
HyDRo1X said:
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
Click to expand...
Click to collapse
ok i switched to a win8 an everything seemed fine, but i get a long list of processing cmd after i type the fastboot flash recovery... and then continued as followed but nothing... still get red triangle
Ok got it... Windows 8 problems
Sent from my HTC One using xda premium
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
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
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.