Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?
mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:
alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted
Related
Hi there so I today truied to update to Eagles Blood custom Rom using Rom Manager to flash the new rom onto my O2x. The rom supposedly installed correctly but then when it booted it just gets to the unlock screen you unlock it then it reboots after a couple of seconds.
I can't get into recovery mode by the usual power on volume down technique as this just results in the phone continuing to load. I have tried different combos of power button reboots with volume button up, volume down and both together none work the only difference is that one of those results in just the LG logo rebooting.
I read a few posts about using nvflash or even the lg recovery tool using imei number etc but still no dice basically when I do the connect to the pc with both volume buttons pressed and the battery out it connects but doesn't recognise the device. I try the device manager and updating or removing the driver but regardless of how and what I try it either tells me it's using the most current driver or that no driver is actually installed.
This the same when using NV Flash i can't apx drivers installed and the device if I try to skip that step and go straight to the flash.bat command i just get usb device not found or connected or something like that.
Please help i am willing to try anyrhing and i really don't have the money for a new phone. I only have to get it working long enough or far enough so i can reinstall my backup i did before attempting the rom install this morning.
try connecting to different usb port(I suggest the backport of your PC)
and if that didn't work, must be a faulty cable.
genemini said:
try connecting to different usb port(I suggest the backport of your PC)
and if that didn't work, must be a faulty cable.
Click to expand...
Click to collapse
Unfortunately the cable is fine as if I'm not holding the power or volume keys I'm charging the batteries. I'm thinking there's something wrong with windows and the way it detects it possibly as i've trawled a fair amount of forums and tried a lot of what others have managed to get working with exception to someone else who had the same problem but couldn't get a resolution (that he posted about).
May be your USB port was broken.
Have you actually installed the apx drivers required for nvflash to work?
http://www.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active/
Sent from my LG-P990 using Tapatalk 2
you're not on Hard Brick, right?
can you try Smartflashing?
you need to install LG united drivers first.
APX won't install
So the problem is that my PC will pick up the unknown device. But it will not allow the install of the drivers. I can install the LG universal driver. The phone will connect as a unknown device only with error code 43 (device has been stopped) you try installing the APX drivers and the install of those drivers fail with error code 10 (can't start the device) this happens on both my stuffed phone and the brand new replacement so I am at a loss I have tried this on Windows 7 pc and also a Win 7 laptop (64 bit and 32 bit respectively).
The whole affair is frustrating as hell as I an't get my new O2x recognised either I can't root that to put my nandroid backup on and I am stuck on Froyo that I can't seem to root at all or even use lg update tool to update it to the latest stock firmware.
WHat about rooting apps
So with the obvious ways not working are there any actual apps I can install on my phone that will root it that way I am certain this is how I did it on my first O2x just can't remember what the name of the app was. So if anyone has apps or links to apps that may do this and or do do this please post back.
Have you actually tried a different USB cable? I notice you said the cable charges the phone, but this doesn't mean that other cores/pins other than the ones used for charging aren't damaged.
Sent from my LG-P990 using Tapatalk 2
different windows and different drivers
My suggestion would be try it on some other computer and different drivers. Or on same computer but reinstall Windows and ofc different drivers.
I'm suggesting this because I had experienced some what similar things on LG phones.
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool
Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/
it sounds like a driver issue. just download all the drivers you can find for your phone.
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file
Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?
agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.
Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.
Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk
Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts
casuk said:
Hi I just recived my mi5 and was wanting to put a stock android rom on it that is stable, I see a couple of ROMs on here but not sure what to use or where to start if anyone can give me a guide and correct ROM to use, I'm in UK Scotland
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If I were you I would definitely flash Lineage OS, its really solid, fast and has a good battery life.
Check this post for instructions. And give him a big thank
Spevky said:
Please help me my phone is in EDL mode and i can't flash anything on it. It does not turn on no led no light no display no response. Just Qualacomm QDLoader 9008
Everytime i flash it gives me an error.
Max buffer sector is 256.
Errors and so on.....
How to fix please
I have reinstalled all drivers and programs , tried a lot of miflash versions , fastboot roms like 6-8. Many pc restarts
Click to expand...
Click to collapse
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.
xdadevet said:
I had the exact same problem, it happened randomly after a normal reboot. I was considering taking it apart to disconnect the battery, try a deepflash cable and EDL but then I solved it.
The problem is your Windows driver. That's why you can't flash anything. Read up on Xiaomi forums about the problem. I can't remember exactly how I solved it, but I think I uninstalled the driver, plugged the phone back in, wait for the automatic install on Device Manager, then for it to update, do a roll back and then flash it via MiFlash.
Click to expand...
Click to collapse
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?
Spevky said:
Thanks. THat must be the problem. But i tried on my friends pc too and it did not work. Maybe Windows 7 is the problem? Im installing Windows 10.
Which OS do you have?
Click to expand...
Click to collapse
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.
xdadevet said:
I don't think Windows 7 is the problem, but I've been using Windows 10 for 3 years (as Beta user) so I can't tell. Boot into EDL (Phone must be powered off, then hold both "Volume UP" and "Volume Down" as you plug it into the computer, only then do you let go) and tell me what driver your phone is seen as in Device Manager.
Click to expand...
Click to collapse
It is detected as QDLoader 9008 version of QDLoader 9008
im trying to follow the guides but im not understanding what to do I have downloaded adb and fastboot I extracted the files to a folder and im now stuck, whats this mean
•Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
that's were im am so far and im basically lost and need so help if anyone is kind enough to go through the steps with me
thanks
Ok I've unlocked the phone but i can seem to be able to root it
Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?
after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.
Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.
FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).
So, I tried to update to Pie.
I was on Stock Oreo rooted without encryption.
Wiped everything except sdcard, installed Pie and the boot img for encryption fix.
Rebooted to TWRP, flashed the zip from verity fix, flashed latest Magisk.
Rebooted to system, stuck with the dots rotating.
Tried to redo it again, adding the step for the firmware flash.
But when wiping i accidentally wiped sdcard too, so I have no more the required files inside TWRP.
Tried to connect both TWRP and bootloader via adb/fastboot but phone is not recognized.
All the drivers are installed it always worked before (Win7).
Now everytime I try to connect the 3T to PC it says Unknown Device in Device Manager, but all the drivers are installed.
Apparently the phone is not sending its data, because in device properties i see VID & PID = 0000.
Trying to manually attach a driver to it (with right click, update driver) gives error, no driver available for the device (using any adb drivers .inf).
So basically now I'm stuck with a phone without files in it, but with only TWRP working.
How can I send the rom files without adb/fastboot? Any trick?
I also tried to use USB OTG from TWRP but apparently any usb stick is not recognized.
Tried different USB ports and different cables. Seems like a problem with the phone usbC port, not sure.
It's an hard brick at this point?
Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk
Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.
pitrus- said:
Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
sandeep_kumar said:
Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.
Click to expand...
Click to collapse
I already tried that too. It always appear as unknown device, even with that method.
Just to be clear, I never had problem before and I already used TWRP mount and fastboot/adb to load files without having a running ROM. I was always able to move file with any of them.
This is different, it seems like an hw problem, the phone it's not sending his IDs when connecting to CP so the PC can't identify what it is even if drivers are installed.
Now, I'm not sure if the problem lies in the physical USBC port or if the failed Pie upgrade ruined somethin in the bootloader or something else.
Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk
pitrus- said:
Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Tried many cables, ports and PCs.
I also tried to clean the port with a wooden stick without luck.
At this point i believe it's the usbC port or the motherboard.
I think something at the USB MTP level went faulty, because charge works fine (dash charge too).
I just can't transfer files anymore. Not even with an OTG dongle.
Since there is no other way to trasnfer the ROM zip (network is not available inside TWRP) I requested an RMA and tomorrow OnePlus send a carrier to pick it up for repair.
I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.
i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries
sandeep_kumar said:
I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.
Click to expand...
Click to collapse
Don't worry, if the USB port is working you can always recover. Just be sure your PC recognize the device first, in case anything happens.
cmurder61 said:
i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries
Click to expand...
Click to collapse
I've been trying for the whole day with 5 different cables, 4 different PC and every usb port of them. I just didn't try with an hub because i don't have one, but i don't think it makes any difference. Anyway the phone i ready to be send for repair now.
if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol
cmurder61 said:
if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol
Click to expand...
Click to collapse
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.
matrixino said:
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.
Click to expand...
Click to collapse
i see, well good luck to ya