My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.
Related
My device was rooted with the old method and I accidentally did an OTA update, so it's bricked right now.
I've tried to flash the pre-rooted system image, but I can't do that if my phone doesn't show up on fastboot, adb or device manager. I've tried connecting to every USB port, in the bootloader, the recovery as well as the normal boot screen (which the phone can't get past).
I've also tried installing the Intel Android drivers through the .exe file, I would do it manually but I don't think I can do that unless Device Manager detects my phone in the first place.
Is there something I'm missing here?
aloy99 said:
My device was rooted with the old method and I accidentally did an OTA update, so it's bricked right now.
I've tried to flash the pre-rooted system image, but I can't do that if my phone doesn't show up on fastboot, adb or device manager. I've tried connecting to every USB port, in the bootloader, the recovery as well as the normal boot screen (which the phone can't get past).
I've also tried installing the Intel Android drivers through the .exe file, I would do it manually but I don't think I can do that unless Device Manager detects my phone in the first place.
Is there something I'm missing here?
Click to expand...
Click to collapse
i'm not sure this link can help you but better trying than do nothing, hope our phone back to normal again
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Phone works normally except it's undetected by pc. It boots itself, boots to twpr (3.0.2.-3) or fastboot. I flashed various roms, after some time detected that couldn't access storage, but didn't actually care - thought it's something with those beta stage roms.
Decided to flash original rom, but neither adb or fastbot are working. Actually, windows even won't detect device. At all. No signal that i connected cable. The phone meanwhile keeps charging. Tried to connect at manjaro linux with same luck - adb devices or fastboot devices won't detect anything.
Formated data in TWRP (thought, that it was encryption i used fault), but no luck. Now i could load to TWRP, bootloader. Is there any possible ways to get phone back to reality before me trying LGUP scary thing?
updated. could that be somehow damaged cable fault?? i checked with my wife's phone (same model) and it's not detected either. it's a nilkin cable, worked perfectly before. could that be possible somehow to damage a cable that it would only charge phone? or i bricked both nexuses?
updated 2. oh my, LGUP also detects nothing. this seems like a bricked phone.
updated. faulty cable.
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!
After rooting the device (n 5110) and installing a custom recovery I had to flash it back to stock (which I had to download because I somehow didn't have it backup from before) in order to get an OTA update. I used Odin to flash back to stock and AFAICT everything seems fine. After the update I don't see what was different, the android system was 4.4.2 before the update, but I was prompted to update so I did. Now am looking to reflash the custom recovery and install a custom rom. I didn't have a custom ROM on it before, just custom recovery and root.
So I'm trying to flash TWRP back on it so I can flash a custom ROM. I recall flashing TWRP and rooting was pretty problematic the first time and I don't recall what I did to get it to work.
This time I've tried following the instructions for flashing lineage os. Running a windows machine. If the tablet is hooked up booted into system windows sees it and I can transfer files to and from the tablet via explorer, both the internal memory and sdcard, if that matters, so I know the cable and usb port are functional. I just flashed stock yesterday, so I guess they would be.
I've enabled USB debugging and checked the box to remember the computer. When it's in system, if I type "adb devices" it reports a device, it did say "unauthorized" before I got the prompt and checked the box to remember my computer, after I got the prompt it just listed the device and it seemed fine. If I kill the adb server and disconnect the tablet and reboot tablet into system it's remembering my computer and granting access. Adb reports the device.
I've gone to the samsung site and downloaded the drivers for the tablet and installed them. I've tried updating them both through device manager and zadig that comes with heimdall.. I've tried all three usb ports and three different usb cables.
However whenever I boot into download mode, and type "adb devices" I get blank. I've tried leaving the device plugged in, unplugging and rebooting, then plugging in, I've tried disconnecting and connecting the device at various times, stopping and starting adb, waiting 30 seconds or so before hitting volume up to confirm going into download mode. Adb devices just pulls up blank.
Odin doesn't light up or say anything when I boot it up into download mode, heimdall throws errors when I try to do anything. I have odin 3.09 so I don't see this "AP" button people mention, I think tha'ts supposed to be "PDA" on my current version? I dunno, if I got it to work I'm not sure how I would flash TWRP with it.
If I type "heimdall print-pit", which is part of the instructions for lineage os, I get the following error.
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The parameter is incorrect.
ERROR: Failed to send data!Releasing device interface...
I dunno, I have to be missing something, but I don't know what.
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.