Database Users

A load of problems...

So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.

Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers

bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery

Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?

bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.

Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?

bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.

Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck

Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!

Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.

Recovery mode, device not detected by Windows

ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,

brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.

sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,

brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.

Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery

How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?

mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!

my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.

Nexus 10 Recovery - USB not enabled

Hi,
When entering recovery mode on the Nexus 10 (Android 4.4.3), when I connect the tablet up the a computer it does not detect a USB device. This is not the usual driver related issue - nothing shows up in device manager - it is as though the USB cable isn't even connected. The usual sound from Windows when you connect a device does not sound.
I can connect fine when the Nexus 10 is booted, and I can call "adb reboot recovery" and the tablet reboots to recovery, but then there is no USB connection.
To reiterate - there are no driver issues as I'm not even getting as far as loading a driver! I've tried two different computers (Windows 8.1 and Windows 7) and two different USB cables.
Anyone seen this before? Why is USB disabled when in recovery?
Thanks,
Gary.

garysargent said:
Hi,
When entering recovery mode on the Nexus 10 (Android 4.4.3), when I connect the tablet up the a computer it does not detect a USB device. This is not the usual driver related issue - nothing shows up in device manager - it is as though the USB cable isn't even connected. The usual sound from Windows when you connect a device does not sound.
I can connect fine when the Nexus 10 is booted, and I can call "adb reboot recovery" and the tablet reboots to recovery, but then there is no USB connection.
To reiterate - there are no driver issues as I'm not even getting as far as loading a driver! I've tried two different computers (Windows 8.1 and Windows 7) and two different USB cables.
Anyone seen this before? Why is USB disabled when in recovery?
Thanks,
Gary.
Click to expand...
Click to collapse
Your on the stock recovery ?

lj50036 said:
Your on the stock recovery ?
Click to expand...
Click to collapse
Sorry should have mentioned. Yes completely stock.

garysargent said:
Sorry should have mentioned. Yes completely stock.
Click to expand...
Click to collapse
I was unaware that the stock recovery had adb..
Let me look into this..
Thx Josh

Figured this out thanks - turns out "adb reboot recovery" doesn't put the device into a state of waiting for a sideload - you have to do a further press of POWER+VolUp to bring up the menu then select sideload via ADB - the USB then kicks in! Doh.

Nexus 4 - bricked? - TWRP - no OS installed

Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock

Try fastboot from the bootloader, and reflash

ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?

breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...

ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.

breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there

my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?

breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk

dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?

breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk

dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.

breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk

dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?

breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk

dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.

breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk

breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?

ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:

As in "no devices detected" ...what is the output? Pfffft I tried!

ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.

Bricked Oneplus 2 Not Connecting To PC

- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop

I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable

Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?

foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable

evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week

fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.

evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken

Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc