Related
Edit: I had switched to a different (charge-only) cable halfway through and not realized it. Switched back and the phone was recognized again.
Steps:
I unlocked my bootloader with Wug's toolkit.
I installed the zips that it asked me to (that it put on my SD card).
I updated SuperSU
I got a notice to update the SuperSU binary.
SuperSU binary won't install via Play.
Tried to install via TWRP and recovery isn't twrp, seems to be stock recovery (thought I installed it, maybe not)
Now the toolkit won't recognize my device. neither will windows. It gives me the USB noise but won't show the device in the folder list and defaults to USB for Charging. I can change it but it doesn't make it recognizable.
I'm trying ot back out and try again but the toolkit says it finds the device but that it's listed as "offline". When I toggle the USB debugging, it doesn't ask me to fingerprint my computer.
When I try the "soft brick" option to flash from the bootloader, the script reports a failure "data transfer failure (unknown error)", then says "rebooting into bootloader..." and does nothing else BUT my phone's bootloader still says "downloading..." When I reboot, the script throws another failure and says "waiting for device". when I bootload into it again and connect, the script throws more failures.
I've been on this for 4 hours, getting pretty fatigued (through the night on a weekend when family is visiting. yes, I'm an idiot for trying this procedure but the 5 went so smoothly I was optimistic).
try reinstalling the drivers. also the OEM-lock option in the dev-settings may help bringing you back to step one.
I was halfway through installing the drivers when I quit for sleep last night.
I'm using the LG-Mobile-Driver_v3.14.1.exe package, and the installer says it installed successfully, but windows says that MTP and PCI Simple Communications Controller had "No driver found", so the device doesn't show up in my drive list and wugfresh won't detect it.
I've removed all Google, LG, MTP, and Nexus drivers in USBDeview, but can't seem to figure this out.
I was able to get the drivers installed on my wife's system, so I'll open another thread about this if I can't get them to work.
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
oubravs2b said:
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
Click to expand...
Click to collapse
so, the reason my computer stopped recognizing the phone was that I switched to a charge-only cable without realizing it. Switched back and the phone recognized fine.
The weird thing is, the charge-only cable worked fine for data xfer on my wife's system.
So I bricked my FireTV last night during an upgrade to rbox's latest fw...
Short story is, it got to the Amazon app optimization after the flash fine so I went back to the computer to start working on the second box while it did it's thing. I mistakenly sent the reboot recovery command to the box that was optimizing itself. I didn't notice I was sending the command to the wrong box until I saw that my second unit was not rebooting to recovery.
Needless to say, it now no longer boots to any logos, and does not turn on at all (no light when plugged in, not even for a split second).
What are my options to unbrick? I'm taking a guess that the SD reader/eMMC method is the only one. If so, is it possible to retain an unlocked bootloader/etc with this method? I've read you'd lose it, but I'm not familiar.
If someone could point me in the right direction that'd be awesome. I tried google but it's filled with loads of outdated or unrelated information (mostly debricking if the amazon logo appears) or info from when the initial hardware root method came out.
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
sparkd said:
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
Click to expand...
Click to collapse
At least you can connect with USB! I get no connection at all to the pc with a A-A cable.
I would suggest for you trying to get the timing right and initiate the fastboot commands right when the device is recognized.
You people need to reflash your partitions, this happened to me months ago. Can't search for the thread now, I think the steps were in the FireTV1 5.0.5.1 thread...
my device bootloader is not unlocked. I was following the steps to downgrade firmware in an attempt to unlock the bootloader.
in Win7 Control Panel > System > Device Manager the FireTV1 appears as QHSUSB_DLOAD - i think I am also going to try this ... http://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
thanks for the advice ldeveraux, ill take a look.
Ordered the eMMC adapter from exploiteers. This is likely the only way I'll be able to fix this as the USB A-A cable is not detecting my FTV
Well I managed to get my device talking with an A-A USB cable while waiting for my eMMC adapter. So now to flash
Is there a way to recover with this method without losing the ability to unlock the bootloader? Bootloader was unlocked prior to the brick.
UPDATE: annnddd it didn't work for me. Was getting I/O errors while writing and now the device no longer gives me partitions in /dev/. The usb device still shows up however.
how did you get the /dev/ partition to appear ?
which linux distro did you download / install as I cannot see any partitions on my device
did you use the linux in a VM ? & did you have the windows drivers installed beforehand ?
thanks
Yesterday I decided to install ClockworkMod. I was running 6.0.0 Marshmallow
I unlocked my bootloader no problem. I decided to root before I flashed the rom. I booted into TWRP using adb, made a nandroid backup, and flashed stock-20a-rooted.zip (I was following this guide). It worked! I used a rootchecker app to ensure I had a good root. Then I went to boot into TWRP to install ClockworkMod. I turned off my phone and did the volume down + power thing, but I got the LG hard factory reset screen. So I decided to use ADB instead and rebooted my phone. However, when I tried to use adb, my device was listed as "unauthorized", and I haven't been able to use adb since! Here's what I tried (but not necessarily in this order):
Using the LG hard factory reset. Nothing changed.
clearing adbkey file on my computer. Nothing changed.
using a different computer with fresh adb and driver install. Nothing changed.
rebooting both PCs. No dice.
tried mtp and ptp on device. Neither worked. Device was not recognized on MTP (used to be recognized by adb when it was on mtp.) device was recognized on ptp, but it was listed as "unauthorized"
tried to revoke usb debugging in settings on device. That option wasn't listed in developer options.
tried to clear adbkey on device and found out that my device still hadn't generated an adbkey file!
throughout this whole time, whenever I plugged in my device, the NSA fingerprint dialog box DID NOT APPEAR.
Questions, thoughts on potential solutions:
can I somehow unroot or go back to stock? I heard we can't do this anymore because it bricks our phones....
I feel like this has something to do with how my device never created an adbkeys file.
SOLUTION
I have been working on this today and I found a solution. I had read that downgrading/unrooting bricks our devices, and so I had ruled it out as an option. After further research I found that we can revert to stock without downgrading and avoid a brick. Since I have an H811 on 20o, I found firmware here and flashed it using LGUP, which you can find here. I suggest using this link to learn how to flash the firmware. After that, ADB worked fine and the NSA fingerprint dialog once again showed up on my device when I ran ADB. Good luck to any of you with the same problem!!! Reply if you need help.
Tl;dr: DM-VERITY error after upgrading, SIM card not recognized. Can't get fastboot to work to try out a solution. Everything is going to ****.
So... this one's a doozy.
I tried to install the update by dropping it onto my phone and using TWRP to install it, which I ended up having to update. After I updated, I get a brief second popup screen when I reboot telling me that there is an invalid DM-VERITY (it only pops up for a second). When the phone loads, it doesn't recognize SIMs.
I did some research and it looks like the issue can be fixed by flashing the stock recovery. So I go to flash the stock recovery, which requires the usage of fastboot. Which I always have problems with.
Sure enough, adb recognizes my device but fastboot doesn't. I have all the drivers downloaded, so I go check on my device in device manager. For some reason, it's always listed under "Portable Devices" no matter what I do... no matter whether I enable/disable USB debugging, MTP/PTP/Charging, etc. I was under the impression that a device not being recognized by fastboot meant that you had to go find it under "other devices" and manually update the drivers. However, the only options here are ADB drivers, not bootloader ones.
So I did more research. Turns out that Windows 10 is ****ty and you have to disable secure boot to install unsigned drivers. So I went into my BIOS, disabled it, booted into safe mode, reinstalled the drivers, and... nothing.
So I'm basically where I started and for the first time in a while, I have no clue what to do. Nothing's working. I even tried to load an older version of OxygenOS and install it with TWRP (sideloading didn't work), which didn't work. I'm totally stuck and I have no idea what to do.
If you don't care about your data, just use the unbrick guide method 2. Don't know about the first one, I have never used that. That will get you to a like new phone. You could even get 4.0.3 version, using the newer unbrick toolkit.
Windows 10 x64 isn't that sh**y. I've never had issues with the drivers, and they all install automatically (fastboot, adb, unbrick tool). They all work with 4 phones without any issues: OP3, Nexus 5X, Nexus 5, Nexus 4.
True, I had just unbrick my op3 2 days back by method 2 .
Well this was wild
So I did try to unbrick and got the Sahara communication error.
But I ended up fixing my problem! Someone on Reddit correctly pointed out that the dm-verity screen often exists simply as a result of unlocking the bootloader. I was assuming that one symptom caused the other. They suggested just reflashing OnePlus's 4.1.3 full ROM. I did it exactly the same way as I had when I got the error (with TWRP) and... it worked!
I'm astounded. My phone wouldn't work with fastboot, wasn't recognized by the unbrick toolkit, and had a host of other issues. I did 7 hours of work on it and the solution ended up being that I just needed to reinstall the OS (again). My hypothesis is that there was some hidden issue that resulted in part of the firmware being incorrectly updated, and when I wiped my device as part of my troubleshooting process it was ready to be reflashed with the OS.
Thank you guys so much anyway!
Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.