Hi,
I am a local repair shop for phones, tablets, iDevices, laptops, pc's etc and I have a customer's phone here Galaxy Note 2 GT-N7105 that am pretty sure they have tried to flash it with some dodgy ROM and hard-bricked it. It is stuck in a boot loop so I can not boot into the android system to change anything in there. When I put it into download mode and connect to the PC (any PC/Laptop), windows says "The device has malfunctioned and windows does not recognize it". I have tried going into device manager on the PC and uninstalling the UNKNOWN DEVICE, then pressing "Scan for hardware changes' and letting windows try to install the drivers again but it immediately comes up "Driver was not successfully installed' and goes straight back to being an unknown device, so using the cable and Odin seems to not be an option. I also have the Samsung USB drivers installed.
This is what I have also tried installing from the SD card in recovery, however I am getting the 'E:signature verification failed' error on all of them:
~ Installing the firmware
~ Installing Clockwork Recovery
~ SuperSU v2.46 (this also gives 2 'Failed to verify whole-file signature' errors as well as the normal 'signature verification failed' error)
~ TWRP 2.8.7.0
I tried CWM because in my searching, I saw that if I install that, I can disable the signature verification, however I can not install that because I get the 'E:signature verification failed' error.
I am pretty much at an end as to what to do now.
Again to sum up:
~ Can't boot into Android system (stuck in boot loop)
~ Can't use the cable and PC (device not recognized/device malfunctioned/unknown device)
~ E:signature verification failed' error with anything I try to install from recovery mode
Does anyone have any ideas ?
Related
Following the video
youtube.com/watch?v=TrP-IBuAeN0
I tried installing custom ROM.
Everything went fine till flashing 'boot.img' using flash tool. After the flash tool showed me a successful message i unplugged my device from the laptop,but I didn't get the menu(recovery- shown in video) even after 30 min..now when i am connecting my device in fastboot mode to re-flash the device the usb driver is not being recognized
with error message in the ADBdriver details
"This device cannot start. (Code 10)
A request for the USB BOS descriptor failed"
I even tried installing the drivers provided in the SONY website, it is not getting updated .... its showing an error
plz help me in fixing drivers issue
thanks in advance
Windows 8 64-bit? Follow this: http://flashtool.net/disabledrivers.html
Ok so here is what happend:
I wanted to root my phone and I did the root fine with stumproot. Then i used autorec to flash the recovery. When i went to boot into recovery it got stuck in fastboot mode without download mode. I finanly got download mode but now I can't get the phone to show up device manager. I was having a issue with the ports but I finanly got that to show up but now all it shows up is communications port with a error.
The error is "Windows cannot determine the settings for this device. Consult the documentation that came with this device and use the Resource tab to set the configuration. (Code 34)"
When I plug in the phone to the computer in download mode it comes up with three options under other devices.
CDC ECM- The drivers for this device are not installed. (Code 28)
CDC Serial- The drivers for this device are not installed. (Code 28)
LGE Android Phone- The drivers for this device are not installed (Code 28)
I have tried uninstalling and re-installing the drivers. I have tried lg's official drivers and koushes universal adb drivers. Nothing seems to make it show up. Can someone please help me. I'm trying to do the restore to factory with tot files since i have the sprint variation. I'm not having anything other issues other than the phone not showing up properly in device manager! i have googled and googled and found nothing that helps. Thanks!
Greetings every one ..
I have a half dead Oneplus 3 Unlocked + Rooted
here is my problem
there is no OS in it and i flash TWRP many times via ADB and wont boot to it
and i tried to flash the stock recovery V2.0 and done successfully
the sideload mode Recognize my OP3 but when i try to flash the Oxygen Rom it Gives me cannot read
also i tried the Unbrick Tool when the device is connect it showing me Qualcomm hs-usb qdloader 9008
but when i power up the tool as administrator it showing me (no device)
see here : https://www.youtube.com/watch?v=BIbagVAXJJk
Thanks .
on the unbrick guide try method 2 but completley power off the device and count to 10 when holding the vol up button THEN plug the device in. i had that issue also. if you get errors or for some reason it dosnt show up again try on a diffrent pc it will work
Try method 2. BTW "cannot read" error has to do with faulty ADB drivers, get the platform ones
I did instal the right ADB drivers in fact
still no luck
The ones from platform tools? Since that "cannot read" error has nothing to do with your device. Have you tried renaming it? Rebooting your PC? Last one did wonders for me for some stupid reason.
Hi,
I also had this message of "can not read" in sideload mode, this problem often happens with Windows 10, so I used Windows 7 on another pc and it was OK.
I tried Windows 10 & 8.1 & 7 & XP
still The same problem
What if you flash Twrp and boot into it? Then u can adb push the filemm
I tried via fastboot and its done right
but when i reboot into the new TWRP recovery its stuck in the boot oneplus as same like the Video shown up
book an appointment with oneplus live chat so a service tec can fix it and if they ask if it was rooted say no
Hi,
If you access TWRP, install the Official Oneplus Recovery 4.0.2
In TWRP click "intaller" then choose "install image" and select the file you will have to copy to the phone in recovery mode.
Then restart in recovery mode, choose english, then "adb sideload mode"
From there you should be able to flash your phone with an official Nougat zip.
Do the under windows 7.
It is necessary to install the Oneplus USB drivers and ADB tool on your PC before any manipulation.
Finally I solved the problem
like i said B4 my phone wont boot into TWRP by any chance
i traid all the Officials TWRP one and they stuck on the boot image or power the phone off
i flashed a modified twrp (blu_spark 3.0.3-x) thanks for this beautiful smart man eng.stk if im not wrong
and thank you all for the help
i had similar issue...with several phones.. download Malwarebytes trial version and run it...i had a few stealth root tool kit viruses.causing my system to have a hiccup....
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.
So I was trying to get the beyond rom on my device, As I was currently flashing through Odin for the rom. I'm not sure what happened during the process of the update but odin shut off on its own and cut the update off. Now I have a message on my device saying " An error has occurred while updating the device software. Use the Emergency Recovery Function in the Smart Switch Mode. ".
I downloaded the smart switch software on my laptop and now the program is saying it's failing to connect to the device. I've reinstalled the samsung drivers tried many different cables not a single one has worked on my device and I've tried a different laptop too nothing has worked.
Really need some assistance on this.
Just flash stock rom with odin.
No need to panic, put yourself back to download mode, reflash firmware with odin
If you can't get it back to D/L mode (like it was in my case), maybe this helps. Mine is a S10+, though. YMMV for an S20xx
An error has occurred while updating the device software
Hi! So my phone is stuck with the "an error has occurred while updating the device software" and that screen only shows when i charge my phone with wall brick. If i try to connect my phone with usb to pc nothing happens. Even if i try to enter...
forum.xda-developers.com