Tried flashing franco to Linneage 15.1 -- need some help unbricking - Nexus 6 Q&A, Help & Troubleshooting

Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
No big deal right? I mean sure, I didn't make a back up first (Mistake #2) but it shouldn't matter because I can just go into twrp and factory reset and reflash everything.
So off I went to copy over the zips to my phone -- went ahead and wiped everything (mistake #3) and then opened up windows explorer to copy over the zips. Turned out my computer couldn't see my phone.
I tried mounting and unmounting and installing and uninstalling drivers. Moving over to my other computer (linux mint) messing around with adb sideloads, and lastly tried using OTG. Turned out my computer just couldn't register my phone at all with adb.
So then I switched to fastboot -- at the very least I should be able to reflash stock and then root and then install custom stuf, right? But I couldn't get my phone to even register on windows or linux with driver changes using fastboot!
I was pretty upset at this point (still am, admittedly).
In fastboot mode whenever I plug in my phone my computer doesn't even bat an eye, and my phone just says it's waiting for a data cable connection. Windows will register it after a while as a "code 43: Windows has stopped this device because it has reported problems" after a while but I still wasn't able to get the right drivers to register the device. Doesn't even show up in lsusb in linux.
Wondering now if maybe when the device was alive I forgot to enable adb debugging first or maybe it doesn't register because it was set to charge only in the usb mode setting. Is there a way to change those settings in recovery like through the terminal? I would love to hear any possible solutions, I've been googling and search xda all over the place so any insight would be really appreciated.
Fortunately I had an extra shamu (with a very cracked screen) left over that I switched to in the mean time, but I'd like to get my old phone back in working order if possible! Any help or insight is appreciated!

gunha said:
Hi all!
Made a really stupid mistake this morning: I was getting frustrated with Linneage 15.1 battery performance, so I tried flashing latest franco kernel (without reading that 15.1 doesn't like custom kernels; mistake #1).
Click to expand...
Click to collapse
You even made more errors. You don't seem to read properly. Franco does only support shamu up to nougat.
- Did you install the latest USB drivers and latest platform tools (adb, fastboot ...)
- Did you boot you phone into bootloader when you tried to connect?

Yup! I installed drivers from Google when I downloaded the platform-tools. I put my phone in bootloader mode when using fastboot, and my phone never indicated 'USB transfer cable connected' it just said 'connect usb.' also fastboot just said waiting for devices when I tried doing a getvar all....

try it on another laptop, try a new usb cable...you seem to have done everything right

I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging

gunha said:
I've tried a bunch of different computers and cables... the weirdest thing is that it'll use the cable to charge just fine, but won't let me transfer anything by mtp (in recovery) or fastboot when in its bootloader :/ still get "connect usb data cable" even if the battery is charging
Click to expand...
Click to collapse
Could be the cable. But the USB port could also be the cause. The simplest solution could be that the port is just full of dust. In that case, cleaning will help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

IF you still have access to TWRP, you can move your zips on an usb drive and connect it via otg and mount in TWRP and flash from the USB drive. Might help.

Related

[Q] MTP MHL not functioning

So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
BCH/HTC said:
I have the exact same thing, but the device is the HTC One V. It'll charge, but any attempt for it to be recognized as a usb device fail. I have figured out that the usb connector is bad.
Do you get a snug fit when you plug it in to a usb cable,or is it loose and wobbly?
Click to expand...
Click to collapse
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
tudorlv said:
It's not wobbly at all. But if it's a usb connector failure, why does charging work?
Click to expand...
Click to collapse
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
BCH/HTC said:
I agree. It's bizzare. If it's charging fine and it's not loose, it doesn't make sense. I assume that HTC sync won't recognize it either? Have you tried relocking the bootloader and go back completely stock? Do you also get the Windows error that the "usb device has failed"?
Click to expand...
Click to collapse
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
tudorlv said:
No, htc sync does not recognize it, didn't try relocking and get stock. Have you? so I don't go that way without succes. Lastly, no windows error when connecting the phone, not even that annoyng beep sounds.
Click to expand...
Click to collapse
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
BCH/HTC said:
Crap. I just realized that relocking the bootloader is impossible if it can't be recognized as "usb fastboot" or "adb device".
That sucks man. It really doesn't make sense. Try uninstalling everything HTC related, reinstall drivers, and then reboot your pc.
install drivers again and see if that does anything.
Click to expand...
Click to collapse
I know it sucks. Already tried uninstalling and reinstalling everything related with no succes. I'm thinking this could be solved (or tried) by terminal emulator commands on Rom toolbox, if it's not hardware related. I will backup my sdcard trough airdroid (it will take long) and try to format it
WTF my internet data connection does't work either, wifi and gps works though
EDIT: data works, carrier fault now it's ok
tudorlv said:
WTF my internet data connection does't work either, wifi and gps works though
Click to expand...
Click to collapse
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
Ok, I will try later this day with other cables, hope it works. I will get back here if successful
BCH/HTC said:
Is there anything you downloaded either to your device or to your PC lately? Does toggling USB Debugging do anything?
Like you said, backup everything, & then completely wipe it all. Like I said, my HTC One V had all the same symptoms, right down to the "Fastboot AC" message. To this day I still can't figure it out, but if I carefully wiggle the usb cable, I can get it to almost get the drivers installed, but it ultimately fails.
I did a little searching on the web & some guy had the same issues & for some reason he was told to update his Windows media player & it worked again. Long shot..I know.
Also..I know you said you tried a few different USB cables, but I would still suggest buying a brand new one and giving it a go. USB cables can be super finicky for some reason. They will charge, but when it comes to data, they won't work sometimes. Just a suggestion.
Click to expand...
Click to collapse
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
tudorlv said:
So tried right now with a working cable, win7, it does recognize a galaxy3 but not the One
Just realised that if I format the sdcard there is no way of reinstalling or recovering anything
Click to expand...
Click to collapse
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
BCH/HTC said:
Man...this is bizarre. I wish I had some other suggestions for you. The only thing I can think of is that the data partition is now corrupted within the device. How that would happen though, I have no idea.
I found this write-up on the web. Maybe it can help you, but to be honest, I am not positive it'll help. There has to be some other more experienced veterans on this site that can help you out some more.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
Click to expand...
Click to collapse
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
tudorlv said:
Well, thank you for trying to help, but it seems nothing that can be done by connecting to a computer (adb fastboot commands) is working.
I am pretty sure that the micro usb port is not damaged because this morning when I booted the One after 3 or so minutes (still connected to my win7 64b laptop) it was detected by windows, even both usb icons appeared in statusbar on phone, and pretty surprised I disconnected and reconnected it but it failed.Tried to move the usb connection in ever way possible without breaking it but nothing. You can't imagine the frustration...
I can't go back to stock as I can't flash the recovery or anything else from computer as I stated before.
As everything else is working perfectly including charging I'm afraid to try possible solutins without being able to revert them easily, so my cry for help is to someone who knows how to use terminal emulator commands and make something out of it.
Thanks again!
Click to expand...
Click to collapse
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
BCH/HTC said:
Sorry to hear that man. I hope everything gets sorted. Good Luck!!:good:
Click to expand...
Click to collapse
Solved, check first post (wipe cache and dalvik cache)
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
Wow!...I can't believe it was that easy. That's awesome though. Glad you got it up and running again.
tudorlv said:
Solved, check first post (wipe cache and dalvik cache)
Click to expand...
Click to collapse
how to wipe dalvik cache without custom recovery
tudorlv said:
So, finnaly solved!
After reading the whole internet (literally) about this problem happening to many HTC (but not only HTC) phones, including not chargind just when turned off, not recognized by computer (including adb, fastboot), going in car mode, I finally found the solution
Here is what I tried
Several custom and stock kernel and recovery flash, different nandroid backups, different roms including stock even clean install (weird, see later why), different cables, drivers, port cleaning.(RUU isn't possible as the phone doesn't get recognized)
The solution however was muck simpler, just wipe cache and dalvik cache and BAM! all working (at my initial arhd rom)
What I suggest (the order doesn't matter) from all the reading done before conclude it's a hardware problem is:
DO A NANDROID BACKUP!
Try different cables and drivers, even computers
Uncheck the fastboot option in power settings and reset
Clean the port with alcohool (or similar), with the phone shut down and then dry it completely
Wipe cache and dalvik cache
Restore the nandroid backup several times, at some people this did the trick
Boot in safe-mode if possible (APM), this way you can check if it's a 3rd party software that can give problems as in safe mode only stock apps are available
Hope I helped
Hello,
Long story short, out of the blue my One doesn't get recognized by any computer, I tried 3 different laptops, all 3 with win7,different cables, latest HTC drivers installed, uninstalled and installed again, but no succes, even my One doesn't get the usb icons show up when I connect it to any laptop, BUT it does charge
Anyway I tried flashing another Rom,factory reset, kernel but nothing changes, adb and fastboot don't recognize my phone
Also the Icon appears when I connect the phone to an MHL adapter but no picture shows up on TV, it worked before
edit: when booted in fastboot it says fastboot AC, not fastboot usb
The get back to HTC solution is a no go as I don,t have any invoice of buying this phone and in EU is required for warranty
I'm currently on ARHD 41.0 kk 4.4 and Elementalx 10.10.1 kernel, S-off, usb debugging on, TWRP 2.6.3.4
What should I try to fix this? Thanks for any suggestions made!
Click to expand...
Click to collapse
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Mr.Ronik said:
HI man , I have a similar problem,the app car mode start automatically, the pc doesn't recognize my htc one and doesn't recharge it, but i have the options of 'fastboot usb' so i've flash other room : cyano and gpe stock, but however it doesn't work. the strange thing is that after connecting the phone to pc i'cant recharge it with the charger but I have to restart it before and so it works. I've wiped cache and dalvik cache but it still not work :crying:
Click to expand...
Click to collapse
I know this is very late but have you get any solution for it?

Help. Nexus 6 not recognized via adb, fastboot.

Nexus 6 running android 7.0 developer preview. I tried to flash something and the device went haywire. Booted into TWRP to try to restore a backup kept getting unable to mount storage error. Decided I would wipe everything and boot into bootloader and flash a factory image via fastboot. Always a very easy way to make sure everything gets fixed! The device will not not communicate with anything. Let me preface this by saying I have searched all the various threads regarding updating drivers etc.....
When I say my device won't communicate with anything I mean AT ALL. Device isn't detectable using ADB while booted into recovery, It isn't detected using "fastboot devices" command while booted into bootloader. Keep getting the "waiting for device' I tried to update the drivers in windows, but the phone no longer shows up in the Device Manager on my Windows laptop which makes it impossible to update the drivers. I also know my drivers are not the problem. I have a Nexus 6p which communicates perfectly on my Mac, on my Windows PC, via ADB and Fastboot..... I tried to see if my mac would recognize the device, so i tried all of the above on my mac to no avail. I also tried to place a rom file on a usb drive, use an adapter to connect the usb to the phone and jump it onto the phones internal storage. No matter the size of file I place on the usb, it always shows as 196Mb, TWRP lets me switch to OTG usb to install the file, but the shows no files on the jump drive.
So I have a phone that will boot into TWRP, but I can't move any files onto my internal storage in order to flash them. I can also boot into the bootloader fine, but the devices isn't recognized so I can't flash a stock Img.
It seems I am screwed at this point. Tried Wugfresh Nexus Root Toolkit as well and get the same "waiting for device" error.
Anybody got anything I can try to bring this thing back to life?
2gskaizen said:
Anybody got anything I can try to bring this thing back to life?
Click to expand...
Click to collapse
Sounds like maybe a wonky usb port. Maybe dirt stuck in there? Maybe replace it (there are videos out there). Maybe just pull the back and push it gently to see if it works then.

Unable to connect Nexus 6 to computer for file transfer - Unknown USB Device

I recently tried to install PureNexus 7.1.2 along with the latest version of GApps 20170610. There seems to be some sort of conflict with that version of Google Play Services that prevents my device from completing setup. Without completing setup, I'm not able to do anything with the phone.
In an attempt to save myself, I want to go back to the older version of the ROM and GApps that worked, but first they need downloaded. In the past, I could go into TWRP and mount my device to my PC and transfer the files I needed to install. Now, Windows is showing my device as Unknown USB Device (Device Descriptor Request Failed). Going through every thread I could find about updating drivers, etc, it still does not work. This used to work just fine in the past on the same PC (Windows 10).
Both adb and fastboot don't seem to work either. There is no device found. When I boot the phone into Bootloader mode and plug in the USB cable, it shows Transfer Mode: USB Connected but running fastboot on the PC still can't find anything.
I am not sure how else to go about getting the necessary files on the device to flash them.
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
tristanlee85 said:
For what it is worth, I was able to get the ROM booted enough to connect to my Mac via Bluetooth and am able to transfer a file that will hopefully work. It still doesn't explain why USB can't connect. I have tried it against (2) Windows 10 PCs and my Mac with 4 different USB cables, one of which I went out a purchased today because of the issue. I am beginning to think something internally has failed on the device.
Click to expand...
Click to collapse
It could be just a dirty usb port.
Where's answers
ktmom said:
It could be just a dirty usb port.
Click to expand...
Click to collapse
Unfortunately I do not think that is the case. I have used a number of different means to clean the connection with rubbing alcohol and electrical terminal cleaner, small utensils to get in there and clean the contacts, but no luck. I am to the point now where the phone won't boot up the OS. I can get into TWRP and the Bootloader, but from there I have no way to transfer files to the device.
Bluetooth was my option before, but that is when the device would boot. There's no way to enable BT from recovery right? I am trying to reset the phone back to stock to trade it in to Google, but I am afraid I am going to be out $100 since it seems to be as good as dead now.

OP3T Bootloop - no way to flash new firmware?

Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out

HELP- my OP3T not connecting to the PC

Hi all,
I have OP3T that just not recognized by my PC. I also have another OP3 that connects just fine to this PC. I tried dev menu and USB debug+ MTP, tried to wipe cache, install a new stock ROM downloaded from OP website, also installed the drivers in the PC.
device manager not shown anything when I connect the phone (no MTP device or Android device) and tried several cables and also another PC.
the phone was rooted until the last update (last December) and now I want to install custom ROM and I can't!
I think you want to fastboot flash a recovery?
What OS? Fastboot devices returns null?
yes, so I can install custom ROM eventually. my PC runs win 10 64X and right now my phone has stock android 8.0 (OOS).
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
is there's an option to flash recovery without using the PC?
Saninisson said:
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
Click to expand...
Click to collapse
No generic MTP or Android device at all? On either PC, trying different ports (I know you said you tried multiple cables - which is good trouble shooting)? And no pop-up on the phone, allowing you to select MTP (move files, or whatever it says)?
If that I the case, I tend to think the USB port is damaged.
Saninisson said:
is there's an option to flash recovery without using the PC?
Click to expand...
Click to collapse
I've seen some folks package TWRP into a bootloader-flashable zip on other devices, but haven't seen anything like that on the 3T.
More importantly, I'd say it's very risky modding the phone with custom recovery and flashing a ROM, without having fastboot and adb tools available. You can get stuck in a real bad jam doing this, with tools to recover the device. I don't recommend it.
Yes I tried it all but there is no indication besides the device is charging while connected to the USB port.
OP support say that this might be the case, but I don't know if I want to replace it since my screen is cracked and it will brake it as soon as I open the phone

Categories

Resources