Related
Hi there,
I`ve got the following Problem:
My One is not detected properly in fastboot mode, adb works like a charm (all cmds working)
In fastboot mode windows says that the device cannot be started (code 10) and cmd cannot find the device and it`s also not charging in fastboot...
I`m using Windows 8 and I know that there are problems with driver signatures, so I disabled the checks through advanced boot, uninstalled all drivers and reinstalled them (the strange thing is, it worked like a charm with my HOX)
After that still the same issues... Then I uninnstalled the HTC drivers and tried the drivers from Google SDK and after that the drivers from PDAnet but nothing helped...
Then I read that there are Problems with USB3.0 and fastboot but I only got USB3.0. So I tried different USB ports and reconnected many times (about 30 times) and maybe the phone says "fastboot USB" but in cmd it`s still not detected...
As I said before with my HOX it worked like a charm... (also Win8 and USB3.0)
Any ideas?
Thanks for your help!
togx
Try disabling Fastboot in the Power Settings.
I tried it again with fastboot disabled but it still doesn`t work... :/
same problem here....
envoy_467 said:
same problem here....
Click to expand...
Click to collapse
hey envoy_467,
I found a solution for this issue:
It seems that microsoft´s own driver for the Intel USB3.0-Host breaks the support for several devices. You can install the Intel drivers for Win7 on Win8 (search google: Windows 8 and Intel USB3.0 host controller there should be a link to plugable. I´m not able to post links cause I don´t have enough posts...) but it only works with the Intel host.
Hope it will help you too!
greetz,
togx
usb device not recognized
I'm having a similar problem using windows 8, but I tried both my usb 2.0 and 3.0 ports but results in same problem. I have a t-mobile HTC One S (JB 4.1.1). Everytime I try to do the fastboot to get my token id my pc tells me my usb device is not recognized. Does anyone have any suggestions? Thanks in advance!
Try THIS
Sorry to bump this thread, but it's better than creating a new one.
Anyway, I have the same issue as the others here: fastboot won't work at all.
Btw, I've tried all possible solutions but installing the intel driver isn't possible due to a limitation on Windows + Intel 8 Series.
Windows 8, Intel 4th generation processor (8 Series/220) on a Gigabyte GA-Z87N-WIFI.
USB eXtensible Host Controller driver by Microsoft can't be modified to work with the Intel 8 Series driver. When trying to install it it says that my PC doesn't have the requirements to install the program (driver can be found here -- 8 Series ONLY!!) probably because I'm on Windows 8 (no, setting the app to run with Win7 compatibility mode doesn't work either).
Using Naked Driver 0.72..
Has anyone tried with a virtual machine? Maybe I could install Ubuntu on a VM to test it when I get the time.
Any other ideas?
VM doesn't work.. Since Windows won't recognize the phone while on fastboot that means that the VM Linux won't find the devide either.
LiveUSB won't install the android SDK either.. I'm stuck..
FIXED, kinda.. Workaround on Linux.
More info:
Just did it..
But not on Windows..
I've created a LiveUSB from Ubuntu 12.04 using the "Universal USB Installer" from: http://www.pendrivelinux.com/downloads/
When creating the LiveUSB I've created with 4gb (4096mb) of free space on a 16gb flash drive just in case, but you can make it work with a 4gb flash drive.
Then I installed the Android SDK.
Then I was able to use fastboot to change the CID to 11111111.. Working great.. Now let's download the developer ruu..
Tutorial used to install the SDK: http://askubuntu.com/questions/318246/complete-installation-guide-for-android-sdk-on-ubuntu
To run all commands faster, just type "sudo su" before starting. After that type "apt-get -f install" to clean everything.
Remember: To install anything the tutorial asks you have to use the command "apt-get install name-of-package", where the name is the item the tutorial says.
Go up to Step 4.
Download and Unzip/extract the AndroidSDK to the desktop (just the SDK, you don't need the full bundle).
Go to the unzipped folder, go to the Tools folder, double click "android", run in terminal, install the SDK and the TOOLS.
When finished, open a terminal window, navigate to your unzipped folder, than navigate to platform-tools and use the command "./adb" and "./fastboot" to work your magic..
Edit: Still not able to install the RUU..
At least now I have the phone ready.. Just have to find a new PC to install the RUU..
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Raistlin1158 said:
Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom.
Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Click to expand...
Click to collapse
Thanks for the quick reply.I did that and it was set to mtp + adb...
When I then connected it it tried installing the driver and I got..
Driver device software was not installed.
Please consult with your device manufacturer for assistance getting this device installed
MTP USB Device X Failed
I tried updating the MTP drivers again from device manager but this time got
Windows encountered a problem installing the driver software for your device
Windows found driver software for your device but encountered an error while attempting to install it.
SAMSUNG Mobile MPT Device
This device cannot start (code 10)
From what I'm reading it's a computer error not the phone. Can anyone suggest a new set of drivers to download (that doesnt involve Kies) as I've had issues with picking up harmful software from random sites when I've been struggling to find drivers.
I tried using the suggestion at the bottom of here r.e.Portable Devices and deleting the Upperfilters string Link but also to no avail.
Oh, and yes I've tried different ports and cables.
Well that's me done for the evening! I've tried everything mentioned in this thread including updating java and windows media player and all the afformentioned stuff but still no dice.
Could it be the actual drivers or a random windows 7 setting that I haven't yet tweaked since my clean install of windows??
http://d-h.st/YpV
Here are the correct drivers, install then reboot your pc.
Raistlin1158 said:
Go here for drivers.
---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------
http://d-h.st/YpV
Here sre the correct drivers, install then reboot your pc.
Click to expand...
Click to collapse
Sorry,I know I'm tired but I can't see a link on your post...
Highlighted in red
The newer drivers don't really wwork with the 9305 so find some older drivers. That works for me
Sent from my GT-I9305 using xda app-developers app
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
woldranger said:
Thanks for the tip.any suggestions as to where I can download these older drivers? I'll try the previously mentioned ones first, but I'm starting to think it might be the drivers themselves
Click to expand...
Click to collapse
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
Cheers, yeah, I was going to try them but I wasn't at my pc at the time I wrote that. I've downloaded the exe package but now it seems there are still drivers to uninstall - I uninstalled the drivers through device manager and went into my C drive and removed the SAMSUNG folder with the USB drivers in it. I'll restart the pc and hope that helps with the removal....
woldranger said:
I've added a few apps to my S3 and altered a few things on my PC and now I can't connect via mtp or ptp. It goes through the usual "installing drivers" and then fails. I've tried pulling the battery and removing the sim and micro sd card then putting everything back. Tried it without the card (currently having to transfer files via a card reader so - at least the card's fine) but to no avail.
I've had a go at uninstalling the drivers through the device manager, rebooting and scanning for hardware changes. I've tried downloading the drivers without kies but it didnt work out (I cant remember the site or the url, but ended up with the following file SAMSUNG_USB_Driver_for_Mobile_Phones) It didn't auto install but even when I tried to point Windows to the folder on my C drive, nothing.
I've spent a couple of hours trawling the net including on here and tried all sorts.
I'm rooted, using the stock 4.1.2 ROM with Windows 7.
I can't use Kies as when it was installed the first time it wrecked all my Synctoy sync's so I really could do with another option please guys.
Click to expand...
Click to collapse
Having the same problem. but I am on 4.3 rom using carbon rom a few days then transferred to pac man rom. My cellphone is not detected in my computer but it is being detected in the safely remove usb options. I tried to use a usb otg cable and a flash disk. No notification is seen on my phone but I can access the files on the flash disk (using usb otg cable) in the file manager. Tried the *#7284# but error occurs and says connection problem or invalid MMI code. I found that MTP udb device says failed
Raistlin1158 said:
The ones I posted work fine on my 9305 so you shouldn't have any issues and as you can see from the site they are nearly a year old.
Try them what have you got to loose, if they don't work you are no worse off
Click to expand...
Click to collapse
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
woldranger said:
It made no difference whatsoever. I used a utility to check for an remove the samsung drivers (USBDeview) as well as uninstalling through device manager and removing with windows "products and features" but even then, when I tried installing the new drivers it mentioned previous drivers. I restarted after each stage of the process.
I've even tried connecting it in download mode and it shows in device manager.
Could there be some remnant of the software I used to root that phone that might be causing the issue??
I'm due to leave the country in 5 days and have loads of things to sort (also have a family member going into hospital for major surgery tomorrow) so I can't just devote all my time to this - but I need to at least know that it's not the phone (I dont have another win 7 computer to try it on).
Click to expand...
Click to collapse
Just got the same problem. But my problem is already solved. Just flash a new rom. In my instance, I flash ripper rom
So I've got a 3T which currently has no OS installed, just the TWRP3.2.3-0. The problem is that every time I connect the phone to the PC, the PC will only recognise the phone as Unknown USB device (Device Descriptor Request Failed). Due to this I cannot use adb to transfer files to the phone or transfer files directly to the internal storage.
I have tried using Minimal adb but device isn't found, tried different USB ports and cables too. For some reason the recovery does not read devices attached to OTG as I have also tried to transfer files using this method.
Any suggestions as to what I can do to make my PC recognise this device? Thanks
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Hayatzada said:
first of all check your usb cable then use this op3/t tool
Click to expand...
Click to collapse
device isn't found, tried different USB ports and cables too
Click to expand...
Click to collapse
So yeah.
@op USB port in the phone is damaged
Hayatzada said:
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Click to expand...
Click to collapse
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
J-_-M-_-C said:
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
Click to expand...
Click to collapse
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Hayatzada said:
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Click to expand...
Click to collapse
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
J-_-M-_-C said:
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Click to expand...
Click to collapse
please please please check your cable
johnybravo.1981 said:
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
Click to expand...
Click to collapse
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
i have the exact same problem as u my friend i had that problem so i just sideloaded my stock rom and searching for a method to fix this if u find a way to make the device recognised in twrp pls let me know
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
johnybravo.1981 said:
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
Click to expand...
Click to collapse
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
J-_-M-_-C said:
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
Click to expand...
Click to collapse
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
J-_-M-_-C said:
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
Click to expand...
Click to collapse
which method do you try? i suggest full method, first one didn't worked for me .
Hayatzada said:
which method do you try? i suggest full method, first one didn't worked for me .
Click to expand...
Click to collapse
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
J-_-M-_-C said:
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
Click to expand...
Click to collapse
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Hayatzada said:
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Click to expand...
Click to collapse
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
J-_-M-_-C said:
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
Click to expand...
Click to collapse
now you should go for a hardware repair of Type C port
Hayatzada said:
now you should go for a hardware repair of Type C port
Click to expand...
Click to collapse
I already said that at the beginning.
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard
Hello!
2 pcs P20 Pro (now servicing). Tested 10 and 9 version, not read OTG (in system or in recovery).
Now offline (not PC) update from SD available only... this phone not support SD-Card! Only OTG-SD.
-Attached 3 other USB-OTG converter cable (1pcs new, 1pcs 20x used)
-Attached pendrive (exFAT, FAT32, NTFS)
-Attached SD (exFAT, FAT32) in Kingston USB-SD converter
Pendrive LED not on: not readed.
Tested OTG cable to other USB device, 5V ok, Data line voltage ok: USB all 4 pin ok!
Tested OTG cables other older droid 5.1 phone, all working, SD readed with converter, pendrive readed correctly.
One P20 Pro bricked. Bootloader locked, fastboot mode available only (screen blank), Multi-Tool flasher/unbricker "stock service flash" downloaded to phone and failed (no write permission). Hisuite not support this phone recovery. No other method to unbrick, only SD-update. How to working this port?
Live system not read OTG and bricked system not read OTG.
Live system developer mode settings (*#*#2846579#*#*) changed to default, Manufactture, Hisuite, same. Developer software upgrade: 1. Memory card, 2. APK standalone, not available OTG/USB. Connected to PC: Photo mode, File mode and Charging mode available only (not available reverse charge).
USB port measurement: not powered live system, booting, recovery "update OTG mode" not powered the USB port!
1 phone= inside cable USB to mainboard bad? 2 phone= 2 cable bad??? Not real!
Charging ok. PC connection ok.
What is a problem???
Hey Looking Forward To Help You..
1.Go To "SETTINGS"
2.Search For "OTG"
3.Some Phones Like Eg.Oneplus Have OTG Option In the Status Bar Customisation Tab..
4.Use An Prober Cable [OR] See If It Works On The Other Phone..
5.Important The Drive/SD You're Using Doesn't Have Any Hardware Issues!
6.Best Thing Is Two Option.
A.Software Update.
B.Factory Reset - Data Loss [Not Recommended]
7.Or It Must Be an Hardware Issue Please Reach Out To The Nearest Mobile Service Centre.
Alwaya XDA Peace
Hello!
I'm writed: NEED TO BRICKED PHONE = no settings, no menu, no system. (1-2-3 point not relevant)
4-5 writed: tested other type phone with cable, SD, pen, all working. P20 Pro not powered OTG (no 5V out)!
6: not available
7. Display changed, back changed, not original phone, not free (guarantee) service. Service + old unrooted, locked bootloader phone, ... too
I'm used IDT to flash. Only have CLT-AL00A-BD_1.0.0.46 Board Software firmware. Flashed in testpoint mode. All upload ok. After power on:
Imei: 000000000000...
Model: unknown
EMUI: 3.1
Droid: 5.1
Only have test softwares this firmware. No browser, etc.
How to update normal version?
*#*#2846579#*#* menu, update sd (read to available dload/update.app), restart, read SD 1-2s, Update failed!
What is a good version for SD update? First 8.1 or latest 10?
HiSuite searching update, no update!
Restored phone with PC and USB.
Problem: The TWRP version.
Changed TWRP version to 3.3, OTG working, newer version (3,4, 3.5) unsupported OTG.
More function not work in old version (restore backed up system partition: error, etc.).
Mr. V. said:
Restored phone with PC and USB.
Problem: The TWRP version.
Changed TWRP version to 3.3, OTG working, newer version (3,4, 3.5) unsupported OTG.
More function not work in old version (restore backed up system partition: error, etc.).
Click to expand...
Click to collapse
Hi there,can you please help me out ?I have one Huawei P20 pro, that had a fall and the back was smashed in to pieces,also glass on the back that's covering the camera was broken.I have cleaned it up and replaced the back on it ,now it was really temperamental,as of you tap on it it will just restat itself,apart from that wa ok,soo I was thinking maybe software error,soo done a factory reset and now is stuck in boot loop.Is not powering on the android operating system.I have tried all the restoration methods that you had tried upper but can't make it load the android operating system....I even bought that small and card reader that you can plug in the charger port to try and install the operating system again ,but even of the led light on the card reader is on , doesn't do anything...any guidance?
Thank you!
departe said:
Hi there,can you please help me out ?I have one Huawei P20 pro, that had a fall and the back was smashed in to pieces,also glass on the back that's covering the camera was broken.I have cleaned it up and replaced the back on it ,now it was really temperamental,as of you tap on it it will just restat itself,apart from that wa ok,soo I was thinking maybe software error,soo done a factory reset and now is stuck in boot loop.Is not powering on the android operating system.I have tried all the restoration methods that you had tried upper but can't make it load the android operating system....I even bought that small and card reader that you can plug in the charger port to try and install the operating system again ,but even of the led light on the card reader is on , doesn't do anything...any guidance?
Thank you!
Click to expand...
Click to collapse
If not rooted, use PC with Hisuite official software.
If not communicated to phone, need to reflash manually. This is not free.
In DC-Unlocker site download 2 software + pay 3 day license for this softwares and use.
Bootloop and cracking not related!
Cleared chaches??? Not solve?
Done factory erase,done cache memory erase,done restart and just staying on the Huawei screen where is saying down at the bottom Powered by Android for few minutes and after that goes in to the white meniu where you can select factory reset,updates (tried the WiFi update is not connecting),now I got the firmware and Kiwibird 4 in 1 card reader that you can plug up the "ass " of the phone usingOTG hopefully I can install the firmware from there...I have downloaded the firmware and just putting it on the SD card...have you tried that way?
Firmware install not working "offline" mode.
TWRP and any other not read OTG, only live system.
Another problem: OTG only support FAT/FAT32, not supported NTFS, ExFAT (Live system: need Paragon software). The firmware file more than FAT32 filesize limit (2GB), only stored NTFS or ExFAT = FW file too large for FAT.
Your FW upload only 3 method.
1. Boot to recovery, and set ADB mode, download the FW zip to DLOAD dir (from PC with USB cable + ADB), and install. (NOT TESTED!)
2. Boot to recovery, and set wifi recovery. Connect to wifi AP, download latest downloadable FW and install. (NOT TESTED)
3. Paid method: DC-Unlocker & DC-Phoenix work with standard recovery (limited access) and work own uploaded recovery (self opened bootloader/virtual testpoint).
OTG/SD not option for FW update!
Thanks you for your time,and writing back to me,yes,good point with different types of partitions,I forgot about it...I did try the nr.2 method and is not working,it can't download anything,I have trying different wiFi points,not starting any download,it does connect to the WiFi but can't find anything to be downloaded.
First method is not going to work as I have no access to set ADB mode,only fastboot mode,and is displayed that phone is locked soo, bootloader is locked and can't open it...soo only method to try is theast one...but don't know how much will that cost me.
Also I am thinking of other people said that the battery can have a problem too as my battery is getting empty fast...also something strange maybe..but if you tap the phone on the upper side on the edge it's restarting itself...I am thinking to open it up and try like that as in the past had been dropped soo back glass and camera glass have been replaced,but was working,until I have done factory reset and the process got interrupted in the middle of it and that was it...since.then..Inhave tried reset, factory reset,wipe cache, nothing working.
The softwares for 3 day ~20$. The DC-unlocker site write correct actual price.
If bootloader not opened, only available FW-update in Hisuite Huawei official software.
Test in recovery mode or bootloader mode.
(My recovery is TWRP, not available recovery method. Your available.)
Test connect to phone this software! If yes, but not available firmware, need to use special VPN software. Download offline your phone firmware to PC, or set specified link to VPN soft and Hisuite: update available! (Need Hisuite downgrade for this VPN method.)
If this update not working, purchase 3day license.
Need offline firmware file for your phone.
Soft-bootloader open if not working, use testpoint. (The DC-Phoenix manual write the testpoint position.)
Start the process in PC, Short testpoint to GND and plug USB. (If need, install drivers.)
Started upload unlocked bootloader and unlocked old recovery. After finished, reboot to recovery. (Without accu, work end... after reboot only work with plugged accu.) (Not need unplug accu!)
After booted recovery, wait PC to identify recovery mode, and started download.
The download 2 part! 1= firmware, 2=cust file. Need all selecting!
The download automated. Please wait for 100%. After end, rebooted to system.
Check IMEI, phone signal, MAC numbers. All ok? End flashing.
Wrong or no IMEI, bad MAC? Need the second software.
The second software unlock bootloader, FRP lock, all lock.
Unlocking bootloader (not need): software say the unlocking number, phone boot bootloader, PC USB ADB (Fastboot) command need to write the code, phone question: yes? Is yes, rebooted to recovery and CLEAR ALL DATA! After cleraing, boot system.
All phone start displayed "Phone untrusted".
Unlocked bootloder = uploadable TWRP or any recovery, after not need testpoint to flash.
Root: only rootable 8.1 system. (Not tested 8.1+, bootloader code not readable.)
Hi there mate,I have manage.to fix my phone,just following an old post here,with one russian website,where I got the firmware,put it on the SD card ,by the way you can make it eXFat ,will work for larger sizes,mine was 128 GB,and had to reboot the phone in update mode but selecting OTG/SD and it worked first time!I manage to update it with Android 10.After that all good,done the updates up to 12.
Thank you for your support and time!
Have a great week!
8.1 (stock) System and recovery not compatibilie / not read ExFat.
I have 8.1 System (rootable). In 8.1 OTG/SD update not working.
Check your filesystems:
Code:
$ cat /proc/filesystems
...
msdos
vfat
exfat
...
(This is a different device.)
Yes, system ok... i was wrong.
TWRP recovery not read any OTG! Other version TWRP read OTG, and not read correctly system partitions (half phone not read).
Standard recovery not available for me to testing.