[HELP] Bricked phone while updating to Pie

matrixino

Senior Member
Sep 30, 2010
165
29
58
Canosa di Puglia
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?
 
Last edited:

pitrus-

Senior Member
Sep 4, 2011
1,258
531
143
Östersund
www.wickenberg.nu
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
 

sandeep_kumar

Senior Member
Feb 21, 2017
488
127
0
Indore
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.
 

matrixino

Senior Member
Sep 30, 2010
165
29
58
Canosa di Puglia
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.
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.
 

matrixino

Senior Member
Sep 30, 2010
165
29
58
Canosa di Puglia
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
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.
 

sandeep_kumar

Senior Member
Feb 21, 2017
488
127
0
Indore
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.:eek::eek:
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.:confused:
 

cmurder61

Member
Apr 23, 2011
30
2
28
Marion
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
 

matrixino

Senior Member
Sep 30, 2010
165
29
58
Canosa di Puglia
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.:eek::eek:
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.:confused:
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.
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
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.
 

cmurder61

Member
Apr 23, 2011
30
2
28
Marion
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
 

matrixino

Senior Member
Sep 30, 2010
165
29
58
Canosa di Puglia
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
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.
 

cmurder61

Member
Apr 23, 2011
30
2
28
Marion
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.
i see, well good luck to ya