Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8 and OP8Pro here is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus 8 bought from T-Mobile.
It will only work with T-Mobile variant IN2017
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.7
OOS 10.5.20: Gdrive - AFH (credits to @rzracer2 )
OOS 10.5.21 (credits @LLStarks for finding it)
OOS 10.5.22 (credits @LLStarks for finding it)
ANDROID 11:
OOS 11.0.5.7
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select TMO.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@Some_Ghost for testing 10.5.7 version on his device
@Titokhan for being a friend and providing inspiration in writing
@AndroidFileHost for the hosting
OnePlus for the device and OS
You're a gentleman and a scholar! #beast
I just tried to download the package from androidfilehost. No mirrors came up. Still uploading?
Some_Random_Username said:
Mod edit: Quoted OP shortened for better reading experience!
Click to expand...
Click to collapse
---------- Post added at 05:05 PM ---------- Previous post was at 05:03 PM ----------
As far as Msm 4.0, here can I get a patched.exe to unlock the bootloader, provided that tmobile didn't close that loophole. Thanks.
Some_Random_Username said:
Mod edit: Quoted OP shortened for better reading experience!
Click to expand...
Click to collapse
@sameog this sounds to be an issue with AFH as otherwise it wouldn't have given a link.
Please try the alternative mirror I linked to in OP (password for it is at its bottom)
Additionnaly, even if executable is named MsmDownloadTool V4.0.exe its version is 5.1.32 if you go to file properties->details.
Patching executables is way beyond my knowledge, so I cannot assist with that.
Some_Random_Username said:
@sameog this sounds to be an issue with AFH as otherwise it wouldn't have given a link.
Please try the alternative mirror I linked to in OP (password for it is at its bottom)
Additionnaly, even if executable is named MsmDownloadTool V4.0.exe its version is 5.1.32 if you go to file properties->details.
Patching executables is way beyond my knowledge, so I cannot assist with that.
Click to expand...
Click to collapse
Hi there,
Here's the error message I'm receiving from AFH:
https://androidfilehost.com/?fid=4349826312261793719[/IMG]
Please look into this.
Thanks.
sameog said:
Hi there,
Here's the error message I'm receiving from AFH:
https://androidfilehost.com/?fid=4349826312261793719[/IMG]
Please look into this.
Thanks.
Click to expand...
Click to collapse
Your attachment is broken, I cannot see any screenshot. I may try to reupload to AFH when I will have time but waiting that, as I said in my previous post, use the other mirror present in the OP.
Mirror: https://anonymouswp.stackstorage.co...ols/OxygenOS/OnePlus+8+T-Mobile&node-id=73351
Click to expand...
Click to collapse
What is the password of the mirror?
N3v3r S3ttl3 tm
Click to expand...
Click to collapse
Some_Random_Username said:
Your attachment is broken, I cannot see any screenshot. I may try to reupload to AFH when I will have time but waiting that, as I said in my previous post, use the other mirror present in the OP.
Click to expand...
Click to collapse
UPDATE: I tried use the mirror and received a failed message. I logged into the mirror server using the given password and the download failed.
sameog said:
UPDATE: I tried use the mirror and received a failed message. I logged into the mirror server using the given password and the download failed.
Click to expand...
Click to collapse
Download works fine for me (I'm in Europe and mirror is in Europe as well), there may be an issue with your ISP in regards to peering agreements to Europe.
Unfortunately I cannot do anything for it. As odd as it seems, you may neeed to VPN to Europe to prevent that issue from happening.
Some_Random_Username said:
Download works fine for me (I'm in Europe and mirror is in Europe as well), there may be an issue with your ISP in regards to peering agreements to Europe.
Unfortunately I cannot do anything for it. As odd as it seems, you may neeed to VPN to Europe to prevent that issue from happening.[/QUOTE
Finally downloaded! My VPN did the trick. Again, thank you for all that you and have done! :good: #rockstar
Click to expand...
Click to collapse
Everything works like a champ! Now I can play more with my device. Thanks a lot
Alotaibiq8 said:
Everything works like a champ! Now I can play more with my device. Thanks a lot
Click to expand...
Click to collapse
How are you getting into edl? are you using button combos? because when I was testing this it took a lot of time and effort and I got into it by chance in the way that is explained in the description. Even on my replacement OP8 I tried to get into edl with numerous button combos with ZERO luck.
Some_Ghost said:
How are you getting into edl? are you using button combos? because when I was testing this it took a lot of time and effort and I got into it by chance in the way that is explained in the description. Even on my replacement OP8 I tried to get into edl with numerous button combos with ZERO luck.
Click to expand...
Click to collapse
I used the volume up and down buttons to get into the edl and it works every time. Make sure you have the right drivers installed and use the original USB cable. Good luck :good:
Alotaibiq8 said:
I used the volume up and down buttons to get into the edl and it works every time. Make sure you have the right drivers installed and use the original USB cable. Good luck :good:
Click to expand...
Click to collapse
is yours TMobile edition?
Some_Ghost said:
is yours TMobile edition?
Click to expand...
Click to collapse
Yes, it's the T-Mobile version.
These are files I have in my system to "unbrick:" my device:
1. OnePlus 8 T-Mobile 10.5.7 -- unzipped the file before you proceed (you all knew that)
2. QUD.WIN.1.1+Installer-10037.3+Setup -- this is required. If need this, copy and paste this in google. These drivers were hard to find at first. Unzip the download.
3. OnePlus_USB_Drivers_Setup -- I thought these drivers were unnecessary but they are VERY necessary. (caps for emphasis)
4. When you have unzipped the QUD.WIN.1.1+Installer-10037.3+Setup file and the OnePlus_USB_Drivers_Setup, go through the setup wizard. NOTE: Oneplus will ask you for something like "Wincom" for something of that nature, click next. It threw me as well. When the drivers have all been setup up and installed, perform a reboot to refresh Windows (it's good practice especially when dealing with drivers.
Guys who are having trouble: This is what I did. I powered off the phone completely. Launch the msm download 4.0. When the dialog box comes up, get your phone ready. When the phone is completely off, press and keep the volume up and down button pressed. Plug the small part of usb into the phone. While holding the volume up and down buttons and phone steady, I plugged in the fat end into the other usb port on your computer since we're dealing with unbricking our phone. You will know when connection is made when you hear the windows "attached" sound and you will see a "connected" text in the field on the top in the msm download tool launch box. Click on the connected to highlight this and click start. Do not play with your phone during this time. Let the program do its thing and your phone will automatically reboot when done.
I hope this helps guys. Wordy yes but it beats being confused as hell....
Some_Ghost said:
is yours TMobile edition?
Click to expand...
Click to collapse
Yup model number IN2017
sameog said:
Yes, it's the T-Mobile version.
These are files I have in my system to "unbrick:" my device:
1. OnePlus 8 T-Mobile 10.5.7 -- unzipped the file before you proceed (you all knew that)
2. QUD.WIN.1.1+Installer-10037.3+Setup -- this is required. If need this, copy and paste this in google. These drivers were hard to find at first. Unzip the download.
3. OnePlus_USB_Drivers_Setup -- I thought these drivers were unnecessary but they are VERY necessary. (caps for emphasis)
4. When you have unzipped the QUD.WIN.1.1+Installer-10037.3+Setup file and the OnePlus_USB_Drivers_Setup, go through the setup wizard. NOTE: Oneplus will ask you for something like "Wincom" for something of that nature, click next. It threw me as well. When the drivers have all been setup up and installed, perform a reboot to refresh Windows (it's good practice especially when dealing with drivers.
Guys who are having trouble: This is what I did. I powered off the phone completely. Launch the msm download 4.0. When the dialog box comes up, get your phone ready. When the phone is completely off, press and keep the volume up and down button pressed. Plug the small part of usb into the phone. While holding the volume up and down buttons and phone steady, I plugged in the fat end into the other usb port on your computer since we're dealing with unbricking our phone. You will know when connection is made when you hear the windows "attached" sound and you will see a "connected" text in the field on the top in the msm download tool launch box. Click on the connected to highlight this and click start. Do not play with your phone during this time. Let the program do its thing and your phone will automatically reboot when done.
I hope this helps guys. Wordy yes but it beats being confused as hell....
Click to expand...
Click to collapse
it turns out it was my laptop the whole time I ended up using my aunts computer and it worked 100%
Wait how are people bricking their devices with T-Mobile s bootloader still unlocked? Did anyone manage to get it unlocked ?
Sent from my IN2017 using Tapatalk
matteosaeed said:
Wait how are people bricking their devices with T-Mobile s bootloader still unlocked? Did anyone manage to get it unlocked ?
Click to expand...
Click to collapse
I bricked mine while we were testing stuff on it
Some_Ghost said:
I bricked mine while we were testing stuff on it
Click to expand...
Click to collapse
You're a champ
OnePlus 8 T-Mobile
Hi, is this tool convert TMobile OnePlus 8 into international oxygen os? Or it is download TMobile stock fireware back to the phone?
sameog said:
Yes, it's the T-Mobile version.
These are files I have in my system to "unbrick:" my device:
1. OnePlus 8 T-Mobile 10.5.7 -- unzipped the file before you proceed (you all knew that)
2. QUD.WIN.1.1+Installer-10037.3+Setup -- this is required. If need this, copy and paste this in google. These drivers were hard to find at first. Unzip the download.
3. OnePlus_USB_Drivers_Setup -- I thought these drivers were unnecessary but they are VERY necessary. (caps for emphasis)
4. When you have unzipped the QUD.WIN.1.1+Installer-10037.3+Setup file and the OnePlus_USB_Drivers_Setup, go through the setup wizard. NOTE: Oneplus will ask you for something like "Wincom" for something of that nature, click next. It threw me as well. When the drivers have all been setup up and installed, perform a reboot to refresh Windows (it's good practice especially when dealing with drivers.
Guys who are having trouble: This is what I did. I powered off the phone completely. Launch the msm download 4.0. When the dialog box comes up, get your phone ready. When the phone is completely off, press and keep the volume up and down button pressed. Plug the small part of usb into the phone. While holding the volume up and down buttons and phone steady, I plugged in the fat end into the other usb port on your computer since we're dealing with unbricking our phone. You will know when connection is made when you hear the windows "attached" sound and you will see a "connected" text in the field on the top in the msm download tool launch box. Click on the connected to highlight this and click start. Do not play with your phone during this time. Let the program do its thing and your phone will automatically reboot when done.
I hope this helps guys. Wordy yes but it beats being confused as hell....
Click to expand...
Click to collapse
paojennes said:
Hi, is this tool convert TMobile OnePlus 8 into international oxygen os? Or it is download TMobile stock fireware back to the phone?
Click to expand...
Click to collapse
This tool only restores your phone if it's bricked. No international conversion method yet.
Related
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated
Thank you guys for letting me know about the link I'm posting it in the OP so that everyone having this issue can upvote on that thread.
Link: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
theevilpotato said:
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated.
Click to expand...
Click to collapse
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
520? :/ Same here. Time to get a new phone for school, I guess.
Yes, a 520 as well.
Just a heads up, if you give the windows phone subreddit a quick read you'll notice we are not the only people to have this issue. Apparently several other people trying to roll back their phone have it completely bricked and in the QHSUSB_DLOAD situation.
I don't think MS can do anything about it, since the boot crapped out you either need to buy the tools or get it repaired by someone having them, but at least it proves there is some kind of problem with rolling back from the preview.
angstdasein said:
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
Click to expand...
Click to collapse
same here
After a bit of reading more and more people are reporting this, so please put your own experience on this technet thread, it's a good idea to centralize reports where Microsoft can see it.
I can't link it here (don't have the permission to post links yet) but it's the first result by typing "Lumia 620 bricked during rollback procedure: recovery possible?" in google.
NL525 w/ red screen here.
feherneoh, pls make tutor!
feherneoh said:
Here it is:
...
Click to expand...
Click to collapse
Praise the Lord feherneoh!
Greatest thanx to ya!
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
azogh said:
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
Click to expand...
Click to collapse
Be sure using good cable. Try few times (i did 3)
[QRCODE][/QRCODE]The same problem with L520. There is already post on Technet regarding this problem
You can search Google by typing in: QHSUSB_DLOAD technet
Please upvote, then we would have some respond from Microsoft, maybe alternative driver, tool or something...
My Nokia does not turn on
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
rickmaran said:
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
Click to expand...
Click to collapse
I don't think there is a solution yet. Just keep and eye on this and hope for the best: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
Have you anyone has try using Lumia Recovery Tool ?
1. Download ffu saperatly. (8.1 GDR1)
2. Install Lumia Software Recovery Tool.
3. Launch recovery tool.
4. Remove battery, usb, device.
5. Select my phone doesn't respond in recovery tool.
6. Insert battery, usb, plug it to pc.
7. A- Press and hold volume down.
B- Press and hold Power + volume down
8. Flash it.
Hope this will work.
feherneoh said:
Here it is:
1: Find your Recovery Tool folder on your harddisk. Mine is "C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool"
There should be a file called thor2.exe there.
2: Open an administrator command prompt here
3: Find the ROM Recovery Tool downloaded. Should be in "C:\ProgramData\Microsoft\Packages\Products"
You will need the FFU file for your device.
Mine is "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
4: To flash your device with THOR2, enter this to commandline:
Code:
thor2 -mode uefiflash -ffufile "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
Replace filename with your own
5: After flashing completes, reboot your phone by entering this:
Code:
thor2 -mode rnd -bootnormalmode
Click to expand...
Click to collapse
It says this error:
THOR2 1.8.2.14 exited with error code 393220 <0x60004>
Click to expand...
Click to collapse
zuchit said:
It says this error:
Click to expand...
Click to collapse
Same case
Same problem with DLOAD
The solution seems to do a JTAG... Bad news for normal people ::crying:
Bricked Nokia Lumia
Actually, the red screen means that the phone went into its UEFI MODE.
In UEFI MODE your phone could be restored as normal by a HARD RESET (see key combo).
If you have a hard luck, your phone will automatically start in Flashing Mode (IMO(0x0000001)) which only works on the downloading procedure when on Rolling back.
The RollBack program has to put your phone in Flashing Mode in order to gain access to it's microchip.
Well the app itself knows what to do, but something failed.
In this point, you disconnected the phone and tried all you've known to power it on. Meanwhile the app deleted it's cache file, it no longer knows why your phone is in that state and your PC will get it as QHSUSB_DLOAD which is a Side_Load driver for Qualcomm Enabled Phones.
At this point, RIFF JTAG is the only solution as your BOOTLOADER is dead.
Good thing? It could be fixed by any GSM Service and the price could be small.
DO NOT try any Nokia Care / Refurbish / Restore app. All of them are created to work with a phone that has it's bootloader working.
None of them will cooperate to reflash it.
Even if you manage to reflash the OS, you don't have a BIOS / BootLoader....
Hopefully, Microsoft will create a tool to fix this as it only occurs when Rolling Back from Windows 10 Tech. Prev. and 8.1 to 8.
But until that, your phone is dead.
Source of info: I'm working as an G.S.M. RepairMan.
feherneoh said:
Maybe some error message before this?
Click to expand...
Click to collapse
at the moment, i get this error when i cmd thor right after connecting phone to usb. (screenshot 1)
i58.tinypic. com/2qnz51d.jpg
Click to expand...
Click to collapse
these is what it says when i try cmd thor after red screen with Nokia logo appers.. (screenhot 2)
i61.tinypic. com/jkftq8.jpg
Click to expand...
Click to collapse
Update:
Update to 7.0 and dirty cow root can be found there.
https://forum.xda-developers.com/lg...gat-7-0-v521-guide-to-update-v521-lg-t3533338
Latest dll for LGUP
https://www.androidfilehost.com/?fid=745425885120701290
Make sure you use upgrade
It's highly recommend to update to 7.0
Thanks @tungkick for making rooted .dz file
Download: https://drive.google.com/file/d/0BwLkiuDnHmY0bTBsOG12VnBOa3c/view?usp=sharing
LGUP: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Install LG Bridge for required drivers.
Download this .dll file https://www.androidfilehost.com/?fid=24588232905722773 Rename LGUP_c.dll to LGUP_common.dll
After installed LGUP, go to C:\Program Files (x86)\LG Electronics\LGUP\model (you must login as administrator)
add new folder \common\ and put dll file there
Make sure you backup the machine with LG Backup.
Unlock bootloader if you didn't do it with the following command in fastboot mode (adb reboot bootloader)
Code:
fastboot oem unlock
After finishing the prerequisite above, it's time to ROOT!
1. Plug your tablet to your host computer. If the battery is lower than 50%, please wait because the process may take up to 15 minutes.
2. Make sure USB is set to file transfer mode.
3. Open LGUP
4. Choose "upgrade" and locate downloaded .dz file. Press start when you're ready.
5. Wait about 15 minutes and it will finish.
(Optional) Update SuperSU binary if necessary.
---- edited version ----
Updated Instructions:
Prerequisites:
1. Download the following:
The .dz File
Download LGUP following the instructions in the thread for installation.
Download LG Bridge for Windows PC for necessary device drivers or use the quick download
Download this .dll file https://www.androidfilehost.com/?fid=24588232905722773 - Rename LGUP_c.dll to LGUP_common.dll
2. After installing LGUP, go to C:\Program Files (x86)\LG Electronics\LGUP\model as an administrator and
add a new folder 'common' ("\common") and put the .dll file there
3. Backup the device with LG Backup.
4. Unlock the device bootloader if you haven't done so already.
Code:
reboot bootloader
fastboot oem unlock
fastboot reboot
5. Check if the bootloader is unlocked by entering:
Code:
fastboot getvar unlocked
After finishing the prerequisites above, it's time to ROOT!
1. Plug your tablet to your host computer. If the battery is lower than 50%, please wait because the process may take up to 15 minutes.
2. Set the USB to 'File Transfer Mode.'
3. Open LGUP and select the LG G Pad X 8.0
NOTE: If it doesn't appear, you may not be in 'File Transfer Mode,' missing device drivers, or have a faulty USB port or cable.​4. Choose "Upgrade" and locate the downloaded .dz file. Press start when you're ready.
5. Wait about 15 minutes and it will finish. The process will hang for a bit at 99% or 100%, this is normal
6. Update SuperSU binary if necessary. (Optional)
You can also revert to stock or unroot when desired
1. Use LGUP and flash the stock .dz
Special thanks to @tungkick for making the rooted .dz file. @mingkee, copy these newer instructions into your post, if desired, by quoting it and removing the quote tags.
It took me only 3 to 4 minutes for the whole root process, also with battery lower than 50%.
I'm seeing Model Unknown or No Handset Found even after putting the DLL in that location. Please tell me if I'm missing something.
avishah395 said:
I'm seeing Model Unknown or No Handset Found even after putting the DLL in that location. Please tell me if I'm missing something.
Click to expand...
Click to collapse
Did you rename the LGUP_c.dll to LGUP_common.dll?
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
To OP: please add bootloader unlock to the prerequisite.
googlephone said:
Did you rename the LGUP_c.dll to LGUP_common.dll?
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
To OP: please add bootloader unlock to the prerequisite.
Click to expand...
Click to collapse
Yes
avishah395 said:
Yes
Click to expand...
Click to collapse
Then it is most likely driver issue. Google LGunitedMobileDriver and install drivers.
googlephone said:
Then it is most likely driver issue. Google LGunitedMobileDriver and install drivers.
Click to expand...
Click to collapse
I installed v4.0.4 from the main thread. I'll try this on another computer. I have bootloader unlocked and USB Debugging enabled.
Check in the device manager on your computer and you should see lg device under COM ports if drivers are installed correctly.
googlephone said:
Check in the device manager on your computer and you should see lg device under COM ports if drivers are installed correctly.
Click to expand...
Click to collapse
I got it to work by changing it from charging only to file transfer. Idk why that worked lol
avishah395 said:
I got it to work by changing it from charging only to file transfer. Idk why that worked lol
Click to expand...
Click to collapse
Change to file transfer is required for and command to work. Maybe this can be added to the instructions in the OP too.
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Click to expand...
Click to collapse
How can I?
mingkee said:
How can I?
Click to expand...
Click to collapse
Look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443747}
Our ET/tag is "lg-g-padx"
Boot loop
Could use some help - followed the OP instructs, the DZ seemed to update successfully with LGUP. Hit 100%, then tablet rebooted, and now it is flashing every two seconds saying
Boot Verification Fail!!!
- cause : MISMATCH_SIG_LEN
Cannot even power off, holding down the power button indefinitely does nothing.
porear said:
Could use some help - followed the OP instructs, the DZ seemed to update successfully with LGUP. Hit 100%, then tablet rebooted, and now it is flashing every two seconds saying
Boot Verification Fail!!!
- cause : MISMATCH_SIG_LEN
Cannot even power off, holding down the power button indefinitely does nothing.
Click to expand...
Click to collapse
Under this situation, you have to pry open the back cover. Open from USB OTG port. The battery connector is on the right side (not on the cam side).
Do not turn the tablet on. Press and hold volume up button and connect to host computer and run LGUP, and install this kdz instead.
https://www.androidfilehost.com/?fid=24588232905722719
avishah395 said:
Look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443747}
Our ET/tag is "lg-g-padx"
Click to expand...
Click to collapse
Done.
You can remove the post
mingkee said:
Done.
You can remove the post
Click to expand...
Click to collapse
Why do you want me to remove it? Nobody else can make that change.
avishah395 said:
Why do you want me to remove it? Nobody else can make that change.
Click to expand...
Click to collapse
Never mind.
I have to use the tag again.
mingkee said:
Under this situation, you have to pry open the back cover. Open from USB OTG port. The battery connector is on the right side (not on the cam side).
Do not turn the tablet on. Press and hold volume up button and connect to host computer and run LGUP, and install this kdz instead.
https://www.androidfilehost.com/?fid=24588232905722719
Click to expand...
Click to collapse
Thanks! So what is different about that kdz, and what do I have going on? Downloading now.
In desperation I was button pushing and with a lot of praying I found that with the USB connected, Vol Up with the reader mode button broke the looping and got me to a download mode! I tried the original kdz again, with the same result. I tried the LG Mobile Support Tool, and attempted to do an "Update Recovery" under Options, but it did a quick scan and then seemed like it was downloading an entire load so I canceled it.
At the moment, both LGUP and the Mobile Support Tool recognize my existing load version as 10b, while when running LGUP the download mode screen on the tablet is saying I am upgrading from 10c to 10c.
porear said:
Thanks! So what is different about that kdz, and what do I have going on? Downloading now.
In desperation I was button pushing and with a lot of praying I found that with the USB connected, Vol Up with the reader mode button broke the looping and got me to a download mode! I tried the original kdz again, with the same result. I tried the LG Mobile Support Tool, and attempted to do an "Update Recovery" under Options, but it did a quick scan and then seemed like it was downloading an entire load so I canceled it.
At the moment, both LGUP and the Mobile Support Tool recognize my existing load version as 10b, while when running LGUP the download mode screen on the tablet is saying I am upgrading from 10c to 10c.
Click to expand...
Click to collapse
Anti rollback???!
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.
rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...
I held the power and vol down and now it shows up under com ports so this is a good sign.
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...
rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...
5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?
Hello, I am completely new to this rooting thing and definitely a noob at this. I have tried to search for solutions, but most solutions I have seen use terminology that I have, for the most part, no idea what they are talking about. I was able to successfully unlock the bootloader. I then tried to root the phone but ended up getting stuck on "Your device software can't be checked for corruption. Please lock the bootloader." It said it would boot in 5 seconds but it does nothing. To make matters worse, I made the mistake of locking the bootloader and now that I turn on the phone it is stuck on the ZTE logo. Assistance would be greatly appreciated .
My phone is the ZTE Axon 7 version 7.1 and A2017U.
radmike12 said:
Hello, I am completely new to this rooting thing and definitely a noob at this. I have tried to search for solutions, but most solutions I have seen use terminology that I have, for the most part, no idea what they are talking about. I was able to successfully unlock the bootloader. I then tried to root the phone but ended up getting stuck on "Your device software can't be checked for corruption. Please lock the bootloader." It said it would boot in 5 seconds but it does nothing. To make matters worse, I made the mistake of locking the bootloader and now that I turn on the phone it is stuck on the ZTE logo. Assistance would be greatly appreciated .
My phone is the ZTE Axon 7 version 7.1 and A2017U.
Click to expand...
Click to collapse
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people who locked their bootloader after getting bricked. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
Thank you very much for the reply! When it comes to theA2017x_NOUGAT_FULL_EDL file, is this what you are referring to? https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
radmike12 said:
Thank you very much for the reply! When it comes to theA2017x_NOUGAT_FULL_EDL file, is this what you are referring to? https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
I don't know, because you haven't told me your phone model. Just look at the back, it should say the model there. But I think it's that. There's a thread with A2017G and A2017 files on the Guides section, made by WesTD. If you have one of those you can use one of the files. If you have an A2017U, you'll have to search. if you find the file, could you send me the link? I want to do a guide but can't find the U file
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Click to expand...
Click to collapse
Yes my toolkit makes it perfectly clear
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
When I hold the two volume buttons the phone does nothing .
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
Nevermind I got it to work! but now it is saying that i am putting in the wrong pin even when I know my own pin.
radmike12 said:
Nevermind I got it to work! but now it is saying that i am putting in the wrong pin even when I know my own pin.
Click to expand...
Click to collapse
That's normal, just unlock the phone and do whatever you were hoping to do before. But use axon7toolkit now instead
A factory reset would also unlock the phone, but you might as well want to unlock and all that stuff since you'll lose your data anyways.
Choose an username... said:
That's normal, just unlock the phone and do whatever you were hoping to do before. But use axon7toolkit now instead
A factory reset would also unlock the phone, but you might as well want to unlock and all that stuff since you'll lose your data anyways.
Click to expand...
Click to collapse
i once again unlocked the bootloader using the toolkit. How to root the phone with the axon7toolkit? When TWRP opens while trying root on my phone I get the message that my device is not conneted anymore. When TWRP opens what do I do after that?
radmike12 said:
i once again unlocked the bootloader using the toolkit. How to root the phone with the axon7toolkit? When TWRP opens while trying root on my phone I get the message that my device is not conneted anymore. When TWRP opens what do I do after that?
Click to expand...
Click to collapse
No, forget about the toolkit. Put the latest Magisk on your internal storage or SD card (or SuperSU if you don't care about SafetyNet), enter TWRP with the key combination (I think it's vol up + power), make a full backup, and flash the zip.
Choose an username... said:
No, forget about the toolkit. Put the latest Magisk on your internal storage or SD card (or SuperSU if you don't care about SafetyNet), enter TWRP with the key combination (I think it's vol up + power), make a full backup, and flash the zip.
Click to expand...
Click to collapse
ok I put Magisk on my sd card. How do i enter TWRP without the toolkit?
radmike12 said:
ok I put Magisk on my sd card. How do i enter TWRP without the toolkit?
Click to expand...
Click to collapse
turn it off, vol up + power
You said you roooted other phones?
Choose an username... said:
turn it off, vol up + power
You said you roooted other phones?
Click to expand...
Click to collapse
I never said I rooted other phones. That's why I called myself a noob on the original post. I now successfully rooted the phone and all that now I want to get Xposed on it. I found o post about it but it says that If I have a systemless root it will break it. https://forum.xda-developers.com/showpost.php?p=68206045&postcount=2
Hey guys, I have the T-Mobile 6T, unlocked and rooted, worked perfect until today.
Today it took the 9.0.5 OTA, it downloaded, installed, rebooted and left me with
"<!> BUILD VERSION and HW VERSION IS NOT MATCH"
Any chance someone can help?
I can't get it into recovery or anything.
The MSM download tool will help you.
https://forum.xda-developers.com/on...t-mobile-oneplus-6t-msmdownloadtool-t3868916/
I had hoped that it would. Unfortunately, I can't get it to work..
it seems that the phone just keeps rebooting before the tool can actually do anything.
The most I get is "Start download firehose binary" and the the phone disconnects.
Next is "Sahara Communication Failed."
after a few dozen more tries, I got a bit more. Now it says "Images do not match the phone!"
Try restarting into qcom mode as well as plugging into diff USB ports. Mine was doing that as well and eventually was able to get it to work.
How do I get into qcom mode?
intrusdave said:
How do I get into qcom mode?
Click to expand...
Click to collapse
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Are you using the T-mobile tool? https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916
I thought I was, but I will re-download and see.
That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.
intrusdave said:
That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.
Click to expand...
Click to collapse
No problem. There's two tools in the guides section and the threads have similar names so it's easy to get mixed up.
In the future if you're going to international 9.0.5 or 9.0.6 make sure to use the full rom and not just OTA.
I have the Same problem
intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Hi, i have the same problem. what do you do to get it work?
Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data
[email protected] said:
Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data
Click to expand...
Click to collapse
Oh boy, look what I found right in the thread about the MSM tool! Please see attached screenshot.
I have this issue on the international variant of the phone (Yes mine truly is the international model, it has dual sim, although its refurbished so the refurbishers borked something)
mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I used the international version on mine (T-Mobile 6T) since was in software and hardware error. You don't have to come back to TMobile software mandatory.
mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I've tried the different tools to no avail. also holding power, vol up and down will only go into fastboot mode. I believe just holding vol up and down is the qcom mode and inserting the usb c cable after about 10 seconds of holding those two buttons. otherwise the device will just keep rebooting into fastboot