Related
I've been running CyanogenMod 10.2 on my rooted HTC One for a good long while now. Since the ROM worked so well, I never had the need to connect the phone to a computer via USB in quite some time. A few months ago, when I attempted to transfer some photos, I ran into a weird and frustrating road block; my phone is simply not being recognized by any computer <see here>
I have updated all drivers
I have enabled debugging in Developer Options
I have tried rebooting Fastboot in bootloader
I have tried using the toolkits
I have tried everything I think I know
The weird part is that the phone charges via USB connected to the computer.
Since it didn't effect much, I just figured it was a glitch and I never ran into a problem again--that is, until today. I hadn't used my MHL adapter with the HTC One (only my GNexus), but after reviewing an intended installation of a Pioneer Appradio, I wanted to ensure that my One would work with the MHL. Hooking up my One to the Samsung MHL adapter (and power supply of course), I get no display on my television.
I am now beginning to wonder if the USB port is damaged. Visual inspection doesn't reveal anything, but I am curious if anyone has had this problem and would appreciate any help. Is there any way to test if I've fouled up the port?
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
cmlusco said:
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
Click to expand...
Click to collapse
No and no
I installed Flashify and did install CWM 6.0.4.7 to see if it would help, but to no avail
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
cmlusco said:
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
Click to expand...
Click to collapse
I have tried adb, but the device never is recognized.
I'm currenty transferring my TWRP backup via WiFi.
I planned on switching to CM11 and see if I can't get it to work after that.
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Yeah, you guys are awsome, it worked!!!!!
Thanks so much for all your help and advice :good:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
gffmac said:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It doesn't need an OTG cable?
Nope, using the supplied cable just connect the micro usb end to shield other to PC and bobs your uncle ?
Sent from my HTC One M9 using Tapatalk
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
beefy143 said:
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
Click to expand...
Click to collapse
It should?
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
beefy143 said:
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
Click to expand...
Click to collapse
Follow the instructions EXACTLY. I have the 16Gb model and mine was doing the same thing as yours.
Just to repeat what others said the back of the shield TV has a microusb port so you don't need a otg cable just use any standard microusb cable you have laying around plug small end into shield TV and big end to laptop/computer
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
You should be using fast boot to do this. Plus, there's no SD card in the instructions. Not sure what you are trying to do.
JoCamel said:
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
Click to expand...
Click to collapse
Try again without an sd card attached maybe. Also try 'fastboot boot recovery.img' instead of flashing it.
Neo3D said:
[*]In the Windows command prompt, type: fastboot devices
[*]Make sure the fastboot device appears.
[*]If you see your fastboot device, then you can follow the instructions
Click to expand...
Click to collapse
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
if i not enable debug? how to do?
fredphoesh said:
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
Click to expand...
Click to collapse
Could be a driver issue? Make sure the drivers are properly installed and working? Try rebooting?
Will these steps work with the 2017 16GB version? Cause I want to have full Android on the Shield but the processes I've seen are pretty confusing.
I want to try this, will this work with the new 5.2 update?
Jabadabaduu!! It solved my problem
Hey Neo
First of all, your guide saved my day! - Thanx!
I know this must be a strange question, but is the person on your XDA profile picture, and the one that has written the article really the same person ?
Neo3D said:
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Click to expand...
Click to collapse
Awesome, works like a charm
Hi Everyone,
I seem to have bricked a nexus 2013 wifi. At first, it was having movie playback issues so I restored it to lollipop using factory image on the google site. I decided to get OTA up to the latest MM. So far so good. But I though about putting a custom rom to it. So I installed TWRP 3.02 for flo and flashed PN MM with the recommended GAPPS. Kernel was what came with it. It worked fine until this morning when I realized that the touchscreen was not responding. I went to BL mode and into recovery. TWRP came up but touch was not responding as well.
So, I connected the device to my PC. It now shows unrecognized device. It still charges and all that but It is now stuck on the google logo. when I go to TWRP, touch wont work. I have tried another cable, still the same. My N6 is detected without issues using the same PC and cable. Since there are no drivers, I cannot reflash anything...
Any thoughts? Or am I just lucky to have bricked it? Appreciate any inputs that will be thrown in this direction. Cheers!
Hi, N7 motherboard gets touch, USB, accelerometer and compass data via the wide silver cable which often suffers from poor contact. Please try this first. If it is still not fixed, then in fastboot mode run and post the output of the following commands:
Code:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Thanks for the help. hmm.. i pressed that part and it booted up to PN, touch is working as well. Not sure if that fixed it but if it happens again im gonna try to press that area. however, its still not detecting the device. I see it in Device manager, it says unknown device and will not take any driver, so fastboot is not an option for me atm.
so just an update. when I was able to boot up, it will not go landscape no matter what. I downloaded check my android and it the tests for compass and sensors were not responding. I decided to open the back cover, it was fairly easy. The thing is I have not the right tools to reseat the silver flex cable and I fear I might damage it, so I tried putting folded paper on to where it connects to on both ends. Now the thing works with landscape and so far, have not experienced touch issues or no boot issues.
I still do not have access to fastboot, though, as it still isnt detected by my computer. so I may have to stick to putting stuff to it over the air. Or should I just reseat that cable? Does it just slide out?
welxiii said:
I still do not have access to fastboot... should I just reseat that cable?
Click to expand...
Click to collapse
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
noahvt said:
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
Click to expand...
Click to collapse
The next step:
disconnect the ribbon cable from both the mobo AND daughterboard
spray the cable's and PCB connectors' contacts with Electronic Cleaner
reconnect and relock
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
Hi,
I really appreciate the assistance. Well, here's what I found.
[*]What's the VID/PID of the non-detected device? USB\VID_0000&PID_0002\6&688A3B8&0&2
[*]Does ADB work if you start TWRP? I don't think it does. In TWRP, I still get a message on my computer that the device has failed. DM shows the device as unknown usb device (device descriptor request failed)
[*]Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it? no it doesnt. same error as above.
[*]Is an OTG flash drive recognized? yes it does.
[*]Maybe Windows has a driver problem - does it work from live Linux? I'm still working on this. btw the same setup works on my phones and they are detected just fine.
update:
Suddenly its now detected by my pc. I connected my usb otg. At first,. It wasnt detected so I tried the usb on my nex6 and it worked. I connected it back to the 7 and voila! No error and DM now shows it as an android device. Whew!
But I have one question, is it safe to leave the folded papers i placed on both ends of the silver connector?
welxiii said:
Suddenly its now detected by my pc...
...is it safe to leave the folded papers i placed on both ends of the silver connector?
Click to expand...
Click to collapse
Yes.
As I mentioned earlier, the silver cable also connects USB data, so if you experience USB detection problems again, then do full re-seating with clean-up.
Cheers :highfive:
Thanks again for the assistance. Hopefully, it doesn't come to that.
unbricked my google nexus 7 tablet
if anyone has bricked there nexus 7 wifi tablet.....you can now unbrick it with the skipsoft toolkit. my tablet was bricked for awhile (it was stuck on the google logo and when I tried to boot into the twrp recovery it showed the android bot with an exclamation point so I was screwed big time) so I just brought another one (different version). after awhile I gave up hope, but today I decided to unbrick it (or atleast try to). at first I was using the nexus toolkit like I did before and I was having problems with it being recognized via adb and it wouldn't flash the stock recovery.img. than I remembered that I also had the skipsoft toolkit installed on my computer and the nexus 7 tablet was also supported on that toolkit so I decided to give it a try. at first, since I had it plugged in, it wouldn't recognize that it was plugged in not realizing that I had to download all the images and recoveries it needed to be able to root it and return it to stock if necessary so I did that and when I finished installing everything it detected that my device was in fastboot mode. I flashed the stock recovery image and it booted up like it was suppose to. I'm writing this just incase so one has bricked there device and has lost all hope in fixing there mistake. I love android and recently have a lg nexus 5x that's rooted with a custom rom on android 7.0 nougat. android is awesome
who ever developed the skipsoft toolkit....your awesome and thankyou for making this possible.
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.
I unlocked the bootloader, I did a wipe data and now the firestick is stuck on the firetv black screen, cant access the menu, cant connect through adb with the computer connected via usb.
I can access TWRP with otg cable and mouse, but I dont have any rom to flash on device, so I cant reflash it, I dont have access to adb to push it either.
If I connect a usb hub to the otg, and connect the mouse and a usb stick at the same time, can I access the usb stick memory to flash the rom zip file?
Help
Update:
Problem solved I did the unlock bootloader process again as Pretoriano80 advised and it worked, I got access again to TWRP, used adb to push the rom and flashed the rom again.
Thank you.
rodainas said:
I unlocked the bootloader, I did a wipe data and now the firestick is stuck on the firetv black screen, cant access the menu, cant connect through adb with the computer connected via usb.
I can access TWRP with otg cable and mouse, but I dont have any rom to flash on device, so I cant reflash it, I dont have access to adb to push it either.
If I connect a usb hub to the otg, and connect the mouse and a usb stick at the same time, can I access the usb stick memory to flash the rom zip file?
Help
Click to expand...
Click to collapse
Yes, if you connect a mouse + usb stick (fat32) you will be able to flash a stock rom. In TWRP you will have to switch from internal memory to the OTG stick.
Thank you for the answer thats good news.
So any usb hub should work right, i will have to buy one.
Sent from my iPhone using Tapatalk
rodainas said:
Thank you for the answer thats good news.
So any usb hub should work right, i will have to buy one.
Click to expand...
Click to collapse
If TWRP works, then you can push a stock firmware from PC to the FireTV Stick with ADB. Just make sure that your stick is connected to your pc with the original USB cable (not OTG).
I already tried.
When connecting directly to pc, no otg cable, I cant use adb, looks like after I wiped data the device lost the adb.
I tried adb shell it says no devices/emulators
I tried adb devices, none listed
So I cant connect through adb, I cant access recovery nor I can push the flashable rom.
The only way I can access is with otg cable + mouse.
That leaves me with only one option, use the hub to connect mouse + stick to the otg cable and flash through otg usb in TWRP.
Sent from my iPhone using Tapatalk
rodainas said:
I already tried.
When connecting directly to pc, no otg cable, I cant use adb, looks like after I wiped data the device lost the adb.
I tried adb shell it says no devices/emulators
I tried adb devices, none listed
So I cant connect through adb, I cant access recovery nor I can push the flashable rom.
The only way I can access is with otg cable + mouse.
That leaves me with only one option, use the hub to connect mouse + stick to the otg cable and flash through otg usb in TWRP.
Click to expand...
Click to collapse
TWRP's ADB should work, but probably you can't boot into TWRP without OTG. The solution is to do the unlock procedure again so after the last step it should boot to TWRP automatically.
If that fails, then you can buy an USB hub.
Thank you for helping really appreciate that.
I will run the procedure again, will keep you posted about the results.
Ok tried it
No response from device
After ./bootrom-step.sh it says waiting for bootrom, I do the short connect the device but the computer doesnt recognize it, keeps saying waiting for bootrom no matter what I do.
So I think theusb hub is the only resource now.
Sent from my iPhone using Tapatalk
Ok Tried again, it works, am on TWRP with adb, pushing the flashable now, will keep updated.
Update:
Good news
Firetv fixed, thank you very much!
rodainas said:
Ok Tried again, it works, am on TWRP with adb, pushing the flashable now, will keep updated.
Update:
Good news
Firetv fixed, thank you very much!
Click to expand...
Click to collapse
Great! No problem, it happened to me once and has been the only that worked for me (without the need of an usb hub, of course), so i was pretty sure that it would work for you too.