Hey all, I recently purchased a new 7TP 5G MCL and decided I'd try flashing a new ROM and rooting it before I had anything on the phone in the first place. I got the unlock token from T-mobile and successfully unlocked my bootloader - and this is where I got careless and didn't notice the difference between 7TP (HD1917 among others) and 7TP 5G (HD1925). After flashing a few recoveries/ROMs, I noticed that the wifi wasn't working. This was the first sign something was wrong.
Since then, I've tried flashing other ROMs, until I realized that the issue was that this phone had a different modem than other 7TP so it needed a ROM that was specifically compatible for this. I tried flashing a 'compatible' recovery/ROM but it doesn't seem to fix my issues.
I just checked my phone settings and it says it's an HD1917. That doesn't sound right.
I'm using the MSM tool and though I have Qualcomm HS-USB showing up in my device manager, nothing substantial is showing up in the MSM tool when I click enum. I just see 39 rows of "Index = #" (ranges from 1 to 39) and "Status of Connection = N/A". For a brief period just now, I was unable to access anything other than the bootloader - since then I was able to flash a new recovery and access it, but haven't tried anything else yet.
Any tips?
If you have the phone from T-Mobile, the 7T Pro 5G Mclaren, then it is the HD1925 (and that must be what you have since you needed the unlock token.
Where is it showing HD1917?
My guess is you flashed a ROM for the international 7T Pro and not the T-Mobile 7T Pro 5G McLaren as you suspected.
Find the thread about how to restore the phone back to stock using the MSM Tool (for HD1925, in these subforums) and see if that helps.
However, if your FP sensor and WiFi still don't work, then you corrupted your persist partition which I fear may be the case. Try the MSM tool and let's go from there.
Yeah, the thing is -- I've tried the MSM tool but nothing of note shows up when I enter EDL mode or click "Enum". My device manager does say I have Qualcomm HS-USB QDLoader9008 connected, though.
The "Device Properties" in settings (all the way at the bottom) is what's showing HD1917.
Edit: I'm trying the MSM tool for HD1925. I don't think I should be trying the one for HD1917...right?
For the record, this is what my Device Manager & MSMDownloadTool looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My lineage 18.1 bootloader recovery logs say, all over the place, "model=HD1917". Looks like this is packed into the phone.
Well, it's back to being an HD1925 again, and wi-fi is connected properly. Weird how that ended up.
I went into recovery mode, clicked a few buttons (mount/unmount system, delete data, ...) and it booted right up like this as JoeF2's lineage 11 in https://forum.xda-developers.com/t/rom-lineageos-18-1-android-11-unofficial-mar3.4192829/page-5.
Thanks for your help glad nothing was permanently broken. Now time to fully set up this phone.
zintegy said:
For the record, this is what my Device Manager & MSMDownloadTool looks like.
View attachment 5373157
Click to expand...
Click to collapse
The issue is the Qualcomm HS-USB QDLoader 9008 has an explanation point by it in device manager, which means you have the wrong drivers installed. Follow the directions in many threads regarding getting MSM tool working to properly update drivers. Then it should show up in the MSM Tool, assuming you are in EDL mode and issue enum command in MSM tool within 10 seconds of entering EDL mode or the phone will automatically exit EDL mode and reboot.
zintegy said:
Edit: I'm trying the MSM tool for HD1925. I don't think I should be trying the one for HD1917...right?
Click to expand...
Click to collapse
Yes, you need the MSM tool for the HD1925. Don't use any other versions of it, such as for the HD1917
starcms said:
Yes, you need the MSM tool for the HD1925. Don't use any other versions of it, such as for the HD1917
Click to expand...
Click to collapse
where did you fine the msm tool for Hd1925 I am searching high and low for it ?
Mitch0115 said:
where did you fine the msm tool for Hd1925 I am searching high and low for it ?
Click to expand...
Click to collapse
It's right here
[OP7TPRO TMO 5G][OOS 11.0.1.5 HD61CB] Unbrick tool to restore your device to OxygenOS
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...
forum.xda-developers.com
Related
Hello guys,
I tried to update my phone to Nougat and I guess I totally failed.
First I just tried to flash this rom: https://forum.xda-developers.com/axon-7/development/rom-purefusionos-official-t3670580 and it did not work. So I thought I might have to update the firmware first and installed the A2017UV1.1.0B32 NOUGAT Update from this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484. I found out I had to flash (with TWRP) the firmware's G version so I took the A2017G_N_Modem.zip from this https://androidfilehost.com/?w=files&flid=148464.
Now I only get the "your device software can't be checked for corruption. Please lock the bootloader".
Can somehow help me and tell me if and how I can get a rom working again?
Thanks in advance.
Check forum. There are topics to unbrick your device.
Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.
multimill said:
Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.
Click to expand...
Click to collapse
When led blinked you are on EDL mode. Screen is black on edl mode.
Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.
multimill said:
Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.
Click to expand...
Click to collapse
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.
WesTD said:
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.
Click to expand...
Click to collapse
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
Good luck. Your device on DFU Mode. There another guide about it.
multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
4th category brick repair manual, google it
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?
I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol
Hello,
This problem has come up a lot i'm sure, but having looked at what feel like everything in xda website nothing has worked for me.
How did this happen? Phone froze and i held power button to shut it off, and it never booted past oneplus logo(Somehow corrupted itself). I went into recovery and wiped the phone since i dont keep much data on it. Instead now my phone is stuck on wiping itself.
FYI, the phone had Android 10.0.1 installed on it if that makes a difference.
My OnePlus 6T is bricked and here is what i can and cannot do:
Can do:
Boot into fastboot mode
Have the phone detected in ADB tools
Have the phone detected as Qualcomm HS-USB QDLoader 9008
Can't do:
Unlock the bootloader(Bootloader has never been unlocked on this device so i cant flash anything)
Boot into recovery mode(Vol up + power boots the phone instead)
Device wont boot past "Wiping, please wait." (Yes, i have waited HOURS for this to fix itself, nothing happens)
Tools i have tried to no avail:
MsmDownloadTool (All versions, nothing works! I get "FireHosecheckrsp failed errno 258" error. I have tried all possible drivers and cables as per some tutorials and discussion but nothing
I have tried MsmDownload tool int Windows 10, 7, even Vista(FireHosecheckrsp failed errno 258 every time)
Tool All In One, I cant flash anything through here since my bootloader is locked and i cant unlock it.
Flashing TWRP or other recoveries doesnt work because of locked state.
Anyway, sorry to ramble here. If anyone has any ideas, i would be happy to hear.
Best Regards
You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
You have several serial ports interfering with the tool, so click the COM port bar and select the one belonging to the Snapdragon modem in the OnePlus 6T phone, and run this tool again. Error 258 is serial port conflicts or USB connection issues.
If unsuccessful, you will need to install Qualcomm USB driver. I am not sure if you have installed it though.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
COM4 is currently the only one that shows in MsmDownlaodTool and Qualcomm drivers are installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
That's odd. Did you either try new USB-C cable, or getting the lints out of the USB-C port on the phone?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I have tried the original cable along with 2 others, which are from OnePlus as well. There is no dust or lint or anything in the port, fairly clean. :good:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
I always power off my phone. Then hold both volume buttons down and plug it in. MSM tool sees my phone and hit start.
which Qualcomm drivers you installed ? because my phone is not connecting with MSM tools ....
I'm having the same issues. Anyone find a fix?
Charles: said:
I'm having the same issues. Anyone find a fix?
Click to expand...
Click to collapse
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Zain ul Abedin said:
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Click to expand...
Click to collapse
Which TWRP?? Did you load it via Fastboot and use Fastboot commands? Are you A11? Which Qualcomm drivers?
I basically forget that , but search about it . And install TWRP in your phone
otoyayamaguchi said:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
Click to expand...
Click to collapse
I think it's supposed to only last for a few seconds. Pull up the MSM Tool and pay attention to the "Status of Connection" field for any of the COM lines in the MSM Tool. When you connect, it should say "Connected" for one of those lines. If that happens at all, then you're good to proceed. Make sure you have TMO selected in the drop-down, click "Enum" once you plug in your device, then click Start. Try to do this quickly. Let me know if this helps.
I am having the same problem with my 7T Pro McLaren, the pc recognizes it but msm tool does not, someone has already found the way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the same issue. One easy fix is switching from a USB 3.0 port to USB 2.0 port. The other method that worked for me is a little more of a process.
1) Have MSM open
2) Connect phone to PC
3) Power phone off
4) Then, the moment it powers down, hold the vol +, -, & power button
5) Keep holding it. Your PC will make a sound notifying you that it's detected the phone, but you want to keep
holding the buttons until you hear it being detected for the second time.
6) Release buttons.
Hopefully that makes it stay in EDL mode for you.
I wrote on this somewhere, but you can try having the program open and placed at the right settings, then move quickly once the phone is in EDL mode. Not ideal but worked for me. Once the process begins it won't exit out of EDL mode in my experience.
hii, from most tutorial i have seen so far, the com number is show in the msm tool upon starting the program, most the two msm tools i have tried so far dont show com number... and its not detecting my phone.