Related
Hi all,
I have this particularily annoying problem that effects my ability to upgrade the rom files on my universal sometimes.
When I put my device into boot mode I don't see USB v1 or even Serial v1, what I get is Serial v2.01
Sometimes when I then connect the USB cable into the universal this changes to USB v2.01 and windows recognises the device and I can perform the rom upgrade. Most of the time however, it stays at Serial v2.01 and windows complains about 'USB Device Not Unrecognized'.
I have tried 2 different USB cables with the same outcome.
Normally after trying s few dozen times I eventually get windows to recognise the universal and perform the upgrade but I have been stuck like this for 3 days now and am getting close to my breaking point which will could shortly result in a broken universal.
Please help.
i cant quite remember the ins and outs but i have faced this problem as well
firstly ensure your connected directly to the computer and not via a hub,
try to do the upgrade if/when you get the message remove the device from the cable and do a soft reset
try the upgrade again and it should be successful this time .
i have had lots of trouble myself with this and i have found a soft reset always gets me there in the end.
goodluck !
I have just retried the upgrade and the display keep changing from USB to Serial about every 10 seconds.
I also noticed that the mouse kept freezing on the screen for a few seconds whilst this was happening. I tried using my other USB cable and the same thing was happening.
Does anyone else have v2.01 displayed on their screen like me?
Update: I stupidly ran Ivan's AKU3.2 upgrade utility whilst the universal was activesynced to my desktop (not in bootloader mode) and now this has executed the EnterBL.exe program which traps you in the booloader unless you upgrade a rom (or use mtty to issue the correct command to escape).
Unfortunately I can't excape via either of these methods as I still can't obtain a USB connection.
I have even tried a different PC but am still stuck.
Maybe both of my USB cables are knackered, so I will obtain another one and try that. If that fails it looks like Orange will be recieving a little parcel from me...
I have now also tried a 3rd USB cable with the same result.
I have a similar problem, I'm stuck in bootloader mode.
I have version 0.60 and if I put a USB in it keeps on saying serial and my computer says he doesn't recognise the device.
I've tried it on 2 different computers as on my new one apparantely all my usb ports are part of a hub. (they come up as all, inluding the ones in my moniter, being part of an usb root hub) But no succes on my other computer either.
I'm thinking that my only option is to do it via a memory card? Can anyone tell me how I'd go about that as I have no clue :shock:
Thanks!
Tim
Success!
I have been plugging in and unplugging my phone all day (with it still stuck in boot mode) and eventually it was recongised by my PC - I then upgraded the radio stack & ce rom and I am up and running again (I know that I could have used buzz's utility but I wanted to upgrade anyway).
The only thing that I did slightly differently this time was that I actually removed the battery from the univeral for a while and then plugged it back in before trying the USB connection. I did try this once of twice before without success though so can't really draw any conclusions apart from I don't know what is going on.
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Try this it shld work
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse
Guru Meditation said:
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Just noticed your user name, I was a big Amiga fan a few years back, still fire up Amiga forever occasionally on my PC when I feel the need.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Click to expand...
Click to collapse
Try it with a different USB cable or in a different USB port (don't go through a hub and if you've been using a laptop then try it on a desktop PC since some laptops have hubs built into them). If that doesn't work then you're out of luck as your Universal isn't detecting that you've connected to your PC and its time to send it in for repair.
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
i am stuck on the same problem and wondering the forum for almost 3 days now with no luck.... please help my device is in boot loader mood but not turning the serial to USB ......... please HELP.......
solution
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Please follow the steps:
1. Plug in ur usb cable in bootloader mode while it is showing 'serial' and version 'x.xx'.
2. Soft reset by pressing Backlight+power+reset pin WHILE KEEPING THE USB CABLE CONNECTED
3. your phone will now reboot into 'usb' mode. Don't remove the usb cable yet.
4. Remove the Memory card while keeping the usb cable still connected and VOILA,your pc starts recognising your phone as Microsoft usb sync.
5. Do whatever you want to do now (upgrade)
Hope it solves the problem now.
Press thanks if it does.
Something else to try
Having had a few issues with my G3 Uni, I've been through my fare share of Uni bootloader issues. When I find that I can't get the 'serial' to go to 'USB', I normally find it's because I haven't taken the memory card or the SIM card out (usually the memory card).
Make sure your memory card is out, then try to enter the bootloader and see if this cures it. If it does, then use mtty and the command 'set 14 0'
This tells it to reboot on reset. if you were to use 'set 14 1' it would go back to the bootloader on reset.
my Htc hd2 t-mobile won't recognize usb on boot-loader mode
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
kaleb2954 said:
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
Click to expand...
Click to collapse
you have the wrong forum friends! This Htc Universal section
to update Android on HTC HD2, you can use the Clock Work Mod Recovery !! for more details should refer to this thread http://forum.xda-developers.com/showthread.php?t=1021837
I-MATE JASJAR hung
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
bechir2013 said:
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
the first point...
A lot easier than to root this device
I'm trying to repair someone's Kindle Fire but there doesn't seem to be anything I can do.
1) Neither of our computers have the Kindle Fire driver installed.
2) When I use the factory USB cable, all I see is a yellow triangle flashing for like 5 seconds, then nothing, then the triangle again, and so on.
3) It won't turn on at all if you press the power button.
4) I can't install the driver no matter how hard I try, the device simply doesn't exist according to my laptop.
By any chance are you using usb 3.0 ports? If so try 2.0 you will have better success. Also sounds like a 5 second bootloop http://forum.xda-developers.com/showthread.php?t=1623244 I have seen it near impossible to correctly install the driver under these circumstances or to get the computer to recognize the kindle for long enough or for windows to do what it does very poorly anyway. To remove the driver problem from the equation I suggest creating a live linux bootable usb drive as in the process described here http://forum.xda-developers.com/showthread.php?t=1670405 but this does not resolve the possible issue at hand a dead battery in addition to creating the pendrive you will want to correctly add firekit found here http://forum.xda-developers.com/showthread.php?t=1430038 in order to usb boot the device and replace the bootloader with one that is designed to charge under such conditions which can be sent using firekit. Good luck
So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.
Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯
I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.
have we even seen a bricked device yet?
twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.