I accidentally drowned my phone. It powers up to the point I need to give my password to unlock it. Unfortunately the touch screen is dead. I have ADB installed to my laptop but I don't know how to get access to my files. Any help is so welcome right now, I don't even have a replacement phone.
iPap said:
I accidentally drowned my phone. It powers up to the point I need to give my password to unlock it. Unfortunately the touch screen is dead. I have ADB installed to my laptop but I don't know how to get access to my files. Any help is so welcome right now, I don't even have a replacement phone.
Click to expand...
Click to collapse
You could try using your phone with computer mouse and OTG cable.
Xokoz said:
You could try using your phone with computer mouse and OTG cable.
Click to expand...
Click to collapse
Hmm, is there a software I have to use?
iPap said:
Hmm, is there a software I have to use?
Click to expand...
Click to collapse
Your screen works but it doesn't recognize touch, right? If so, you can just enable MTP on your phone with mouse and then connect it to your laptop and access the files from there.
And no, I don't think any mouse require software to work if used with OTG cable.
E: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
You can try adb push/pull method though. Haven't done it myself so I can't be much help with that.
Xokoz said:
Your screen works but it doesn't recognize touch, right? If so, you can just enable MTP on your phone with mouse and then connect it to your laptop and access the files from there.
And no, I don't think any mouse require software to work if used with OTG cable.
Click to expand...
Click to collapse
Well it used to work, not right now. It vibrates sometimes when I press the power button, so it's not 100% dead yet. So as soon as I connect it via OTG I will have the option to access it? Interesting...
iPap said:
Well it used to work, not right now. It vibrates sometimes when I press the power button, so it's not 100% dead yet. So as soon as I connect it via OTG I will have the option to access it? Interesting...
Click to expand...
Click to collapse
If your phone boots up and you can see your screen working normally except for the touch part, then yes. But if you don't have OTG cable or mouse now and you have to order them, you might want to try those adb commands in link I edited to my previous comment.
Xokoz said:
If your phone boots up and you can see your screen working normally except for the touch part, then yes. But if you don't have OTG cable or mouse now and you have to order them, you might want to try those adb commands in link I edited to my previous comment.
Click to expand...
Click to collapse
I'll try to use the ADB as I don't have an OTG cable. I'll try it now, thank you.
Edit: It won't communicate with the device with 'adb devices'. I guess I'm in trouble...
iPap said:
I'll try to use the ADB as I don't have an OTG cable. I'll try it now, thank you.
Edit: It won't communicate with the device with 'adb devices'. I guess I'm in trouble...
Click to expand...
Click to collapse
Have you installed TWRP?
Xokoz said:
Have you installed TWRP?
Click to expand...
Click to collapse
Yes, I try to boot into TWRP but no chance. I think it's dying.
iPap said:
Yes, I try to boot into TWRP but no chance. I think it's dying.
Click to expand...
Click to collapse
Oh, that is actually a bad sign. I was wondering if you had your phone decrypted by any chance so you could've just booted into TWRP and copied internal storage to your laptop from there.
Xokoz said:
Oh, that is actually a bad sign. I was wondering if you had your phone decrypted by any chance so you could've just booted into TWRP and copied internal storage to your laptop from there.
Click to expand...
Click to collapse
I'll just let it dry in rice for a couple of days and will try several stuff again. Ill get back as soon as I have news. Thanks mate.
I do not know how high your geek-level is, but I would recommend booting twrp, decrypt the data partiton with adb and pull the complete data partition to the PC:
1. Get a bootable twrp e.g. fastboot boot twrp-XX.img
2. adb shell twrp decrypt <Password>
3. adb pull /dev/block/dm-0 ./decrypted-data.img
(Credits go to stackoverflow)
If this does not work I would attach an USB Hub after booting into twrp and attach a mouse and a storage device to the hub. (And a keyboard)
Related
Hi......
My PC & my laptop won't recognise my phone despite several failed attempts! No mass storage no fastboot, nothing! not even when i mount it via recovery! Android debugging is checked.
My phone is on CM10.1.3
Pls help!
saleh9416 said:
Hi......
My PC & my laptop won't recognise my phone despite several failed attempts! No mass storage no fastboot, nothing! not even when i mount it via recovery! Android debugging is checked.
My phone is on CM10.1.3
Pls help!
Click to expand...
Click to collapse
When you start in bootloader and choise fastboot and connect the phone what you see in device manager. Are you install latest drivers. Are you try only in Windoes7, try on XP. Are you change the cable maybe is broken.
This with RED letter is important first try change the cable
Thant said:
When you start in bootloader and choise fastboot and connect the phone what you see in device manager. Are you install latest drivers. Are you try only in Windoes7, try on XP. Are you change the cable maybe is broken.
This with RED letter is important first try change the cable
Click to expand...
Click to collapse
"Fastboot usb" but when i try to flash kernel or erase cache it gives me <waiting for device>! i should mention that everything used to work perfectely a while ago!
and yes i've tried with W7 & XP and with different cables, but nothing changed! only charging.
saleh9416 said:
"Fastboot usb" but when i try to flash kernel or erase cache it gives me <waiting for device>! i should mention that everything used to work perfectely a while ago!
and yes i've tried with W7 & XP and with different cables, but nothing changed! only charging.
Click to expand...
Click to collapse
Are you using the stock cable and is the usb port your using a 2.0 port? if not then it wont work or well it might but not stable.
saleh9416 said:
"Fastboot usb" but when i try to flash kernel or erase cache it gives me <waiting for device>! i should mention that everything used to work perfectely a while ago!
and yes i've tried with W7 & XP and with different cables, but nothing changed! only charging.
Click to expand...
Click to collapse
Change the cable first!!!! Are you tried with different cable?
fader910 said:
Are you using the stock cable and is the usb port your using a 2.0 port? if not then it wont work or well it might but not stable.
Click to expand...
Click to collapse
Yes, and i don't think that would make any difference! cause if it was "1.1 port" it would work but slower!
Thant said:
Change the cable first!!!! Are you tried with different cable?
Click to expand...
Click to collapse
I've mentioned that i used different cables! htc/sony/samsung
saleh9416 said:
Yes, and i don't think that would make any difference! cause if it was "1.1 port" it would work but slower!
I've mentioned that i used different cables! htc/sony/samsung
Click to expand...
Click to collapse
then if you have the latest drivers and no working again you have hardware problem with the USB port on your hox,
Thant said:
then if you have the latest drivers and no working again you have hardware problem with the USB port on your hox,
Click to expand...
Click to collapse
I hope not! and the confusing part is the phone charges via the USB port!
Thanks anyway.
saleh9416 said:
I hope not! and the confusing part is the phone charges via the USB port!
Thanks anyway.
Click to expand...
Click to collapse
Yes your power pin 1 and 5 work. your pin 2 Tx(from phone to computer) not work and pin 3 Rx(from Phone to computer)work.And for this you see your device fastboot usb becouse the phone receive from computer and know to go in fastboot usb but when you send command from computer fastboot getvar all the computer wait for response from the phone but your Tx is broken and you see waiting for device.
Please try to run the comand fastboot reboot-bootloader and report back
saleh9416 said:
Hi......
My PC & my laptop won't recognise my phone despite several failed attempts! No mass storage no fastboot, nothing! not even when i mount it via recovery! Android debugging is checked.
My phone is on CM10.1.3
Pls help!
Click to expand...
Click to collapse
hello! I had the same issue recently, so I solved it by next actions: I typed in the Windows command line(cmd.exe) 'pnputils -e', so I could see all drivers I have installed and their 'oem*.inf' files. I had 4 HTC drivers, it was like they were in a conflict. Then I deleted each driver with next command: 'pnputils -f -d <oem file name>.inf'. So after that, I plugged in the cable and the HOX was recognized by the computer!
Report back if that helped you!
Thant said:
Yes your power pin 1 and 5 work. your pin 2 Tx(from phone to computer) not work and pin 3 Rx(from Phone to computer)work.And for this you see your device fastboot usb becouse the phone receive from computer and know to go in fastboot usb but when you send command from computer fastboot getvar all the computer wait for response from the phone but your Tx is broken and you see waiting for device.
Please try to run the comand fastboot reboot-bootloader and report back
Click to expand...
Click to collapse
The same message "waiting for device"
saleh9416 said:
The same message "waiting for device"
Click to expand...
Click to collapse
Try the metod on @Timofey_K
Wich recovery are you using? Try enter from there, mount the Phone as mass storage from recovery
Sent from my HTC One X using xda premium
matitorres07 said:
Wich recovery are you using? Try enter from there, mount the Phone as mass storage from recovery
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You really have to read the OP again :sly:
Timofey_K said:
hello! I had the same issue recently, so I solved it by next actions: I typed in the Windows command line(cmd.exe) 'pnputils -e', so I could see all drivers I have installed and their 'oem*.inf' files. I had 4 HTC drivers, it was like they were in a conflict. Then I deleted each driver with next command: 'pnputils -f -d <oem file name>.inf'. So after that, I plugged in the cable and the HOX was recognized by the computer!
Report back if that helped you!
Click to expand...
Click to collapse
Unfortunately it didn't work! I've found only 1 HTC driver & I deleted it anyway, but the issue remains unsolved!
I presume the issue is within my phone! maybe it's a hardware problem as @Thant have said.
Thanks anyway.
i was having a similar (not exactly same) problem that on CM 10.2, my phone storage was not being mounted on my pc but it mounted in recovery and fastboot... this is what i did..
Connect your phone to pc, go to device manager from control panel and see if the device shown with a yellow triangle.
right click it, chose to update driver software, select manually from a list, chose android adb interface from list, then either chose google or htc (depending on your rom, for CM, prefer google).. Your phone will be recognised by pc
Khizar Amin said:
i was having a similar (not exactly same) problem that on CM 10.2, my phone storage was not being mounted on my pc but it mounted in recovery and fastboot... this is what i did..
Connect your phone to pc, go to device manager from control panel and see if the device shown with a yellow triangle.
right click it, chose to update driver software, select manually from a list, chose android adb interface from list, then either chose google or htc (depending on your rom, for CM, prefer google).. Your phone will be recognised by pc
Click to expand...
Click to collapse
The phone isn't shown in device manager!
saleh9416 said:
The phone isn't shown in device manager!
Click to expand...
Click to collapse
Then try using a different data cable... also try connecting it to a different pc and also check if otg usb is working or not.. coz if otg does not work then its a problem with your port
I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up
Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing
USB debugging enabled?
Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues
canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices
Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked
canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep
canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
tnsmani said:
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
Click to expand...
Click to collapse
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
manto02 said:
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
Click to expand...
Click to collapse
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
tnsmani said:
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
Click to expand...
Click to collapse
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
manto02 said:
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
Click to expand...
Click to collapse
Just now, I switched off USB debugging in my OP3 and connected it to the Laptop. While the command 'adb devices' does not find the phone, as soon as it is connected, it shows up as a storage device and I can open it and copy data. I think that for this to work, you should have enabled MTP option for file transfer.
Check this on your phone.
EDIT: Check THIS as there seems to be a way though I am not sure that it works on current Android versions since the file locations may be different. Read till the end.
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
manto02 said:
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
Click to expand...
Click to collapse
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
tnsmani said:
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
Click to expand...
Click to collapse
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
manto02 said:
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
Click to expand...
Click to collapse
Have you tried fastboot flash twrp recovery and then fastboot reboot to recovery
You can try usb c to hdmi adapter , connect to a monitor or tv.
I am not sure but worth trying!!!
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
From what i can remember, the recovery mode, accessible from the fastboot menu, has a usb access mode.
If worst comes to worst though, i personally have replaced the screen on my OP3, and its not as difficult as it seems or is made out to be. Took me max 4 hrs.
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.
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.