Database Users

cant bring up bootloader again

Hey guys,
So I'm attempting to root the nexus. I was following the instructions and put it into bootloader mode. I accidentally hit the power button while it said start at the top of the screen and it restarted. Now every time I power off and try to enter bootloarder mode it wont display the android guy. How can I bring that back up?
thanks,
Mike

try adb reboot-bootloader?

opticaldh said:
try adb reboot-bootloader?
Click to expand...
Click to collapse
my phone also isnt getting recognized by my computer now as well

hkdflip2 said:
my phone also isnt getting recognized by my computer now as well
Click to expand...
Click to collapse
try adb devices. If nothing shows up, then I think you should reinstall your driver. I used the Nexus Root Toolkit to install the driver.
After you uninstall the driver and plug in your device again, if Windows keeps installing autimatically the driver, then you should disable the Automatic Driver Update (or something named like that). I used to stuck with this Driver Update for 2 days. After I disable it, uninstall driver, then install again through Device Manager. Everything is OK now.

Cross check if USB debugging is enabled before connecting via adb. I have never used that Start option so don't know what it does apart from booting your phone.
---------- Post added at 04:23 AM ---------- Previous post was at 04:19 AM ----------
I reproduced the actions that got you the bug (selected Start from boot loader screen). But my boot loader still shows up.

Try adb bootloader
sent from my nexus 4; cat on lap, beer in hand

So i figured out most of it, im following the instructions from http://www.youtube.com/watch?v=g88PPZyvfDI however i get to the part about 11 1/2 minutes in where my phone should be rebooting once i put usb debugging on however i put it on and my phone doesn't restart and the nexus toolkit just says waiting for usb debugging to be enabled. Any suggestions

Unable to flash anything with fastboot

Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.

pfederighi said:
Hello.
I recently installed the 4.3 ota update. I knew I would have to reroot. After the update I have tried everything I can think of to flash a new recovery or bootloader or anything. All without success. Fastboot simply says "Sending...", the phone says "downloading..." and that's the end of it. They would both sit in that state forever if I let them.
I know I'm not alone on this issue. I have searched and searched without finding a solution. Does anyone know of one?
Thanks.
Click to expand...
Click to collapse
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?

gee2012 said:
1. Usb debugging enabled and bootloader unlocked?
2. Correct drivers installed, try these usb naked drivers for instance https://www.google.nl/url?sa=t&rct=...=RUlfH35SAJki_DdLfo8MeA&bvm=bv.51773540,d.Yms.
3. Used the original usb cable or tried another usb port?
4. If you type fastboot devices in fastboot mode do you see a serialnumber? The same for adb devices in adb mode?
Click to expand...
Click to collapse
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.

pfederighi said:
USB debugging is enabled.
I've tried the original USB cable and others. I've tried different USB ports.
adb works fine. Fastboot recognizes my phone and prints a serial number. Fastboot even works for locking/unlocking the boot loader.
There are no "drivers" in the Linux world. Should I find someone who has a Windows system and ask to use their computer?
Thanks.
Click to expand...
Click to collapse
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro

Solved
gee2012 said:
Yes, you may try that. I`am talking about a windows pc and never had an issue. I don`t have xperience with linux computers.Good luck bro
Click to expand...
Click to collapse
So. I solved the problem. I now feel like an idiot.
I plugged my phone into a Windows system and a nice notice popped up saying that my device could run faster if it was plugged into a USB 2.0 port. Then it dawned on me that only a few of the ports on my computer are 2.0 and that I had tried one of them previously but with an extension cable (because it's in the back and hard to reach). I unplugged the extension cable and plugged the USB cable directly into the port and all was well.
I hope that others who have had this issue find this useful.
Thank you for your help.

[Q] softbrick

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..

Oneplus 2 Bricked, Help!

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

How to use EDL Qualcomm Download cable

Hello,
I have a moto g4 plus with locked bootloader and no OS.
I also have a EDL cable with button, but when i try it my device manager only adds (uknown device) and some error, but i cannot install the qualcomm on that device.
The device automatically goes to fastboot when plugging in usb mode.

You need EDL drivers and also press the button for about 8 seconds just after plugging in the device.
---------- Post added at 12:36 AM ---------- Previous post was at 12:30 AM ----------
There's another way to get into EDL mode that was posted, although it's for a xiaomi device. It uses a modified fastboot.exe to get he device boot into EDL mode...
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718

Can you help me get the correct drivers?
Im affraid i have tried that method but it said booting to download mode.. and then (remote) command not found

http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/
Clicking on the download link will give a .7z file, having QDLoader in the filename... The page is in Turkish though, please translate it.

I have installed the 64 bit one and pressed 8 seconds but still the yellow triangle and uknown usb(unknown device device descriptor request failed)

On the old LG G2, you have to short a capacitor with tweezers to put it in this mode--maybe the same for Athene

HueyT said:
On the old LG G2, you have to short a capacitor with tweezers to put it in this mode--maybe the same for Athene
Click to expand...
Click to collapse
how to do that, i have my phone dissambled now.

codGmer said:
I have installed the 64 bit one and pressed 8 seconds but still the yellow triangle and uknown usb(unknown device device descriptor request failed)
Click to expand...
Click to collapse
my phone is completely dead, no display no fastboot nothing shows on pc. but when I tried to boot it to edl it gives the same error as you faced even though I have all the drivers. if you have found a way to fix this, share with me and Qualcomm flasher rom of moto g4 plus.

emsumit said:
my phone is completely dead, no display no fastboot nothing shows on pc. but when I tried to boot it to edl it gives the same error as you faced even though I have all the drivers. if you have found a way to fix this, share with me and Qualcomm flasher rom of moto g4 plus.
Click to expand...
Click to collapse
Connect it to PC, then go device managers and show me the ports. Then screenshot and give me

Ayan Uchiha Choudhury said:
Connect it to PC, then go device managers and show me the ports. Then screenshot and give me
Click to expand...
Click to collapse
i'm unable to upload the image but it was showing unknown device (device descriptor request failed)
i used edl cable

emsumit said:
i'm unable to upload the image but it was showing unknown device (device descriptor request failed)
i used edl cable
Click to expand...
Click to collapse
Use a normal cable. If it detects anything as Qualcomm, then you're safe

Ayan Uchiha Choudhury said:
Use a normal cable. If it detects anything as Qualcomm, then you're safe
Click to expand...
Click to collapse
With normal cable its shows nothing. It was showing q loader 9008 before giving it to service center, but they did something, it doesn't now.
And now i know it could've fixed with Qualcomm flasher back then.. but now it doesn't connect anymore without edl cable.

edl cable
emsumit said:
With normal cable its shows nothing. It was showing q loader 9008 before giving it to service center, but they did something, it doesn't now.
And now i know it could've fixed with Qualcomm flasher back then.. but now it doesn't connect anymore without edl cable.
Click to expand...
Click to collapse
adb reboot edl