Related
Alright, I am having some trouble with the Nexus and hopefully someone can help me with this. Then Nexus was unlocked and rooted but I was still rocking the stock rom on there. The tablet used to be recognized by the computer and everything was fine. I used a car charger today to charge the tablet, came home, and the tablet would no longer show MTP when connected to the computer but rather would only charge.
I thought it was an issue with the rom so I downloaded a new rom, made a backup and went to flash it. Something happened when I was flashing the rom which forced the tablet to reboot and all it would get to is the Google screen. It won't go past that. I can get into the bootloader but can't boot into recovery or the system. Its not being recognized in fastboot mode either so I have no way to flash a recovery onto it...
Any suggestions?
have you tried force rebooting it a few times to try to get it ti boot up?
simms22 said:
have you tried force rebooting it a few times to try to get it ti boot up?
Click to expand...
Click to collapse
Multiple times. I have also used several different USB cables and ports on the computer. Still nothing
Any other thoughts?? I'm really in a bind
rmerchant786 said:
Any other thoughts?? I'm really in a bind
Click to expand...
Click to collapse
Can I take a look at it for you? Send me a PM and we will chat on google talk. I have some ideas though, we can connect remotely with teamviewer and I'll see if I can tell what's going on.
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Engstrom said:
Any luck? I'm having the same problem.
The device is not recognized by the computer at all and the bootloader freezes then I connect it to the computer or the charger.
Click to expand...
Click to collapse
change your wire it maybe faulty or try it again on another pc
ngoralph said:
change your wire it maybe faulty or try it again on another pc
Click to expand...
Click to collapse
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Engstrom said:
I've tried three usb cables on three computers (with W7, W8, Ubuntu and OS X). Makes no difference.
It does however indicate charging then it's off.
Click to expand...
Click to collapse
out of ideas but i used the wire given on the box and it worked but when i used different plug it didn't work
I have the same problem too after i meet flashing error in TWRP ~
I'm trying to flash Paranoid ROM update in TWRP, somehow the recovery show error when flashing so i decided to reboot system.
After that it stuck at Google logo and when I try to plug in the usb to computer, the fastboot freeze...
What to do man? Please help me
Please anyone help help ???
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
I had similar issue
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
Thanks for the reply mate
I can get into fastboot but once I connect the usb, it freeze and the toolkit I used (GNEX TOOLKIT) couldn't get my device :crying:
And sorry to ask, what is adb connection?
I only know fastboot, now my N7 only can boot in fastboot without usb plug in :silly:
But I will try to use the toolkit you recommend me, hope it works :fingers-crossed:
Thanks a lot
---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------
exglynco said:
Are you two able to get an adb connection? If so, and you can get into fastboot, you can download and flash the Google factory ROM.
If you are not familiar with adb, try the Nexus 7 Toolkit from Skipsoft.net to flash the OEM ROM.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
wtgserpant said:
When I first unlocked and rooted my N7 .... and then tried to flash AOKP, I had a very similar issue as it would not boot into OS or CWM! SO i left it for some time and then crossed my fingers and tried to boot into bootloader 1 day later and then CWM ..... and it worked!
I think this is quite good advice for u to try out!
Click to expand...
Click to collapse
Haha...so what I have to do is wait for a few day and try again
Thanks for the advice
Google Fasfboot and ADB. Between the two of them, you can flash recovery, push & flash ROMs, etc. The Nexus 7 Toolkit makes Fasfboot & ADB commands pushbutton choices.
I'm not the lowest of the low, but I am the slowest of the slow.
Problem: USB driver failure for Nexus 4. The android composite USB driver loads. Portable device driver (MTP) does not.
I have the latest v7 Google USB drivers in the extras 4.2.2 SDK folder, and pointing the driver install to this folder has worked in the past. Now, I never get the portable device MTP to install. I have both windows 7 and windows 8 machines that used to recognize the phone. I suspect my phone USB firmware is corrupted ( or something else software related?), but don't know how to find or make a zip file I can flash via custom recovery to test my theory.
I've tried multiple USB cables, all which have worked in the past. Simultaneously, I can only charge at USB rate. This all started occurring a week ago.
Any recommendations?
LG-E960
A different Nexus 4 connects fine, mine has no response to USB. It will charge off the PC, but no adb device found, no fastboot device found, no portable device MTP. I think something is wrong with my USB firmware on the phone.
LG-E960
Are you sure usb fast charge is not on?
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
gee2012 said:
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
Click to expand...
Click to collapse
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
I too,, have tried to clear all old drivers and use the universal driver, but nothing works. I went through the tedious windows 8 advanced startup to allow unsigned drivers.
LG-E960
This sucks. I still cant resolve this, and 4.3 is coming. Maybe I'll try Ubuntu.
Sent from my Nexus 4 using Tapatalk 4 Beta
Still sucks
LG-E960, Tapatalk b4
Problem with Nexus 4
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
muzicfreako said:
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
Click to expand...
Click to collapse
Any updates about this?
I'm going through the same thing with my Nexus 4.
Adeelx said:
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Any updates about this?
I'm going through the same thing with my Nexus 4.
Click to expand...
Click to collapse
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
I still have the same problem as you.
LG-E960
Resolved
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
It was the same with my phone. Wasn't detected on other computers too.
Here's what led to the problem resolution (kinda):
1. Formatted /system, /data, /cache, and flashed CM 10.1.2: http://get.cm/get/jenkins/34261/cm-10.1.2-mako.zip
2. Restarted the phone, then I came upon this forum post which mentioned that Trickster MOD Kernel Settings should be used to test for fast charge.
3. To install Trickster Mod I had to have Play Store (and thus the GApps package), so I rebooted into recovery.
4. After flashing the GApps package and rebooting the phone got detected and I was back in business.
5. Immediately flashed the factory image JDQ39 (it was the one I had available at the time.
6. Received the 4.3 OTA update about an hour ago and the phone is again back to not functioning on USB.
(Worth mentioning here that before this fiasco started, I was on CM 10.1.2, linked above.)
-- Update --
Rebooted a few times, phone appears on USB now and is there consistently, I'm beginning to think this is a hardware issue but I cannot apply for a warranty claim until the problem is consistent enough.
I've been having the same problem the last few weeks. I am on v4.3 stock. The phone is not being detected in any computer i've tried. I've used several USB cords and none of them work. The phone can be charged, but only in USB mode, so charging is slow, even when using AC charger.
I think this problem was triggered by charging on a cheap car charger. The Nexus 7 also can get into this state from what i've been reading.
I haven't come across a fix yet, so I think I'm going to RMA it before the warranty runs out.. its to bad though, I think this is a software problem related to 4.3. I used a lot of cheap chargers without this problem coming up before upgrading to 4.3.
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that. I also replaced the USB flexible circuit card ($25 amazon) and nothing changed. I'm glad their are people like xDA member, enfrant, that provides zip files for updating the phone, else I'd be stuck with a non- updateable nexus 4, which would be a nightmare for a flash junkie.
LG-E960
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
MTP not detected Nexus4
jigarbond said:
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
Click to expand...
Click to collapse
Hi There, i faced same problem. No matter what i did, still my XP could not detect my Nexus 4 storage. ( I must have deleted all drivers..samsung..nexus..android..from my device Manager when trying to install Nexus driver with WUGs Nexus Toolkits.) .BEST solution.."Restore System " to the date when everything was running fine.....walla.........problem solved:good::good::good:
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much - it worked for me as well!
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
I apologise for potentially getting your hopes up, but I am in the exact same situation. I am very much interested in this thread.
Google 15 second adb drivers xda. You probably need to get adb and fastboot setup for the pc to recognize your device. In order to fix it you'll meet to use fastboot or adb commands
Sent from my Nexus 5 using XDA Free mobile app
honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
nicknc said:
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Going to try that now.
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Ihsahn_ said:
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Click to expand...
Click to collapse
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Ihsahn_ said:
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Click to expand...
Click to collapse
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not at the moment. I have had this appear in the past but this is the point I'm trying to get back to. Unfortunately I can't work out how to get it to appear here. My device is in the bootloader.
---------- Post added at 10:23 PM ---------- Previous post was at 10:13 PM ----------
Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
honorguard said:
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
Click to expand...
Click to collapse
Did you do a clean install?
Have you used a different USB cable? Some cables are charging-only, with no indication otherwise. Internally damaged cables can also turn into charging only cables. Ironically, I just replaced one hooked into my daughter's phone today that would only charge intermittently.
There is no reason that wiping partitions in recovery would prevent your phone from being recognized by your PC at all.
Try a clean install of the drivers on a fresh pc with a different cable.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
Ihsahn_ said:
[Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
Click to expand...
Click to collapse
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
nicknc said:
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
[/COLOR]
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
If it Works with that cable please give me a headsup
Verstuurd vanaf mijn ST25i met Tapatalk
Ihsahn_ said:
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
Click to expand...
Click to collapse
OK.
Sent from my Nexus 4 using Tapatalk
Well, I had similar issues when I bought this phone (coming from a HTC one s) connecting to fastboot.
What I did was:
Delete all drivers related to adb/fastboot/android (use a software to completely clean the files).
Booted my phone into fastboot mode.
Connect to PC and wait for windows to show the new hardware dialog.
Install the correct drivers (which i had downloaded and extracted) using the dialog box.
Profit.
Sent from my Nexus 4 using XDA Free mobile app
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
honorguard said:
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
Click to expand...
Click to collapse
Did you try on a different PC, installing the adb and fastboot drivers before connecting the phone for the first time?
Have you tried a different USB cable?
Sent from my Nexus 4 using Tapatalk
A brief update
I remembered I have a second Android phone knocking around. I plugged this in with one of the cables from earlier - perfect installation with all drivers, etc. This has further convinced me that the hardware of the USB port on the phone is the issue.
Thanks for all help - I'll update again if the hardware change works, or doesn't.
ok, ive installed a new windows and installed all the drivers and then i connected the phone.
Nothing.
i'm getting desperate here..
Hi!, I have a bricked Oneplus 2 so heres how it happened
My device was running oxygen os 3.0 with TWRP 3.0 and I decided to flash the resurrection remix ROM on my phone through twrp, and when I did flash it I think it gave me some error code, and then I rebooted my phone and now its stuck in a bootloop with no OS installed.
I tried going to TWRP and adb was not working and adb side load was not working, I went to fastboot and my computer wont detect my device through fastboot. I tried first aid kit and my phone was not being detected. I did try this with using 2 other computers running windows 10 and I tried it with a computer running Linux Mint. How ever when I check in Device Manager It shows "communications port (COM1) I tried updating that driver with the Oneplus 2 Qualcom drivers and it gave me a error code 10 and I tried installing an ADB interface driver to that to and I got the same error code 10. I also tried this method below with no luck.
"https://forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/"
Please help me and the community facing this problem, Thanks!
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
SirMika said:
I have a same problem. so any advice how to fix this is more than welcome. Except Firstaid kit gave back Recovery (twrp) which Oxygen 3.0 Beta removed etc, Now i have TWRP 2.8.7.0 and thats it. PC just dont find device so that i could transfer nesessary files
E: Does it matter is this Oneplus 2 recovery tool for A2001 or A2003? i just noticed that the one i downloaded, folder name is A2001_save_brick_mini
Click to expand...
Click to collapse
And does your phone get recognized by fast boot? because you were saying that you used first aid to get recovery, and first aid uses fastboot, because you will beable to fix your phone through fastboot
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
SirMika said:
yes, i just run fastboot commands and its unlocked etc but PC dont find OPT
---------- Post added at 10:27 AM ---------- Previous post was at 10:23 AM ----------
i just cant figure out how i transfer flashable zips in device to get oxygen or some decent rom
Click to expand...
Click to collapse
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
fahad999 said:
This might help you if your phone can be detected in fastboot:
http://www.androidsage.com/2016/03/12/restore-oneplus-2-full-stock-firmware/
It is a stock rom that you flash through fastboot
Click to expand...
Click to collapse
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
SirMika said:
Sure i can try but i dont expect to get this work anymore..at leat awhile. earlier i tried to sideload stock OxygenOS but it failed because it says i need adb v 1.0.32 or newer, and surprise surprise it dont work properly in Windows 10.
Click to expand...
Click to collapse
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
fahad999 said:
It should work if your phone is recognized by fastboot, you have to download stock rom fastboot file and extract it, then connect your phone to fastboot to pc, then in the stockrom file click the run-all.bat and your phone should work but the problem with my phone is that my phone is not being recognized by fastboot
Click to expand...
Click to collapse
not sure but i did similar procedure yesterday. see second post http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863 but i had no idea what i suppose to do..all i had was stock recovery..
in adb, running command fastboot device it shows my phone
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
it seems there is no way to fix it..my skills and knoledge aint high, but i´v done all by the book and nothing. it also goes in fastboot and twrp but thats it. i wish i could help you but were in a same boat
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Danm, that sucks. Later I may try using a virtual machine of Linux Mint on my computer and see if it will detect my phone in fastboot. And the sad thing is that this oneplus 2 is my only phone
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
fahad999 said:
Just to refresh, the problem that we are looking at is that your PC does not recognize our phone (Driver Problem)
So together we have to find a solution to this driver problem, so this is the main problem. I myself am running Windows 10
Click to expand...
Click to collapse
I think i need to get in my hands PC with Win7. i also came that conclusion the problem is Windows.
Oneplus drivers (/D) just keep pop-upping asking what todo, when selected nothing happens
EDIT: is it possible install proper softwares via USBstorage?
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Getsuga Tenshou said:
Guys, I am running a dual boot machine (windows 7 and 10) and on both there is not even a sign of detection. Same is happening on another laptop which runs on windows 7 too. Only phone boots to bootloader on connected (like a charger and nothing else).
Just before my fp stopped working. Last time it did, my usb type c cable also died. This time I don't know since I directly restored from twrp and did not connect it to my pc. There is a slight chance that our usb type c cables have malfunctioned (which is better than permanent brick). If you have any access/ friend with that cable please try it. If it works we might be in luck.
Note: SirMika, For you usb is working, you do not need to try this, did you try flashing revert files
Click to expand...
Click to collapse
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
fahad999 said:
I just got a Linux Mint virtual machine and still the phone is not being detected via ADB and Fastboot in Linux Mint, I think the only possible solution that we have is purchasing a USB Type C USB OTG and Side-loading a ROM on their and flashing it through recovery. But this possible solution is for people who still have access to their recovery and luckily I do.
Oxygen OS 3.0 Flashable ZIP: http://downloads.oneplus.net/2016-03-30/op2/OnePlus_2_OxygenOS_3.0_Beta/
USB TYPE C OTG: http://www.amazon.com/Adapter-RAVPo...qid=1463938874&sr=8-1&keywords=usb+type+c+otg
Click to expand...
Click to collapse
Update! I know why our phones are bricked! when we installed custom roms you wiped the phone right. I was reading that there was a new feature in android in which you wipe the phone with a password, the bootloader gets locked. So I believe that our devices now have a locked bootloader
fahad999 said:
I caint do any thing in twrp to, but I heard that there was a problem with twrp 3.0 that you caint transfer any files to pc, I think you might fix the problem by getting a usb type c usb otg and flashing the stock rom from there possibly. but I doint want to pay the price for it right now, but hopefully I will find a solution
Click to expand...
Click to collapse
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
Getsuga Tenshou said:
Guys I am stuck too, form oxygen os 3.0 I decided to restore my all old backup from twrp, and now my device is fried, recovery is not working too. I tried ton of ways, it can boot into fastboot, but my pc cannot detect it for some reason. In pc no fastboot devices. Nothing in ports. that 10second trick is also not working. Someone plz help
Click to expand...
Click to collapse
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Guihardrock said:
in twrp press format data (i mean format data no wipe data)...then yes...reboot and now your phone is well partitioned
after that (in orange twrp flash a oxygen oos 3.0 or h2os) or if you want to return to oos 2.x or any other custom rom use the LP steps in this forum....http://forum.xda-developers.com/oneplus-2/general/guide-helper-zips-to-switch-oos-3-0-oos-t3351253
---------- Post added at 10:26 PM ---------- Previous post was at 10:15 PM ----------
see in connected devices that there is one that has no name or isnt recogniced the press update driver and choose update from a list drivers not update from online then choose android device and then try every (google or clockworkmod driver i think that the one who work is android adb interface...then your computer should detect your phone if not search one the internet because every computer is different in terms of drivers i am telling you the way that i solve alway in mine (you can allways use that chinese program to restore your phone to oos 2.1.1)
Click to expand...
Click to collapse
Sorry to say that this is not working for me and I have no OS installed, I formatted data in twrp and typed yes and still I got no luck. My device is not being recognized by pc in twrp, I installed many drivers (Oneplus Drivers, Google USB Drivers, 15 Sec ADB & Fastboot Drivers, Universal ADB Drivers) Still I got no luck, and nothing shows up in device manager, I tried this in 2 Computers awwell.
i have unlocked bootloader, latest TWRP but no OS. instead zip fils it should be image. adb cant find phone but fast boot does
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Got a pic?
I have same thing
Same for me.
same here and cant get fastboot working also can flash twrp
Same here and it is also strange that I can't connect with my windows.
- the cmd: Fastboot devices
doesn't return the serial number.
---------- Post added at 03:10 PM ---------- Previous post was at 03:00 PM ----------
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
Did you already got an solution for your fastboot?
hmm wierd mine said the same
i can boot into fastboot
so i have allready unlocked oem an rooted
Unable to connect OnePlus 5 to windows 10, Fastboot reads phone as QC Reference Phone
I am having the same issue. Oneplus 5 is not being recognized as a valid USB device in windows 10.
In fast boot the device shows as a QC REFERENCE PHONE.
Please Help.....do i need a replacement ?
hounter17 said:
same here and cant get fastboot working also can flash twrp
Click to expand...
Click to collapse
didt u enable debug an oem in developer before u enter fastboot
Jonnyn93 said:
So I recently booted my Oneplus 5 into fastboot, just because.
And for some reason my device name is QC Reference Phone.... what the heck!
Has the factory QC phone somehow ended up being packed up and shipped out to me?
Can anyone else check their device and see if it says anything similar.
Click to expand...
Click to collapse
I am having the exact same issue...
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
When i connect my phone with te pc I hear te tone from recognizing or making contact ,but there is no drive visible as a folder in explorer. Ofcourse In die all settings in the developer options.
I'm missing the right driver. But I tried several.
Oneplus 5 showing up as Qualcomm HS-USB Diagnostics 900E
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Spider1996 said:
Got the same problem. After some reboots and USB Debugging on/off the device was shown as a drive in Windows. Then there was a driver in this Drive. Installed. Problem solved. My Phone is shown as QC Reference Phone but Everything working great yet. (Fastboot, Sideload, USB Debugging, File Transfer)
Click to expand...
Click to collapse
@Spider1996 :
This is my issue, any thoughts on that.
I got my OP5 today in the mail and the phone itself is working fine.
Although when connected to PC(Windows 10 64bit) it says "USB device not recognized". - Have already tried to set USB to MTP in developer Options.
And the device connected Reads "Qualcomm HS-USB Diagnostics 900E", did i receive a bricked Phone from the company ?
PLEASE HELP.
This was my Problem too. The normal USB Drivers from other devices are not working. Try to delete the driver in the device Manager from Windows and replug (with usb Debugging enabled and disabled) until a new drive is shown in Windows. After that install one of the .exe from this Drive. This helped me
---------- Post added at 04:45 PM ---------- Previous post was at 04:34 PM ----------
There are the Drivers from my Device Folder (Windows, Mac and Linux)
https://www.dropbox.com/s/nc7mgnj1k8kli92/OP5 Drivers.rar?dl=0
Try to use them for your OP5 in the device manager.
I think your device is not bricked/corrupted whatever
-fluffy- said:
didt u enable debug an oem in developer before u enter fastboot
Click to expand...
Click to collapse
yes i did it
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
hibby50 said:
I have the same thing. QC reference phone, no BL version or baseband version shown in fastboot mode. I also could not flash TWRP. I could fastboot reboot and see the device's serial # in fastboot but it wouldnt report the target size and errored out saying the file was too big for the target or something along those lines. I updated my ADB and fastboot EXEs just in case. What ended up working was switching USB ports on my laptop, despite the fact I use that one all the time and it was still recognized by fastboot. Hope this helps.
Click to expand...
Click to collapse
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
hounter17 said:
just the same happend to me, so u finally flash the recovery and root or nay??
y try all the usb ports and nothing...
Click to expand...
Click to collapse
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
hibby50 said:
I got the recovery to flash yes. It took me a while. It didn't stick because I didn't delete that file you have to delete but it flashed and booted into TWRP eventually.
Click to expand...
Click to collapse
so the only solution is to try in different usb plugs till it goes on someone?
wich file i must delete?
pritamk88 said:
I am having the exact same issue...
Click to expand...
Click to collapse
So maybe it isn't an issue, I'm not sure.
Oneplus replied "QC means qualcomm". So does this mean the phone is based off of a qualcomm reference board, and they just slapped it into a oneplus shell....