Database Info

Did I completely mess up my Captivate?

So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.

I pull out my battery and let it discharge for about 15 secs and hold volume buttons then connect USB cable and finally insert battery while still holding volume buttons of course, it'll get you into download mode. Never failed me. I've had my phone not even turn on the screen, it stays dark during a screwed up flash with odin. I then flash UCKI2 with bootloaders and then flash to gingerbread ROM I like. If you plan on installing custom ROMs your phone will semi-brick numerous times. If its showing a phone, exclamation mark and computer with a message saying firmware flashing failed. That is perfect! Just make sure you have Samsung USB drivers and simply flash using odin, it'll show COM and a number like 5 (COM5) then just flash. I'd advise you to remove any external SD card and restart before using odin it acts up. Hope this helps

hupo224 said:
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
Click to expand...
Click to collapse
The "Phone - ! - PC" will be your download mode screen. Just download from there.

However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen.
If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Click to expand...
Click to collapse
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.

asasione said:
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
Click to expand...
Click to collapse
100% - I had similar experience with my first flash but after a few goes at it and 3 or 4 "soft-bricks" all has been great!

Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..

It seems I got it in download mode this morning with the jig. Just trying to get my damn pc to read it. Sometimes the right drivers work sometimes they don't. ugh

Connection issue in my sig

Any chance you have another pc to try it with? Or possibly another cable?

Going to try one click on ubuntu...

Ive had issues in the past before with certain USB ports on my PC not reading the phone.
Try plunging in your phone to a different USB port and it can make a world of difference with the driver issue (even if you have to plug it in the back of your PC).

try one click unbrick in the android development page

hupo224 said:
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
Click to expand...
Click to collapse
Are you running x64? If so are you running the 64 bit drivers?

I also had the same issue a couple of times, which is technically called a "soft brick" . You could resolve this issue using ODIN flasher and reverting back to stock. Now coming to USB problem in windows, this is a known issue with windows (especially Vista and Win7) and samsung!! The remedy which I found is as follows :-
1.Disconnect the phone from USB
2.Remove samsung USB driver software from your windows PC.
3.Reboot and then navigate to C:\Program Files\ (assuming that C:\ is your windows OS partition)
Delete "samsung" folder.
4.Download latest samsung USB Drivers for captivate and install.
5.Reboot the phone.
6.Open ODIN and connect your Phone to PC.
It should detect the COM Port by now. Try this and get back
"Thanks" , If I helped U

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh

Nexus 5 HARD BRICKED ( wont come on )

i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:

you know that the "max download size" thing is just a WARNING message, in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
anyway, see if it really wont come on, my phone was like that, but in fact it was in qualcomm´s QD-LOADER 9008 (i had to install some drivers for it to show up on pc). if your phone does get detected(even if as an unknown device)then you have some hope, if not - too bad you are mostly screwed.
Check your device manager

opssemnik said:
in fact a lot of phones displays it for all operations(being all operations all fastboot flash operations), on the n5 it only shows when installing recovery (afaik).
Click to expand...
Click to collapse
It showed for every fastboot flash I did just a few days ago. I don't recall that warning showing up back when I flashed 4.4.4 and prior. I think it's a change with the new bootloader.

Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable

shiva-x said:
Have you tried to use Google recovery that flashes stock ROM on your device ?
I had made a very bad thing with my N5, which resulted in a bootloop, two hours after receiving the N5 and I was almost crying. Download a stock recovery from android dev site. A Nexus is unbrekable
Click to expand...
Click to collapse
Wrong...

Google- said:
i was trying to flash android L through root toolkit ( wug fresh )
but i got an errors saying max download limit ????? bytes
then i just unplugged the phone from the computer and like an idiot
and now it wont come on
when i plug it in charge it doesnt show anything aswell
Please Help how can fix ? I Bought this with my own pocket money brand new from play store for £300
:crying: :crying: :crying:
Click to expand...
Click to collapse
Tried a forced reboot? (Power + volume down button for bout 15 seconds).
Seems like the go-to solution but I see no one asked you yet.
Do this while connected to a charger.

Also try booting into the secondary bootloader by pressing volume up , down and power simultaneous.

Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.

gee2012 said:
Noob + Toolkit = Leathal combo
Try to learn fastboot and adb so you have control over whats happening and don`t use toolkits.
Click to expand...
Click to collapse
Agree , but it should still be salvageable - assuming the incomplete firmware didn't cause hardware damage.

Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?

nirmal212 said:
Is there any solution found? I ran into the same situation. I installed CM 11S and that prompted me an error which was unable to read the binary input file. I then reinstalled the firmware and did a reboot Now, it's hard bricked. Won't boot at all.
How do I power my N5 back?
Click to expand...
Click to collapse
any new device showing up in the device manager when you connect your phone to your pc?

bitdomo said:
any new device showing up in the device manager when you connect your phone to your pc?
Click to expand...
Click to collapse
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.

nirmal212 said:
It's showing up as "QHSUSB_BULK". Then I tried to install the qualcomm driver. Now nothing is showing up.
Click to expand...
Click to collapse
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here

bitdomo said:
press and hold volume_down+volume_up+power keys until you see it again. It should take 20-25 seconds. Try to fix the drivers (turning off dirver signature enforcement helps a lot) to show Qualcomm HSUSB QDLoader 9008 device then follow my guide here
Click to expand...
Click to collapse
Can I perform this action even if my device is not started? I tried all the button options and still the device won't power on.

Have I bricked my Nexus 5?

Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake

jake.Hall30 said:
Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake
Click to expand...
Click to collapse
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?

Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.

jake.Hall30 said:
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?
Click to expand...
Click to collapse
Try other usb ports and usb cables or even other PC

hey guys, thank you for the response!
Telyx said:
Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.
Click to expand...
Click to collapse
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
bitdomo said:
Try other usb ports and usb cables or even other PC
Click to expand...
Click to collapse
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?

jake.Hall30 said:
hey guys, thank you for the response!
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?
Click to expand...
Click to collapse
I would try if I were you

bitdomo said:
I would try if I were you
Click to expand...
Click to collapse
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)

jake.Hall30 said:
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)
Click to expand...
Click to collapse
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link

bitdomo said:
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link
Click to expand...
Click to collapse
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
EDIT: Dude, i absolutely love you! Thank you so so much, just having someone to talk to about it has helped!
For anyone who comes across this looking for an answer, what I have done is install TWRP (custom recovery), used the adb commands found here: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 to fix the persistent partition, I then had a different boot loop, so I reinstalled the rom and voila! She's back!
Just a question: how did this happen, out of the blue, in the first place? is this something I did?
Thank you to the xda team, you guys are great

jake.Hall30 said:
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
Click to expand...
Click to collapse
Restart your device to recovery again.
You can also try the fastboot boot <<whateverfilename>>.img instead of flastboot flash recovery <<whateverfilename>>.img

Phone Bricked After Installing OTA Update

I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.

adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.

MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.

adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.

MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"

Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues

OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?

jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.

adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works