Database Users

[Q] Nexus 4 mid root status "Offline"

I was running through the root video (http://www.youtube.com/watch?feature=player_embedded&v=g88PPZyvfDI) when I occurred an error at 16:40ish
it appears that I have unlocked my bootloader, then when it was beginning to root the device it installs a insecure boot rom, This appeared to go ok until I tried to enable debugging mode again.
so I enabled it and I got the message about the secure code and ticked the box and accepted that but I was unable to progress. I tried to switch the modes from PTP and MTP but still no success.
ive been running "adb devices" in a command prompt but I still cant get anything other than my serial code and "Offline". I tried installing several drivers but im unsuccessful with anything so far.
I had a HTC Desire Z before the nexus 4 and i rooted that ok but because that was a long time ago I redowloaded the android sdk and re-set up the environmental variables "path" but it hasnt changed anything as of yet...
does anyone have any suggestions as to what else I can try?
EDIT:
just got "device" to show up.. but my device was non responsive to the adb in fastboot? i received this error:
http://pastebin.com/JMvNpb7q
EDIT2:
maybe I dont have a insecure boot image... but the error above may be a reason?

Update your adb.exe tool its out of date that's way it says offline
From my BLACKED OUT N4

i solved the issue and it was a weird one but maybe it will help someone else in the future...
if you are pretty sure you have everything fine, try a different USB slot.
try not to use a USB slot from a USB card but instead directly on the motherboard.
for some reason my TOP USB allowed my device to be found in FASTBOOT
and my BOTTOM USB allowed my device to be found in USB DEBUGGING MODE
so all I had to do was time it right and quickly swap between the top and bottom USB devices in the "waiting" phases.
It was quite a struggle but I managed to get there in the end!
final question... what rom is now on my device? what is the rom that ends up on your device at the end? is it a stock rom or a insecure rom or something else?
Thanks again for everyone who helped =)

[RESOLVED] Need Driver Help getting bootlooped phone to show up in Devices

My son attempted a flash without reading through much.. he had the newest firmware and now it won't boot into anything but TWRP and what i think is download mode (it just shows the LG logo, but I do have adb access). The issue is in these modes, I can't get windows to recognize the device to be able to assign it to port number 41. I can manually pick a driver, but then it only shows up as that driver, not the phone on the devices location in Windows. .. So, the LGFlashtool doesn't recognize it and nothing works. I've even tried assigning it the LGE Android Platform USB Serial port driver, set to port 41 and it still won't work.
Any suggestions? Is there another method from the LGflashtool one detailed? Thank you for any advice! (this experience is enough punishment and a great lesson for my son to learn to READ and follow instructions).
This is for the AT&T model.

FIXED. Through multiple attempts and multiple threads, I ran into this thread:
http://forum.xda-developers.com/showthread.php?t=2451696
I did it through TWRP Terminal. Upon rebooting, I'd see the LG logo super fast and then nothing.. I held down power for some time, then the up volume, plugged in and I HAD DOWNLOAD MODE! whew.
From here, all is well, it shows up on devices and I can push the factory firmware. -Yay for google, yay for XDA and all the resources these forums have pooled together!.
(thanks)

Return to stock has gone a bit Pete Tong - help!

I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.

crank_girl said:
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
Click to expand...
Click to collapse
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
p.s. can you actually flash something with adb??

Lots of people seem to confuse adb with fastboot. Is that what you want to use?

Thanks both for responding. I think I've gotten myself a bit confused over what is supposed to be working at any given time.
I can get the phone into EDL mode and fastboot. Fastboot devices finds my phone. MiFlash doesn't find my phone despite having the QHSUSB driver installed.
What's the easiest way to return my phone to stock? I have MiFlash and Axon7toolkit installed.
Cheers!

Choose an username... said:
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
Click to expand...
Click to collapse
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
Click to expand...
Click to collapse
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!

You have the wrong drivers.

crank_girl said:
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
Click to expand...
Click to collapse
I tried to post yesterday and for some reason the XDA app didn't post the answer... Basically this:
-Forget ADB and that program that you're using to see the devices. EDL uses COM protocol, has nothing to do with adb at all.
-Go to Device manager and find where QUSB_BULK is. If it is in Unknown devices, either right click on it and try to install the driver automatically, or search for "Qualcomm HS-USB QDLoader 9008 drivers", download, install and try to install it on QUSB_BULK. If it is in an "USB devices" tab or on Ports "COM & LPT" simply right click, Uninstall device, Delete driver software for this device

I've done that several times over but miflash still isn't detecting it.

crank_girl said:
I've done that several times over but miflash still isn't detecting it.
Click to expand...
Click to collapse
all right. Try EDL Tool by djkuz. I don't know if the same packages work but just download another edl package

It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.

crank_girl said:
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
Click to expand...
Click to collapse
How come? The right driver literally appears on the last photo...

Choose an username... said:
How come? The right driver literally appears on the last photo...
Click to expand...
Click to collapse
I know, right? It's a mystery. Never had this happen before.

crank_girl said:
I know, right? It's a mystery. Never had this happen before.
Click to expand...
Click to collapse
If it doesn't work try MiFlash on another PC, it sometimes happens that it won't detect it by any means

Broken EDL mode

Hello everyone. I'm stuck here on strange bug: when device rebooted to EDL it gives "unknown usb device (device descriptor request failed)". Tryed on desktop Win10, worked before but not now. Connected to laptop Win7, never attached device before, gave me same error. So I assume I broked edl some way? Is it possible to recover?

EDIT: Make sure you install them, especially the Qualcomm driver while Driver Signature Mode is disabled.
If you haven't already, try installing the Qualcomm USB Drivers. You can follow the simple guide here:
https://bit.ly/2EdPjlm
Afterward, reboot and try again.

KwesiJnr said:
EDIT: Make sure you install them, especially the Qualcomm driver while Driver Signature Mode is disabled.
If you haven't already, try installing the Qualcomm USB Drivers. You can follow the simple guide here:
https://bit.ly/2EdPjlm
Afterward, reboot and try again.
Click to expand...
Click to collapse
QC drivers already installed, and EDL mode worked fine week ago - when I flashed TWRP.

Solved. There was two problems:
1) Zadig WinUSB driver, which prevents phone from normal EDL work
2) When you reboot phone in EDL mode and unplug it, you get 43 error 100% no matter what. All manipulations with device and it's drivers must be made right after reboot to EDL without unplugging

@KwesiJnr: There is no need to disable Driver Signature Enforcement in Windows. I have flashed with MiFlash quite a bit on Windows 10, never had to disable it.
@SionGrey: Just follow the instructions in the first couple of paragraphs of https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514. You don't need to flash the packages linked there. The version of MiFlash that @jcadduono provides is sufficient for flashing Marshmallow/Nougat EDL packages. In you are flashing an Oreo EDL then I think you will need the version of MiFlash from December 2016 (Google it), I never had any luck with @jcadduono's version when flashing Oreo. The installer is in another language but the program runs in English. Zadig's WinUSB drivers will definitely interfere with MiFlash, uninstall them from Device Management before installing the Qualcomm drivers. I never got a failure at 43%. You can restart EDL mode on the phone without unplugging, just hold Volume Up + Volume Down + Power (in that order) until you see a red light blink in the upper left corner of the phone. Then just refresh in MiFlash.

@AnonVendetta
You got wrong idea. There was no any 43% flashing error. I posted above that I solved my problem. It was "unknown usb device (device descriptor request failed)" in device manager, and it happened because phone MUST be plugged-in during reboot to EDL mode. No un-plugging and re-plugging when phone is already in EDL

SionGrey said:
@AnonVendetta
You got wrong idea. There was no any 43% flashing error. I posted above that I solved my problem. It was "unknown usb device (device descriptor request failed)" in device manager, and it happened because phone MUST be plugged-in during reboot to EDL mode. No un-plugging and re-plugging when phone is already in EDL
Click to expand...
Click to collapse
Thanks man, you helped me a lot - appreciate it. I didn't plug in the phone to my computer at the right time. I got it now.

I noticed someone had quoted me recently. But I can't be of any help. It's been over a year since my Axon 7 was stolen. I've moved on to a better device. The A7 was still a pretty good phone though.

Need help - OP 6t not recognized in fastboot

Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.

Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.

I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.

And just to be certain, do you have USB Debugging enabled in developer options?

Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.

I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.

Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.

lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now

lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com